Messages

I'm so sorry, I realise now I didn't give you a method of getting them over to us!

If you could email them to [email protected] that would be awesome 

Could you send over the log files listed below from one of the affected devices please?


    %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

Good Morning,

Thank you for making us aware of this, we will take a look into it and see what's going on here.

Thanks,
Antony

Hi Chris,

No silly questions here

For application updates, the publisher will send any products you have enabled down to WSUS and then these will be pulled into SCCM on the next SUP sync that runs after our publisher sync finishes. These updates will then appear under "All Software Updates" in the SCCM console. It is then up to you how you choose to deploy these to your end user devices, but the updates will only update existing installs of the applications across your end user devices, if a device doesn't have the app installed then our detection method scripts will not pick it up so nothing will happen.

For application base installs, the publisher will send the selected products directly to your SCCM console when our publisher sync runs, again from here it is completely up to you how you deploy these to your end user devices. Under ConfigMgr apps tab in the publisher within "Options" you can choose to "update an existing apps metadata....." this would then overwrite the previous application in the console whilst retaining the set deployment.

For any available app deployments, these will still show up as available in the Software Center if they have an older version of the app installed. So if you choose the option previously mentioned, those apps will be available in the Software Center to end users that already have the app, but an older version installed.

If you would like to book a setup call, one of our engineers can run through how integration works and how the apps and updates also work and how they behave depending on how you deploy them - https://patchmypc.com/schedule-setup-call

If I can help any further then let me know.

Thanks

Antony

Good Morning,

Could you please send over the logs to [email protected] and we can take a look at what's going on here.


    %PatchMyPCInstallDirectory%\PatchMyPC.log
    %PatchMyPCInstallDirectory%\PatchMyPC*.lo_
    %PatchMyPCInstallDirectory%\Settings.xml
    %PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv
    %PatchMyPCInstallDirectory%\PatchMyPC-PublishingHistory.csv
    %SiteServerLogsFolder%\wsyncmgr*.log
    %SiteServerLogsFolder%\WCM*.log

Thanks,

Antony

Unfortunately not, we do not directly install any driver updates, we will allow you to deploy this app to your end user devices and from there they would need to install the driver updates from the app.

Hi Aleksander,

Could you provide some more clarity around this please?

What do you mean by the configuration? Also which platform are you deploying this from (SCCM or Intune).

Thanks,

Antony

Hello,

This is very odd, I have checked and the silent install string is still part of the latest version. Could you please send over the log files listed below from one of the affected end user devices and we can take a look.


    %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

Thank you!

That's great news, glad you've resolved the issue.

Please reach out again in future if you have any issues 

Hey!

I'm unable to reproduce this in my lab environment. Could you please send over the logs listed below to [email protected] and we will take a look at what is going on here:


    %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

Thanks,

Antony

Good Morning,

Unfortunately, due to Techsmith only allowing certain TLS Ciphers you will be unable to download on a Win2012R2 server. These installers will require a manual download then you can copy them into your local repository for the publisher to push out from there.

We have this detailed on our known issues page, you can find more information here - https://patchmypc.com/known-issues-and-considerations-when-using-patch-my-pc?fbclid=IwAR0nYzW6Mi-N4IDPp1YLSW0oY3wTSPYtGxggi_hysSMvdtv8vdEJ771-Hts

Thanks,
Antony

Hi!

This isn't something we currently offer as part of our "Manage Assignments" feature, but I think it would be a great if you could raise this as a feature request on our ideas page - https://ideas.patchmypc.com/?fbclid=IwAR1oXS6Y08Mcww3Ux30qZh2OTm7xfmplzA6F_jITpUx5WjSIvdowVLV6YwY

Thanks,

Antony

Hi Lars,

Can you please send over the below log files from one of the affected devices to [email protected] so we can take a look at what is happening here:

For SCCM client devices:
%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
%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

For Intune enrolled devices:
%ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
%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

Thanks
Antony