If you need to get hard-core with NAT-T, these registry entries may be useful. Keep reading →

Consider the following scenarios.

Scenario 1

1. You install Windows Vista on the C partition on “Computer A.”
2. After you install Windows Vista, you use the System Preparation tool (Sysprep.exe) to prepare an installation of Windows Vista for imaging to another computer. You use the following command:
   

   sysprep /oobe /generalize

3. You restart “Computer A.”
4. In Windows Preinstallation Environment (Windows PE) 2.0, you use the ImageX tool to create an image for Windows Vista.
5. You deploy the image to “Computer B,” and then you restart the computer.

Scenario 2

1. You install Windows Vista on the C partition on “Computer A.”
2. After you install Windows Vista, you use the System Preparation tool (Sysprep.exe) to prepare an installation of Windows Vista for imaging to another computer. You use the following command:
   

   sysprep /oobe /generalize

3. In Windows PE 2.0, you use the ImageX tool to create an image for Windows Vista.
4. You deploy the image to “Computer B.” However, you use a different partition than the C partition.
5. After you deploy the image to “Computer B,” you restart the computer.

In these scenarios, you may receive the following error message:

The system registry contains invalid file paths. Installation cannot proceed. This system image was applied without guaranteeing that drive-letter assignments would match across computers

You have a Microsoft Windows XP-based computer or a Windows Vista-based computer in a domain. Some registry-based policy settings are lost on the computer when either of the following conditions is true:

• Group Policy settings are changed.
• Group Policy settings have to be reapplied at set intervals to the computers in the domain.

Additionally, error messages that resemble the following may be logged in the Application log:

Message 1

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1096
Date: 26/04/2006
Time: 06:14:57
User: NT AUTHORITY\SYSTEM
Computer: Computer_Name
Description:
Windows cannot access the registry policy file, \\Domain.NET\SysVol\Domain.NET\Policies\{82787E36-87C9-4C34-AD95-72365A389553}\Machine\registry.pol. (The process cannot access the file because it is being used by another process.).

Message 2

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1043
Date: 26/04/2006
Time: 06:14:56
User:
Computer: Computer_Name
Description:
Windows cannot access the registry information at \\Domain.NET\SysVol\Domain.NET\Policies\{82787E36-87C9-4C34-AD95-72365A389553}\Machine\registry.pol. (The process cannot access the file because it is being used by another process.).

On a computer that is running Windows Vista, when you use the Reg.exe tool to query a registry subkey, you may receive the following error message:

ERROR: More data is available.

This problem occurs if the registry subkey contains null-terminate registry entries. These registry entries have some non-standard letters. Although these registry entries appear to be correct, their binary data does not reflect a correct value.

On Windows Vista-based computer, you cannot use Registry Editor to load a registry hive file that is on a shared network resource. You receive the following error message:

Cannot load \\HivePath\FileName: Access is denied.

This problem occurs even if the user account that you use is granted Full Control permission to the registry hive file.

This problem also occurs if you use another utility to load a registry hive file that is on a shared network resource, and the utility uses the RegLoadKey API.

In Windows Vista, you add the CopyFileBufferedSynchronousIo registry entry to improve the speed of a file copy operation. However, when you use Windows Explorer to copy a file from the Windows Vista-based computer to a computer that is running an older Windows operating system, the file copies only slightly more quickly.

Note: The file copies more quickly if you use a command-line tool to copy the file. You can use command-line tools such as Robocopy.exe and Xcopy.exe to copy the file.:

When you use the Sysprep tool to deploy Windows Vista, you cannot use the DevicePath registry entry to install out-of-box drivers.

Note: The DevicePath registry entry is located in the following registry subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\