Messages

[Note: this will not work in the PMPC publisher until the vendor has officially released this build.]

Hey Ryan,

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.

Link to the Github Post:
https://github.com/d2phap/ImageGlass/issues/1708

Link to new MSI: https://drive.google.com/file/d/1m7YBMEyIjVLajxUvJdy6t_6SQAcfhLgl/view?usp=sharing
Note: this will not work in the PMPC publisher until the vendor has officially released this build.

I also confirmed that the update from 8.10 to the new MSI 9.0.7.1130 (Installed via SYSTEM using ALLUSERS=1 for both installs) installed successfully!

Please be on the lookout for the next release of ImageGlass as that should resolve the issues we're seeing with the current 9.0 build!

Thank you, sir! This is helpful in understanding how the new installer functions! I'll pass this along to our app team and see if there is anything we can do to work around this issue!

Hey Ryan,



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.

Hey Ryan,

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.

I've informed our application team and they're going to post on this GitHub thread for traction:
https://github.com/d2phap/ImageGlass/issues/1708

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! 😊 

Hello!

Thank you for reaching out to support! Are you deploying this update via ConfigMgr/WSUS or Intune?

Thanks,

Spencer Cruz

Hey Trevor,

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.

Hey Trevor,

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.

https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications

Best,

Spencer Cruz

Thanks for reaching out to support!

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.

The IntelliJ update has the same pre-defined uninstall script attached to it. You would need to add the copy post script to the update as well to retain the user settings.

Again, you can see this script by right-clicking on the update package in the Publisher and clicking on the Patch My PC Defined Pre/Post Scripts option.

If you have further questions, please don't hesitate to reach back out!

You can also email me at [email protected] if that would be an easier method of communication!

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.

The script can be found here: https://patchmypc.com/scupcatalog/downloads/scripts/PatchMyPC-Remove-Application.ps1

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.

More information on Pre/Post scripts can be found here: https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#:~:text=Applicable%20To%3A%20Applications-,Add%20custom%20pre/post%20scripts,-This%20option%20allows

If multiple products are configured with that setting, then I would check at the top level (All Products) to verify if MCP is enabled there. If so, check to see if "Prevent Start" is enabled and disable it from there.

As for the use of that "Feature", I wouldn't enable it unless you notice a product trying to relaunch itself when the processes are closed. Some VPN clients do this to maintain their client connections. So, to ensure that the process doesn't restart, you can enable that feature.

Otherwise, I wouldn't even touch it as it does tend to cause issues if the PatchMyPC-ScriptRunner.exe process exits unexpectedly or times out and doesn't have enough time to delete that key after the update.

Hey Bugs,

Thanks for reaching out to support!

I would recommend checking the conflicting processes options on that application/update to ensure you don't have the option to "prevent the user from starting the process during installation" selected as that is what is causing these issues.

More information on that option and how to remove that registry key can be found here:

How to remove the registry value: https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications#:~:text=by%20another%20process.-,Update%20in%20progress%E2%80%A6,-When%20the%20option

Overall information on MCP options: https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

Hey Matt,

Thanks for reaching out! Usually this is some type of networking issues. I would confirm that the SYSTEM account of the machine hosting the publisher has access through any firewalls or proxies being used.

You can also confirm that those vendor domains are not being blocked by referencing our Firewall list here:
https://patchmypc.com/list-of-domains-used-for-downloads-in-patch-my-pc-update-catalog

We can also look into the log files from the Publisher. You can collect them from under the General Tab by clicking the "Collect Logs" button and send them to [email protected].

I'll review them and will provide any updates via email!

Oh interesting! I'll pass this along internally as it may have gotten lost in translation! We still need to update the msi to the latest version in the publisher to allow for publication, but this should prevent future delays!

Perfect, I'm sending this over to our app team now so they can get this added to the catalog! We should hopefully have it in there today or tomorrow for you!