Reaper Posted January 8, 2009 Posted January 8, 2009 So you have your images on ServerA and WDS on ServerB? Or is the Images folder just a Network Share?
DrPerceptron Posted January 8, 2009 Posted January 8, 2009 It's a virtualised WDS box now and there's not a lot of space left in the disk groups... but the SAN we have has plenty of space... Just wondered whether it's feasible to use that space easily? EDIT: Seems WDS does not let you do it without looking at iSCSI...
Reaper Posted January 8, 2009 Posted January 8, 2009 When you add an image to WDS it copies it into it's internal folder structure and that can't be changed (as far as I know). Also (and this is just observation I haven't read anything to back this up) WDS seems to adjust the image into different files and if you have two images that are near identical, it takes all the identical stuff and merges that into one file and will then create separate files for each image based on the differences. If you look in your images folder on WDS it has a big file called Res.RWM and then smaller files with the image name e.g. OctImage01.wim Please correct me if I'm wrong on any of this.
TheFopp Posted January 9, 2009 Posted January 9, 2009 I've hit a snag with injecting network drivers into my XP Deployment image. I've successfully icaptured HP dc5700 and dc5800 desktops (and had to do the shift f10 thing to install vista network drivers to do the capture of the 5800) and the images works fine and can be rolled out OK. Trying to do a HP 6730s laptop today. I've captured the image fine (again having to supply vista drivers prior to the capture so it could talk to the WDS server), but now when trying to deploy its failing to connect to the WDS at the point I should be choosing my image saying that it doesn't have the vista drivers in the PE Image. So on the WDS I've mounted the .wim (exported from the WDS) using ImageX imagex /mountrw d:\Temp\boot.wim 2 d:\Temp\Mount which is fine but when I try to inject the drivers peimg /inf=d:\Temp\Driver\*.inf /image=d:\Temp\Mount I'm getting the error "the image directory specified is not a valid windows pe image" WDS is running on Server 2003 SP2 with WAIK 6000.16386.061101-2205-LRMAIK_EN installed. Any help would appreciated as I could really do with getting this working..... or at least understanding why its not working! Cheers in advance.
Reaper Posted January 10, 2009 Posted January 10, 2009 imagex /mountrw d:\Temp\boot.wim 2 d:\Temp\Mount which is fine but when I try to inject the drivers peimg /inf=d:\Temp\Driver\*.inf /image=d:\Temp\Mount have you tried doing it without /image=d:? From the instructions I have seen the command peimg /inf=d:\temp\Driver\*.inf Temp\Mount Should do it as you have already specified where the image is mounted to in WinPE
TheFopp Posted January 12, 2009 Posted January 12, 2009 have you tried doing it without /image=d:? From the instructions I have seen the command peimg /inf=d:\temp\Driver\*.inf Temp\Mount Should do it as you have already specified where the image is mounted to in WinPE Still get the same error I'm afraid..... why can't Microsoft make this a simple thing to do i.e. Open up WDS right-click on image and choose Inject Drivers! Anymore help would be appreciated.
TheFopp Posted January 13, 2009 Posted January 13, 2009 Now tried to do this on my XP SP3 machine instead of my Server 2003 SP2. Now when I get to the peimg /inf=d:\temp\driver\*.inf /image=d:\Temp\Mount stage, I get the message: Installing INF package: c:\temp\driver\yk51x86.inf quickly followed by PEIMG failed to complete the operation with status code 0x800703fb Any other thoughts anyone.... I'm really starting to get cheesed off with this!
TheFopp Posted January 14, 2009 Posted January 14, 2009 Solved it By running the WAIK on a Vista Virtual PC rather than on XP or server 2003.
Reaper Posted January 14, 2009 Posted January 14, 2009 Well that's a royal pain in the ..... Well done on finding a solution
TheFopp Posted January 14, 2009 Posted January 14, 2009 Well that's a royal pain in the ..... Well done on finding a solution You're telling me... especially when Virtual PC and VMWare server both refused to read the Vista Business DVD. Had to install XP then upgrade to Vista... even then it would only work if I captured the ISO image for Vista rather than read it off the DVD.... Oh well, at least I now have a way of actually injecting drivers.
tmcd35 Posted February 3, 2009 Posted February 3, 2009 I was PM'd by another Edugeeker asking for a basic setup guide to WDS. I've put together an entry on the Edugeek Wiki which glosses over the basics as far as I can work out... Windows Deployment Services Setup 3
browolf Posted February 3, 2009 Posted February 3, 2009 I was PM'd by another Edugeeker asking for a basic setup guide to WDS. I've put together an entry on the Edugeek Wiki which glosses over the basics as far as I can work out... Windows Deployment Services Setup You can get boot.wim from the trial version of vista too!
DrCheese Posted February 17, 2009 Posted February 17, 2009 Has anyone managed to deploy an XP client without needing to put a domain join account and password information in the sysprep.inf? RIS never needed this information before so I'm a lil confused why it now wants it. I don't feel great about putting in it a plaintext file, nor do I really want to have to create another account just for domain joining. It seems a bit backwards to me.
TheFopp Posted February 17, 2009 Posted February 17, 2009 Ok.... I think I'm being a bit thick but lets see! I'm setting up WDS to push out an XP image. Have successfully imaged a PC using the WDS capture and can successfully push out on to the same and similar hardware using the WDS boot image. Have successfully used ImageX and PEIMG to inject NIC drivers to the Boot.WIM. Would now like to inject drivers into the actual XP image so that I can use the same image a number of PCs with differing chipsets (but all intel based). Can mount the image fine using ImageX but when I try to inject drivers into this image I get : The image directory specified is not a valid Windows PE image. PEIMG failed to complete the operation with status cod 0x8007000d Now, I guess that I should be able inject drivers into the main XP image not just the Boot.WIM, or am I wrong? I suppose the XP image captured using the WDS capture isn't really a Windows Pre-Environment image so is perhaps I shouldn't be using PEIMG for this. Or SHould just be pushing all drivers for all the hardware into the Boot.WIM not the main XP image?
akc3448 Posted February 20, 2009 Posted February 20, 2009 Hello , Looks like you have deployed images to few machines.I'm just a beginner and trying to get to know more about WDS .I'm stuck at WDScapture.exe.Appreciate ur help Sorry to dig up this thread, has anyone got any ideas how to add a network driver to the windows PE environment? I've sucessfully used WDS to image windows XP on a few types of machine, but I've one type of IBM machine that gives me an error 'can't communicate with the WDS server' whenever I boot it up in the image capturing mode. The only reason I can come up with is that it doesn't have the correct network drivers loaded. I've trawled the net, but information is sketchy and not very clear when it is there. Any help apprecicated Cheers, Mike.
Reaper Posted May 27, 2009 Posted May 27, 2009 Anyone else had problems getting custom drivers to install? Any tips I've missed out on?
Reaper Posted June 4, 2009 Posted June 4, 2009 Bit of an update, I have managed to get the driver installation to work (Thank something) except for the RealTek High Definition Audio driver. Does anyone have any experience in deployed an image with this driver?
loucoll-Dave Posted June 8, 2009 Posted June 8, 2009 Guys i hope you can help me because i'm going to go mad and throw this machine out the window soon......right we have wds on server 2008 32bit...gx520 745 755 images boot fine, cant fault it. my boss goes to me about 4 hours ago can you do a image for the GX270's i said your having a laugh right, he goes do i look like i'm joking...so i shut up...... I have tried the drivers on the intel site i think its the E1000325......i have injected the driver but when i get past the username password part i find no images....can anyone throw any light onto this or is it going out the window :-) cheers in advance
somabc Posted June 8, 2009 Posted June 8, 2009 Can you use RIS and WDS? What I mean is initially you see the RIS login screen, then there is the RIS menu one of the options takes you to the WDS menu. This way you can install XP with RIS and Vista with WDS. If you see what I mean?
loucoll-Dave Posted June 8, 2009 Posted June 8, 2009 we are deploying xp with wds......reason being my boss refuses now to pay the 5k licence for ghost
pete Posted July 24, 2009 Posted July 24, 2009 Anyone done a 2003 > 2008 upgrade on a WDS box? (I'm after the improved driver functionality). Microsoft hints that it's better to do a clean install / migrate the services than an upgrade.
powdarrmonkey Posted July 24, 2009 Posted July 24, 2009 I did an upgrade this week, and it's fine. One caveat: if you have legacy images that show up as RISETUP (not RIPREP), you must convert them first or you won't be able to later. Do it by pulling them down to a machine and then immediately capturing them again as boot images. This caused us problems with some Ghost auto-images. 1
flaviorodrigues Posted August 5, 2009 Posted August 5, 2009 Hi, i have a windows xp image, and i like to integrate some drivers, but i get C:\Windows\system32>peimg /inf="H:\Pcs sala 5\outros drivers\Audio\WDM\HDXCPC.in f" /image=d:\Mount Preinstallation Environment Image Setup Tool for Windows Copyright © Microsoft Corporation. All rights reserved. The image directory specified is not a valid Windows PE image. PEIMG failed to complete the operation with status code 0x8007000d. what can i need to do?
powdarrmonkey Posted August 5, 2009 Posted August 5, 2009 peimg is for integrating drivers into boot images, not install images. Use imagex and sysprep, there are plenty of guides around for them. 1
flaviorodrigues Posted August 5, 2009 Posted August 5, 2009 peimg is for integrating drivers into boot images, not install images. Use imagex and sysprep, there are plenty of guides around for them.can you give me any tutorial so i can see how this works? thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now