Upgrading to ConfigMgr 2012 SP1, and using Applications?
January 28, 2013 Leave a comment
Check out my MVP colleague Kenny’s blog to learn what you need to do to get applications healthy.
Enterprise Systems Management – the good, bad, and ugly
January 28, 2013 Leave a comment
Check out my MVP colleague Kenny’s blog to learn what you need to do to get applications healthy.
January 25, 2013 3 Comments
We recently encountered an issue that has been around for a while, but no real documentation on it except for a couple posts in the TechNet Forums. Hopefully this post will save you some time.
Consider the following scenario:
When you run the stand-alone media build process, the task sequence fails on any step that is configured to “Install a Program.” The errors appear in the smsts.log and execmgr.log, as shown below:
smsts.log:
Failed to invoke Execution Manager to Install Software for PackageID=LAB003EA
InstallSoftware Failed. hr=0x87d01004
Process completed with exit code 2278559748
Failed to run the action: Install FOO Client. The program is disabled. (Error: 87D01004; Source: CCM)
This message may also appear: Failed to invoke Execution Manager to Install Software x80008004
execmgr.log:
TS Step required to run a disabled program. Rejecting.
This is a known issue. Here are your options for work-around:
WMIC /namespace:\\root\ccm\policy\machine\requestedconfig path ccm_SoftwareDistributionClientConfig CREATE ComponentName="Enable SWDist", Enabled="true", LockSettings="TRUE", PolicySource="local", PolicyVersion="1.0", SiteSettingsKey="1" /NOINTERACTIVE
You don’t need to do all three steps-choose one.
Greg