Messages

Thanks Andrew!

FYI, it looks like ours is failing with version 130.0.2849.80. The github post references version 131.0.2903.48.

We had Edge Webview2 in our esp and autopilot is failing. We should deploy the old version instead until this is hopefully resolved in the next release?

I wanted to re-launch Outlook and teams after the install because I am closing them. I don't think launching them as the system account works but I could test again. The script did work to re-launch as the user before I moved it to a PMPC custom app though.

Thank you Dan that looks really good and I think I might try out that Invoke-ServiceUI.ps1 script.

The problem I ran into with using the PMPC custom app is that I have a couple lines that re-launch Teams and Outlook as the user but they don't work now that the app is a PMPC custom app-
Execute-ProcessAsUser -Path "$PSHOME\powershell.exe" -Parameters "-Command `"start outlook.exe`"" -Wait
Execute-ProcessAsUser -Path "$PSHOME\powershell.exe" -Parameters "-Command `"start ms-teams.exe`"" -Wait

If you know why those might have not worked, please let me know.

I was first checking to see if the process was running before I closed them-
$TeamsProcess = Get-Process -Name ms-teams -ErrorAction SilentlyContinue
$OutlookProcess = Get-Process -Name OUTLOOK -ErrorAction SilentlyContinue

Then if those variables were not empty, it would execute the process as the user to launch them.

Sorry I didn't realize at first that adding the additional files is done in the publisher. I never finished creating in the cloud apps because I didn't see that option. I missed that part and I get it now. Thank you!!

Thank you for the reply. I think we are cloud only for custom apps but I know we do have the publisher. How can I tell if I can make this work? I do see the option to add additional files but I don't see the option to add additional folders.

We have been using PSADT to install Kofax Power PDF Advanced with an Intune Win32 app and it allows us to prompt the user to close applications. We have to use ServiceUI.exe so that the user can see the prompt.

The issue is that if a user is not logged into the computer, then the application will not update.

I found this article as a possible solution but it is 5 years old- https://svdbusse.github.io/SemiAnnualChat/2019/09/14/User-Interactive-Win32-Intune-App-Deployment-with-PSAppDeployToolkit.html

I am wondering if I should go this route (which runs a PowerShell script to see if the user is logged in or not and then tells PSADT to run in non-interactive mode if a user is not logged in) or if PMPC or others have a better suggestion that we should be using instead?

In the past I've asked about utilizing the PMPC notification window for installs and was told to use PSADT instead. The install also has lots of files so I don't think PMPC custom apps is an option either.

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.