Jump to content


Sign in to follow this  
RGB09

Windows XP and WDS

Recommended Posts

Hi Guy's this is just a simple question, and maybe someone can help me with some tips and suggestions. I have been trying to deploy/capture an XP image from a HP DC7900 ultra-slim form PC. I have deployed images before with RIS with no problems, but now I am trying to use WDS to image and deploy to the aforementioned PC's.

I have follwed the instructions on this site, I have even managed to inject the NIC drivers, unfortunately I am still trying to find the correct ones.

A couple of questions to start with;

1- if I want to capture an XP machine, does it have to have the pre-installed version of XP, the one that is on the recovery disc, or can I use any ISO version?

2- has anyone successfully captured and deployed an XP machine? if so how did you do it?

 

Sorry to be a pain, but I have serched the net for this but everything thing seems to be on deploying Vista or Server 2008....

 

Any help would be appreciated :rolleyes:

Share this post


Link to post
Share on other sites

the capture WDS should function just as stated in the guide, have you tried it yet ? what problems did you see ?

Share this post


Link to post
Share on other sites
the capture WDS should function just as stated in the guide, have you tried it yet ? what problems did you see ?

Thanks for getting back so quick, I think my problem is a driver issue if I have understood it right. I get as far as loading the image I want to capture window, and when I try to copy it to the server after a while it errors and say's "The network location cannot be reached". I never had this problem before in my previous place of work. Would you know which *.inf file or drivers I have to inject for a HP DC7900 ultra-slim form PC? which runs Windows XP SP2?

I have tried both the vista and xp drivers. Help!!!!

Share this post


Link to post
Share on other sites

you need to add the Windows Vista network drivers for your computer to the BOOT.WIM file that you created in this post

 

you can use imageX to do that

Share this post


Link to post
Share on other sites
you need to add the Windows Vista network drivers for your computer to the BOOT.WIM file that you created in this post

 

you can use imageX to do that

Once again thanks... I will try to locate the correct drivers

Share this post


Link to post
Share on other sites
Once again thanks... I will try to locate the correct drivers

 

This is proving more difficult than I thought! I have installed/injected every Vista NIC driver for this PC and I still get the error message... does any one have any other suggestions I could try... this is now getting really desperate!!!

Share this post


Link to post
Share on other sites

Still no luck on the drivers front, I have tried injecting drivers from the Intel site and also the HP site, I even tried the XP drivers for RIS to see if they made any difference!

Is there anyone out there who has successfully deployed and captured an image for the HP DC 7900 ultra-slim or slim form PC?

CAN ANY-ONE HELP....PLEASE!!!!

Share this post


Link to post
Share on other sites

give me a download link for the driver you tried please

Share this post


Link to post
Share on other sites

you only need to add NETWORK drivers to boot.wim (or storage, but thats not your problem)

 

whcih boot.wim file did you update ?

Share this post


Link to post
Share on other sites

ok i've created a boot.wim file for you to import into WDS and test

 

to create it I used my windows server 2008 DVD, i then imported the boot.wim file from the dvd into wds and once in there i made the boot.wim file OFFLINE

 

i then located the file and it's location was d:\remoteinstall\boot\x86\images\boot.wim

 

i then created a temp folder on c: called c:\mount

 

i then opened an Administrator command prompt and changed directory to the WAIK imagex tools

 

here are the commands I used to inject the 4 INF files into the boot.wim, first though you have to identify the boot index number from within the boot.WIM file

 

Imagex /info Drive:\remoteinstall\boot\x86\images\boot.wim

 

Notes:

 

• Drive:\remoteinstall represents the path at which the Remoteinstall folder is installed.

• Boot.wim is the name of the boot image.

 

Note the boot index number of the bootable image that is displayed. To identify the boot index number, locate the line that contains "boot index: X."

 

Note X is the boot index number. The number indicates that image number X is marked as bootable and that the image is to be updated. The second image is the default image that you would typically modify.

 

 

C:\Program Files\Windows AIK\Tools\x86>

 

imagex /mountrw d:\RemoteInstall\Boot\x86\Images\boot.wim 2 c:\mount

 

ImageX Tool for Windows

Copyright © Microsoft Corp. All rights reserved.

 

 

Mounting (RW): [d:\RemoteInstall\Boot\x86\Images\boot.wim, 2] ->

[c:\mount]

 

Successfully mounted image (RW).

 

 

 

C:\Program Files\Windows AIK\Tools\x86>cd ..

 

C:\Program Files\Windows AIK\Tools>cd PETools

 

C:\Program Files\Windows AIK\Tools\PETools>

 

peimg /inf=c:\imagex_temp_driver_folder\Win32\E1E6032.INF "c:\mount\Windows"

 

Preinstallation Environment Image Setup Tool for Windows

Copyright © Microsoft Corporation. All rights reserved.

 

Installing INF package: c:\imagex_temp_driver_folder\Win32\E1E6032.INF

 

PEIMG completed the operation successfully.

 

C:\Program Files\Windows AIK\Tools\PETools>

 

peimg /inf=c:\imagex_temp_driver_folder\Win32\E1K6032.inf "c:\mount\Windows"

 

Preinstallation Environment Image Setup Tool for Windows

Copyright © Microsoft Corporation. All rights reserved.

 

Installing INF package: c:\imagex_temp_driver_folder\Win32\E1K6032.inf

 

PEIMG completed the operation successfully.

 

C:\Program Files\Windows AIK\Tools\PETools>

 

peimg /inf=c:\imagex_temp_driver_folder\Win32\e1q6032.inf "c:\mount\Windows"

Preinstallation Environment Image Setup Tool for Windows

Copyright © Microsoft Corporation. All rights reserved.

 

Installing INF package: c:\imagex_temp_driver_folder\Win32\e1q6032.inf

 

PEIMG completed the operation successfully.

 

C:\Program Files\Windows AIK\Tools\PETools>

 

peimg /inf=c:\imagex_temp_driver_folder\Win32\E1Y6032.INF "c:\mount\Windows"

 

Preinstallation Environment Image Setup Tool for Windows

Copyright © Microsoft Corporation. All rights reserved.

 

Installing INF package: c:\imagex_temp_driver_folder\Win32\E1Y6032.INF

 

PEIMG completed the operation successfully.

 

C:\Program Files\Windows AIK\Tools\PETools>

 

cd..

 

cd x86

 

C:\Program Files\Windows AIK\Tools\x86>

 

imagex /commit /unmount c:\mount

 

ImageX Tool for Windows

Copyright © Microsoft Corp. All rights reserved.

 

 

Unmounting: [c:\mount]...

 

Successfully unmounted image.

 

I've copied the file onto my server here, please download it and verify if it resolves your problem.

Share this post


Link to post
Share on other sites

Hi this is great, I will try this tonight and let you know what happens... thanks for all your help. BTW which drivers did you use in the end???

Share this post


Link to post
Share on other sites

IT WORKS!!!! this is great, I have managed to capture an image and also deploy an image successfully... I have followed your steps closely about injecting drivers and they are the same steps I used! Did you copy all the drivers into the boot.wim file?

Now I just have to see if I can image some Toshiba Laptops :unsure: I'll let you know how I get on ;)

Share this post


Link to post
Share on other sites

great stuff.

 

always when injecting drivers into boot.wim verify that the file date changes afterwards (and size)

 

imagex /unmount c:\mount

 

will not commit any changes you make unless you do it as follows

 

imagex /commit /unmount c:\mount

Share this post


Link to post
Share on other sites
great stuff.

 

always when injecting drivers into boot.wim verify that the file date changes afterwards (and size)

 

imagex /unmount c:\mount

 

will not commit any changes you make unless you do it as follows

 

imagex /commit /unmount c:\mount

 

This is interesting, I have just re-read your instructions for injecting drivers, does it make any differance that when I injected the inf files I used *.inf rather than name the .inf files individually? I can't see how that makes any differnce, or does it?

Share this post


Link to post
Share on other sites

i don't think it should have made a difference, my guess is you just forgot to commit the changes,

 

can you verify ?

Share this post


Link to post
Share on other sites
i don't think it should have made a difference, my guess is you just forgot to commit the changes,

 

can you verify ?

 

Yes you were right I checked my other notes and I did not have the commit switch... again thanks ;)

Share this post


Link to post
Share on other sites

Hi

 

Does the same commands and options work if i go for VISTA or Server 2oo8 ? I mena on Server 2008 server install WDS and capture image of Vista runing of compaq laptop.

Share this post


Link to post
Share on other sites

it should work as long as you do what has been explained in the posts here

have you tried it yet ?

Share this post


Link to post
Share on other sites

Hello Admin

I Want to install xp using wds server 2008 i want to install os on c:\ partition without change of other drive. is this possible or not ! if Yes how?

Plz reply

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...