What is "The Deployment Guys"?

"The Deployment Guys" is a blog focused on deployment.

"The Deployment Guys" is a combined effort.


There many different blogs out there with useful deployment information. This is great but it can be difficult to keep track of them all, there must be a better way.

With this in mind we have decided to combine out deployment related blogs into one blog, this blog!

But that is not all.... We have also managed to convince a number of deployment gurus from within Microsoft Services that do not currently have blogs to contribute.  These are guys that have great information to contribute and will really add something to the blog.

So look out for posts from Richard Smith, Daniel Oxley and Ben Hunter as well as a host of others. We have a lot planned.

We have high hopes for this blog hopefully you will find it useful as well.


This post was contributed by Ben Hunter a consultant with Microsoft Services New Zealand.

Comments (16)

  1. Ben Hunter says:

    Hi Charles,

    This is not normal. I would suggest looking at the logs in the minintsmsosdosdlogs folder as this will give you an idea of what is happening.



  2. Ben Hunter says:

    Hi Charles,

    Did you delete the C:MININT folder between each of your tests?

    This folder stores information about the build and if there is a pre-existing MININT folder then "weird" things will happen.



  3. Ben Hunter says:

    Hi Alex,

    We are intending to keep the old blogs in place.

    I think your idea is a good one. I will look at creating a post that is an overview of all the useful posts from our previous blogs.



  4. Anonymous says:

    Hi Ben,

    Thank you for your and your colleagues efforts!

    What about the old blog? There are a lot of useful information there and it would be great to have it under the same roof. Is it possible to migrate it somhow to this new blog or create some kind of KB in this blog based on the information previously posted in old blogs?


  5. Ben Hunter says:

    Hi Andrea,

    You should not need to create more than one image. Remember you only need to setup BitLocker when you apply the image.

    You should be able to use one task sequqnce to deploy an image with or without BitLocker.



  6. Ben Hunter says:

    Hi Manfred,

    Unfortunately I don’t have an answer for you, maybe you can try posting your question here:




  7. Anonymous says:

    Hi Ben and all of you !

    I have a strange situation:

    We deploy our XP clients through windows deployment (WDT & WDS)

    all clients can be rolled out very fast and correct.

    BUT: new hp xw4600 with BC5755 chipset needs over 1 hour to copy the sources from network share to the local disc.

    if i start a second command prompt during WinPE session and manually copy the sources, it works

    fine, very fast. Only the copy procedure from LTIApply.wsf needs that long


    I’m really frustrated now and don’t know, where to search.

    Only this hardware, only the LTIApply script… everything else works fine.



  8. Anonymous says:

    First, I would like to clear up any confusion regarding my previous post for other readers.  Where you see Windows Deployment server, I meant to type: Microsoft Deployement server.

    This error occurred the first time I tried to deploy to a machine that never had BDD, or Microsoft Deployment touch it before. I typed: \MicrosoftDeploymentServerNamedistribution$ScriptsLiteTouch.vbs and it went to the BDD server instead.  Each time a build fails I always delete the C:MININT folder.  I am able to repeat this error every time.  Just curious if you guys heard of anything like this happening?


    -Charles H.

  9. Ben Hunter says:

    Hi Andrea,

    How did you import the image?

    You can easily deploy an image to C: and leave D: intact. To do this you simply need to adjust the ZTiDiskpart.wsf script so that it does not perform the diskpart actions.



  10. Ben Hunter says:

    Hi Andrea,

    Unfortunately I don’t think there are any plans to change the way the KMS server works. Your only real option is to use a MAK key during testing.

    I am not sure if WAIK 1.1 will fix the enumeration error. Also the new version of MDT will simply be an upgrade/patch so it wont blow away your configuration.



  11. andream says:

    Ben- First thanks to all you guys for the deployment help.I’m stuck. After I’ve captured an image with MDT and import it as an OS, when I create a std client task sequence it bombs out with the error "The location does not include a valid Windows image or contains files that cannot be opened with read/write privileges." I’ve tried a few different things but thought you guys are my best chance for pointing me in the right direction.

    Also, I’m with some others out there with pointing users folders to a different partition (which was easily done in XP, and has been great for 5 years) but is it really necessary to do that with Vista? Theoretically can’t you just "re-image" a machine where you don’t specify a wipe disk and preserve data? Any thoughts about that? I can’t tell you how many times I’ve have to re-image just a c partition to get users data that wasn’t backed up.



  12. Andrea says:

    Thanks Ben. The error I was getting was because I captured both the C & D drive, once I removed that I no longer got the message. But then I received a different error because I had the win updates installed in the captured image. Michael Neihaus points to a problem with WAIK for that error.He says "It’s actually a WAIK issue,  See http://blogs.technet.com/mniehaus/archive/2007/11/28/collection-was-modified-enumeration-operation-may-not-execute.aspx for the details."

    I’m trying to keep customizations to a minimum, but want to capture a ref image with apps to keep install time down. My next challenge is doing a bitlocker image. Would I create a ref image, capture that and then in a new task sequence enable Bitlocker, any suggestions?

    One more thing, is there a reference out there for Windows customizations? I can do the sidebar,IIS and games, but I see nothing on Network discovery service. I plan on doing Group Poilies for a lot of stuff, is there a policy for turning that on?

    Oh, and by the way thanks to all you deployment guys. I "am" the deployment team with an already full time job so it’s a challenge for me. I do love the MDT, it’s a great tool. I did everything manually last year to learn all the tools, but Microsoft deployment is great stuff. I’m glad to have the resource.



  13. Andrea says:

    Ben – Can’t I just change the task sequence? I’ll probably do more than one image- notebooks & bitlocker, so I’ll want to partition differently for both. I’ve decided to do away with a d drive but use an alternative method for data backup, either synch or network initiated scheduled backups.



  14. andream says:

    Rightly so, but I’m deploying both Vista Business and Vista Enterprise- My next big question is licensing. I spent a lot of time last year looking into how I can do a pilot group using VL- & KMS. I only have 14 pc’s right now and I’ve only found some ways to push off activation for a period of time using command line options etc. I have a few users that I’ll use the MAK for. Is it possible for Microsoft to consider changing the licensing for Volume Licensing non OEM? How would you recommend that I do a pilot group? My biggest stress about Vista deployment so far.

    I was able to capture an image and deploy it by turning off auto windows updates after the machine re-booted during task sequence, and also disabling the steps in the task sequence. If I install the new WAIK 1.1, will that resolve the enumeration error? Will it blow up anything I’ve already created? On the same line, will the new version of MDT (heard it’s going to be released end of Feb, blow away any of the configurations or files that I have in the distribution point now?



  15. Charles H. says:

    Not sure if this is some kind of bug, but:

    I have a BDD2007 server deploying Vista images.

    I created a new separate server using the latest Windows Deployment Toolkit (Microsoft Deployment).

    On the BDD server, I have multiple custom images.

    On the Windows Deployment server, I have only one custom image.

    Both deployment scenarios are launched from within a client OS (specifically Windows Vista Business).

    If I create a shortcut to the LiteTouch.vbs script on the BDD server and launch it from the client’s PC, I  get a list of all the enabled builds on the BDD server.

    If I create a shortcut to the LiteTouch.vbs script on the Windows Deployment server and launch it from the client’s PC, I get a list the one enabled custom image on the Windows Deployment server.

    Here’s where it gets kind of weird:

    If I use the command prompt on the client’s PC to launch the LiteTouch.vbs script on BDD server I get a list of all the enabled builds on the BDD server.


    If I use the command prompt on the client’s PC to launch the LiteTouch.vbs script on the Windows Deployment server, I get a list of all the enabled builds on the BDD server, not the Microsoft Deployment server.


    Both servers were created independantly of each other and have different deploy point names.  They do no share any builds.

    Why does this happen?


  16. Bri says:

    Hi Manfred,

    I have the same problem with the hp xw4600.

    Did you managed to solve the problem?

    If so, how did you solve it?

    Thanks in advance

Skip to main content