The focus of this blog is to detail solutions to common and unique issues involving ConfigMgr OSD that we see within CSS. We will also be sharing best practices and lessons learned from handling support cases involving OSD.
The below article was first published over The Configuration Manager Support Team Blog site. However we recently discovered that the method described in the article would only work when deploying from an Operating System Install Package (deploying from Windows installation source files). For that reason I recently updated the article to describe what to do when deploying from an Operating System Image.
In addition, there was also a couple of problems with the section where the XML code for the unattend file had to be copied and pasted. The first problem was that the XML code was wrapping in the blog post, which could cause the XML code not to be properly copied and pasted. The second problem was if an existing unattend file was already being used, not all of the lines in the XML code were needed. This made it difficult to figure out what lines in the XML code were needed and where those lines should be copied to. For this reason I changed the instructions to create/edit the unattend file using Windows System Image Manager (WISM) instead. Using WISM ensured that the unattend file would be created/edited correctly.
Please find the updated blog post below.
When deploying Windows Server 2008 using a Configuration Manager OSD Task Sequence, additional disks may show as offline when the Task Sequence completes
When using a Configuration Manager 2007 OSD Task Sequence to deploy Windows Server 2008 or Windows Server R2 to a server that contains disks that are not local (such as SAN or SAS disks), when the Task Sequence completes, the additional disks may not come online and may show as offline. Specifically in the Disk Management, the additional disks will show offline with the message:
Disk is offline due to a policy set by an administrator
This issue usually happens with the Enterprise and Datacenter editions of Windows Server 2008 and Windows Server 2008 R2, but may also happen in the Standard edition. In the Enterprise and Datacenter editions of Windows Server 2008 and Windows Server 2008 R2, the default SAN policy is to set the disks to be offline. Please see the following for more information:
You may see "Media is Write Protected" Error or VDS error 80070013 after bringing SAN disk online via Diskpart in Windows Server 2008http://support.microsoft.com/kb/971436/
Configure the SAN policyhttp://technet.microsoft.com/en-us/library/dd799290(WS.10).aspx
To resolve the issue, for the WinPE phase, the steps from KB971436 need to be added to the Task Sequence. Additionally, for deployments from Operating System Install Packages (Windows source files) the component and setting described in the SanPolicy TechNet article needs to be added to the unattend.xml file. For deployments from Operating System Images, a registry key value will need to be updated with the correct SAN policy value.
To bring the SAN online and make it read/write while in WinPE:
Full Windows OS - Operating System Install Package
If deploying from an Operating System Install Package (Windows installation source files), to change the default SAN policy for the full Windows OS, a custom unattend.xml file needs to be added to change the setting. If a custom unattend.xml file is already being used, the existing custom unattend.xml file needs to be modified that adds the setting that changes the default SAN policy for the full Windows OS:
Full Windows OS - Operating System Image
If deploying from an Operating System Image, an unattend file cannot be used to change the default SAN policy for the full Windows OS. When deploying from an image using a Configuration Manager OSD Task Sequence, Windows Setup never runs during the WinPE portion of the deployment. Therefore the settings pass offlineServicing is never processed. Since the Microsoft-Windows-PartitionManager component and the SanPolicy setting can only be added to the offlineServicing settings pass, then a method other than using an unattend file needs to be used. Instead of changing the SanPolicy setting via the unattend file, the equivalent registry key value can be modified once the OS image has been applied. To change the default SAN policy for the full Windows OS when deploying from an image, follow the below steps:
In the "Name:" text box, enter:Load System Hive
In the "Command line:" text box, enter in the following registry command:reg load HKU\temp "%OSPART%\Windows\System32\Config\System"If there was already a variable name entered in Step 4, then in the above command line replace "OSPART" with the variable name from Step 4.
In the Task Sequence, select the newly created "Load System Hive" task.
Click the "Add" menu and choose "General" --> "Run Command Line". This should add a "Run Command Line" task immediately after the "Load System Hive" task.
Frank RojasSenior Support Escalation Engineer