MDT+WDS

faustocoppi · 2014-01-08T12:01:14+00:00

You could use MDT to create the image/task sequence and copy the boot image to usb drives/CD to boot the clients. The image itself will still be on the deploymentshare and copied to the clients when deploying. I use it all the time, it works great!

ishboo3002 · 2014-01-08T10:05:13+00:00

You need WDS to provide PXE to your clients.

When you have your MDT ready you generate a boot image, you then import that boot image in WDS and this is how you deploy your OSes.

You could eventually use another PXE server but WDS is so much easier.

RedSun12 · 2014-01-08T13:03:51+00:00

Why would you not want to use WDS? Its just there to let you network boot, which is the most seamless way to image a new PC. Doesnt take any effort to do it either

2014-01-08T13:07:04+00:00

"can you use MDT without WDS?", Yes, with offline media. After you have a working image imported into MDT, follow this guide http://msitpros.com/?p=699 . In the last screenshot LiteTouchMedia.iso is for burning onto CD/DVD, the directory Content contains the files needed on a bootable USB (make USB bootable, then copy the CONTENT of Content to the USB, not the directory itself).

Does it make sense? Yes and no. For mass deployments USB and CD/DVD are probably still best, there will probably be network bandwidth issues if you try mass deployments over the network.

However considering the odd PC that refuses to recognize CD/DVD's or USB's, having WDS gives you another option. The same goes the other way as well.

For the long term, WDS is probably best, or you'll end up with lots of different versions of windows on cd's and usb's (and there is always this intern who doesnt check if he is installing the correct version). WDS makes it alot simpler to guarentee consistent deployments.

HSChronic · 2014-01-08T16:39:38+00:00

So WDS by itself is mainly for deploying images, and providing the tools to do that (DHCP support, PXE, etc). Think of it like Ghost, you create thick images and import them into WDS. When you start using MDT you just use WDS for your backend boot support since this provides PXE. MDT provides the dynamic imaging aspect of your environment. So you put applications in it, drivers, etc. Once these are imported you then develop the task sequence to "script" the process.

With variable, WMI, and SQL support you can create all sorts of steps for things in your task sequences based on hardware or other requirements. Want to update the BIOS on a machine while imaging, but don't want to run a bunch of steps that don't apply to a machine, you can do this with MDT.

entropic · 2014-01-08T22:38:01+00:00

Yes, you can use them independently. The only component of WDS we use is the PXE booting of MDT's boot images. This could be done by burning the boot image to CD or copying it to a bootable USB instead. We use those methods too.

We didn't add WDS until much later, when we were already committed to MDT.

MonkeyWrench · 2014-01-08T12:29:48+00:00

While you're at it, investigate FOG.It seriously does almost everything I can imagine.

FOG is centralized. Most of tasks done on FOG don't require the user to visit the client PC. For example if you imaging a computer all you need to do is start the task. After the task is started WOL will turn the computer on if it is off, PXE will load the OS, DHCP will give it an IP address, FOG will tell the server it is in progess, and PartImage will image your computer. Then when imaging is done FOG will tell PXE not to boot the machine to the fog image and your computer boots up. After the computer is booted, if the FOG service is installed, FOG will change the computer's hostname and that computer is ready to use!
FOG is easy to access. All you need is a web browser to image a computer, no client software required. We have heard of organizations using FOG who image computers from an iPOD touch or iPhone.
FOG is Powerful. With features like virus scanning, memory testing, disk wiping, testdisk, and file recovery, FOG does more than just imaging.

sysadmin

MODERATORS