Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Cody Mathis

Pages: 1 [2] 3 4 5 6

I believe this is the first issue we are hearing of. You are welcome to submit a support case at the below URL and provide the logs described in the second UR: below.


Thanks for the heads up. We will get this updated in the next day or two.

Ahh, these are MSP.

We should have this updated later today to resolve this issue.

We also intend to add the ability to set the command line for MSP in the near future. Sorry about that!!

This is likely due to a new UWP app that Adobe is packaging with the software. We will be updating our commandline today but you should be able to add  INSTALLUWPAPP=NO to your command line to prevent these errors from happening.


It looks like this install fails in some cases when no user is logged on due to a new UWP app that is packaged with the software.

For now you can add  INSTALLUWPAPP=NO to your command line and it should resolve the issue.

We intend to add this to our catalog today as well.

What are you referencing?

The issue this thread references is in relation to a bug with a trailing space on the custom command line.

Rich, can you please open a support case for this and provide your settings.xml as well as your patchmypc.log file?

You can find the idea for this application below.

This item was accidentally added to the list of software prior to us having the work complete.

This is how the Teams Machine Wide Installer functions from Microsoft. They discuss this in their docs here With the notable line being: "The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of the Teams app will be installed in that user's AppData folder. If a user already has the Teams app installed in the AppData folder, the MSI installer will skip the process for that user."

So, any user will have Teams installed in their user profile the next time they log into their PC, which is typically when the PC reboots in most cases. They say 'new Windows User Profile' in the doc but it really just applies to the first time a user logs on after the Teams Machine Wide installer has been installed.

I hope this helps clear up what is happening.

If you are experiencing this issue I would encourage you to submit a support case so we can look into what might be happening.

If do you remove the Adobe and HP catalog I would recommend you decline the updates for them as well to ensure they are not scanned against by clients anymore.

Is this issue for all clients? Or are you noticing it on clients over the CMG / IBCM?

There is generally not anything special going on specifically for third party updates. We have seen this delay happen though if you also have the Dell, Lenovo, or HP driver catalogues in place. They have very complicated applicability rules and can greatly increase CPU load / scan time.


Can you please submit a support ticket here and please zip up and include the logs mentioned here.

This should help us identify what is going on for detection.


These are different 'major versions' of the software. We should be able to add 7, but I would encourage you to add it as a requested application on our uservoice.

We have to do some work to determine how to detect version 6 vs. 7. The registry entries and files are very similar between the two, oddly enough...

Pages: 1 [2] 3 4 5 6