Messages

During a silent installation, I believe our service would be auto-closed and reopen to close our handle on the DLL's.

Sounds reasonable and logical. Hard to say whether it is in fact trying to auto-install the new version.
All I know is the in-console notification about an available update. But since the console is usually never opened on this system, I'm not sure if it would auto-update. Couldn't find a reference to that in the product docs.

The PmP Publishing Service is installed on the only WSUS server in this environment. The same server is also the ConfigMgr (CM) Primary Site Server.

The CM Admin Console is normally operated remotely from this server. Which is why I didn't notice until today I that the CM Console wouldn't connect to the SMS Provider.



The Admin Console version on this server appears to be behind at version 1910. The Site is at 2002.



Upon running ConsoleSetup.exe from the CM tools folder, it tells me the PmP service is in the way of completing the update.



Could it be that the service prevents an auto-update of the console and eventually causes the 'cannot connect' error?
in any case, I wanted to make you aware of this. You might want to document this as expected behaviour if the WSUS server has the CM Console installed on it.

Build 1.5.9.0

Yes, there's activity as this is the first publishing run since implementation. So resource usage is expected, just didn't expect it to be this high, is all.

Thanks for your reply Justin.

We've made the customer fully aware of that! Changes are planned for coming months.

I appreciate your technical insight. Not really seeing spikes though. Rather a consistent usage while downloads and publishing is ongoing.

What CPU usage is everyone seeing for the PatchMyPCService during publishing?
Running on the Primary Site Server which is also the WSUS/SUP. Only 2 vCPUs @2.6Ghz
Process uses both CPUs and uses about 40-60% CPU usage.

Infra changes are planned to better scale for ConfigMgr. But I'd like to know what others see.