Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

ConfigMgr 2007: The ZTIBde.wsf script from MDT 2010 does not work in x64 Windows OSs


Symptoms

When MDT 2010 is integrated with ConfigMgr 2007 and the ZTIBde.wsf script is attempted to be run in a ConfigMgr 2007 task Sequence via a "Run Command Line" task in an x64 Windows OS, the script will fail. Examining the logs reveals the following errors:

SMSTS.log
About to run command: cmd /c DEFRAG.EXE c:  >> C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\ZTIdefrag.log 2>&1 InstallSoftware
Process completed with exit code 6726 InstallSoftware
Return code from command = 1 InstallSoftware
FAILURE ( 6726 ): 1: Execute cmd /c DEFRAG.EXE c:  >> C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\ZTIdefrag.log 2>&1 InstallSoftware
Command line returned 6726 InstallSoftware

Process completed with exit code 6726 TSManager
!--------------------------------------------------------------------------------------------! TSManager
Failed to run the action: Partition Disk for Bitlocker.
The kernel transaction manager had to abort or forget the transaction because it blocked forward progress. (Error: 00001A46; Source: Windows) TSManager


ZTIBde.log
About to run command: cmd /c DEFRAG.EXE c:  >> C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\ZTIdefrag.log 2>&1 ZTIBde
Return code from command = 1 ZTIBde
FAILURE ( 6726 ): 1: Execute cmd /c DEFRAG.EXE c:  >> C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\ZTIdefrag.log 2>&1 ZTIBde


ZTIDefrag.log
'DEFRAG.EXE' is not recognized as an internal or external command,
operable program or batch file.

↑ Back to the top


Cause

This problem is caused by an error in the ZTIBde.wsf script that causes it not to find Defrag.exe in x64 Windows OSes. Defrag.exe is used by the script to defragment the existing partition before shrinking it to create the partition needed by BitLocker.

↑ Back to the top


Resolution

To resolve the problem, upgrade to MDT 2010 Update 1. The ZTIBde.wsf script has been corrected in MDT 2010 Update 1. If an upgrade to MDT 2010 Update 1 is not possible, theZTIBde.wsf script in MDT 2010 can be corrected using the below steps:

  1. In the ConfigMgr 2007 Admin Console, navigate to the "Computer Management" --> "Software Distribution" --> "Packages" node.

  2. Under the "Packages" node, locate the the MDT 2010 Toolkit Package.

  3. Right click on the MDT 2010 Toolkit Package and choose "Properties".

  4. Click on the "Data Source" tab. Under "Source directory" determine the location of the MDT 2010 Toolkit Package source files.

  5. Click on the "OK" button to close the MDT 2010 Toolkit Package properties window.

  6. Navigate to the directory determined in Step 4 and open the "Scripts" folder.

  7. Make a back  copy of the ZTIBde.wsf file.

  8. Right click on the original ZTIBde.wsf file and choose "Edit". This should open theZTIBde.wsf script in Notepad.exe.

  9. Find the following line in the ZTIBde.wsf script:

    ElseIf oFSO.FileExists(oEnv("SystemRoot") & "\sysnative\ServerManagerCmd.exe") then

    and change it to

    ElseIf oFSO.FileExists(oEnv("SystemRoot") & "\sysnative\defrag.exe") then

  10. Save and close the file in Notepad. When saving the file, make sure that the .txt extension is not added onto the file. The files should maintain the original name ofZTIBde.wsf.

  11. In the ConfigMgr 2007 Admin Console, update the Distribution Points that the MDT 2010 Toolkit Package are on.

↑ Back to the top


Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2254610
Revision : 1
Created on : 1/8/2017
Published on : 11/22/2010
Exists online : False
Views : 110