+ Post New Thread
Results 1 to 5 of 5
O/S Deployment Thread, Which unattend.xml? in Technical; Something I've never really understood, when I create my image the last thing I do us run sysprep.exe /generalize /oobe ...
  1. #1

    Join Date
    Jul 2008
    Location
    Merseyside
    Posts
    297
    Thank Post
    16
    Thanked 10 Times in 10 Posts
    Rep Power
    14

    Which unattend.xml?

    Something I've never really understood, when I create my image the last thing I do us run sysprep.exe /generalize /oobe /shutdown /unattend:x64unattend.xml

    The x64unattend.xml is my own XML file that I include on the image. However, in MDT in the /DeploymentShare/Control/001 folder theres another unattend.xml file in there.

    Which one is actually being used then?

    Or are both being used?

    Thanks!

  2. #2
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    970
    Thank Post
    41
    Thanked 80 Times in 76 Posts
    Rep Power
    20
    Its for the deployment of the os. So sysprep doesn't have one afaik. As the unattend.xml is applied to the image in depoyment. So your image is more flexible.

  3. #3

    Join Date
    Jul 2008
    Location
    Merseyside
    Posts
    297
    Thank Post
    16
    Thanked 10 Times in 10 Posts
    Rep Power
    14
    Huh? Sorry, I totally didn't understand that :s

  4. #4
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    970
    Thank Post
    41
    Thanked 80 Times in 76 Posts
    Rep Power
    20
    The unattend.xml is applied to the image when applied to a computer. You should use mdt to do the build and capture.
    There is also the sysprep and capture ts. You can edit the unattend.xml for sysprep with that ts. The ts must be started from within windows.
    Last edited by free780; 14th September 2013 at 06:18 PM.

  5. #5
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,450
    Thank Post
    10
    Thanked 493 Times in 433 Posts
    Rep Power
    111
    The unattended option on the *server* (for x86, x64 etc)
    This is used by the Windows PE phase to automate the image selection, login, format the drive etc
    You can only have one of these specified in the gui, but if you prestage a machine you can have it use a different one (handy to make different machines automatically install different images each time).

    The unattended option on the *image* is coped to the machine during the above deployment phase, and is used when the machine reboots, in the normal manner for an unattended sysprep file.
    It just means you can change the image unattended file without having to recapture etc, you sysprep the base image without one.

SHARE:
+ Post New Thread

Similar Threads

  1. [MDT] unattend.xml
    By garethedmondson in forum O/S Deployment
    Replies: 8
    Last Post: 28th November 2011, 02:38 PM
  2. Replies: 1
    Last Post: 19th August 2010, 12:24 PM
  3. unattend.xml not running on a custom syspreped image??
    By burgemaster in forum Windows 7
    Replies: 2
    Last Post: 25th March 2010, 10:21 AM
  4. [WDS] Win 7 unattend.xml help
    By Ste_Harve in forum O/S Deployment
    Replies: 5
    Last Post: 1st February 2010, 01:51 PM
  5. WDS - Unattended.xml has anyone got one?
    By Dos_Box in forum Windows Server 2008
    Replies: 2
    Last Post: 20th February 2008, 03:49 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
  •