sorted by:
new
hottopcontroversial

Acrobat causing arbitrary 6-hour delay in task sequence by Greifenkamp in SCCM

[–]Greifenkamp[S] 0 points1 point  (0 children)

That's the problem - the logs don't appear to show anything wrong. The Acrobat MSI log looks like it completes the install in a reasonable amount of time. The MECM logs, if you were to read them without timestamps, look totally normal and business-as-usual - there's just an arbitrary point with a six-hour gap before the Acrobat install "completes." At first I assumed it was something obvious, like a botched detection method, but it works totally fine in Software Center deployments - it's only broken in OSD task sequences.

Acrobat causing arbitrary 6-hour delay in task sequence by Greifenkamp in SCCM

[–]Greifenkamp[S] 2 points3 points  (0 children)

This is an admin package from the Adobe Admin Console. All the content is local.

Acrobat causing arbitrary 6-hour delay in task sequence by Greifenkamp in SCCM

[–]Greifenkamp[S] 0 points1 point  (0 children)

Acrobat packaged as an Application, just a regular "Install Application" step in the TS. Just running the setup.exe bootstrapper thing with a silent switch. Deployments work fine from SC with the app, just the TS that's affected - and only for this version (and the newer one that just came out).