Messages

I'm really happy to hear you're working with the PSADT group on this.

We did end up using a PSADT notification instead, but like we've all said, it would be really cool if we could use the PMPC one instead. Thanks Andrew!

I have an application install that silently installs a BIOS update but I would like to notify the user that they need to restart and give them the option to snooze/dismiss only to bother them about it again later in the day.

I love the PMPC notification that pops up for Intune updates and was wondering if it's possible for me to use this on my application?

Hello, I'm creating a custom app with an exe for InfoZoom (InfoZoom_2023_en-US.exe). It looks like the install is running but will time out because it is running in the background. Is there a way to run it without it being silent? I see the "Silent Install Parameters" is required when created it and I don't know why that is.

We have GlobalProtect 5.2.9 required to our autopilot device group so that it installs in the ESP.

I want to pilot GlobalProtect 6.2.2 but I'm not sure how to avoid 5.2.9 re-installing automatically.

In our testing it looks like we have to have an app (5.2.9) required for it to install in the ESP. If it is just in the ESP without a required deployment, then it will not install, so it has to be required.

So to pilot 6.2.2 the options I've found are:
1. Add a requirement script to version 5.2.9 so that it won't install if a newer version is installed.
2. Exclude a pilot collection from the 5.2.9 deployment.

If I did option 1, I see that PMPC gives the option on Intune Apps/Updates to "Override Win32 application options" and then to "Copy the requirements from previously created applications or updates when an updated application is created". This would stop a newer version such as 5.3.0 (if it existed) from installing if it was released and packaged by PMPC.

Option 2 isn't ideal if the pilot group was made available and some people are choosing to install it and some are not. We would have to get their devices and add it to a device collection.

I also considered turning on supersedence for 6.2.2 but I believe it would automatically upgrade everyone in the pilot users group (that's only an available deployment) from 5.2.9 to 6.2.2 and we don't want that to happen.

Is adding a requirement script to the old version (and using PMPC's option to copy the requirements) the best option we have in this scenario? Or do you have any better suggestions? I wonder if others have found a better way to make an available deployment of a new version of an app that has an old version of the app required because of the autopilot ESP.

Thanks for the reply. We ended up using an Intune remediation that runs every 5 hours to delete Chrome shortcuts.

I tried making my own version of your master_preferences file but it still didn't work. It looks like Google changed the name to intial_preferences but the old name should still work. I'm not having any luck finding a way to prevent a chrome desktop shortcut for new users.

I'm really surprised this can't be done with an install switch or with group policy either.

Did you ever find a solution to this issue? I'm also trying to find a way to remove the desktop shortcuts for a new user that logs in. I've tried the Initial_preferences file too.

I also verified that deleting the application and source content and republishing has fixed it for me as well. Thanks!

I have the pre script now but mine is still failing. I am on a machine that has never had Putty installed before. Is this fixed for anyone?

Looks like this is still an issue for us. Are others still seeing the Putty install failing?

We are also having the same issue.

Thanks for the fast reply Wes! I submitted the idea- https://ideas.patchmypc.com/ideas/PATCHMYPC-I-2226.

In the PMPC right click options I'm able to change the Application name, localized name, description, and icon but I don't see the option to add keywords.

If I do this in the application in config manager, will it stay when the application is updated?

I just wanted to update and let you know that I think our issue was caused by Cylance. After delaying it, the Patch My PC install of Team seems to work fine. Thanks

Hmm, I don't see teams when I search in the start menu now. I also don't have the PreventInstalltionFromMsi key under HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Teams.

I'm guessing our only option is to go back to putting teams in the Office install and stop using the Patch My PC install of Teams. Maybe if we try it sometime in the future a newer version will work. Thanks for trying to reproduce it at least.