Windows 2003 SP2 WDS (help) pls

[Joel Pritchard 0]

"Sorry for the repost I think i posted it in the wrong section so I am now posting it here."

 

Hello Everyone,

 

I have a WDS Setup on Windows 2003 SP2 with legacy, everything is going good I can boot off pxe and install the operating system however I cannot figure out how to make an unattended file. Can anyone please point me into the right direction basically I want the entire process automated, dont have to enter cd key, name or anything else.

 

Also is there a way to install i386 to the c:\ while installing.

 

 

here is my sysprep.inf http://pastebin.ca/1416567

 

here is my unattended.txt http://pastebin.ca/1416570

 

Maybe I am not putting these in the correct place?

 

Thanks Ahead of time.

[anyweb 480]

Windows Deployment Services supports 3 main methods of deploying clients, manual, unattended and multicast. If you want to do unattended installs then you'll need to configure WDS to support this by doing as follows:-

 

 

Unattended Deployment. This method automates the Windows Deployment Services client and the latter stages of Windows Setup. For instructions, see Using unattend files in the "Windows Deployment Services Role Step-by-Step Guide". For examples, see "Sample Unattended Files" in the unattended installation chapter at http://go.microsoft.com/fwlink/?LinkId=88439 . This two-stage approach is accomplished by using two different unattend files:

 

a. Windows Deployment Services client unattend file: This file uses the Unattend.xml format and is stored on the Windows Deployment Services server in the \WDSClientUnattend folder. It is used to automate the Windows Deployment Services client user interface screens (such as entering credentials, choosing an install image, and configuring the disk).

 

b. Image unattend file: This file uses the Unattend.xml or Sysprep.inf format, depending upon the version of the operating system in the image. It is stored in a subfolder (either $OEM$ structure or \Unattend) in the per-image folder. It is used to automate the remaining phases of setup (for example, offline servicing, Sysprep specialize, and mini-setup).

 

get your sample unattend.xml file from here >>>>> http://technet.microsoft.com/en-us/library...80.aspx#client1