Tips for Installing ConfigMgr Apps during OSD

Posted on Updated on

Similar to a previous post on 10 Tips for a More Successful Windows Image Build & Capture, this post outlines tips to help you successfully deploy ConfigMgr 2012 R2 Applications during OS deployment for an image build/capture on a workgroup computer.

  1. First, review the top tips for OSD (10 Tips for a More Successful Windows Image Build & Capture)
  2. Second, if your DP is setup for HTTPS, skip to the last step in this sequence
  3. Enable anonymous authentication on the DP properties
  4. Install the latest CU for the ConfigMgr client with the PATCH property
  5. Ensure the Network Access Account (which is also used by workgroup computers to access resources) has been defined and has the appropriate access to the DP resources
  6. Install hotfix KB2522623 as a package – for Win7 SP1
  7. Install hotfix KB2775511 as a package – for Win7 SP1
  8. Command to enable SWDist Agent via command

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

  1. Command to enable PowerShell Scripts: reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\PowerShell /v EnableScripts /t REG_DWORD /d 1 /f

Command to enable PowerShell ExecutionPolicy: reg add reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\PowerShell /v ExecutionPolicy /d Unrestricted /f

  1. Application deployment types: set Content > Deployment options – Download content from DP and run locally
  2. Ensure the property “Allow this application to be installed from the Install Application Task Sequence action” has been enabled (hint: it’s on the General tab for the application’s properties)
  3. Then if all else fails, ditch applications for doing a build and capture…

Deploying Microsoft Hotfixes via the ConfigMgr 2012 App Model

Posted on

In this example, I will use the new ConfigMgr 2012 application model to deploy the a Microsoft hotfix.  While this is not intended to be a full demo on how to create a script installer for the application model, this will feature a few key components — the installation/uninstallation command lines and then using PowerShell to detect the presence of the hotfix’s installation status.

For the install/uninstall command lines, be certain to NOT call the .wsu installer directly as this will fail with message “Method EnforceApp failed with error 87d01104” in the AppDiscovery.log file.  Rather, use wusa.exe to trigger the install.  Also, ensure the file name is surrounded by double quotes and the appropriate parameters are added after the quotes.

  • Install – wusa.exe “KB1234567” /quiet
  • Uninstall – wusa.exe “KB1234567” /uninstall


For the detection logic (in the Deployment Type), select to use script type “PowerShell” and click edit.  For the script contents, run command

Get-HotFix | Where-Object {$_.HotfixID -eq 'KB1234567'}



And this should be the main components you need to have in place to successfully detect and deploy a hotfix with the ConfigMgr 2012 as an Application!