Steg

My Windows Install disk is the volume licensing version, and I did tick the box for mini setup, and yes my folder structure is $OEM$\$1\sysprep, I just tried it again from scratch and wrote down what I did, Build Windows XP SP3 from disc (Volume licensing version) Install Drivers/software etc (Though for testing I created a new image with just drivers so it's faster to image) Remove from Domain and restart Extract files from deploy.cab from XP CD into a created folder C:/sysprep (I also downloaded it from the MS website but the versions are the same anyway) run setupmgr.exe Create new answer file Sysprep Setup Option Windows XP Proffessional Fully automate the installation Go through Setup process filling in appriopriate fields Save to default location C:\sysprep\sysprep.inf Copy Sysprep folder to USB pen drive (Leave on machine as well) Run Sysprep.exe Tick Use Mini-Setup Shutdown Mode - Reboot Click Factory Machine syspreps and restarts Log in after sysprep auto starts click "Reseal" (I don't check the mini-setup box a second time do I need to?) Machine reboots again PXE Boot into Capture image Select C: Volume Name Image Save to local machine in created folder on C: I don't upload the the server at this point as I had a duplication issue WDS Captures image Once image captured reboot machine run through welcome screen applying settings etc Copy image saved to C: to WDS\Custom Images folder Add Install Image to Install Image Group Copy sysprep.inf file from pen drive taken from machine to created folder \images\imagegroup\imagename\$oem$\$1\sysprep\ (Also tried copying entire sysprep folder) PXE machine to deploy to, select image, delete partitions etc, Image deploys fine but after restarting get the Welcome to Windows XP screen etc as if it was just "resealed" and didn't read the answer file.

Hmm, I've tried both Duke's suggestion by copying the entire sysprep folder into the $oem$ etc folder structure however that didn't work and I also tried your method Apeman and that to didn't work. I also removed the folder structure after changing the wdssystemtemplate just incase and I restarted the WDS Service after each change. I don't know if its worth mentioning but I noticed the sysprep folder in the C: Drive on the image is gone after I have deployed it, is Sysprep meant to remove the folder after running? It just seems that C:\sysprep\i386 is refenced in the answerfiles, yet it doesn't exist, and on that note the i386 folder doesn't exist in my sysprep folder when extracted from the .cab. I don't know, I'm not getting any errors or anythign it just doesn't seem to read it.

That is exactly what I did do, but when I restart the machine after capturing the image the sysprep folder has been automatically deleted, so I copy the sysprep.inf file before hand as well and put in the $OEM$ etc structure but when I image a machine it still prompts for the serial number etc. As for MDT I've no idea how it works and the manual seems to be 500 pages long, does it work on a similar thought process like WDS?

Hello, I don't know if anyone can help but I'm getting a major headache over getting WDS to deploy Windows XP unattended. I have WDS on Windows Server 2008 R2, I can get the images for XP to deploy but I just can't get the unattended part to work. I don't want to make the initial WDS setup unattended (Ie loggin in choosing image/disk etc) but I do want to automate the machine setup after the image is deployed. Everywhere I have read simply states I need to put the sysprep.inf file in a created folder structure located at remoteinstall\images\imagegroup\createdimagenamefolder\$OEM$\$1\sysprep\sysprep.inf Which I have done, I assume the image file itself stays in the Imagegroup folder, but I deploy the image and it just doesn't automate. Can anyone help? Below is the sysprep.inf file I am using.

Hello, I did some searching but couldnt really find some definative answers so I thought I would ask myself and see if I could get some confirmation We are currently considering upgrading from Office 2003 to Office 2007, however there are a handful of issues that we are unsure of before making the switch. Does Office 2007 work with Sims, this is the main concern for upgrading, however I have read that there are no issues with 2007 and Sims now. Will all files currently saved in 2003 open in 2007 okay? I've heard issues with Access being awkward when trying to open older files in newer versions. How well did the teaching staff take up 2007? We will give plenty of forewarning and training material etc, but do you have any good advice to help ease the process? The students seem to be increasingly using Office 2007 and dispite the conversion packs and notices about saving as 95-2003 we still get a decent number of students needing us to convert them for us so any help would be greatly appreciated!