Topics

We are having a problem with the PMP Putty 0.78 package (SCCM). It is failing to install on all computers we have attempted, returning the same error code. The error code is 0x8000(32768). Do not believe we are having any problems with other PMP Application packages installed from the Software Center. As a test, I verified that the WinMerge package installs successfully.

This is a log from AppEnforce.log of one of the computers:

+++ Starting Install enforcement for App DT "PuTTY 0.78 (x64)" ApplicationDeliveryType - ScopeId_F8C75349-4CF6-4711-9C4A-97B6298C64CB/DeploymentType_98cf91a3-634e-4e8b-8c46-cedaf12309db, Revision - 4, ContentPath - C:\WINDOWS\ccmcache\1ec, Execution Context - System   AppEnforce   12/15/2022 9:04:45 AM   22020 (0x5604)
    Performing detection of app deployment type PuTTY 0.78 (x64)(ScopeId_F8C75349-4CF6-4711-9C4A-97B6298C64CB/DeploymentType_98cf91a3-634e-4e8b-8c46-cedaf12309db, revision 4) for user.   AppEnforce   12/15/2022 9:04:45 AM   22020 (0x5604)
+++ Application not discovered with script detection. [AppDT Id: ScopeId_F8C75349-4CF6-4711-9C4A-97B6298C64CB/DeploymentType_98cf91a3-634e-4e8b-8c46-cedaf12309db, Revision: 4]   AppEnforce   12/15/2022 9:04:47 AM   22020 (0x5604)
    App enforcement environment:
   Context: Machine
   Command line: PatchMyPC-ScriptRunner.exe /InstallPackage
   Allow user interaction: No
   UI mode: 1
   User token: not null
   Session Id: 1
   Content path: C:\WINDOWS\ccmcache\1ec
   Working directory:    AppEnforce   12/15/2022 9:04:47 AM   22020 (0x5604)
    Prepared working directory: C:\WINDOWS\ccmcache\1ec   AppEnforce   12/15/2022 9:04:47 AM   22020 (0x5604)
    Prepared command line: "C:\WINDOWS\ccmcache\1ec\PatchMyPC-ScriptRunner.exe" /InstallPackage   AppEnforce   12/15/2022 9:04:47 AM   22020 (0x5604)
    Executing Command line: "C:\WINDOWS\ccmcache\1ec\PatchMyPC-ScriptRunner.exe" /InstallPackage with user context   AppEnforce   12/15/2022 9:04:47 AM   22020 (0x5604)
    Working directory C:\WINDOWS\ccmcache\1ec   AppEnforce   12/15/2022 9:04:47 AM   22020 (0x5604)
    Post install behavior is BasedOnExitCode   AppEnforce   12/15/2022 9:04:47 AM   22020 (0x5604)
    Waiting for process 16472 to finish.  Timeout = 120 minutes.   AppEnforce   12/15/2022 9:04:47 AM   22020 (0x5604)
    Process 16472 terminated with exitcode: 32768   AppEnforce   12/15/2022 9:04:49 AM   22020 (0x5604)
    Looking for exit code 32768 in exit codes table...   AppEnforce   12/15/2022 9:04:49 AM   22020 (0x5604)
    Unmatched exit code (32768) is considered an execution failure.   AppEnforce   12/15/2022 9:04:49 AM   22020 (0x5604)
++++++ App enforcement completed (3 seconds) for App DT "PuTTY 0.78 (x64)" [ScopeId_F8C75349-4CF6-4711-9C4A-97B6298C64CB/DeploymentType_98cf91a3-634e-4e8b-8c46-cedaf12309db], Revision: 4, User SID: S-1-5-21-xxxxxxxxx] ++++++   AppEnforce   12/15/2022 9:04:49 AM   22020 (0x5604)

I doubt this is anything specific to Patch My PC, but I've noticed that it seems to take much longer for ConfigMgr clients to install third-party updates than it does to install Microsoft updates on my computers. More specifically, it seems to take longer to start the installation. For example, if I initiate an installation of several Microsoft updates and several Patch My PC updates, the Microsoft updates will begin to install and finish much quicker than third-party (Patch My PC) updates to start and finish. Is this typical? I perform regular database maintenance on the SUSDB, such as deleting obsolete updates and declining updates that I do not need. I know when unused updates build up in the database, it can cause clients to take a long time to scan.

The only thing I can see going on while the client is waiting to start the installation of an update is the WmiPrvSE.exe being highly active. Once the installation starts, it pretty much goes idle. I know the client uses WMI host for much of its work. What is it doing when it goes to install these updates? Is it scanning all updates every time it install a third-party update? If so, why does it not seem to do this for Microsoft updates? I have also looked at scanagent.log and UpdatesHandler.log and there doesn't seem to be a too much going on in there during this time.

Hi. We have just purchased Patch My PC and I am in the process of getting it setup. I have custom SSRS reports for displaying data on "needed" and "failed" updates for our computers. I am building a report just for third-party updates and looking for a simple way to query for just Patch My PC updates. I am using the dbo.v_UpdateInfo view to pull in a list of update names. I thought to use the ArticleID column, WHERE ArticleID LIKE 'PMP%' but I have noticed PMP updates do not always being with PMP. There is no Vendor column, nor do I see any type of vendor uid in this view. SCCM console can filter on Vendor, so it is obviously possible. Any suggestions appreciated. Thanks.