Messages

Hi, we had a specific scenario that caused the zscaler uninstall not to work.  Posting here in case it helps others.  We deployed zscaler to all devices, then identified that some devices being display machines with generic logins were getting an authentication prompt which was never acknowledged.  We pushed the PMPC Zscaler uninstall and it failed on all.  identified that there were a couple of processes missing from the executable list in the deployment type.  Once added, the uninstalls started happening. 
These should all be added if not there already

ZSATray.exe
ZSATunnel.exe
ZSAService.exe
ZSAHelper.exe
ZSAUpdater.exe
ZSAUpm.exe
ZSATrayManager.exe

Last two are the missing ones

OK< thanks. 

somebody just reminded me that Broadcom have bought Vmware and pretty much demolished all things vmware in the transition, so there is likely a broken link involved there somewhere. 

Hi, first my questions - Where do I find documentation on "known Errors" and how do I resolve the 522 error?

Our daily emails have this error (shown in Screenshot "Error 522.jpg") and I'm not sure why.
Error 522, but the link indicated doesn't include any information about this error. 

The "code" below appears to be the relevant part of the patchmypc.log file, indicating to me that there is no issue with "VMware Workstation Pro 17 17.5.1 (EXE-x64) " unless it is maybe a minor version change within 17.5.1. 
I have verified that the files exist.  Shown in "VmwareWorkstation files.jpg" Screenshot. 

Code Select Expand

15/05/2024 9:55:22 PM Processing Installable Application: 24/101. (VMware Workstation Pro 17 17.5.1 (EXE-x64)) 8 (0x0008)
15/05/2024 9:55:22 PM The application [VMware Workstation Pro 17 17.5.1 (EXE-x64)] meets the criteria for enabled products based on the search pattern [Include: VMware Workstation Pro 17 % (EXE-x64)] 8 (0x0008)
15/05/2024 9:55:22 PM Resolving content paths for VMware, Inc.:VMware Workstation Pro 17 (EXE-x64) 8 (0x0008)
15/05/2024 9:55:22 PM Identified latest release of VMware, Inc.:VMware Workstation Pro 17 (EXE-x64) at the expected path of [\\corp\cm\Updates\PatchMyPC\Applications\VMware, Inc_\VMware Workstation Pro 17 (EXE-x64)\c96dd81f-3821-4c13-bb2e-1bd8ed6e64d0] 8 (0x0008)
15/05/2024 9:55:22 PM Finished resolving content paths for VMware, Inc.:VMware Workstation Pro 17 (EXE-x64). A total of 1 related content directories were found. 8 (0x0008)
15/05/2024 9:55:22 PM Found source content for [VMware Workstation Pro 17 17.5.1 (EXE-x64)] [\\corp\cm\Updates\PatchMyPC\Applications\VMware, Inc_\VMware Workstation Pro 17 (EXE-x64)\c96dd81f-3821-4c13-bb2e-1bd8ed6e64d0] - checking if ConfigMgr application exists 8 (0x0008)
15/05/2024 9:55:22 PM The application: [VMware Workstation Pro 17 17.5.1 (EXE-x64)] is already created with source folder [\\corp\cm\Updates\PatchMyPC\Applications\VMware, Inc_\VMware Workstation Pro 17 (EXE-x64)\c96dd81f-3821-4c13-bb2e-1bd8ed6e64d0] 8 (0x0008)


OK, thanks. 

not sure if it is related, but for some we get the type of thing shown in the screenshot - two apps with the same name and version and the deployment remains on the older iteration. 

Hi, we have a bunch of these type of messages in our PatchMyPC.log.  (for various applications)

An error occurred while processing postponed application update. Could not find file 'D:\Program Files\Patch My PC\Patch My PC Publishing Service\PostponedBinaries\a95d0b1f-5b21-466d-a4fe-8abeef851538\InventoryExtensions.msi'. [D:\Program Files\Patch My PC\Patch My PC Publishing Service\PostponedBinaries\a95d0b1f-5b21-466d-a4fe-8abeef851538]

I have verified, that MSI does not exist.  the norm for these appears to be that there will be two files "appinfo.xml" and "sdp.xml"

I did a search for all exe and msi files in these directory and got a total of 7 of the guid type directories out of 17 that have an installer of these types, the other 10 just have the two files. 

Do I need to do anything here or can the errors be ignored?

same for handbrake on first run.  "would you like to allow handbrake to automatically check for updates"

Keepass also gives a "enable automatic update check" message when starting it for the first time. 

side note, I've just gone into "help - about" in google chrome after a fresh install of V124.0.6367.61 and it has done a self-update too. 

Hi, we have "Disable self-updater" set at "All Products" level, however after installing Audacity 3.5.0, it prompts that "Audacity 3.5.1 Alpha is available with an "install update" button.  Is this expected behaviour, or is there something I have missed to stop this popup?

thankyou.

Hi, is there a list anywhere of the gotcha's for each of the app's PMPC can create applications for?  We are still setting up and I am going through testing some of the application installs.  I found that Handbrake after installing doesn't work as it requires .Net desktop runtime be installed first.  It actually prompts the user to download it which isn't going to work so I need to add it as a dependency.  I have manually done that, but I figured maybe all these types of manual requirements, might be documented somewhere. Might save me some time with testing if I can do all the manual components before trying to test.   

Hard to read my own post Is this what you are saying the process would be?

 - allow PMPC to create the applications,
 - in MCM configure the main app with the other apps as dependencies. 
 - each time PMPC creates a replacement application for one of the components, we need to go into MCM and update the dependencies of the main application
 - However if it is the main application, we need to start over with that application and set up all the dependencies again.

 Does that sound about right?

Hi, we just use MCM for applications currently. (we have intune in place but currently only use it for the store apps (since store for business went offline))
I understand the concept of dependencies, but we script mostly because of the fact that dependencies are ignored during an uninstall.  This may just be a change of process I guess because prior to PMPC, to update, we completely removed an app and installed the new version but with PMPC doing updates automatically now, that isn't required. 

I need to retrain my brain

So basically, what you are saying is that we allow PMPC to create the applications, then in MCM we then set up the main app with the other apps as dependencies. 

Then each time PMPC creates a replacement application for one of the components, we then need to go into MCM and update the dependencies of the main application but if it is the main application, we need to start over with that application and set up all the dependencies again.  Does that sound about right?