What is "The Deployment Guys"?

re: What is "The Deployment Guys"?

Bri — Wed, 28 May 2008 13:39:22 GMT

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

re: What is "The Deployment Guys"?

Ben Hunter — Wed, 20 Feb 2008 10:54:08 GMT

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

re: What is "The Deployment Guys"?

manfred.czujan@frequentis.com — Mon, 18 Feb 2008 19:40:34 GMT

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

re: What is "The Deployment Guys"?

Ben Hunter — Thu, 14 Feb 2008 01:23:06 GMT

Hi Charles,

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

Thanks,

Ben

re: What is "The Deployment Guys"?

bddinstaller — Wed, 13 Feb 2008 15:11:52 GMT

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: \\MicrosoftDeploymentServerName\distribution$\Scripts\LiteTouch.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.

re: What is "The Deployment Guys"?

Ben Hunter — Wed, 13 Feb 2008 10:32:25 GMT

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

re: What is "The Deployment Guys"?

Charles H. — Tue, 12 Feb 2008 19:27:36 GMT

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.

\\BDDServerName\distribution$\Scripts\LiteTouch.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.

\\MicrosoftDeploymentServerName\distribution$\Scripts\LiteTouch.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

re: What is "The Deployment Guys"?

Ben Hunter — Mon, 11 Feb 2008 02:32:11 GMT

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.

Thanks,

Ben

re: What is "The Deployment Guys"?

AndreaM — Fri, 08 Feb 2008 15:51:35 GMT

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?

Thanks,

Andrea

re: What is "The Deployment Guys"?

Ben Hunter — Fri, 08 Feb 2008 11:16:48 GMT

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