MDT 2010 Update 1: Scripts Changed

Since MDT 2010 Update 1 was released, I’ve been intending to write a series of blog postings talking about the changes that have been made.  While my intentions were good, I’ve been too busy to really act on them.  So I’m going to force myself to do this one posting, and hope that encourages me to keep going from there…

You’ve already seen the list of new features mentioned in the official announcment, so I thought it would be good to list the scripts that were actually changed in Update 1.  I do intend to talk about why some of those have changed, but that will need to come later – right now, I want to just focus on the list.

So which have changed?  Well, all of them – but that’s only because the build number is embedded in the scripts by our build process, so you’ll see that all of the scripts have been modified so that they say “5.1.1642.1” instead of “5.0.1641.0”.  So let’s look past that and focus on the ones that had real changes:

  • BDD_Welcome_ENU.xml
  • Credentials_ENU.xml
  • DeployWiz_Definition_ENU.xml
  • DeployWiz_Initialization.vbs
  • DeployWiz_Validation.vbs
  • LiteTouch.vbs
  • LiteTouch.wsf
  • LTIApply.wsf
  • LTICleanup.wsf
  • LTICopyScripts.wsf
  • LTISuspend.wsf
  • Summary_Definition_ENU.xml
  • Summary_Scripts.vbs
  • Wizard.hta
  • WizUtility.vbs
  • ZTIApplications.wsf
  • ZTIAuthorizeDHCP.wsf
  • ZTIBackup.wsf
  • ZTIBcdUtility.vbs
  • ZTIBde.wsf
  • ZTIConfigFile.vbs
  • ZTIConfigureADDS.wsf
  • ZTICopyLogs.wsf
  • ZTIDataAccess.vbs
  • ZTIDiskpart.wsf
  • ZTIDrivers.wsf
  • ZTIGather.wsf
  • ZTIGather.xml
  • ZTIGroups.wsf
  • ZTINicConfig.wsf
  • ZTINicUtility.vbs
  • ZTIOSRole.wsf
  • ZTIPatches.wsf
  • ZTISCCM.wsf
  • ZTIUserState.wsf
  • ZTIUtility.vbs
  • ZTIValidate.wsf
  • ZTIWindowsUpdate.wsf

OK, so maybe it would have been easier to list the scripts that weren’t changed.  As you can probably tell from the list, the changes were rather widespread, sometimes to fix bugs, sometimes to add enhancements based on your requests, and other times to support new features.  Some of these changes were fairly minor, others were more substantial (more details on the actual changes to come later).  Regardless, if you’ve modified any of the MDT scripts, you’ll want to save a copy of your modifications and then compare them against the new scripts (after upgrading your deployment shares or toolkit file packages) to see how to integrate your changes, or even if they are still needed.

There were also some new script files added (all used by the new UDI scenario):

  • UDIWizard.wsf
  • UDIWizard_Config.xml
  • UDIOffline.xml
  • ZTIConfirmDiskpart.vbs
  • ZTIErrorMsg.wsf
  • OSDStartTime.vbs
  • OSDEndTime.vbs
  • OSDBranding.vbs
  • OSDBranding64.vbs
  • ZTISetBackground.wsf
  • OSD_BaseVariables.vbs
  • OSDLocalAdmins.vbs

Next up:  Exploring the changes made to the MDT task sequence templates.  That can wait for another day.

Comments (4)
  1. You will get a "login failed" message like that when using named pipes and not specifying a "SQLShare" value in CustomSettings.ini; that value is used to first map a drive to the specified server to establish a security context so that the integrated SQL connection can work.


  2. BarryB says:

    Argh after updating to 2010update 1 my MDT 2008 database update script no longer works, yes I forgot to back up 🙁 I have added the ZTIdatabase.vbs to the ZTIGather.wsf, checked my boot disks have ADO, but still no joy, any ideas? It doesn't appear to be passing my credentials :/ This script was taken from Ben Hunters add machine to database and was working OK before.

    ADO error: Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. (Error #-2147217843; Source: Microsoft OLE DB Provider for SQL Server; SQL State: 42000; NativeError: 18456)

  3. BarryB says:

    Thanks for replying Michael, this script worked before the update and already makes 2 calls to the database (Computer / Location) before the custom section runs, I tried adding the SQLServer / Share/ Database and Netlib but all that does is try and do a query then doesn't run my UserExit script. I have searched for ages to resolve this and it is frustrating that it isn't working. I could go down the custom SLQ query route I have seen posted but this method did work OK, prior to 2010 and I have some cusomtisation I want to use in the Custom Wizard.

    Priority= Locations, ComputerSettings, CheckDB, LSettings, LRoles, CSettings, RSettings, Default

    Properties= CheckDatabase, MyCustomProperty


    SQLServer= serverpath










    Below is that start of the script, and it fails to connect using the con_Provider below, am I missing something that has changed sue to the update?

    Function UserExit(sType, sWhen, sDetail, bSkip)

    UserExit = Success

    End Function

    Function CheckDB()

    Dim oRECORDSET, oCONNECTION, strSQL, sMACAddres, oAdapter, oNetworkAdapters, objWMI, strChassis

    con_PROVIDER = "Provider=sqloledb;Data Source=server.domain;Integrated Security=SSPI;Initial Catalog=MDT_2010"

  4. Mark Morrow says:

    I have installed MDT 2010 and I can deploy an image to via Windows 7 CD. When I customize and capture the image

    "Error unable to find setup need to install image \computer name.

    Lite touch failed Return Code, = 21747467259 0x8004005

Comments are closed.

Skip to main content