Messages

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

Hi Ray,

If you uncheck an application, you only prevent it from being updated it does not delete it from the Intune tenant, this is expected behaviour.
If you want to delete apps from the Intune tenant, you can also do that from PMPC Publisher, by clicking on the black cloud icon on the right side on the "Intune Apps" tab, from there select the apps you want to delete and then just click the button on the bottom right "Delete applications".

Hope to have helped, have a good one

Hi there jcochrane,

We're sorry to hear that you are experiencing that situation, I would recommend you to open up a support case with us as it seems to be related to your own environment and not a general issue, you can do so by sending an e-mail to [email protected] describing the situation and one of us will have a more detailed look and help you out there.

Thank you for your time and patience.

Hi there fkhan,

From your print screen seems the app itself failed to install, in order for us to help you in this specific case and have a better understanding, could I please kindly ask you to please send over some log files from a endpoint and the general logs by clicking on the "Collect logs" button on the Publisher (it's present on the "General" tab) over to us at [email protected]? See below the relevant logs from the endpoint.

%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.

Hi there Gregorz,

Thank you for submitting this post.

So on this specific case we cannot modify the default command line to include one " because then the ending " would be missing and also if we actually include both of them, then you would not be able to add the license key manually on that specific argument you would still have to add another, also if we change the default command line that change would apply to all PMPC customers and some might not want to push a license key directly and only do so on a user basis, so the solution here for you is to simply pass the /v/qn argument again, whatever arguments are passed using the "Modify command line" will always take precedence over the arguments we pass by default, so the solution here for you specifically would be too click on the "Modify command line" and enter:
/v"/qn LICENSEKEY=XXXX-XXX-XXXX-XXXX-XXXX USERNAME=USER /l*v c:\logs\succesfull_install_from_pmp.log"

Hope to have helped.

We wish you a rest of a great week ahead

Hi gzrock,

As for the DB's, it doesn't matter but SQL is more performant, WID has some memory limitations which might be hit and then you will see some degraded performance depending on how many clients are phoning in and using WSUS.

Hope to have helped.

Hi Trevor,

PMPC has a built-in feature to "Disable self-updater" for installers that support it, it seems that however VSCode does not support this feature, so the workaround here would be to use a custom script to do this for you after the installation/update is complete, to do so you can right-click the app/update of VSCode, enable the option "Add custom pre/post scripts" and from there select the script that will disable the self-updater for for you.

Hope to have helped!