Messages

Hi there Iraklis,

Just to complement my colleague Ben reply, if that's something you like to see implemented, you can create a request for it in our ideas portal, so that our dev team can have a look and assess if it's feasible or not:
https://ideas.patchmypc.com/

Ideas are assessed as a best effort basis and they are not guaranteed to be implemented, just to be transparent.

Hi there TJ,

You will likely have to republish the updates, they will still exist on the SUP, but no longer in the SUSDB (the ones you lost by going a month back with the backup), there are going to be a lot of errors for those missing updates, as PMPC will check if they still exist in the SUSDB, but they won't exist. Also, when PMPC will publish a newer version, it will try to supersede the old version, but that won't exist in the SUSDB either. So republishing is key here.
Depends which updates you have published in the last month, there are ways to determine that, but if you don't have many updates enabled, might as well republish all of them.

Hope to have helped, hope you have a great day!

--
Best,
Hugo

Hi there Trevor,

Nice to know you managed to fix your issue, have a great weekend ahead

Best,
Hugo

Hi there Asgeirk,

I think you also sent us an e-mail this morning about this and my colleague Adam replied to you there, so this issue is fix correct?

Thank you

HI there IT-Wikinger,

I'm sorry to hear that, you can click on the button "Collect logs" found on the bottom of the "General" tab, that will generate a .zip file with the relevant server side logs, you can then e-mail that over to us at [email protected] and we can have a look what can be happening there. Ideally you would also send us client side logs, if you have the option "Manage installation logging" enabled, their default location is either:

SCCM:
%WinDir%\CCM\Logs\AppDiscovery*.log
%WinDir%\CCM\Logs\AppEnforce*.log
%WinDir%\CCM\Logs\AppIntentEval*.log
%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\CIAgent.*log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
%WinDir%\CCM\Logs\PatchMyPC-SoftwareDetectionScript.log
This may be found in the %temp% of the user who clicked 'Install' in Software Center if it was an 'Available' deployment.
%WinDir%\CCM\Logs\StateMessage.log
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml


Intune:
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Company Portal.
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareUpdateDetectionScript.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
%ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml
Note: Some Patch My PC log files listed above may be found in %WinDir%\CCM folder if that folder exists.

Hey IT-Wikinger,

The German.lngx is in the same folder as the package itself client side when downloaded from wsus/sccm/intune, so in your script you can use the command below:

Code Select Expand

Copy-Item -Path ".\German.lngx" -Destination C:\Program Files (x86)\KeePass2x\Languages

Hope to have helped, have a rest of a great day!

At the moment it's not possible, but be on the lookout as we will support Custom Apps in a very near future and when we do, you will be able to provide the .exe like you mentioned and always keep it up to date.

Hi there JJS,

Seems like someone else already had the same idea as you and submitted it in our ideas portal:
https://ideas.patchmypc.com/ideas/PATCHMYPC-I-3374

I would suggest you upvote the idea, so that you are notified of any status changes, plus any additional vote helps us see other people are also interested in the idea.

Have a rest of a great day ahead!

Hi there Jimmy,

Seems that someone else already requested this about 1 year ago in our ideas portal:
https://ideas.patchmypc.com/ideas/PATCHMYPC-I-2331

And the feedback that we provided is that, sadly, it is not possible.

We appreciate your understanding.

If it's the "Core Hosting Bundle", we already support that like my colleague Raunak showed with the print screen, however the product only supports base installations and not software updates

Hey there zapulver,

We're glad to hear you managed to fix the issue from your end, if you need any further support, do let us now.

Have a great day ahead

"can i do it for all Updates by right click on All Products and select Republish during...?"
Yes, that would be the correct procedure here.

"This will only republish the selected updates, correct?"
Correct, only the selected updates, it will not publish any others you have not selected.

"does it have any impact on the clients?(Will it be reinstalled on the systems?)"
I assuming you are asking if you republish an update, will it be reinstalled on a client device? If so, then no.

"If we would let the old cert on the clients, what happen if the cert expires? will they still be able to install the existing (not newer ones, after the new cert is imported) updates if we don't republish these Updates?"
If the certificate expires, but remains on the device, any updates signed by that certificate will still be trusted and installed provided it is timestamped.

Hi there Zuerom,

If you have a new certificate, you will need to import pfx certificate into the publisher so any newly published updates get signed with that new certificate, you can do so from the "General" tab and then by clicking the button "Import PFX certificate".
 
If you plan to keep the old certificate on your devices as well as the new one, you won't need to republish anything, however, if you are removing the old cert, you will need to republish all of your updates so they get signed with the new certificate and won't fail on install.

Hope to have helped, have a rest of a great day ahead!

Hi Mica,

To make sure the custom requirements are preserved in ConfigMgr Apps, you need to update the application and not create a new one, can you please check if you are doing so by going into the "ConfigMgr Apps" tab, clicking on "Options" and make sure the option "Update existing application metadata, deployment type, detection method, and content files (Default)", also, if this option is set (which is default), then deployments should remain through an app's lifecycle. i.e. if an application is updated, then its deployments to collections will remain unchanged - so it should give the net result of I think what you're asking for.

Just with the exception of there being no ADR functionality, if you only want software updates installed on workstations (and not servers), you should create a collection which contains just your workstations and deploy the software updates to that.
This is better than using applications in my opinion.

Hope to have helped, let me know if you require further assistance, have a rest of a great day ahead

Hi there mpotase,

We kindly ask you to send over some log files to [email protected] for us to be able to give you proper support on your specific situation, we ask of you to pull the logs listed below from a client where updates are failing to install:
%WinDir%\CCM\Logs\CAS*.log
%WinDir%\CCM\Logs\DeltaDownload*.log
%WinDir%\CCM\Logs\DataTransferService*.log
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center.
%WinDir%\CCM\Logs\ScanAgent*.log
%WinDir%\CCM\Logs\StateMessage.log
%WinDir%\CCM\Logs\UpdatesDeployment*.log
%WinDir%\CCM\Logs\UpdatesHandler*.log
%WinDir%\CCM\Logs\UpdatesStore*.log
%WinDir%\CCM\Logs\WUAHandler*.log
%WinDir%\WindowsUpdate.log
You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell.
%ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log
%ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml

And the ones below from the server side:
%SiteSystemLogsFolder%\SMS_ISVUPDATES_SYNCAGENT*.log
%SiteServerLogsFolder%\wsyncmgr*.log
%SiteServerLogsFolder%\WCM*.log

Looking forward to review your log files