djones Posted January 28, 2008 Author Posted January 28, 2008 (edited) Step-by-step guide to using WDS/SYSPREP to deploy hardware independent Windows XP images Ok, a little later than planned but nevermind! It is still a tad rough around the edges but the gist is there. I haven't yet written up the WDSClientUnattend.xml bits yet, the caveats/troubleshooting steps I stumbled upon or the list of reference sites and docs I used but the bulk is there! Edit: WDSClientUnattend.xml section is complete and I'm gradually adding to the troubleshooting section. If you do have a look or even use any bits, please leave some feedback - especially if there are mistakes or parts that don't make sense. Dave. Edited May 25, 2008 by djones
boomam Posted January 30, 2008 Posted January 30, 2008 On our images i just have: XP SP2 All windows updates Ogg codec. ffsshow. Ac3 filter. Currently we have any apps that cant be MSI'd or on a shared drive in them as well, but in future, they're going. Im using the excuse 'for future compatibility'. lol.
Sirbendy Posted January 31, 2008 Posted January 31, 2008 I always start with a fresh XP install every year, install flash/Shockwave/JRE, Realplayer etc, codec pack, PDF reader/writer and all the basics and packages. Then I join it to the domain, install Office 2003 with transforms, AV, Set up outlook and so on. Then I set no swapfile, remove Sys restore points, remove any hibernate file and defunct junk, copy the drivers and sysprep folder over preconfigured. The "Finish" folder goes in and contains a batch file that runs post sysprep to execute regmerges to set swap, cleartype, and run any other "additional" programs off a networked drive that may be needed "between image revisions". Then nip into device manager and set the HAL back to "standard PC" and let it reboot with all that. Then sysprep, boot off PEbuilder and ghost the base image. Hal independance is great..at some point, maybe the LEA will catch up. It's not hard to stick the HAL lines in sysprep to have the machine figure itself out, after all. No WDS servers, no PXE booting...not upto us at this point. We just make do with ghostcaster. Can do an entire suite in an hour or so..good enough.
farmerste Posted February 4, 2008 Posted February 4, 2008 one 'trick' that i have learnt is:- after a fresh install of windows xp and all updates, logon as the hidden administrator account, and set up things how you like them, the main advantage of this is that you can set power settings . sysprep the machine, and the administrator gets copied over the default user. restart the machine, and when it is up and running rename the administrator to admin, this stops the above sysprep problem occuring next time. now setup the local default user profile, but it is already part way done, plus it has had the power settings adjusted how you want them.
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