I faced the issue that the “Apply Operating System” failed. I wanted to install the OS with the original MS sources, so I haven’t created a new.wim file. When I was testing it, the Task Sequence failed and the following error appeared in the smsts.log file:

The error occurding because the Folder I pointed the Operating System Installer to, only contained the install.wim file. I thought that’s all that is needed, but in fact the full Content of the OS cd is needed. The error is gone after I’ve copied the full Content and re-distributed the OS Install to the DP.

There is a nice diagram from TechNet that explains which component in the unattended file runs at what time:

I run into the issue that the collation of my existing MS SQL 2012 Server wasn’t according to the pre-requisites of the SCCM 2012 SP1 Installation. So I had to Change the collation on the SQL Server to SQL_Latin1_General_CP1_CI_AS, this is the syntax:

Setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName
/SQLSYSADMINACCOUNTS=accounts [/SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName]

In my example, I executed the following:

Setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER
/SQLSYSADMINACCOUNTS=Domain\Administrator
/SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS

If you have a CAG with AAC in place and once tried to do a login with Internet Explorer 10, you might know that when you enter your credentials, it always returns back to the login prompt. The issue is IE10. If you enable the compatibility view in IE10, the issue is gone. A better way to fix it is so add a meta tag into the webpage that will automatically enable the compatibility mode in IE10:

Add the following line into the meta header part of the file BasePage.aspx:

<META http-equiv=”X-UA-Compatible” content=”IE=EmulateIE9″ />

The BasePage.aspx file can be found in the root of your logon point on the AAC server.