We had a special case with our PMPC environment; we were running a trial with Advanced Insights and needed new licences. Now it happened that the licence expired at the end of the year on the 25th of December.
What we did not expect is that for a few applications (about 15-17, probably updated during the downtime) the problem caused PMPC to renew the deployment packages and start with a whole new set of deployment packages. Now we have to clean up the mess "we" made.
My question:
Do you have a good way of monitoring that the update frequency is working as expected? It would be great if the update history could be detected so you could track the update process within the PMPC and CM.
Kind regards,
AMi
Hello,
I'm not sure I understand what exactly occurred here. Patch My PC does not manage the deployment packages within ConfigMgr. It will only push the updates into the WSUS database, which ConfigMgr will then sync and deploy depending on ADRs. The Patch My PC license expiring should only cause Patch My PC to not publish new updates to WSUS. When the license is re-enabled, it will then publish any new updates found in the catalog.
The Publisher does log each update it publishes in a file found here: "C:\Program Files\Patch My PC\Patch My PC Publishing Service\PatchMyPC-PublishingHistory.csv"
We'd also be happy to look at log files for this case, feel free to open a support case with us here: https://patchmypc.com/technical-support (https://patchmypc.com/technical-support)