Partager via

Scripts updated in MDT 2008 Update 1

  • Article

A few people have asked about the script updates that were made in MDT 2008 Update 1.  Here's the quick summary listing all the scripts that were modified in MDT 2008 Update 1 and a very brief description of the changes made to each:

  • DeployWiz_Definition_ENU.xml.   If the deployment type is blank, show the deployment type wizard pane even if directed to skip it.
  • DeployWiz_Initialization.vbs.   Better handle task sequences that reference OSes that no longer exist.  For new computers, filter out task sequences that aren't for the current architecture of Windows PE.  Don't display the application selection pane if there are no "Install Application" steps in the task sequence.
  • DeployWiz_Validation.vbs.   Preserve the preconfigured DeploymentType value while clicking through task sequences.
  • LiteTouch.wsf.   Add hooks for the LTI OEM preloading process.  Send proper "beginning" events to the management pack.
  • LTIApply.wsf.   Set the right image path, pointing to the locally-cached image, when performing multicast Windows Vista or Server 2008 deployments.
  • LTICleanup.wsf.   Changes to support the LTI OEM preloading process.
  • LTISysprep.wsf.   For Windows XP and Server 2003, set the local Administrator password to blank before running sysprep.
  • ZTIBackup.wsf.   When capturing a Windows XP or Server 2003 image, remove the boot folder and bootmgr file so that they don't confuse ConfigMgr 2007 if the image is later used with ConfigMgr.
  • ZTIBcdUtility.vbs.   Fixed a problem when running BCDEDIT on a non-English OS.  (See https://support.microsoft.com/?id=952573.)
  • ZTIDiskpart.wsf.   Changes to support the LTI OEM preloading process (don't repartition and reformat the disk if the deployment point is on it).
  • ZTIDiskUtility.vbs.   Use DiskIndex instead of Index when querying WMI for disk information.
  • ZTIGather.wsf.   Fixed logic for setting SMSDP variable.  Modified computer name assignment logic so that logging and management pack behaviors are more consistent.
  • ZTIGather.xml.   Added OSDComputerName property.  Fixed ADDSUserPassword to be ADDSPassword.
  • ZTIMediaHook.wsf.   Added logic to wait for an advertisement after adding a new unknown computer.
  • ZTIMoveStateStore.wsf.   If the "move" process fails, try to copy the state store directory.
  • ZTISCCM.wsf.   Cache the MDT files package content even in Windows PE, as long as there is a place to put it, to avoid later network access issues.
  • ZTIStorageDrivers.wsf.   Don't do anything when installing an image (only for unattended installs of Windows XP and Server 2003).  Use XCOPY to copy mass storage drivers, removing read-only attributes.  Remove "IDE CD-ROM" entry from unattend.txt that caused problems on non-English OSes.
  • ZTIStorageDriversSysprep.wsf.   Fixed a variety of errors related to the processing of TXTSETUP.OEM files.  Added "hdc"-class drivers to the selection criteria.
  • ZTIUtility.vbs.   Modified the management pack event file creation logic.  Changed the computer name assignment logic to be more consistent, especially during ConfigMgr deployments.  Properly build SQL connection strings when specifying named pipes and a port.
  • ZTIWindowsUpdate.wsf. Add logic to opt in to Microsoft Update.  Restore the original state of the Window Update Agent when done performing updates.

There are also two new scripts:

  • LTIOEM.wsf.   Load a Lite Touch media deployment point onto the hard disk.
  • ZTIOEM.wsf.   Save and restore needed task sequence variables to support the split two-part OEM task sequence templates.

Comments

  • Anonymous
    January 01, 2003
    Thanks again Mike for your reply. That helped tremendously. After playing with it for a while (after my last post, obviously), RSAT is being injected and installed (though not configured). I have discovered that through modifying the ZTIOSRoles.wsf script, I can "add support" for Windows Vista and run OCSetup to enable the various roles/features within RSAT. I'll post my changes to the code back when I have successfully configured RSAT using LTI deployment with MDT.

  • Anonymous
    January 01, 2003
    This is great info Michael, thanks for spending the time to blog the changes. This will come in handy in things to expect after the update is applied.

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    There are no scripts involved with Workbench - it's all compiled code.  It is possible to do this via PowerShell, calling the Microsoft.BDD.ConfigManager methods that perform this task, but this is likely to change in the next version of MDT which would break the PowerShell script. -Michael

  • Anonymous
    January 01, 2003
    Thank you for a nice study I would like to make my few shares

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    Thanks for the info Michael. I would like to create a distribution share automatically. Which script is called when clicking on "Create distribution share directory". Thanks in advance.

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    January 01, 2003
    P.S. To my post above: I guess what I'm really asking is, architecturally speaking, where should certain things be done? I can write a custom section in the ZTIPackages.wsf script to detect whether Roles and Features were requested to be installed and on what OS and install RSAT for Vista if I need to. If I can place these settings in CustomSettings.ini, then ZTIGather.wsf will do a lot of work for me. Then, modifying ZTIOSRoles.wsf can enable me to enable the specific features/roles requested. What we really need for the MDT is good documentation regarding the scripts. What are the methods on oUtility, oEnvironment, oLogging, etc. Yes, you can glean a lot from the scripts, but nothing is as good as documentation. Especially since oUtility is an object that is implemented in a binary Dll (Microsoft.BDD.Utility.dll) for which there is no documentation at all. I hope that this kind of documentation will be added in MDT 2010.

  • Anonymous
    January 01, 2003
    PingBack from http://videoxdrivers.net/2008/10/01/scripts-updated-in-mdt-2008-update-1/

  • Anonymous
    January 01, 2003
    Thank you for the reply. I will hope for and look forward to those changes in MDT 2010.

  • Anonymous
    September 15, 2010
    The comment has been removed