The automatically decline superseded updates is not something you can configure within the publisher. This can however be set in the Software Update Component Properties within the SCCM console itself, head to the Supersedence Rules tab and configure as shown below in the attachment on my message.
Since you raised the post we found a bug in our detection logic due to FileZilla changing the naming convention of the product in the latest version. This has since been fixed and will now work as intended moving forward.
Could you please send the logs listed below from one of the affected devices over to [email protected].
%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.
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
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
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.
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