| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 110492 | 2010-06-19 12:05:00 | WDS Discover boot image error | jwil1 (65) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1111622 | 2010-06-19 12:05:00 | Hi, I'm trying to automate imaging Windows 7 machines using Windows Deployment Services (WDS). I've used an unattend answer file that works until I tell it info like what disk to install on and what partition. When I boot from the network it errors before I get to choose the image, with error "Windows cannot parse the unattend answer file's <DiskConfiguration> setting." Here's what I want it to do: - Automatically logon to the WDS server with supplied credentials - Ask me what image to install - Automatically format disk 1 - Automatically install image on disk 1, partition 1 with no other partitions created. Here's a copy of my answer file: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="schemas.microsoft.com xmlns:xsi="www.w3.org <WindowsDeploymentServices> <Login> <Credentials> <Domain>{domain}</Domain> <Password>{password}</Password> <Username>{username}</Username> </Credentials> </Login> <ImageSelection> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> </ImageSelection> </WindowsDeploymentServices> <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Extend>false</Extend> <Format>NTFS</Format> <Label>Windows 7 System</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> <TypeID></TypeID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> </DiskConfiguration> <LogPath>C:\WDSLOG.TXT</LogPath> </component> </settings> <cpi:offlineImage cpi:source="wim:d:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> Any ideas as to what I'm doing wrong?? :help: |
jwil1 (65) | ||
| 1111623 | 2010-06-19 12:38:00 | Just been playing about with that today actually, thats after doing it Via WinPE See this thread (pressf1.pcworld.co.nz), using Server 2008 Small Business Edition. What I'd suggest is do it manually Via the Discover CD first, then once working then use the unattended file. Do you have the Documentation of WDS ?? If you dont you can download it From here (www.box.net) Just uploaded it --- Read the Getting started sections ( page 9 onwards) |
wainuitech (129) | ||
| 1111624 | 2010-06-19 13:53:00 | Got rid of the error now, but now I've got another problem :( WDS doesn't seem to be taking any notice of my <DiskConfiguration> section: <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Size>100</Size> <Type>Primary</Type> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>Primary</Type> <Extend>true</Extend> <Size></Size> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Order>1</Order> <PartitionID>1</PartitionID> <Active>true</Active> <Label>System</Label> <Format>NTFS</Format> </ModifyPartition> <ModifyPartition wcm:action="add"> <Order>2</Order> <PartitionID>2</PartitionID> <Letter>C</Letter> <Label>Windows</Label> <Format>NTFS</Format> <Extend>true</Extend> <Active>true</Active> </ModifyPartition> </ModifyPartitions> <WillWipeDisk>true</WillWipeDisk> <DiskID>0</DiskID> </Disk> <WillShowUI>Never</WillShowUI> </DiskConfiguration> According to all my googling at help-file browsing this should automate everything but it's not... :( |
jwil1 (65) | ||
| 1111625 | 2010-06-19 23:35:00 | Maybe SolMiester can help out -- In the thread I posted before Re WinPE he mentioned using WDS himself so may have some positive answers. I know when I was playing about with it over the last few days I have it set up as this. Made a unattend file, booted the PC from DVD - the unattend did the rest., which made up a reference PC. Did an image.wim capture to the SBS. Then did another using sysprep on the reference PC, so I ened up with two. One for my own PC, the other for installs on customers since sysprep wipes all hardware related drivers, etc. On WDS - loaded in the correct Boot.wim from SBS DVD, as well as the image I wanted which was Windows 7 Home Pre. Made up a discover CD. From the PC I was wanting to load the image into -- change the BIOS to allow network Boot - the Discover CD located the W7HP image and away it went -- come back 6 minutes later (literally) and the system as all up and running on a fresh install. Since I'm only doing very small numbers I find it easier to do it the way with the discover CD I put above, because at the end of the day on customers PC's I still have to put in their product key and User Names after using the syspreped Image. |
wainuitech (129) | ||
| 1111626 | 2010-06-19 23:50:00 | You could also try the Sample unattend altering as required. It also configures the disk layout – for example, the image will be installed on the first partition (<PartitionID>) and the first disk (<DiskID>) on the client computer. <?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>username</Username> <Domain>Fabrikam.com</Domain> <Password>my_password</Password> </Credentials> </Login> <ImageSelection> <WillShowUI>OnError</WillShowUI> <InstallImage> <ImageName>Windows Vista with Office</ImageName> <ImageGroup>ImageGroup1</ImageGroup> <Filename>Install.wim</Filename> </InstallImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> </ImageSelection> </WindowsDeploymentServices> <DiskConfiguration> <WillShowUI>OnError</WillShowUI> <Disk> <DiskID>0</DiskID> <WillWipeDisk>false</WillWipeDisk> <ModifyPartitions> <ModifyPartition> <Order>1</Order> <PartitionID>1</PartitionID> <Letter>C</Letter> <Label>TestOS</Label> <Format>NTFS</Format> <Active>true</Active> <Extend>false</Extend> </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-US</UILanguage> </SetupUILanguage> <UILanguage>en-US</UILanguage> </component> </settings> </unattend> Edited: the above is from the WDS Deployment Guide page 78 |
wainuitech (129) | ||
| 1111627 | 2010-06-20 00:09:00 | Got it working! Turns out Windows 7 needs that 100MB partition and won't install without it. Set it to setup 2 partitions and away she went! |
jwil1 (65) | ||
| 1111628 | 2010-06-20 01:23:00 | Cool --:thumbs: I found out the hard way as well about that partition -- from the thread I posted before I do remember trying it a few days ago to install only to one partition using the autounattend file -- It really spat the dummy 100MB is no big deal. |
wainuitech (129) | ||
| 1111629 | 2010-06-20 01:31:00 | With that annoying 100mb partition, the AMD here wouldnt go past the post screen (it hung) after the first reboot (after installing Win7, with that partition). So, I had no choice BUT to make the partitions bigger, so setup couldnt create it. That was the only way Win7 would install. So, you dont need it with all systems (well you've got no choice, but to make the partitions bigger if it hangs, otherwise Win7 wont install at all) | Speedy Gonzales (78) | ||
| 1 | |||||