Messages

Code Select Expand

+++ Starting Install enforcement for App DT "Adobe Acrobat Reader DC 22.003.20314" ApplicationDeliveryType - ScopeId_A2D6993C-1000-4444-8375-9EB0D5869039/DeploymentType_c7334577-8cfc-4ed3-b377-747c3518ac59, Revision - 2, ContentPath - C:\WINDOWS\ccmcache\10, Execution Context - System    AppEnforce    1/26/2023 12:19:39 PM    24596 (0x6014)
    Performing detection of app deployment type Adobe Acrobat Reader DC 22.003.20314(ScopeId_A2D6993C-1000-4444-8375-9EB0D5869039/DeploymentType_c7334577-8cfc-4ed3-b377-747c3518ac59, revision 2) for system.    AppEnforce    1/26/2023 12:19:39 PM    24596 (0x6014)
+++ Application not discovered with script detection. [AppDT Id: ScopeId_A2D6993C-1000-4444-8375-9EB0D5869039/DeploymentType_c7334577-8cfc-4ed3-b377-747c3518ac59, Revision: 2]    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
Found a logged on user instance    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
    App enforcement environment:
    Context: Machine
    Command line: PatchMyPC-ScriptRunner.exe /InstallPackage
    Allow user interaction: Yes
    UI mode: 0
    User token: null
    Session Id: 4294967295
    Content path: C:\WINDOWS\ccmcache\10
    Working directory:    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
    Prepared working directory: C:\WINDOWS\ccmcache\10    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
    Prepared command line: "C:\WINDOWS\ccmcache\10\PatchMyPC-ScriptRunner.exe" /InstallPackage    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
    Executing Command line: "C:\WINDOWS\ccmcache\10\PatchMyPC-ScriptRunner.exe" /InstallPackage with user context    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
    Working directory C:\WINDOWS\ccmcache\10    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
    Post install behavior is BasedOnExitCode    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
    Waiting for process 20640 to finish.  Timeout = 120 minutes.    AppEnforce    1/26/2023 12:19:40 PM    24596 (0x6014)
    Process 20640 terminated with exitcode: 3010    AppEnforce    1/26/2023 12:22:01 PM    24596 (0x6014)
    Looking for exit code 3010 in exit codes table...    AppEnforce    1/26/2023 12:22:01 PM    24596 (0x6014)
    Matched exit code 3010 to a PendingSoftReboot entry in exit codes table.    AppEnforce    1/26/2023 12:22:01 PM    24596 (0x6014)
++++++ App enforcement completed (141 seconds) for App DT "Adobe Acrobat Reader DC 22.003.20314" [ScopeId_A2D6993C-1000-4444-8375-9EB0D5869039/DeploymentType_c7334577-8cfc-4ed3-b377-747c3518ac59], Revision: 2, User SID: ] ++++++    AppEnforce    1/26/2023 12:22:01 PM    24596 (0x6014)


Despite having /norestart in the command line options, some of our users are getting reboot prompts from Software Center when yesterday's update of Adobe Acrobat Reader DC 22.003.20310.

Is there anything we can do / provide to help figure out why?

I've checked off Microsoft -> ConfigMgr Client Toolkit, run a sync (several times) and nothing seems to be happening with it.  Other apps continue to create in SCCM, but that one is being ignored.  Nothing in the failure list in Teams, nothing in the success list, and no application is created.

I'm just getting started with PMPC, and our crew here is pretty much self-taught in SCCM, so if this is a dumb question, please bear with me.

From my understanding, when an app has updates, PMPC will drop the new files in and do the equivalent of an Update Content on the SCCM Application.  My question is what then happens in the following scenarios:

• "Required" Deployment - app is forcefully installed on a collection of devices (we tend NOT to target required deployments to user collections)
• "Available" Deployment - app is available to a collection(s) of users or devices, and the users can install from Software Center

I'm assuming that for required deployments, SCCM will notice the new version number and automatically redeploy the updated app to the collection?  I'm also further assuming that the PMPC installer will gracefully take care of removing the old version if needed?  Or perhaps SCCM does an uninstall / reinstall cycle?

My main worry is for available deployments where folks already have the app installed from Software Center.  Will SCCM automatically redeploy to those people?

Oh, and I just came up with a third class of installs - what if the application was on the user's device before we made it available?  Is SCCM smart enough to realize this and add that device to the "devices where XX is installed" list?

As you can probably see, I'm just trying to wrap my head around what to expect to happen once I start replacing our current deployments with PMPC deployments.  I'd rather not have any user-facing surprises if I can help it.

I appreciate any input anyone might have!

-Chris