A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
Hi PMPC, currently the package is not using the installer that we are required, we need the installer from this: attached file, kindly let us know for the update
Hi Team, is there any way to get this working without updates? Unless certain registry keys are set, Bloomberg will auto update, so just getting the initial install working would be a huge win. My expectation is that PMPC would just grab the most recent version, install and disable any version checking. Thanks Adam.
@Adam Cook, I would love to provide this feedback to my Bloomberg rep as a feature request. It sounds like they are not using "best practices" with thier software development, thus making it difficult to manage the software in a standardized way.
Do you/PMPC happen to have a template email that we could use to send to our account reps at Bloomberg requesting that they make this change?
To summarize, we would request that they use this key to increment their version numbers, instead of their proprietary path, which is industry standard.
SOFTWARE\[WOW6432NODE\]Microsoft\Windows\CurrentVersion\Uninstall\DisplayName and \DisplayVersion.
The reason why we can't support in Intune is because the vendor keeps DisplayVersion in the registry always a 1.0.
The most popular registry key for Add and Remove Programs is SOFTWARE\[WOW6432NODE\]Microsoft\Windows\CurrentVersion\Uninstall. Today, our Intune detection scripts loop these keys and generally depend on DisplayName and DisplayVersion registry values for detection. Nearly all software as a loose convention follow this pattern. However, Bloomberg Terminal only stores the real version number is HKLM\Software\WOW6432Node\Blloomberg L.P.\Components.
At this time, our detection scripts for Intune cannot support this.
From an earlier comment in this thread, I wrote "We can make this work, but only for WSUS/ConfigMgr customers. Not Intune Apps or Updates. This is due to how the vendor stores information in the registry and with how our Intune detection scripts work today."
We can make this work, but only for WSUS/ConfigMgr customers. Not Intune Apps or Updates. This is due to how the vendor stores information in the registry and with how our Intune detection scripts work today.
What is the general interest for this being in ConfigMgr/WSUS right now?
This would be a big help for us too. Updates currently done manually by IT staff on all the Bloomberg terminals, having PatchMyPC take it off our plates would be great.
Just a note on this, not everyone will use conn_type=internet as some use a conn_type=private . I assume we'd be able to modify this command line via Publishing Service.
I just wanted to let you all know we haven't forgotten about this request. We are working through some others at the moment that more unique customers are following. If any others come across this idea, please vote it up if it's one you would like to see added.
Please add the Bloomberg terminal software application to your repository. While you need authorization from Bloomberg to turn on the application. This happens after the install with a phone call so your process will work well with this app.
Hi PMPC, currently the package is not using the installer that we are required, we need the installer from this: attached file, kindly let us know for the update
Hi Team, is there any way to get this working without updates? Unless certain registry keys are set, Bloomberg will auto update, so just getting the initial install working would be a huge win. My expectation is that PMPC would just grab the most recent version, install and disable any version checking. Thanks Adam.
Hey Dan,
We don't have a template as such, however you could share with them the link to this idea with the above analysis. Your summary is correct.
You are welcome to copy me in adam@patchmypc.com and I'll be happy to offer more insight as part of the suggestion to the vendor.
@Adam Cook, I would love to provide this feedback to my Bloomberg rep as a feature request. It sounds like they are not using "best practices" with thier software development, thus making it difficult to manage the software in a standardized way.
Do you/PMPC happen to have a template email that we could use to send to our account reps at Bloomberg requesting that they make this change?
To summarize, we would request that they use this key to increment their version numbers, instead of their proprietary path, which is industry standard.
SOFTWARE\[WOW6432NODE\]Microsoft\Windows\CurrentVersion\Uninstall\DisplayName and \DisplayVersion.
The reason why we can't support in Intune is because the vendor keeps DisplayVersion in the registry always a 1.0.
The most popular registry key for Add and Remove Programs is SOFTWARE\[WOW6432NODE\]Microsoft\Windows\CurrentVersion\Uninstall. Today, our Intune detection scripts loop these keys and generally depend on DisplayName and DisplayVersion registry values for detection. Nearly all software as a loose convention follow this pattern. However, Bloomberg Terminal only stores the real version number is HKLM\Software\WOW6432Node\Blloomberg L.P.\Components.
At this time, our detection scripts for Intune cannot support this.
Hi Marko,
Thanks for your comment.
From an earlier comment in this thread, I wrote "We can make this work, but only for WSUS/ConfigMgr customers. Not Intune Apps or Updates. This is due to how the vendor stores information in the registry and with how our Intune detection scripts work today."
On our website, you can also see it's listed only as a WSUS/ConfigMgr software update: https://patchmypc.com/supported-products
I hope this helps. Let me know if you have any other questions.
Why is the request set to shipped ?
I still can't find it in PatchmyPC ! (for Intune)
Where is it ?
Is there still an option to add this as a base app install through ConfigMgr? At this point i only see it available as an update.
Can we get this added for intune? Also the application self updates so base install is what we really need!
Just finished some testing on this app, and we should be able to add it as a WSUS/ConfigMgr Update!
+1 - Most trading firms use Bloomberg, and this would be a huge addition (even just for configmgr/wsus customers).
Well there is still interest for CM based application for me.
We can make this work, but only for WSUS/ConfigMgr customers. Not Intune Apps or Updates. This is due to how the vendor stores information in the registry and with how our Intune detection scripts work today.
What is the general interest for this being in ConfigMgr/WSUS right now?
This would be a big help for us too. Updates currently done manually by IT staff on all the Bloomberg terminals, having PatchMyPC take it off our plates would be great.
This is how i got it going.
Would like this as well
Just a note on this, not everyone will use conn_type=internet as some use a conn_type=private . I assume we'd be able to modify this command line via Publishing Service.
I just wanted to let you all know we haven't forgotten about this request. We are working through some others at the moment that more unique customers are following. If any others come across this idea, please vote it up if it's one you would like to see added.