WDS walk through with Windows XP?????
-
Wednesday, March 28, 2007 5:46 PM
I was just wondering if anyone has found or has made a good guide for using WDS with Windows XP systems. I want to use it basically like I use my RIS server.
1) I want to be able to upload my custom image through my network.
2) Then I want to be able to re image computer using PXE booting.
I have tried to read the Microsoft technet "step by step guide" here: http://technet2.microsoft.com/WindowsVista/en/library/9e197135-6711-4c20-bfad-fc80fc2151301033.mspx?mfr=truIt
It just does not make sense to me.
Answers
-
Wednesday, March 28, 2007 8:01 PM I'll try to sum it up:
First off install the wds service.
Then get a hold of a Vista dvd and in the WDS MMC right click on boot-image and choose to add a new boot image. Call it something with BOOT in the end so you recognize it.
Then browse your way to the vista dvd and the source folder. It will contain a file called boot.wim.
Choose that file and let WDS do its thing. Then right-click on that newly created file in WDS MMC and choose to convert to a capture image, call it something with CAPTURE in the name. Again let WDS do its job.
Now right-click on install images and choose to create a new image group, call it what ever you want.
Now install reference computer and sysprep it with the desired paramters.
When sysprep is done let it restart the computer, during that restart PXE boot the computer and choose the CAPTURE option in the menu, the WDS client will appear.
Hopefully all your drivers will be found and you should be presented with a windows where you can choose the desired partition and enter notes.
When you choose next you will be able to save that image, note that you have to save it locally before it is uploaded to the server, make sure you check the "Upload to server" option. If you don't have any space on the harddrive to save the image file locally you can press shift+f10 to receive a command prompt from where you can map a network drive and save the image directly to the server. Note that this isn't recommended because of network glitches damaging the image.
Now the image should appear on your server.
Reboot the desired computer that is to be installed, This time choose the BOOT image and there you can choose your windowsxp image and continue the installation.
Hopefully I havn't forgotten anything but I'm sure someone else can fill in any missing details.
All Replies
-
Wednesday, March 28, 2007 8:01 PM I'll try to sum it up:
First off install the wds service.
Then get a hold of a Vista dvd and in the WDS MMC right click on boot-image and choose to add a new boot image. Call it something with BOOT in the end so you recognize it.
Then browse your way to the vista dvd and the source folder. It will contain a file called boot.wim.
Choose that file and let WDS do its thing. Then right-click on that newly created file in WDS MMC and choose to convert to a capture image, call it something with CAPTURE in the name. Again let WDS do its job.
Now right-click on install images and choose to create a new image group, call it what ever you want.
Now install reference computer and sysprep it with the desired paramters.
When sysprep is done let it restart the computer, during that restart PXE boot the computer and choose the CAPTURE option in the menu, the WDS client will appear.
Hopefully all your drivers will be found and you should be presented with a windows where you can choose the desired partition and enter notes.
When you choose next you will be able to save that image, note that you have to save it locally before it is uploaded to the server, make sure you check the "Upload to server" option. If you don't have any space on the harddrive to save the image file locally you can press shift+f10 to receive a command prompt from where you can map a network drive and save the image directly to the server. Note that this isn't recommended because of network glitches damaging the image.
Now the image should appear on your server.
Reboot the desired computer that is to be installed, This time choose the BOOT image and there you can choose your windowsxp image and continue the installation.
Hopefully I havn't forgotten anything but I'm sure someone else can fill in any missing details. -
Thursday, March 29, 2007 11:41 AM
Hi Alvedon
Thanks for the guide. I followed it part way and got lost lol.
I already have a RiPrep Image as lagecy Image, just need help converting it into a .WIM file. I followed another post and managed to get the converting going and ended up with an error code "0x80360051", so the conversion was not complete.
I also have a boot Image from WAIK package.
Do you have to run sysprep on a computer?
I got to the stage of creating an image group of your guide and got stuck. When I boot a computer with PXE boot it comes up with 2 options:
Microsoft Windows Vista PE (x86/x64)
Remote Installation Service
If i follow the first option it starts to load Vista, if I choose second option it goes to good-old "simply-work" RIS.
Where do I fit in your "...CAPTURE option in the menu, the WDS client will appear"?
Any idea where i am going wrong?
Thank You
-
Friday, March 30, 2007 11:43 AMHi CC-Khan,
Not really sure if you want me to explain about how to convert or about how to create a new image? I'll try to answer a little bit of both.
To be honest I have never comverted a legacy image or used WDS in legacy mode. The "CAPTURE" image is only used to capture an image of a computer but since you already have a riprep image which if I remember correctly also needed sysprep you will not have to use the CAPTURE mode.
You should use the boot.wim from VISTA and not the one from WAIK. This will give you an option like the one you have "Microsoft Windows Vista PE (x86/x64)". When you boot this you should if the conversion was successful be able to see your image and be able to deploy it.
If you want to create a new image then the reason why you don't get the CAPTURE part is because you most likley haven't converted the boot.wim image to a capture image. To do so simply right-click on the bootimage in the Boot Image folder and press "Convert to capture image" (not 100% that it is called so but you will see it) and then append CAPTURE at the end of the name.
Then your computer should see that image and you can boot from it and then follow the rest of the guide.
I think I lost my self in the text above but hopefully it clears some things out. -
Monday, April 02, 2007 9:19 AM
Hey Alvedon
Man!1 You are a star, I had no idea that a Vista boot.wim and WAIK boot.wim will have so much difference. I will give it another go with native WDS server.
Gona setup a new server to test out things and get back to ya
Thanks for the post mate
-
Monday, April 02, 2007 2:39 PM
Hi Alvedon
Had a great time installing WDS lol, WDS service wouldn't start and giving errors, eventually sorted it out and started WDS servie.
I have followed your guide and managed to do the following steps:
Added a boot.wim Image
Created capture image from the boot.wim
started up a client with PXE and got this messege:
TFTP
PXE - T01: FILE NOT FOUND
PXE - E3B: TFTP ERROR - FILE NOT FOUND
PXE - M0F: EXITING (MANUFACTURER) PXE ROM
I have been doing some search on this site and it does not say much. Other people have been reporting the same problem and not much of an idiot's guid provided by anyone yet.
If you have any idiot's guide PLEASE foward them on, they will suite me PERFECT.
Thanks
Khan
-
Monday, April 02, 2007 4:48 PMHi Khan
Not sure on how to solve that problem, noticed that it occured for a lot of people that installed wds over an existing ris installation.
What solved the problem for them was entering commandprompt and running wdsutil uninitalize-server (not sure about the spelling, run wdsutil /? and you'll see the correct command) and the running wdsutil initialize-server.
What this done is simply uninstalling the wds service and then installing it. Note that this has worked for a WDS that is installed/activated over an existing RIS, not sure if it will help any with a pure WDS installation.
Not that sure if removing / adding a boot image will help in any way-
Another thing you could do is open the dhcp mmc and there look under server options or what its called. You should be able to see the information your DHCP server sends to the clients, there should be a option 67 or 60 that contains a path to your reminstall directory and a file. Make sure that you have such a option and that it points to a valid file.
Unfortunatly I dont have any real 100% solution to this problem but hopefully someone else does. -
Tuesday, April 03, 2007 9:42 AM
Hi
When I ran the WDS configuration wizzard it had given the options to select "do not listen on port67" and "add option 60 to pxe clients". I have selected both of these options and they are in working order as far as I can see. I could not find any Ref to DHCP option 66 or 67.
I will detail my WDS server setup maybe someone can suggest any missing settings.
Server Properties:
PXE Response tab> Respond to All ( no other modification)
Advanced Tab>Allow WDS to dynamically discover valid Domain Servers (wds and AD on same server)
DHCP Tab> Do not listen on port 67 and Configure DHCP option 60 tp "PXEClient" Selected
Boot tab> x86 Architecture: boot\x86\pxeboot.com (not bothered bout others as i am not using them)
The rest of the settings are default.
First thing first , I have a Windows Vista Ultimate x64. I added the boot.wim of that vista x64 and boot\x86 folder didn't get any modifications. So i put the WAIK DVD and grabbed a "Microsoft Windows Vista PE (x86)" boot Image. Right-clicked the "Microsoft Windows Vista PE (x86)" and selected "Create capture Image" and saved it in a new folder in "Reminstall" folder.
Booted a client with PXE pressed F12 to enter PXE Boot. Was given the following error messege:
"Windows Blessing"
Windows failled to start. A recent hardware change might be the cause. to fix the problem:
1 Put in cd-rom
2 scream Loud
3 go suicide
4 rest in peace
If you do not have this disk "taugh luck mate", you are screwed.
INFO: RAMDISK DEVICE CREATION FAILED DUE TO INSUFFICIENT RAM
Press Enter = Continue
The following screen comes up
Choose an option:
Microsoft Windows Vista PE (x86)
Press F8 for more options
If I select the option, I (the fortunate one) get the "Windows Blessing" again ( very lucky to receive "Windows Blessing" again)
So like, my brain is bout to explode. Do I need a vista 32bit? That is gona be a BURN having to buy vista 32 bit JUST so that I can use my current system with the new SP Update, not to mention the £100 cost for the Vista dvd.
Any ideas as to where I am going wrong? ohh ya the main reason I am moving to WDS, coz my RIS clients were giving me errors. If you open up txtsetup.sif and move to the [SCSI] section, you will see a lot of drivers for storage controllers. My RIS kindly giving me errors for each one of those file and I am having to manually copy them from XP cd and rename them. Perfectly working RIS corrupted outa nowhere
Thanks in advance for all your help guys.
Khan
PS. pardon my fustration
-
Tuesday, April 03, 2007 8:09 PMModerator
Hi Khan,
Windows PE (which is the pre-install OS) requires 512MB of RAM. How much do you have on the client?
And is your client machine x86 or x64 based? If it's a 32 bit machine it won't run 64 bit WIndows PE. If it's 64 bit then it can run either, depending on which OS you want to install.
You can continue getting your RIS functionality on SP2 by using WDS in Legacy or Mixed modes.
So my questions for you are:
1) Is DHCP on the same box?
2) Is your client x86 or x64?
3) How much RAM does your client have?
Thanks,
Jez -
Wednesday, April 04, 2007 7:31 AM
Hi Jez
Thank you for the imput.
Yes, DHCP on the same server
x86 clients
256MB RAM on clients
I have converted my WDS server to Mixed mode, so I am able to use my RIS now. Just have to set up everything again. At least I know how to get a working RIS.
Thanks to you all for helpful posts.
-
Wednesday, April 04, 2007 2:30 PM
Hey guys
Got a WDS going now, I am a little stuck on Image Capture Wizzard now.
Booted a syspreped/ripreped computer and selected Capture Image. The Image Capture Wizzard has started.
Step1: Read it and pressed Enter
Step2: Selected C:\ drive from drop down list and gave it names and description.
Step3: Selected to saved it on C:\ Drive and clicked on "Upload Image to WDS Server" check box and typed in server name<server>, full server name <server.domain.com>, typed in Ip address <10.10.10.1>. All of them came up with error stating "The Network location cannot be reached......" and yet the client boots in from the server !!. I did scream like a monkey running arround the room pulling my hair for a bit, but error kept comming back after each restart.
Any ideas?
-
Wednesday, April 04, 2007 5:10 PMModerator
Hi Khan,
The client is booting from the server using the PXE ROM. It boots into a Windows PE image containing the Image Capture Wizard which may or may not have drivers for the network card.
At the image capture wizard page, hit Shift+F10 to launch a command prompt and run an ipconfig to see whether you have any network connectivity. If not you will have to add the NIC driver to your Windows PE image. Instructions for this should be in the Windows AIK.
-
Thursday, April 05, 2007 12:40 PM
Hello Jez
Thank you for the post. I have checked the setupapi.app.log and it shows that my NIC is loaded successfully and it recognised it correctly too. The Failures are Audio controller and Video controll, but i dubt they will intefere with Network issues.
However I pressed ShiftF10 to bring up Command prompt and ran ipconfig /all. It didn't show up wth any ip addressing details. I could not ping anything from there either. Tried to renew and release all failled.
I do aggree that there is an issue with NIC, but no idea with what or how to fix it.
Thanks again for your support
-
Thursday, June 07, 2007 1:33 PMKhan I am having the same problem as you. I have computer with 256 RAM. I installed 512 RAM and it works. The boot image seems to be having a problem booting with that amount of RAM.
-
Thursday, June 07, 2007 6:38 PMModeratorThat's correct. Windows PE requires 512MB of RAM in order to boot.
-
Thursday, June 07, 2007 7:05 PM
Just FYI:
I have had a problem with images showing up after I captured them.
If you computer supports Hyperthreading:
Turning hyperthreading on sometimes makes the image on the list show up, or the other way around. At times I have to turn hypertheading off after I have created an image.
-
Monday, June 25, 2007 4:31 PMI have followed your instructions perfectly and when i boot from PXE and choose "Microsoft Windows Lorghorn Setup (X86)" It will load the PE enviroment. Once completed it has me verify my credentials and and then the next page is where the images should be listed. I don't have any yet so I know that none should be listed. What I cant find is anything that will let me initiate are upload to the server. I never have another other options but to download and image from the server, which I can't do because I have never uploaded them. I thuoght that it was a security probelm with that "new install group" so I added my account as well as the Domain Admins security groups. Still all I get is just an option to download and image and never to upload. I also used shift+F10 and I do have a IP address so its getting to the server and verifying credentials. What am I doing wrong?
-
Monday, July 02, 2007 8:06 AM
Anybody can help me, how to get PXEBOOT.com files for wds.
My Setup
-------------
1) I have installed WDS in Server 2003 R2, and DHCP is installed on doamin in Server 2003, all relative ports are open on servers.
2) DHCP is authorised for WDS.
3) WDS is configured and already run risetup for window xp image.
4) Client bios is setup to boot fron network
Problem Facing
----------------------
When I start client pc to install WIndow XP , it takes ip address from dhcp and also find my WDS but unable to boot os. Offcourse its msg file not found.
In my WDS property there is not available pxeboot.com file and that folder is empty in every architecture.
What do I need
---------------------
I want to install Window xp remotly and i need pxeboot.com (either x86 or x64) file but still i could not get, if anyone is here who can solve my this problem and tell me step by step that how can i get these bootable file for WDS.
I will be higly thankful the person.
-
Monday, July 02, 2007 11:43 PM
Sorry to jump in but I have a "sort of" releated question.
I have successfuly created an image from a reference computer and can (PE)boot to the computer installing that new image on the new computer. The problem is at the first login XP does not see the Network drivers and just sees "new hardware" and asks for the location of the drivers.
1) The Reference computer has these drivers installed and works just fine prior to the sysprep
2) I remember encountering something similar with RIS and just had to "put" the drivers in a certain directory but that was for booting with RIS.
3) I am trying to have the new images joined to a domain and have created the unattended install file with setupmgr.exe
4) is there a place that I need to copy the drivers to other than just in the "reference computer" like somewhere in the image dir on the WDS Server?
Any help with this would be much appreciated
Thanks
M
-
Thursday, July 05, 2007 7:23 PM
Hi!
I have a problem with WDS and XP SP2 image deploying.
On my 2003 R2 SP2 server run WDS in native mode, with Vista boot.wim (and I create the capture boot.wim too) . I create a reference XP SP2 install, use sysprep.exe and capture boot.wim, the capture finish successfully. Then I boot the new PC (same type that the reference) with PXE boot, I get IP address from the DHCP server, boot with Vista boot.vim, found the uploaded image for XP, the files copying successfully, then the PC is rebooting, then I get error message: missing or corrupted windows\system3\hall.dll.
Please help me find the solution!
THX!
-
Wednesday, September 05, 2007 9:25 AM
Hey Crys
I had the same issue with a Dell laptop. When i decided to screw everything and go the old fassion way with a XP disk and install it again, i relised the Hard Disks are devided into different chunks (whatever dell setup they use).
I deleted all partitions and had approx 60GB un-partitioned space. Booted up with WDS and pressed enter all the way and it worked. I think the Hal has a problem with different hard disk partitioning or something. but have a play and see what you come up with.
Hope it helps.
-
Wednesday, November 21, 2007 12:04 PM
Hi Folks,
I have been following this thread carefully as I am having problems getting a working image of windows XP pro with WDS.
I have had several years experience working with RIS and all the problems that came with it. Since starting a new job I have been asked to implement WDS, unfortunately I am having problems with the whole thing. I have read the How to guides that MS have provided, but they have as always confused things and rather than clarify it has made things harder to understand.
This is my set up:
I have a VM PC running 2003 SP3 with WDS installed and configured. We have DHCP, DNS and AD configured and running.
The problem I have is that to properly run WDS you need to have a vanilla Vista DVD to hand and not the ones that come preinstalled with the machines. (Which is a DELL).
Is there any way of obtaining a copy of the Boot.wim and Install.wim files that are on the Vista DVD? Or must I resort to copying it from my own personal home copy? Surely Microsoft could ship a working copy of the above .wim files with WAIK, or is this too much to ask?
All I want to be able to do is create and deploy XP images just like I did with RIS
Any help would be great
-
Monday, November 26, 2007 10:21 AM
Ninja_Prime wrote: Is there any way of obtaining a copy of the Boot.wim and Install.wim files that are on the Vista DVD? Or must I resort to copying it from my own personal home copy? Surely Microsoft could ship a working copy of the above .wim files with WAIK, or is this too much to ask?
Any help would be great
Hi
Firstly, they have provided different versions of those files, some require more work and some less. Save yourself that time and get a coffee instead.
ok here is the simplest and fastest way (that I know of) to get a working WDS:
1. Copy those files from your personal CD (it does not ask for product key to copy those .WIM files so I do not think it's copy protected)
2. You have a working WDS
3. Post if you get stuck
-
Monday, November 26, 2007 11:13 PM
Hello,
i've been given a project to get wds working on our network but it's not going as we want it to
.
Installed: Server 2003 SP2(dhcp, dns, ad, etc.), WDS, BDD 2007, WAIK
Our goals:
Make a universal image of Windows XP SP2 (incl. office 2003, acrobat, virtual pc, msn etc) for multiple types of computers.
Image must be installed with almost no user interference.
Must automaticly be added to the domain with a computername we choose at installation.
Working so far:
We can boot WinPE 2.0 with the right drivers. (created by BDD 2007)
Deploy a windows xp sp2 with all the drivers and updates(updates slipstreamed with nLite)
Deploy a captured image using WinPE.
Problems:
None of the images is automaticly added to the domain when we install them (manually configured and unattended.txt not working).
It installs no software when we make a image using WinPE. (not taken along when we make a image ?)
Any advise/howto would be helpfull, we are working on it for 7 days now and we can't get it working properly. No other people in our envirenment have experience with this program.
Greetings,
Mart
-
Tuesday, November 27, 2007 1:31 PM
Hi Martjah
Try capturiing boot.wim from a Vista DVD. For some reason WAIK boot.wim is not fully operational as boot.wim from Vista is.
so try the following steps:
1. Configur WDS
2. add boot.wim from Vista dvd
3. create capture image with boot.wim
4. install xp on a computer
5. create an answer file for sysprep with setupmgr.exe from XP CD\Support\ folder
6. save sysprep.inf (answerfil) to c:\sysprep\ folder on ref PC and sysprep that pc
7. pxe boot ref PC and try to capture the image.
See how you get on with those steps. Post back if you get stuck.
-
Tuesday, November 27, 2007 5:14 PM
Hello Khan,
thanks for your help, we had it working the same way about 1 hour before you posted
it all works well now on the test PC.
this week we will try following this guide: http://www.vernalex.com/guides/sysprep/index.shtml
and try to make the image universal for differend pc's/laptops.
i'll let you know how that works.
Greetings
-
Wednesday, November 28, 2007 12:18 PM
Thanks Khan,
will try your suggestion, it's a real shame that MS had to make it all so complicated to start with, anyone would think they didn't want us to use this service!
-
Wednesday, November 28, 2007 12:26 PM
hey Ninja
I am sure they didn't make it complicated on purpose. Maybe they push those develops too hard for fast results and developers never get the time to automate things for us users
But again, I would be shouting "Big Issue!! Big Issue!!" in the local high street if everyone could do what we "techies" do
Goodluck and hope it works for ya
-
Wednesday, November 28, 2007 12:43 PM
Haven't had time to do it this week, but I will let you know how things go. I have re-installed the RIS server and got that running all nice and sweet so no problem there.
My only moan is that MS should have released WDS ready to use, I know we Techs do all the donky work and stuff that no one see's, and that's how it should be, but like most of the guy's here, we struggled with RIS all those years ago, WDS should have been better in that regards.....
It's still new really, I'm sure MS will improve it in a future SP or something.......
-
Wednesday, December 05, 2007 4:22 AM
Abdul Mueed wrote: What do I need
---------------------
I want to install Window xp remotly and i need pxeboot.com (either x86 or x64) file but still i could not get, if anyone is here who can solve my this problem and tell me step by step that how can i get these bootable file for WDS.
I will be higly thankful the person.
When you add the first boot image to the server, the boot files are extracted for this architecture from this image and added to the server. My guess is that you haven't yet added a boot image to your server, or have added an image for a different architecture then your clients report themselves as. -
Wednesday, December 05, 2007 4:35 AM
mjhummer wrote: 1) The Reference computer has these drivers installed and works just fine prior to the sysprep
2) I remember encountering something similar with RIS and just had to "put" the drivers in a certain directory but that was for booting with RIS.
3) I am trying to have the new images joined to a domain and have created the unattended install file with setupmgr.exe
4) is there a place that I need to copy the drivers to other than just in the "reference computer" like somewhere in the image dir on the WDS Server?
Basically, you're looking for what's called a "configuration set" in most of the WDS and setup related documentation. Chapter 7 of the WDS whitepaper briefly touches on configuration sets, but you'll really want to read up in the WAIK "Walkthrough: Build a Configuration Set", which can be downloaded here: http://go.microsoft.com/fwlink/?LinkID=53552. -
Wednesday, December 05, 2007 4:38 AM
Ninja_Prime wrote: Haven't had time to do it this week, but I will let you know how things go. I have re-installed the RIS server and got that running all nice and sweet so no problem there.
My only moan is that MS should have released WDS ready to use, I know we Techs do all the donky work and stuff that no one see's, and that's how it should be, but like most of the guy's here, we struggled with RIS all those years ago, WDS should have been better in that regards.....
It's still new really, I'm sure MS will improve it in a future SP or something.......
What would you have liked to see done differently? Have you tried using any of the Longhorn versions of WDS? -
Wednesday, December 05, 2007 4:44 AM
Tous wrote: I have had a problem with images showing up after I captured them.
If you computer supports Hyperthreading:
Turning hyperthreading on sometimes makes the image on the list show up, or the other way around. At times I have to turn hypertheading off after I have created an image.
You're running into HAL (Hardware Abstraction Layer) image filtering. The WDS client UI will only display images that match the HAL type of the computer that it's running on. By enabling hyperthreading, you've most likely gone from "ACPI Uniprocessor PC" to "ACPI Multiprocessor PC". You'll need to create your reference image from the same HAL type as the computers you wish to deploy to for pre-Vista Windows.
See this for more information on Windows HAL types: http://support.microsoft.com/kb/309283
-
Thursday, December 06, 2007 6:11 PM
hey back again
we got it all working except the partitionating part.
we are using a xml file for WinPE
all we have to do is: login and select image..
the problem is that we have 1 big disk at the moment.
what i want is:
Format the whole disk,
partitionate in 2 parts.
Part 1: 20gb --> WindowsXP
Part 2: ??gb --> Data (the rest of the disk.)
has anybody a working code for that in the xml file ?
we've been trying thousends of differend combinations, but all we get are errors at the start of WinPe
greetz.
-
Thursday, December 06, 2007 8:29 PM
ohjeah, we have also been trying to skip the keyboard settings part but were not succesfull in that.
we could skip it if we dit the login part automaticly but we must log in for security reasons.
-
Friday, January 11, 2008 1:31 PM
We have it all working like we want it
next question: "is there a program or something (freeware?) that can be used to "ris" a whole selection of pc's?"
at the moment we got 2 differend classrooms but we don't want to log on every pc to activate the wds installation.
but we want something to automate that.
-
Friday, January 11, 2008 2:59 PM
Never got round to using any of the Longhorn versions, Only just started using WDS for the first time. Once I get it up and running, which no doubt I will, I will see how easy it is to use. If I get problems I will be posting very soon. I have been asked to get a working WDS server up and running soon.
Aaron, I found the instructions confusing, maybe it was me, but I had to read it a few times to make sure that I understood it, and even then I had to search the web before I could make sense of it.
-
Friday, January 11, 2008 8:16 PM
if there a lot request for a step by step guide for WDS + Windows XP incl. sp2
i made one for my company in Dutch, but i can translate it into english if alot of people want it.
but does anyone have a idea about starting the RIS/WDS installation on alot of machine at once with some kind of program or something like that ?
-
Sunday, January 13, 2008 6:38 PMHi
I gor all those steps BUT when I PXE boot the ref PC I get the welcome screen and hit next, then I should choose the volume to capture, the name and the description. Well there are NO volumes to capture in the manu!
Any suggestions? -
Sunday, January 13, 2008 6:43 PM
Khan531302 wrote: Hi Martjah
Try capturiing boot.wim from a Vista DVD. For some reason WAIK boot.wim is not fully operational as boot.wim from Vista is.
so try the following steps:
1. Configur WDS
2. add boot.wim from Vista dvd
3. create capture image with boot.wim
4. install xp on a computer
5. create an answer file for sysprep with setupmgr.exe from XP CD\Support\ folder
6. save sysprep.inf (answerfil) to c:\sysprep\ folder on ref PC and sysprep that pc
7. pxe boot ref PC and try to capture the image.
See how you get on with those steps. Post back if you get stuck.
Hi
I gor all those steps BUT when I PXE boot the ref PC I get the welcome screen and hit next, then I should choose the volume to capture, the name and the description. Well there are NO volumes to capture in the manu!
Any suggestions? -
Sunday, January 13, 2008 9:32 PM
you have to use sysprep first, then you will see the partition. -
Saturday, January 19, 2008 11:30 AMHi Martjah
Do you have an english translation of your setup guide for distribution? I'd even appreciate the Dutch Version, as I'm Afrikaans speaking, and therefore will understand the Dutch version I'd assist in the translation if you wish?
Regards,
Marthinus Bester -
Saturday, January 19, 2008 11:44 AM
Hello Martinus,
i'll translate it for you and then send it to you.
send me an e-mail to m a r t j a h AT g m a i l . c o m (against spambots
) and i will reply with the translated version.
greets,
Mart
-
Tuesday, January 22, 2008 6:04 PM
Martjah wrote: Hello Martinus,
i'll translate it for you and then send it to you.
send me an e-mail to m a r t j a h AT g m a i l . c o m (against spambots
greets,
Mart
Hello Martjah,
Good of you to translate a guide. I've sent you an email requesting a copy in English but I thought it proper to post back here with a post saying as much.
Appreciate your effort and I look forward to reading it should you decide to send.
Cheers!!
-=J=-
-
Tuesday, February 05, 2008 6:05 PM
I have read several articles on setting up a boot and capture image WIM file and everyone is basicly the same. I am able to complete all the setup with out any issues, but when I boot to PXE on my Dell 755 the capture image is no where to be found.
I am running WDS in mixed-mode with legacy RIS images which are visable when booting via PXE, just not the capture or boot images that I created. Am I missing something? Please advise.
Thanks,
Niles
-
Tuesday, February 05, 2008 7:47 PM
nilesf67 wrote: I have read several articles on setting up a boot and capture image WIM file and everyone is basicly the same. I am able to complete all the setup with out any issues, but when I boot to PXE on my Dell 755 the capture image is no where to be found.
I am running WDS in mixed-mode with legacy RIS images which are visable when booting via PXE, just not the capture or boot images that I created. Am I missing something? Please advise.
Thanks,
Niles
be more specific plz, it's a little bit vague
if you push F12, what do you see then ?
have you added boot.wim and capture.wim to the boot images in WDS?
-
Sunday, February 10, 2008 1:17 AM
I've put the guide online and also found out how to add drivers.
alot of thanks to John J Penrose for the final translation and reordering the document.
the link: http://www.vkgbijdehand.nl/upload/Martjah/Install_WDS_Server_EN.pdf
-
Monday, February 11, 2008 4:31 PM
I am getting this error anyone knows
"WDS Client: An error occurred while starting networking a mactching network card. Network driver for this Machine to the windows PE image omn the windows deployement service server"
This is on the Dell 755 PC
-
Monday, February 11, 2008 4:36 PM
try google.com or read my guide -
Monday, February 18, 2008 10:31 AM
i made sysprep with windows xp and captured the xp image and uploaded the file to the wds server.
all these steps worked without an error.
but when i tried to deploy the xp i can choose the image, and when i choosed the c
rive and formated it, i get an error.Windows cannot install required files. Make sure all files required for installation are available, and restart the installation
anybody know help?
with kind regards,
sebastian
-
Saturday, February 23, 2008 6:25 PM
I think you should delete your current boot.wim and capture.wim and get a new one from you Vista DVD
Or take it from another Vista DVD.
i googled your problem and i think the error is in one of those files.
-
Monday, April 14, 2008 5:47 PM
A new/updated manual can be downloaded here:
http://vkgbijdehand.nl/upload/Martjah/Installing_and_Configuring_a_Microsoft_WDS_Server_EN.pdf
-
Friday, December 04, 2009 4:19 PMNow install reference computer and sysprep it with the desired paramters.how to? i dont understand this step
-
Monday, March 08, 2010 6:36 PMI changed my domain so this is the new link for the manual
http://martjah.nl/uploads/documenten/WDS/Installing_and_Configuring_a_Microsoft_WDS_Server_EN.pdf
people recommend coffee for computer employees, i like Coca Cola -
Wednesday, April 21, 2010 9:59 PMHas anyone been able to get Windows XP to deploy using Server 2008 and WDS. Including the driver installation? I'm at a point where it's deploying but the drivers are not being installed. http://social.technet.microsoft.com/Forums/en/itprovistadeployment/thread/c727ecfc-db28-4b55-8a94-8b91053088e3 I posted a fresh thread but it seems like everyone that views it does not have any answers. I hope someone here has some pointer for me that I haven't done yet.
-
Sunday, June 13, 2010 12:30 AM
Has anyone been able to get Windows XP to deploy using Server 2008 and WDS. Including the driver installation? I'm at a point where it's deploying but the drivers are not being installed. http://social.technet.microsoft.com/Forums/en/itprovistadeployment/thread/c727ecfc-db28-4b55-8a94-8b91053088e3 I posted a fresh thread but it seems like everyone that views it does not have any answers. I hope someone here has some pointer for me that I haven't done yet.
I have collected some info from various different websites and summerised here; This worked for me & hope it helps...Prepare WDS for Windows XP Imaging
WDS Server must have the full workstation control permission in workstation’s OU. Otherwise the server cannot approve pending devices; (Optional)
1. In Active Directory Users and Computers (dsa.msc) navigate to the OU you assigned as the OU for new clients in the WDS configuration.
2. Right click on the OU and select Delegate Control
3. In the Delegation of Control Wizard, select Next
4. Add the WDS computer account as the selected User or Group and select Next
5. Select Create a Custom Task and then select Next
6. Select Only the following objects and tick Computer Objects
7. Tick the Create Selected Objects tick box and then select Next
8. Select the Write All Properties option and then select Next and complete the wizard.
Configure WDS Server’s property
1. After Installing and configuring the WDS role on the server, right-click the server name – property
2. On PXE Response tab – select Respond to all Client Computers & tick Require administrator approval for known computers (Optional)
3. Configure PXE boot policy as required
4. On Client tab, click enable unattended installation, then add the unattend.xml file such as this;
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<Disk wcm:action="add">
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Type>Primary</Type>
<Extend>true</Extend>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Format>NTFS</Format>
<Label>WinXP</Label>
<Letter>C</Letter>
<Order>1</Order>
<PartitionID>1</PartitionID>
</ModifyPartition>
</ModifyPartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
</Disk>
</DiskConfiguration>
<WindowsDeploymentServices>
<Login>
<Credentials>
<Domain>your domain</Domain>
<Username>domain username</Username>
<Password>password</Password>
</Credentials>
</Login>
<ImageSelection>
<WillShowUI>OnError</WillShowUI>
<InstallImage>
<ImageName>Image Name as displayed in WDS</ImageName>
<ImageGroup>Image Group</ImageGroup>
<FileName>WIM Image Filename</FileName>
</InstallImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
</ImageSelection>
</WindowsDeploymentServices>
</component>
</settings>
</unattend>*Save this filet in the WDS Server’s Image Store Folder (\RemoteInstalls\WdsClientUnattend).
5. Right-Click “Boot Images” on WDS tree – add Boot Image
6. Insert the Windows 7 (x86) disk and select the “boot.wim” from sources folder and name the image
7. Right-Click the “Install Images” – Add Image Group – Give it a name such as Clients
Create a windows PE Disk (Optional)
1. On a Windows AIK installed computer, open cmd and type each command separately;
Cd Program files\windows aik\tools\petools
Copype.cmd <x86 or x64> <desitination> (e.g. copype.cmd x86 c:\winpe_x86)
Copy “c:\program files\windows aik\tools\x86\imagex.exe” c:\winpe_x86\iso
Oscdimg –n –bc:\winpe_x86\etfsboot.com c:\winpe_x86\ISO c:\winpe_x86\winpe_x86.iso
2. Burn the image to a cd-rom
Option A: Capture a XP Master Image using Windows PE disk
1. Create a folder c:\sysprep before moving on to the next
2. Run the setupmgr and copy the Sysprep.inf file, sysprep.exe and setupcl.exe to C:\sysprep folder.
3. Append the following code at the end of the sysprep.inf file:
[Sysprep]
BuildMassStorageSection = Yes
[SysprepMassStorage]
4. run Sysprep –bmsd. This will modify your sysprep.inf and add all of the mass-storage Ids
5. copy your sysprep.inf file off to a share, then run sysprep -reseal -mini -shutdown,
6. Reboot to Windows PE and connect to a UNC share (recommended) using this:
NET USE Y: \\myserver\myshare
/USER:DOMAIN\USER password
7. Now capture the image by using the following:
ImageX /capture C: Y:\NewImage.wim "Title of the image, DO NOT USE special chars"
8. Then shut down the system and Reboot to Windows PE and connect to a UNC share:
NET USE Y: \\myserver\myshare
/USER:DOMAIN\USER password
Option B: Capture a XP Master Image using WDS
Follow the same process as above until process 5
6. Right-click the boot image created earlier – Create capture Image – Capture Name/Destination Location
7. Right-click the “Boot Image” – Add Boot Image – select the destination location specified above – Name/Destination
8. Start a computer with PXE and select the name of the boot image created in 3
9. Follow the wizard
Option A: Applying the image to a PC using Windows PE Disk
1. Boot a new PC from WinPE disk
2. Run Diskpart
Then type each line separately
select disk 0
clean
create partition primary
active
format fs=ntfs quick
assign letter=c
exit diskpart
3. Run bootsect.exe /nt52 z: /force
4. Then apply the image as follows:
ImageX /apply Y:\NewImage.wim 1 C:
5. Reboot (from hard drive)
Option B: Applying the image to a PC using WDS
1. Open WDS
2. Browse and select the newly created Image file (.wim)
3. Start a new PC with PXE and finish imaging
-
Monday, December 27, 2010 9:48 AM
Hello,
I`m getting a strange error "the specified location does not contain a valid sysprepped windows installation." I`m sysprepping a windows xp machine. when i create a capture image the only thin i get is this error, hope you can help me thanks
-
Thursday, July 07, 2011 10:08 AM
This isn't as straightforward as Microsoft claim (or don't claim!)
I created an article on my blog piecing together the whole XP deployment puzzle. If you follow that guide you should be succesful
Installing Windows XP over the network using Windows Deployment Services | Thom's HeadSpace http://bit.ly/o0iYgS
Thom McKiernan (UK) @thommck | thommck.wordpress.com | MCSA | MCTS
.png){kind=spacer}
