Dear sir/madam,
We are a Dutch OEM currently working on deployment and DIS. I have a question about deployment I’m hoping you can help us with.
We were tought to deploy images via USB using the following script:
dism /Apply-Image /ImageFile:%1 /Index:1 /ApplyDir:W:\
md T:\Recovery\WindowsRE
attrib -h -a -s W:\windows\system32\recovery\winre.wim
copy W:\windows\system32\recovery\winre.wim T:\Recovery\WindowsRE\winre.wim
W:\Windows\System32\bcdboot W:\Windows /s S:
W:\Windows\System32\reagentc /setreimage /path T:\Recovery\WindowsRE /target W:\Windows
Mkdir R:\RecoveryImage
Copy %2 R:\RecoveryImage\
W:\Windows\System32\reagentc /setosimage /path R:\RecoveryImage /target W:\Windows /index 1
This works perfectly for single systems. However, since we’re planning on building a lot of units we want to automate installation over network. We’re building a solution to deploy custom images on tablets, laptops and desktops based on WDS. We currently have a working MS Server 2012 WDS server and several working custom images. The question we have is regarding the system recovery functions (PBR). I’ve managed to automate login to WDS, language choice and disk partitioning using WDSunattend (see below). WinRE and Recovery Image partitions are created. We can manually select the image we want to deploy and it will successfully install to the Windows partition.
<?xml version="1.0" ?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
<WindowsDeploymentServices>
<Login>
<WillShowUI>OnError</WillShowUI>
<Credentials>
<Username>Administrator</Username>
<Domain>WDS.assemblage.com</Domain>
<Password>xxx</Password>
</Credentials>
</Login>
<ImageSelection>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>4</PartitionID>
</InstallTo>
</ImageSelection>
</WindowsDeploymentServices>
<DiskConfiguration>
<Disk>
<DiskID>0</DiskID>
<WillWipeDisk>false</WillWipeDisk>
<CreatePartitions>
<CreatePartition>
<Order>1</Order>
<Size>540</Size>
<Type>Primary</Type>
</CreatePartition>
<CreatePartition>
<Order>2</Order>
<Size>260</Size>
<Type>EFI</Type>
</CreatePartition>
<CreatePartition>
<Order>3</Order>
<Size>128</Size>
<Type>MSR</Type>
</CreatePartition>
<CreatePartition>
<Order>4</Order>
<Size>20000</Size>
<Type>Primary</Type>
</CreatePartition>
<CreatePartition>
<Order>5</Order>
<Extend>true</Extend>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition>
<Order>1</Order>
<Format>NTFS</Format>
<Label>WinRE</Label>
<PartitionID>1</PartitionID>
<TypeID>de94bba4-06d1-4d40-a16a-bfd50179d6ac</TypeID>
</ModifyPartition>
<ModifyPartition>
<Order>2</Order>
<PartitionID>2</PartitionID>
<Label>System</Label>
<Format>FAT32</Format>
</ModifyPartition>
<ModifyPartition>
<Order>3</Order>
<PartitionID>3</PartitionID>
</ModifyPartition>
<ModifyPartition>
<Order>4</Order>
<PartitionID>4</PartitionID>
<Letter>C</Letter>
<Label>Windows</Label>
<Format>NTFS</Format>
</ModifyPartition>
<ModifyPartition>
<Order>5</Order>
<PartitionID>5</PartitionID>
<Label>Recovery</Label>
<Format>NTFS</Format>
<TypeID>de94bba4-06d1-4d40-a16a-bfd50179d6ac</TypeID>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
<SetupUILanguage>
<WillShowUI>OnError</WillShowUI>
<UILanguage>en-GB</UILanguage>
</SetupUILanguage>
<UILanguage>en-GB</UILanguage>
</component>
</settings>
</unattend>
Here’s the problem: I can’t find any information on creating PBR functionality using unattend anywhere. Is this possible? If it is, can you help us find a solution?
Since I can’t find any info on creating PBR using unattend I’m assuming that we have to add PBR functionality using scripts after Windows setup is completed. How do we get this done using WDS?
With kind regards,
Frank Wessels.