MSFN Forum: How to guides on deploying Windows XP WIM Images - MSFN Forum

Jump to content


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

How to guides on deploying Windows XP WIM Images Rate Topic: -----

#21 User is offline   cluberti 

  • Gustatus similis pullus
  • Group: Supervisor
  • Posts: 11,208
  • Joined: 09-September 01
  • OS:Windows RT
  • Country: Country Flag

Posted 20 November 2009 - 08:51 PM

You can't deploy an XP WIM from MDT - MDT's Windows PE is hard-coded to run setup.exe from the install medium to install the WIM, which is how Vista and Win7 are deployed. However, XP doesn't deploy from setup.exe, and as such you'll simply hang when trying to deploy. You will have to use a flat-file install of XP to use MDT to deploy it, or you'll have to create a post-image task sequence and call it after you deploy the XP WIM from WDS.


#22 User is offline   Bloodboy 

  • Group: Members
  • Posts: 1
  • Joined: 07-January 10

Posted 07 January 2010 - 05:54 PM

Hey Guys, :hello:
my name is Tobias and im from germany. I train as a IT specialist.
Now the end of my education is close, so i have to prepare a project for my final audit.
Ive chosen the Windows Deployment Services as my topic.

Via google ive found the Blog from ashinator, but ive got some questions about it.

When i crreate the hardware independent XP image, why i have to do step 58 - 62 and the same in 74 - 77 ? Is it not enough to record the image at the end?

And in step 38, can i use the driver packages from http://driverpacks.net ?

Excuse me for my bad english and I know that the thread is quite old, but i hope anyone can help me!

#23 User is offline   cluberti 

  • Gustatus similis pullus
  • Group: Supervisor
  • Posts: 11,208
  • Joined: 09-September 01
  • OS:Windows RT
  • Country: Country Flag

Posted 07 January 2010 - 08:11 PM

Welcome to the forums, Tobias. I need you to make sure you've read the rules here, because your question pretty much falls afoul of rule 2.c:

View Postxper, on Apr 25 2004, 01:22 PM, said:

2.c Requesting help with academic material, such as assignments, is not permitted on MSFN. Receiving such help is often viewed as plagiarism in many schools, and therefore cannot be allowed. This is for your own protection in your academic career.
Your questions are innocuous, but you'll learn more if you try for yourself and determine if you can or cannot do these things. The project and your education should be yours, not MSFN's to help with. I am sorry, but these rules are in place to help people who are doing things for their education, not to hinder you.

#24 User is offline   P2PGuru 

  • Group: Members
  • Posts: 3
  • Joined: 08-February 10
  • OS:Windows 7 x64
  • Country: Country Flag

Posted 08 February 2010 - 05:28 AM

Great post but I'm wondering what happens to the VMWare Tools. I don't see that these are uninstalled before syprep is executed.
I know that sysprepping removes the drivers but this doesn't uninstall the VMWare tools. Am I missing something here?

This post has been edited by P2PGuru: 08 February 2010 - 09:56 AM


#25 User is offline   knifesk 

  • Group: Members
  • Posts: 8
  • Joined: 26-March 07

Posted 08 February 2010 - 09:28 PM

dude... this is an amazing guide!! you should make the video!! haha

Thanks a lot... I guess ill put it on practice soon!

#26 User is offline   knifesk 

  • Group: Members
  • Posts: 8
  • Joined: 26-March 07

Posted 13 February 2010 - 12:24 PM

View Postaltjx, on Aug 3 2009, 12:39 PM, said:

Nice guide, when I get to
40. Type into the command prompt:

peimg /inf= Drivers\*.inf /image=build_install

If that didn’t work you may have to type the ones that didn’t work manually.

Ex: peimg /inf= Drivers\e1000.inf /image=build_install

I get errors "PEIMG failed to complete the operation with status code 0x80070003. Followed the guide exactly step by step. I'm doing this on a physical machine, not virtual btw.


same error @here... using boot.wim from seven x64 instead 2008, since I dont have a 2008 copy

even tried to remove the space after /inf=(space)Drivers

any suggestion?

#27 User is offline   cluberti 

  • Gustatus similis pullus
  • Group: Supervisor
  • Posts: 11,208
  • Joined: 09-September 01
  • OS:Windows RT
  • Country: Country Flag

Posted 14 February 2010 - 05:31 PM

That error equals "COR_E_DIRECTORYNOTFOUND", so keep that in mind when troubleshooting - it's not finding something it expects.

#28 User is offline   ebaker 

  • Group: Members
  • Posts: 1
  • Joined: 07-June 10
  • OS:XP Pro x86
  • Country: Country Flag

Posted 07 June 2010 - 08:07 AM

View Postknifesk, on 13 February 2010 - 12:24 PM, said:

View Postaltjx, on Aug 3 2009, 12:39 PM, said:

Nice guide, when I get to
40. Type into the command prompt:

peimg /inf= Drivers\*.inf /image=build_install

If that didn’t work you may have to type the ones that didn’t work manually.

Ex: peimg /inf= Drivers\e1000.inf /image=build_install

I get errors "PEIMG failed to complete the operation with status code 0x80070003. Followed the guide exactly step by step. I'm doing this on a physical machine, not virtual btw.


same error @here... using boot.wim from seven x64 instead 2008, since I dont have a 2008 copy

even tried to remove the space after /inf=(space)Drivers

any suggestion?



You need to change the path to wherever you have the drivers. For instance, I downloaded the drivers to c:\drivers so the command is peimg /inf=c:\drivers\*.inf /image=build_install

#29 User is offline   saydin82 

  • Group: Members
  • Posts: 1
  • Joined: 18-June 12
  • OS:2003 x86
  • Country: Country Flag

Posted 18 June 2012 - 04:59 PM

The ashley didn't say where is your wmware tools drivers folder

in your computer goto C:\Program Files\VMware\VMware Tools\Drivers\vmxnet

in wmxnet folder they are wanted .inf files

Attached File(s)



Share this topic:


  • 2 Pages +
  • 1
  • 2
  • You cannot start a new topic
  • You cannot reply to this topic

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy