Messages

Hey,

Restoring the PMPC config is easy, we have a guide for that at https://patchmypc.com/backup-and-restore-publisher-settings

You should also consider the code-signing certificate and SUSDB.

If the code-signing certificate private key is marked as exportable, its recommended to move that to your new WSUS server - especially if its a self-signed certificate. If the code-signing certificate is issued from an internal PKI, its not so essential to use-the same one (assuming the code-signing certificate that you use on your new WSUS server to sign updates is also trusted by your clients).

Typically we recommend to use the existing SUSDB if you are doing a site migration. You can install WSUS on your new site server and use the existing DB. You should then also migrate/use the existing WSUS Content folders too. This is a great video on considerations for moving WSUS to a new server https://www.youtube.com/watch?v=bBcJY8_uHCQ - of course, WSUS should be installed be you configure the SUP role as per https://learn.microsoft.com/en-us/mem/configmgr/sum/get-started/install-a-software-update-point

Hello,

Unfortunately, HP pulled their warranty API, see more at https://developers.hp.com/hp-client-management/forum/warranty-api-currently-unavailable

There is no other accurate way to pull inventory data for HP devices. For this reason, we can only pull in warranty data for Dell and Lenovo devices.

Thanks for the info Grzegorz. Please allow us a little time to review and we will let you know our findings

Thanks Tim,

We resolved this today with Lukas. The downstream WSUS server had corrupt column information for some of the updates in the database. We cleared those up and the errors were resolved.

Ah, we are working on this with Lukas today

Hi Tim,

Are you syncing Oracle Java SE Development Kit 8/11/21 out of interest?

Hi AndAuf,

Just swinging back round to this. It appears that Screaming Frog may have always been x64 architecture but has recently changed to x86. Me may have some work to do to fix our detection and better understand how we update teh catalog. Please bear with us and we will post an update here very soon.

You can also monitor our catalog release page to see when we release an updated Screaming Frog version if you would prefer

https://patchmypc.com/category/catalog-updates

Thanks

Thanks for bringing this new major version to our attention. Ill let our catalog team know to test and update this in our catalog.

PS. We only have the 64bit version in our catalog, not an x86 version

Thanks again AndAuf

Hey PS_Alex

We are explicitly calling Windows PowerShell to run our pre and post scripts.

(_sysPath, "WindowsPowerShell\v1.0\powershell.exe")

We dont have any plans to consider other interpreters at this time. If you think that would be beneficial, we do have an ideas page where you can drop that suggestion in with a use case

https://ideas.patchmypc.com/

Hope that helps!

ah ok, gotcha, my mistake here, its an MSI - sorry for the oversight, need more coffee! Let me do a quick test and come back to this thread with my findings. Thanks Madd

Hi Madd,

The Intune detection script for the Printer Installer Client will return "Detected" if we find a newer version of that app installed on a device. We are not looking for a GUID specifically but DisplayName and DisplayVersion (see script below if with easier formatting to read)

Are you saying the Intune Detection Script is showing the app as detected on devices that have a lower version installed than 25.0.0.935?

Hey there, sorry we missed your question. What do you wish to manually edit on the backup xml file?

Hey, thanks for letting us know. Ill let our catalog team know. If we missed this update, we will update our detection methods and get it added to our catalog promptly. Thanks again.

Thanks for bringing this to our attention. While we can't lean in and help fix this it is useful so we can feed the info back to customers who might be having the issue. Appreciate it!

Hello,

Artifex still do not allow silent installs of their app which is the reason we cannot continue to include newer 10.x versions in our catalog.

They have an announcement here

https://artifex.com/news/ghostscript-10.01.0-disabling-silent-install-option

You can read an in-depth discussion here

https://bugs.ghostscript.com/show_bug.cgi?id=706495#c1

We still have the last update for 9.x in the catalog.