+ Post New Thread
Results 1 to 6 of 6
O/S Deployment Thread, WDS and ESXi in Technical; Short story, I've got an ESXi server setup, and can successfully boot WDS inside of a VM. Capturing and dumping ...
  1. #1
    Duke5A's Avatar
    Join Date
    Jul 2010
    Posts
    731
    Thank Post
    74
    Thanked 113 Times in 99 Posts
    Blog Entries
    8
    Rep Power
    27

    Question WDS and ESXi

    Short story, I've got an ESXi server setup, and can successfully boot WDS inside of a VM. Capturing and dumping an image is not a problem. When I deploy a prebuilt XP image and reboot, it will come up, go through mini setup, and join the domain. It's when it reboots for the second time that it gives a BSOD complaining about an "Unmountable Boot Volume." I'm familiar with this error when creating images, as it is generally an indication that there isn't the correct south bridge drivers in the image for the hardware it is trying to boot on. The thing is, it booted once and successfully completed mini setup, why not a second? I don't get it.

    This same image will deploy on physical hardware just fine. No configuration changes were made to the VM in between those boots either.

    The VM is setup with a Bus Logic controller, Windows XP 32bit for the guest OS, and an e1000 NIC (Forced this since VM Flex drivers don't exist for PE).

    Any ideas would be greatly appreciated, as I'm all out of my own. Thanks guys...

    Some more details to tickle the brain... The XP image I am trying to deploy, was built in a VM with the same hardware spec. If I capture it, and dump it into a new VM using Ghost32 11.0, it works great. But capturing and dumping from WDS causes the above problem. I'm going to go mad...
    Last edited by Duke5A; 19th July 2010 at 08:52 PM. Reason: Additional details...

  2. #2


    Join Date
    Dec 2005
    Location
    In the server room, with the lead pipe.
    Posts
    4,534
    Thank Post
    271
    Thanked 752 Times in 590 Posts
    Rep Power
    218
    I'm betting it's something to do with vmware-tools (it nearly always is). Does the vm have vmware-tools installed when you capture it? Try removing them before capturing.

  3. #3

    Theblacksheep's Avatar
    Join Date
    Feb 2008
    Location
    In a house.
    Posts
    1,876
    Thank Post
    127
    Thanked 279 Times in 204 Posts
    Rep Power
    164
    boot critical hard drive drivers.

    2nd mini setup uses the actual OS.

  4. #4
    Duke5A's Avatar
    Join Date
    Jul 2010
    Posts
    731
    Thank Post
    74
    Thanked 113 Times in 99 Posts
    Blog Entries
    8
    Rep Power
    27
    Quote Originally Posted by pete View Post
    I'm betting it's something to do with vmware-tools (it nearly always is). Does the vm have vmware-tools installed when you capture it? Try removing them before capturing.
    No it doesn't. The image is pretty bare as it is used as a base image for multiple departments and hardware specs.

  5. #5
    Duke5A's Avatar
    Join Date
    Jul 2010
    Posts
    731
    Thank Post
    74
    Thanked 113 Times in 99 Posts
    Blog Entries
    8
    Rep Power
    27
    Quote Originally Posted by Theblacksheep View Post
    boot critical hard drive drivers.

    2nd mini setup uses the actual OS.
    Are you sure? I've created images where I've forgotten Intel SATA drivers before and it would BSOD on first boot. Besides, both VMs, the VM where the image was created, and the one that it is being dumped to, are using Bus Logic.

  6. #6
    Duke5A's Avatar
    Join Date
    Jul 2010
    Posts
    731
    Thank Post
    74
    Thanked 113 Times in 99 Posts
    Blog Entries
    8
    Rep Power
    27
    Figured it out, here is the low-down...

    I'm used to the Ghost way of imaging, that is Ghost handles all the partition related tasks. WIM on the other hand, is strictly a file level method of imaging that relies on outside means of handling partitioning; in this case, it's WDS. To automate the process, I created an unattended.xml for my WDS server and specified for it to wipe the disk and recreate the partition. The WinXP Pro WIM would then be dumped onto the drive and it would reboot. Mini setup would start up, it would ask for name, join the domain, reboot once more, and then BSOD.

    The problem was in my sysprep.inf. It makes since seeing as how it booted for the first time, and bombed out on the second boot. I had to remove the following lines from the XP sysprep.inf.

    [Data]
    AutoPartition=1
    [Unattended]
    ExtendOemPartition=1
    FileSystem=ConvertNTFS
    Repartition=Yes

    Presto, problem gone. Something with how WDS and Windows XP sysprep handles partitioning. Never was a problem when using Ghost.

    So note to self, don't put partitioning options into sysprep when deploying XP with WDS.

    Thanks guys.

SHARE:
+ Post New Thread

Similar Threads

  1. vSphere and ESXi
    By vgopinat in forum Thin Client and Virtual Machines
    Replies: 0
    Last Post: 20th June 2010, 03:44 AM
  2. VMware ESXi zombie problem: Unable to reset kill or register VM in ESXi 4
    By albertwt in forum Thin Client and Virtual Machines
    Replies: 3
    Last Post: 29th April 2010, 09:55 AM
  3. ESXi and HDDs
    By Chuckster in forum Hardware
    Replies: 9
    Last Post: 9th December 2009, 10:25 AM
  4. ESXi @ Home
    By Hightower in forum Thin Client and Virtual Machines
    Replies: 9
    Last Post: 17th October 2008, 03:30 PM
  5. WDS Legacy Mode vs WDS
    By markwilliamson2001 in forum Windows
    Replies: 0
    Last Post: 15th July 2008, 12:50 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
  •