I had to use two different kernels to cover about 25 types of PC with FOG, with WDS there was one batch of particularly shoddy PCs that would crash in WinPE and when it doesn't work you don't have any options. WDS + MDT will do a lot of the hard work with Windows 7 Sysprep though, and also do dynamic driver injection. Someone recently posted some code on the FOG forum to do something similar with drivers but the Windows side will be more fiddly with FOG as you'll have to manage your own Sysprep process.
I would read up on Windows 7 Sysprep and decide from there if you want to manage this yourself or get some tools to help you out.
Fog driver setup is pretty simple - nearly all drivers can be installed using silent installers via the snap-ins capability of Fog. If they don't have a silent install for a particular driver, you can create your own with the driver inf file and related files, and a script calling dpinst.exe.
Takes a couple of minutes to do the latter, seconds to do the prior.
you can fire out fat images with all your software preinstalled with mdt/wds it just required an extra step or 2 (bacically the same as creating any image) install on test pc setup how you want, if using wds only sysprep and pull to server as a deploy image if using mdt use the scripts in \\server\deploymentshare$ and pull that image to the server and create a task that fires the image back out and injects drivers on new pcs as needed. Fat images are really no harder in mdt/wds than say ghost
is there an idiot gudie that i can follow for WDS please? im slowly trying to get my head around it. but not really working..
http://www.edugeek.net/forums/o-s-de...ete-guide.html which is very useful .. :)
Thanks for that.
Also we are running Vlans. The server on a different address than the client. Is ther some i need to change in DCHP on each server??
How do the clients normally get their IP addresses? As it should work pretty much the same way, just making sure that your listen on / don't listen on the relevant ports .. however, I've never done it that way, so I'm just theorising here .. :)
They get them all by DHCP. Is there not something i need to put in the server options of DHCP?
sted said, if they're on the same box set the options, if not, don't.
I have my DHCP and WDS on separate servers (the WDS runs on our old "retired" server so that I can work on it, reboot it, to my hearts content when trouble shooting for it whilst the other 2 servers look after the network as is) and it works fine. I guess all should be the same for yours. My advice, set it all up and see if you can get it PXE Booting. If not, start troubleshooting from there.
Ok. im getting somewhere now.
If i plug a laptop in to the network from the same subnet it works.
But get this error when i try to allow it.
"the name provided is not a properly formed account name"
Just need to work all the silly stuff out now.
I would go with WDS, If you use multiple vlans you need to add the helpers to DHCP options 66 the host name of your deployment server and 67 points to the correct file location for example boot\x86\wdsnbp.com
The main issue with WDS are getting the correct nic driver for the boot image(basic windows 7 setup). also people get confused that you need a boot image for x64 and 32bit depending on what hardware version you are deploying but you import this off your windows 7 disks into WDS as the boot image is just the basic windows 7 install off the windows 7 disk with the drivers injected into it. The drivers then need injecting into the boot image. (The driver cache for windows 7 is pretty good and will find a lot of hardware)
The most successful image creation is done if you boot the PC that you want to use as your master image into WinPE from a WinPE dvd and then use the built in imagex to create the wim. (This can take a while)
imagex /capture D: D:\Win7ULT.wim "windows 7 ultimate x64"
(Sometimes windows PE will use a different drive letter i.e. c or d so if the imagex command is not recognised change drive letter)
Then import the wim file you have just created into WDS for deployment (install images)right click in WDS on the install images folder install and point it at the wim file to import
This method works every time as long as you have the correct drivers in the boot image on the WDS server.
If you get a batch of new PCs in you can simply add the new drives to the boot image in WDS and deploy your standard image no messing creating another image etc
If you deploy a KMS server on site that will register you windows 7 clients and office 2010 (if you do the separate install to enable the office registration)
Once its setup correctly you basically just press f12 f12 and select your image and walk away. You could easily deploy a school with 700 PC's with a new image in a week as long as your backbone is quick enough.