PCgeek215

Yeah, I was coming to that conclusion myself. I'm now pretty sure that Task Sequences using Zero Touch and MDT 2010 is the way to go. I'm pretty sure that during PXE boot, the user gets a prompt to use a specific task sequence. All I need to do is to setup task sequences for the various configurations I require. I've also come across this: http://mdtwebfrontend.codeplex.com/ which looks like a promising solution to MSTSCing into the MDT server when ever a change is required.

I dont have very much exposure to WDS / MDT at all at this point in time. That is why I'm doing some R&D into it. How do task sequences fit into the deployment procedure. I know I can do this with several images / wim install files but how are the customisations done on these installs? I know in can use answer files to set the language and disable the firewall and other setting required by all clients but how do sequence task sequences get associated with a deployment?

What I am basically asking if... How do I use WDS to deploy images to different clients from within the one environment. Some of the per-client customisations I would like to have: Insert the VLK product key for windows Office 20xx and a VLK Key Other apps needed by the client (such as citrix NN etc.) Set the Local Admin Password Install a monitoring Agent. All these things change from client to client, what is the best way of doing using the one installation of WDS? Are answer and MDT the answer?

Hi All! I currently work for a managed service provider. We manage the IT needs for roughly 20 clients with over 2000 workstations at over 90 sites. We currently build and re-build each workstation by hand when it is required (following a procedure of course). I am now looking into a WDS solution that would basically automate the solution up to the point of naming the workstation and sending it out to site. I plan to setup a build environment (domain outside our production environment) with a server running all the services (AD, DHCP, DNS, WDS, WSUS, MDT, MAIK etc) neeeded for an automated build. We mainly use HP workstations so these will be the only ones I will load drivers for initally. Out of the box drivers for 90% of the time and MDT the other troublesome drivers based on the System Model filters. The problem I am coming up with is applying the customisation for each client without generating an image for each of them... I plan to have three standard, localised images for Win XP x86, Win 7 x86 and Win 7 x64. The only way I have come up with thus far is to create 20 (x3) answer files for the three OSs, one for each client. These answer files will install the correct VLK OS key, the correct version of office and the VLK Key for that and any other customisations required such as local admin password, desktop icons, register a DLL file needed etc. The only down-side to this approach is the need to MSTSC into the server before each depployment (even one workstation) and to set the asnwer file for an image. It also means I can't deploy Win 7 x86 to two different clients at once because they will use different answer files. Without putting a WDS server on each site (90 sites... come'on...) what would be the best way (other than the above) to approach this? Your expertise and advice is greatly appreciated!!