When creating stand-alone media from a CAS, allow primary site selection
Please add the ability to select a primary site or site code when creating stand-alone media from a CAS.
When creating stand-alone media today, it automatically sets the SCCM client to install using the site code of the site that is used to create the media. When using a CAS to create the media, this will cause the client to deploy without a usable site code.
You cannot currently override this behavior through setting installation properties in the Setup Windows and ConfigMgr step.
This was solved with bug 419146 – released in SCCM 2012 R2 Sp1. The code was updated to use SMSSITECODE=“AUTO”
Updated by bobmn for sangeev/OSD
This issue is not resolved. I am running SCCM 2012 R2 SP1 CU3 and the stand-alone media doesn't pick up policies so some install software actions (requiring reboot) fail.
Install software actions that require restart fail with the following:
Failed to run the action: <action name>. The requested operation is successful. Changes will not be effective until the system is rebooted. (Error: 80070BC2; Source: Windows)
That's actually just a 3010 return code which should be handled by the task sequence but it sees it as an error because it doesn't have any success and reboot exit codes in the cached policy on the media.