Thanks for reaching out here on the forum! I have reached out to our catalog team and they have agreed to make this change in the command line for TortoiseHG! This should be available in the next catalog release (No later than 4pm est.)
Let me know once you've had time to test if that's working for you! 😊
I wanted to post an update as the dev responded to one of the Github posts:
Looks like the dev responded to this thread and posted an unofficial build offering an option to install for everyone (All Users). I confirmed that the ALLUSERS=1 flag is now supported and will install properly with shortcuts when installed as SYSTEM using that flag.
It's totally possible to install as SYSTEM! Unfortunately, though when installing as SYSTEM, ImageGlass will install but, there are no shortcuts or start menu programs created for users. You'll need to go into the program files folder to launch the program.
The vendor has the MSI set to install per-user and not per-machine. We have reached out to them to see why this change was made as it makes it difficult to mass deploy and manage when installing per user.
Thanks for the extra info! I was able to replicate this in my lab and found that the vendor has changed the installer to only install under the user context (Per-User). This was a change from a SYSTEM wide (all users) installer.
This causes multiple entries listed in the registry since the User-based installer isn't able to replace the SYSTEM wide installer.
We may need to change this to be a User-based application. This means that WSUS will not be a supported method of deployment since it doesn't support user based installations. You will however, be able to publish the application package and deploy that to update that application.
We'll keep you posted once we've made the changes! 😊
The application team has confirmed that they will be adding this as a default command in the next catalog release today. Let me know if you have any questions or don't notice the new command line in the Show Info Pane.
Sorry for the delay! Just now getting back from the holiday vacation!
I can reach out to our app team and see if they can make this the default behavior for DB Browser. For the time being, you can add that same command line to the package via the right-click option " Modify Command Line." That will allow you to pass through any custom parameters to the installer package.
You can accomplish this using collections and ADR's in ConfigMgr. You'll need to exclude the device from the primary collection used on the All Updates ADR. Then create a new collection with the machine(s) you want to exclude. Create a new ADR excluding those specific products and deploy those to the excluded machines collection.
Hey There! Thank you for reaching out on the forum! All of our IntelliJ packages have the following pre-defined script which will remove the older versions as the installer doesn't remove them during the upgrade.
If you would like to view the script in the publisher, you can right click on the products and select the Pre-defined script.
If you know where the settings are stored, you can script a copy of those files over to the new directory post-upgrade. The script can then be set as a Post-Script on the IntelliJ package to retain those settings for the user.