+ Post New Thread
Results 1 to 14 of 14
O/S Deployment Thread, Unattended Windows XP deployment. in Technical; Hello, I don't know if anyone can help but I'm getting a major headache over getting WDS to deploy Windows ...
  1. #1

    Join Date
    Jan 2009
    Posts
    5
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Unattended Windows XP deployment.

    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\createdimagenamefo lder\$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.

    ;SetupMgrTag
    [Unattended]
    OemSkipEula=Yes
    InstallFilesPath=C:\sysprep\i386

    [GuiUnattended]
    AdminPassword=616ebdcc419c5adc48425b0d78f8a45ddd4a 50eca914823336ce52aeea2090b5
    EncryptedAdminPassword=Yes
    OEMSkipRegional=1
    TimeZone=85
    OemSkipWelcome=1

    [UserData]
    ProductKey=blahblah
    FullName="user"
    OrgName="school"
    ComputerName=*

    [RegionalSettings]
    LanguageGroup=1
    SystemLocale=00000809
    UserLocale=00000809
    InputLocale=0809:00000809

    [SetupMgr]
    DistFolder=C:\sysprep\i386
    DistShare=windist

    [Identification]
    DoOldStyleDomainJoin=Yes
    JoinDomain=DOMAIN
    DomainAdmin=domain\user
    DomainAdminPassword=password

    [Networking]
    InstallDefaultComponents=Yes

  2. #2
    tosh74's Avatar
    Join Date
    Dec 2006
    Location
    Scotland
    Posts
    136
    Thank Post
    27
    Thanked 43 Times in 27 Posts
    Rep Power
    23
    Deploy XP Images in the Computer Lab with Windows Deployment Services on Server 2003.
    This guide works well for me - start at Prepare the client machine for imaging with Sysprep

  3. #3


    Join Date
    Oct 2006
    Posts
    3,411
    Thank Post
    184
    Thanked 356 Times in 285 Posts
    Rep Power
    148
    Never sussed WDS on it own out personally, try MDT.

  4. #4
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,183
    Thank Post
    206
    Thanked 221 Times in 190 Posts
    Rep Power
    72
    Go with MDT 2010 on top of WDS, its free and makes life so much easier

  5. #5

    Join Date
    Jan 2009
    Posts
    5
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by tosh74 View Post
    Deploy XP Images in the Computer Lab with Windows Deployment Services on Server 2003.
    This guide works well for me - start at Prepare the client machine for imaging with Sysprep
    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?

  6. #6
    alexsanger's Avatar
    Join Date
    Oct 2009
    Location
    London
    Posts
    117
    Thank Post
    21
    Thanked 23 Times in 21 Posts
    Rep Power
    14
    Quote Originally Posted by themightymrp View Post
    Go with MDT 2010 on top of WDS, its free and makes life so much easier
    +1 - Exactly what we're doing here with XP and 7

  7. #7
    Duke5A's Avatar
    Join Date
    Jul 2010
    Posts
    789
    Thank Post
    79
    Thanked 129 Times in 112 Posts
    Blog Entries
    8
    Rep Power
    31
    You've got the path right, but you need the entire contents of the sysprep directory placed in there and not just the inf.

  8. #8

    Join Date
    Jul 2010
    Posts
    106
    Thank Post
    0
    Thanked 14 Times in 14 Posts
    Rep Power
    11
    if all your xp machines are going to use the same sysprep.inf information (ie global settings) you can just put it all in the WdsSysprepTemplate.inf file which is located in Reminst\Templates. if you do this then you WONT need to create a sysprep.inf for each image you deploy

    here is my wdssyspreptemplate.inf

    ;SetupMgrTag
    [Unattended]
    DriverSigningPolicy = Ignore
    OemPreinstall = yes
    OemPnPDriversPath=\Drivers\Network;
    OemSkipEula=Yes
    InstallFilesPath=C:\sysprep\i386

    [GuiUnattended]
    AdminPassword=*
    OEMSkipRegional=1
    TimeZone=85
    OemSkipWelcome=1

    [UserData]
    ProductKey=1111-1111-1111-1111-1111
    FullName="SYSTEM ADMIN"
    OrgName="School Name"
    ComputerName=%MACHINENAME%

    [Display]
    BitsPerPel = 32
    Xresolution=1680
    YResolution=1050

    [TapiLocation]
    CountryCode=44
    Dialing=Tone
    AreaCode=

    [RegionalSettings]
    LanguageGroup=1
    SystemLocale=00000809
    UserLocale=00000809
    InputLocale=0809:00000809

    [SetupMgr]
    DistFolder=C:\sysprep\i386
    DistShare=windist

    [Identification]
    JoinDomain=domain.com
    DoOldSysleDomainJoin=YES
    DomainAdmin=user
    DomainAdminPassword=password
    MachineObjectOU="OU=Orphan Machines,OU=Workstations,DC=domain,DC=com"

    [Networking]
    InstallDefaultComponents=Yes
    Last edited by apeman; 12th December 2011 at 10:03 PM.

  9. Thanks to apeman from:

    Steg (15th December 2011)

  10. #9

    Join Date
    Jan 2009
    Posts
    5
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    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.

  11. #10

    Join Date
    Jul 2010
    Posts
    106
    Thank Post
    0
    Thanked 14 Times in 14 Posts
    Rep Power
    11
    hmm that should of worked. where did you get your windows install disc from?? volume licence?? or did you just use the version of windows that came with the machine??

    when you sysprepped windows before you captured it, did you tick the box that said use mini setup??

    the wdssyspreptemplate.inf should get copied to c:\sysprep and renamed to sysprep.inf and then it will be read by sysprep when it runs

    you are correct the sysprep folder will go from c: once sysprep is complete
    Last edited by apeman; 13th December 2011 at 09:36 PM.

  12. #11


    Join Date
    Feb 2007
    Location
    51.405546, -0.510212
    Posts
    8,709
    Thank Post
    220
    Thanked 2,615 Times in 1,926 Posts
    Rep Power
    777
    Quote Originally Posted by Steg View Post
    I've tried both Duke's suggestion by copying the entire sysprep folder into the $oem$ etc folder structure however that didn't work
    Did you place the SysPrep folder in $OEM$\$1? i.e.

    Code:
    $OEM$
      |
      |-- $1
           |
           |-- SysPrep

    Quote Originally Posted by Steg View Post
    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?
    Yes. That's normal.

  13. #12

    Join Date
    Jan 2009
    Posts
    5
    Thank Post
    2
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    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.

  14. #13

    Join Date
    Jul 2010
    Posts
    106
    Thank Post
    0
    Thanked 14 Times in 14 Posts
    Rep Power
    11
    Quote Originally Posted by Steg View Post
    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 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?)


    I don't upload the the server at this point as I had a duplication issue
    i would always download the latest sysprep from microsoft and not use the one off the disc

    when you run sysprep you DONT use the factory option and reboot, you just tick mini setup and then click reseal

    i have never had the issue with WDS having duplication issues, i would imagine that its because you used the same image name when you save it to your local drive, i always put the date and computer model in the image name (14122011delld600), as it helps identify when it was made and keeps the name unique

  15. #14
    Duke5A's Avatar
    Join Date
    Jul 2010
    Posts
    789
    Thank Post
    79
    Thanked 129 Times in 112 Posts
    Blog Entries
    8
    Rep Power
    31
    You don't let the machine boot up again after sysprep finishes. This when you're supposed to capture it as an image. Run sysprep with these options:

    sysprep -mini -reseal -shutdown

    Then capture it and import into WDS.

  16. Thanks to Duke5A from:

    Steg (15th December 2011)

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 2
    Last Post: 10th June 2011, 07:36 AM
  2. [MDT] Windows XP Deployment ignore sysprep configuration on MDT2010
    By morganw in forum O/S Deployment
    Replies: 12
    Last Post: 10th February 2011, 11:50 AM
  3. using the same wds server for xp and windows 7 deployment
    By ful56_uk in forum O/S Deployment
    Replies: 6
    Last Post: 16th June 2010, 10:06 AM
  4. [Windows Software] Deploying Windows XP VM
    By albertwt in forum Licensing Questions
    Replies: 5
    Last Post: 5th April 2010, 08:29 AM
  5. [WDS] Windows XP Unattended Deployment
    By Jack_F in forum O/S Deployment
    Replies: 7
    Last Post: 7th February 2010, 05:30 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •