WDS for Multiple MSP Clients

[PCgeek215]

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!!

[cluberti]

What specifically are you trying to accomplish (above and beyond deploying images, of course)? You shouldn't really ever need to create an image at all - use the stock WIM off the Windows CD or the flat XP install source and customize with MDT. Knowing more about what you're trying to do should help us get you answers .

[PCgeek215]

What specifically are you trying to accomplish (above and beyond deploying images, of course)? You shouldn't really ever need to create an image at all - use the stock WIM off the Windows CD or the flat XP install source and customize with MDT. Knowing more about what you're trying to do should help us get you answers .

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?

[cluberti]

It is better to use task sequences and answer files rather than create multiple images. It's a bit harder on XP because it takes longer to install a flat-file XP image, but it does give you more flexibility in the end (no 'lock-down' once an image is sysprep'ed, for example). Usually what I do is create a base task sequence that installs all the common software I need (after adding the applications to the applications node in deployment workbench and then hiding them), and put that in a group in the TS. Then, you have to decide if users get to pick and choose software from the wizard, or if you're going to direct this from Task sequence steps (either separate task sequences or WMI or variable queries on each step in a base task sequence).

It can get pretty intricate, but it's not complicated. What exposure or experience level do you have with MDT right now?

[PCgeek215]

It is better to use task sequences and answer files rather than create multiple images. It's a bit harder on XP because it takes longer to install a flat-file XP image, but it does give you more flexibility in the end (no 'lock-down' once an image is sysprep'ed, for example). Usually what I do is create a base task sequence that installs all the common software I need (after adding the applications to the applications node in deployment workbench and then hiding them), and put that in a group in the TS. Then, you have to decide if users get to pick and choose software from the wizard, or if you're going to direct this from Task sequence steps (either separate task sequences or WMI or variable queries on each step in a base task sequence).

It can get pretty intricate, but it's not complicated. What exposure or experience level do you have with MDT right now?

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?

[cluberti]

In MDT, a task sequence is the actual sequencing of deploying the base WIM down to the client, injecting drivers, installing applications, etc. Basically, MDT allows you to do repeatable installations (and capture the result to a WIM to re-deploy, as necessary). There really isn't much need to "customize" a Windows WIM at all when using MDT - the task sequence does that.

[PCgeek215]

In MDT, a task sequence is the actual sequencing of deploying the base WIM down to the client, injecting drivers, installing applications, etc. Basically, MDT allows you to do repeatable installations (and capture the result to a WIM to re-deploy, as necessary). There really isn't much need to "customize" a Windows WIM at all when using MDT - the task sequence does that.

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.

[cluberti]

Yes, you can use the web front end - note it requires you use the database, which may or may not be required depending on your config. Are you planning on letting others edit/update/create task sequences and such? If so, this starts to make more sense. If you plan to have a small number of "creators", then using the deployment workbench is easier.

[Tripredacus]

Microsoft recently released a tool called Express Deployment Tool that I checked out the other day. After going through everything, it turned out to not be of any use to me, since I already have a custom setup that does everything it does. Concerning a "Cloud WDS" is a subject I'm interested in, however I already have a working Cloud WDS model and can't particularly share it because it would be a "business secret." However, this tool from Microsoft may give you some ideas or potentially be just what you are looking for.

The link above does go to MS OEM but it doesn't require you to be logged in to get there. It does say it requires the OPK Tools, but I am wondering if maybe it will work with the WAIK as well. At worst, you may need to have a standard Partner account to log in.

[cluberti]

It requires tools in the OPK that don't exist in the WAIK, so this may be a no-go without an OEM account.