Error 0x80004005 when installing Applications to a WORKGROUP system during Build and Capture Task Sequence

I use a task sequence to perform the initial build of my Windows 7 reference pc, install Microsoft Office 2010 and then I capture it manually.  I’ve been doing this for quite some time using ConfigMgr 2007 without any issues, however I was seeing an error with ConfigMgr 2012 when it tries to install Microsoft Office 2010 as an “Application” (as opposed to a traditional “Package”.)  The SMSTS.LOG on the failed build would record an ‘unspecified error’ 0x80004005.

I finally figured out, after a lot of head scratching and forum posting, that the SMSMP switch needs to be used in the “Setup Windows and ConfigMgr” step of your reference build task sequence AND you also need to ensure that you have IP Range/IP Subnet based boundaries within your Boundary Group.  AD Site name boundaries alone will not work.  This is a very similar issue to what we had/have with ConfigMgr 2007 and Software Updates during OSD.

This problem does not occur when using a Task Sequence to install Applications to a system that has been Domain Joined during the Windows Setup phase.  This makes sense, as the Domain Joined client wouldn’t have any problem locating the Management Point or figuring out it’s boundaries – as it can query Active Directory.  A WORKGROUP joined system needs to be spoon-fed the name of the Management Point – even though it is already communicating with a defined management point (as set by the boot media.) and also be able to associate itself to a boundary using it’s IP Address.



ConfigMgr State Migration Point Error: Health check request failed, status code is 500, ‘Internal Server Error’.

I encountered a problem earlier this week provisioning a new ConfigMgr 2012 environment with a State Migration Point (SMP).  I am used to just installing the SMP role and pointing it at a drive letter to use and letting it create the folder structure it needs.  However, I think there may be an issue with ConfigMgr 2012 with this method as it seems to want to modify the permissions of the folder that you specify, and if this happens to be the drive root then we see some problems.

When attempting to install the SMP role and specifying the drive root as a target, the SMPMGR.LOG records the following errors continually;

Call to HttpSendRequestSync failed for port 80 with status code 500, text: Internal Server Error
Health check request failed, status code is 500, 'Internal Server Error'.

What seems to happen is that the SMP role setup routine modifies the permissions of the target folder and now has insufficient permissions to create the necessary MigrationStatus folder within the SMPSTOREF_12345678$ folder.  This issue does not occur if you use the drive root which ConfigMgr is installed on as a target, weird.

So in summary, you must create a sub-folder (maybe called SMP or SMSSMP) on the drive you intend to use for your SMP role and use that path as the target, never the drive root itself.