plexer Posted December 22, 2009 Posted December 22, 2009 I am bashing my head against a wall here. Pentium D celeron machines in our ict suites. I do a fresh install of XP SP3 fully patch it, sysprep it, capture it with wds. Boot the machine next to it and choose to deploy from the wds menu, tell it I'm in the UK then I get "no images available" I'm thinking that maybe windows setup isn't installing the correct hal and that wds does detect the correct hal and decide no images are available. I've just installed MDT 2010 on the WDS server as well but can't find a good guide for deploying XP using it. Help!!! Ben
plexer Posted January 5, 2010 Author Posted January 5, 2010 Grr I've been fighting for days with this. I have now modified my setup so that my wds server gives out a pxelinux menu which allows me to boot into other deployment tools and diagnostic stuff as well as still being able to boot into wds and choose wim images. I captured a drive using ghost and still had trouble deploying it to the hardware and whilst there maybe some issue with the hardware it's a pain. I also want to be able to boot a boot.wim image and then have it kick of a xp sp3 install from a network share so that it can be used when creating reference images etc... Ben
plexer Posted January 5, 2010 Author Posted January 5, 2010 I'm going to be reduced to cloning physical hard drvies side by side soon. Ben
pritchardavid Posted January 5, 2010 Posted January 5, 2010 Right what hal is showing in the WDS console? If you don't now how to find that out - Right hand click your image, your trying to use and click properties Also have you tried updating your boot images? We use the newest boot image from the windows 7 disc, that may help you, give that a try Had a lot of experience with deployment, so i reckon we can get this working together 1
plexer Posted January 5, 2010 Author Posted January 5, 2010 I'll check on the hal tomorrow and look into obtaining a win 7 disk to try those images. I'm also going to try using my original boot media rather than my version thats been stuffed with drivers etc.. Ben
pritchardavid Posted January 5, 2010 Posted January 5, 2010 It would be best has I said to use the windows 7 one Seems to have more drivers in it, so less chance you have problems with not having Ethernet drivers for your Ethernet card Havent had a problems with ethernet drivers, since I updated/changed it to that
plexer Posted January 5, 2010 Author Posted January 5, 2010 Ok will try it not had issues with adding drivers into the vista one tbh. Can I get mdt to base it's litetouch pe image on the win 7 boot image?
pritchardavid Posted January 5, 2010 Posted January 5, 2010 mdt2010 is based off that version I believe, its the same build number
plexer Posted January 6, 2010 Author Posted January 6, 2010 Ok the HAL type for my image that won't deploy is acpipic_up as is the HAL that's on the machines in the room. Ben
strawberry Posted January 6, 2010 Posted January 6, 2010 mdt will pickup its pe from whatever is installed, if you have a version of 7 imported to it then it will use that. 1
plexer Posted January 6, 2010 Author Posted January 6, 2010 Ok just to move this tale on a bit further. I successfully used MDT 2010 to install XP SP2 using my original install media as the source onto one of my NEC's which has had a new motherboard installed. Ok great I figured maybe it's something with the older motherboards that isn't quite right. I then took my SP2 media and slipstreamed just SP3 into no updates or anything esle and deployed this via MDT to a laptop we needed to reinstall on. All went well. I thought I'd try another NEC with an older motherboard in it just in case it was the 2 I had been trying on earlier and it deployed XP SP3 to it fine. Ben
plexer Posted January 6, 2010 Author Posted January 6, 2010 Well it's working so far on these machines lets wait until I roll it out to the rest of the rooms Ben
strawberry Posted January 6, 2010 Posted January 6, 2010 if you need any help setting up the programs to deploy with xp let me know.
little_alien Posted January 25, 2010 Posted January 25, 2010 ive been using a HAL independant image for a while now by putting the following in the [unatended ] section UpdateUPHal=ACPIAPIC_UP, %windir%\inf\hal.inf and then the drivers installed using oemPreinstall="Yes" OemPnPDriversPath="....." how that helps
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