Share via

What is "The Deployment Guys"?

  • Article

"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

  • Anonymous
    January 01, 2003
    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. Thanks, Ben

  • Anonymous
    January 01, 2003
    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. Thanks, Ben

  • Anonymous
    January 01, 2003
    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. Thanks, Ben

  • Anonymous
    January 01, 2003
    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? -Alex

  • Anonymous
    January 01, 2003
    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. Thanks, Ben

  • Anonymous
    January 01, 2003
    Hi Manfred, Unfortunately I don't have an answer for you, maybe you can try posting your question here: http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.deployment.desktop Thanks, Ben

  • Anonymous
    January 01, 2003
    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 time. I'm really frustrated now and don't know, where to search. Only this hardware, only the LTIApply script... everything else works fine. regards Manfred

  • Anonymous
    January 01, 2003
    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? thanks -Charles H.

  • Anonymous
    January 01, 2003
    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. Thanks, Ben

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    February 07, 2008
    The comment has been removed

  • Anonymous
    February 07, 2008
    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. Thanks, Andrea

  • Anonymous
    February 08, 2008
    The comment has been removed

  • Anonymous
    February 12, 2008
    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. \BDDServerNamedistribution$ScriptsLiteTouch.vbs 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. \MicrosoftDeploymentServerNamedistribution$ScriptsLiteTouch.vbs Both servers were created independantly of each other and have different deploy point names.  They do no share any builds. Why does this happen? -thanks

  • Anonymous
    May 28, 2008
    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