Description of the update rollup for the Solution Accelerator for Business Desktop Deployment 2007

INTRODUCTION

An update rollup released for Solution Accelerator for Business Desktop Deployment (BDD) 2007. The update rollup sustains for Windows Vista as well as Windows XP Pro.
Issues that are fixed in the update rollup
The given problems are fixed by update rollup.

• When you attempt to utilize BDD 2007 to back up a PC, it is not saved to hard disk. This problem happen if ComputerBackupLocation line is not set to a value in the CustomSettings.ini file. By default, it is blank.

• When you utilize the BDD 2007 Workbench to package hotfixes and updates for use to PCs on the network, not each hotfix is installed.

• BDD 2007 used in a 64-bit operating system to organize a 32-bit deployment point, the 64-bit versions of some files is duplicated to the deployment point.
After downloading Windows Vista security update, you cannot import update to the BDD 2007 Workbench. This problem happens because the BDD 2007 Workbench cannot import .msu files. To solve this problem, extract the .cab file from the .msu file.

• After you add a program from the 2007 Office system to BSD 2007 as an program, the program does not set up only the cache when you attempt to do a cache-only installation.

• The BDD 2007 Workbench does not add all the drivers that are listed in a comma-separated string when you try to install Windows XP Service Pack 2 (SP2). as well, the BDD 2007 Workbench may install only the driver for 64-bit versions of Windows XP with SP2.

• You cannot recognize a configuration file to make use of with BDD 2007. The update rollup enables a fresh parameter in BDD 2007 that lets you identify an XML configuration file. The configuration file describes the settings that the Windows User State Migration Tool (USMT) should migrate along with the settings that USMT should not migrate.

• In BDD 2007, you can add CaptureGroups=ALL to the CustomSettings.ini file. This setting migrates all security group memberships in an existing operating system to a new operating system. However, when you do this, no group members are captured or restored. Additionally, you receive the following error message:
ZTI ERROR - Unhandled error returned by ZTIGroups: (-2147463168)

• If the case of a directory given name is altered when the contents of a shared distribution resource are being restored, the BDD 2007 Workbench creates duplicate entries in the Operating Systems list. For example, if you back up the Windows Vista directory, and then you restore the directory as WINDOWS VISTA, the BDD 2007 Workbench lists "Windows Vista" and "WINDOWS VISTA" as two operating systems.

• Whenever you make use of BDD 2007 together with USMT 3.0 to restore a user state, the files as well as folders are restored to the unique locations instead of to the new locations. Also, invalid shortcuts are migrated. This issue occurs because all data in the store is migrated if you do not specify any files on the LoadState command line. Migration rules that you specify on the ScanState command line in an .xml file do not apply.

• Whenever you make use of the BDD 2007 Workbench to make an ISO image, hidden files are not included in the ISO image.

• When you generate an $OEM$ folder at the top level of a directory structure, the directory structure is not copied to a network or else to a media deployment point. Such as, this problem occurs if you generate a directory structure that resembles the following:
\Distribution\$OEM$

• When you try to download the following programs, you receive an error message:

o USMT 3.0 (x86)
o USMT 3.0 (X64)
o KMS Management Pack for MOM 2005

• After you disable a Windows Vista update in the BDD 2007 Workbench, the disabled update is installed during deployment.

• When you identify a subfolder of a network shared folder as the location to save the BitLocker external key, the key cannot be saved. You can save the key only to the network shared folder itself.

• When you run a backup from an SMS Operating System Deployment Feature Pack (OSD) update, files are not excluded from the backup as expected. This happens because the Wimscript.ini template file uses drive letters to exclude folders. For example, the Wimscript.ini template file may exclude C:\Windows.old. However, if the Windows.old file is on a drive other than C:, the file is not excluded.

• If the UNC path of the ImageX.exe utility contains a space, a ZTIBackup script cannot build a command line to run ImageX.exe. ImageX.exe is used to perform a full volume backup during deployment.

• The Lite Touch Installation (LTI) wizard cannot start if the network share name of the deployment point contains a space.

• ZTIUtility cannot locate a file when you use it together with a custom .ini file to look up information in a database.

• By default, the C:\Drivers folder is included in an image when you use BDD 2007 to capture the image. When you use Windows Vista Setup to install the image, the C:\Drivers folder is moved to the C:\Windows.old folder. Therefore, the driver files that are required for the PC are not available to the Windows Vista Setup program.

• When you attempt to utilize the CustomSettings.ini file to set the BDERecoveryPassword option, the recovery password is not created. This behavior happen if you skip pages in the BitLocker wizard. This behavior happens because the BDERecoveryPassword property is not defined in the ZTIGather.xml file. Therefore, the CustomSettings.ini value is ignored.

• When you attempt to utilize the BDD 2007 Workbench to insert a Windows Deployment Services (WDS) custom image, the WDS custom image is not included.

• When you attempt to utilize the Pre-Boot Execution Environment (PXE) to deploy the WDSServer service property from Windows Deployment Services, the property is not set properly.

• When drivers for a single device are there both in BDD 2007 for 64-bit operating systems and in BDD 2007 for 32-bit operating systems, both drivers may not be copied to the PC.