MDT2010 – Moving Deployment Share from One Machine to Another – Important Aspects

This week I was finally ready to move my MDT 2010 Deployment Share from my virtual machine to my physical machine.

After some readiness and asked some Microsoft people the main idea passed was that MDT 2010 was designed to make possible to move de Deployment Share to another machine by just doing a Copy-Paste action.

Well…this is almost true.

But…like almost everything in life, this is not that linear.

From my experience after move and add the Deployment Share to the new machine there are always 2 action you need to take:

:: 1 ::

You’ll need to open you’re bootstrap.ini file (\\DeploymentShare$\Control\Bootstrap.ini) and change the DeployRoot entry
(Ex.: DeployRoot=\\OLDMACHINE\DeploymentShare$ | DeployRoot=\\NEWMACHINE\DeploymentShare$)

 

:: 2 ::

You’ll also need to change the Deployment Share Properties:

The field Network (UNC) Path needs to be changed

Microsoft Deployment Toolkit (MDT) 2010 Beta 2 Webcast

Fresh news from the MDT 2010!

Michael Niehaus recorded a new webcast for the MDT 2010 Beta 2.

The link for the webcast is this one:

http://msevents.microsoft.com/CUI/InviteOnly.aspx?EventID=3A-78-05-A7-61-B7-4B-2B-08-41-98-B1-8C-3B-92-B4&Culture=en-US

You’ll need to register first before download it.

I’ve not seen it yet, so please feel free to give some feedback about it.

Reducing installation time after image deployment and sysprep

Those of you that experienced Windows XP deployment may notice, now with Windows Vista, that after sysprep and image deployment, the consumed time it’s a little higher than before.

These happens mainly for 2 reasons:
- First, because the new Vista Deployment is file based and not volume based (like for example Ghost) and it takes a little more time to decompress the WIM file, specialy if you’ve set the compression to high when creating the WIM.

- Second, because after the sysprep (OOBE) one of the actions on Windows Vista setup, is the collect of system assessment information using the Windows System Assessment Tool (WinSAT) mainly for rating the machine and select the best appearance for the operation system.
The assessment is made during the reference image creation, but Sysprep cleans this information.

This pass, can be “suppressed” specialy if you have an hardware controlled environment and don’t need Windows to check what to use.

Microsoft has made available an hotfix to avoid this behavior, and preserve the WINSAT information collected before the sysprep process.

More information about this hotfix can be found here:
http://support.microsoft.com/kb/958011

To apply this hotfix:

Tools Needed:
- KB958011 (download it through the website mentioned above)
- GimageX (optional) – this is a freeware tool and a GUI for Microsoft imageX to mount/unmount WIM files. You can download it at AutoIt Website

Steps:
- Mount your Windows Vista WIM
   (to c:\mount for example)

- Expand the KB958011 to a temp directory
  (ex.: expand Windows6.0-KB958011-x86.msu –f:* c:\temp)

- Apply KB958011 offline to the mounted Windows Vista directory
   (ex.: start /wait pkgmgr /n:c:\temp\Windows6.0-KB958011-x86.xml /o:”c:\;c:\mount\windows” /s:c:\sandbox)

- Wait a little so the hotfix is applied…

- Unmount (commit changes) the WIM file.

- Launch MS Workbench and edit your unattend.xml file

- After Windows SIM opens, reload your WIM file (on the left bellow pane)

- Again on the Windows Image pane, you’ll find a new component called Microsoft-Windows-Sysprep-SpWinSAT.

- Right-click on this new component and had it to Generalize pass.

- Change the PreserveWinSATData flag to True.

- Add a RunSynchronousCommand pass with the following command line:
winsat.exe moobe formal

- Save it all.

- Done.

In my particular case, this changes made me get less 11 minuts of Windows installation.

Hope this help you too.

Caution: MDT 2008 Update 1 may cause some damage

Sometimes having lots and lots of work in hands can be very useful (ok, not too many times…) but in this particulary case it does!

It seems like Microsoft Deployment Kit (MDT) team has received a lot of issues over the past few days because of the Update 1 for MDT 2008.

It seems like some deployment point and settings may disappear after this update.
The MDT team has posted some info about it, and the best way to apply this update.

So please follow this link for a step-by-step on upgrading MDT:
http://blogs.technet.com/msdeployment/archive/2008/08/05/how-to-upgrade-to-mdt-2008-update-1-lite-touch.aspx