Duplicate computer names are generated if you use a Windows Setup program to generate random names for a large number of computers

Consider the following scenario:

• You are deploying operating systems, such as Windows Vista or Windows Server 2008, to a large number of computers.
• You use a Windows Setup program to generate random computer names for these computers.

In this scenario, duplicate computer names may be generated. Computers that have duplicate names cannot join the network or access network resources. You have to redeploy the operating systems to these affected computers.

This issue occurs because of an error in the algorithm that is used to generate the random computer name.

A hotfix is available to resolve this issue. This hotfix introduces a new method to generate greater probability of random computer names.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, the computer must be running one of the following:

• Windows Vista Service Pack 1
• Windows Vista Service Pack 2
• Windows Server 2008 Service Pack 1
• Windows Server 2008 Service Pack 2

Restart requirement

You have to restart the computer after you apply this hotfix.

Instructions to apply the hotfix package

Use the following procedures to apply the hotfix package.

Update each image in the Install.wim image file

1. Install the Windows OEM Preinstallation Kit (Windows OPK) or the Windows Automated Installation Kit (Windows AIK).
2. Use either of the following methods to apply the hotfix package to the Windows image that you are deploying:
   • Double-click the Microsoft Update Stand-alone Package (MSU) file on a computer that is running Windows Vista to install the hotfix package.
   • To install the hotfix package offline, use the instructions that are included in the Windows OPK or in the Windows AIK. To do this, see the following topics in the OPK.chm file or in the WAIK.chm file:
     • Windows Preinstallation Phases \ Phase 5: Image Maintenance \ Servicing an Image
     • Windows Preinstallation Phases \ Phase 5: Image Maintenance \ Maintenance Walkthroughs \ Walkthrough: Servicing a Windows Image Offline
3. Copy the updated Install.wim file to Installation_Point\sources, where Installation_Point is the location of the contents of the Windows Setup media.

Update a Setup binary in image 2 of the Boot.wim file

1. Expand the MSU file (Windows6.0-KB970485-arch.msu) for the architecture that is being serviced to a temporary folder. For example, type the following command at the command prompt, and then press ENTER:
   Expand.exe Path_To_MSU_File -F:* Path_To_TemporaryFolder1
2. Expand the CAB file (Windows6.0-KB970485-arch.cab) from the previously created temporary folder to another temporary folder. For example, type the following command at the command prompt, and then press ENTER:
   Expand.exe Path_To_CAB_File -F:* Path_To_TemporaryFolder2
   Note In Windows XP or in Windows Server 2003, this command may generate an error. If you receive an error message, use the version of the Expand.exe tool that is included in the Windows OPK or in the Windows AIK to extract the files.
3. Copy the Boot.wim file from the Sources folder of the Windows Vista installation media to a local temporary folder.
4. Mount the "Microsoft Windows Longhorn Setup" image (index 2) of the Boot.wim file using Read/Write permission. For example, type the following command at the command prompt, and then press ENTER:
   imagex.exe /mountrw Path_To_Boot_WIM_File 2 Mount_Location
5. Copy the following files from the "Path_To_TemporaryFolder2 \x86_microsoft-windows-setup-component" folder that you created in step 2 to the Mount_Location\Sources folder:
   • actionqueue.dll
   • diager.dll
   • diagnostic.dll
   • setup.exe
   • spprgrss.dll
   • w32uiimg.dll
   • w32uires.dll
   • wdsutil.dll
   • win32ui.dll
   • winsetup.dll
6. Unmount the Boot.wim file, and then commit all changes. For example, type the following command at the command prompt, and then press ENTER:
   imagex.exe /commit /unmount Mount_Location
7. Copy the modified Boot.wim file to the Installation_Point \Sources folder.
   
   Note Installation_Point is the location of the contents of the Windows Setup media.
8. Delete all temporary folders.

Update a Setup binary that exists on installation media that does not use a Windows Image Format (WIM) file

1. Expand the MSU file (Windows6.0-KB970485-arch.msu) for the architecture that is being serviced to a temporary folder. For example, type the following command at the command prompt, and then press ENTER:
   Expand.exe Path_To_MSU_File -F:* Path_To_TemporaryFolder1
2. Expand the CAB file (Windows6.0-KB970485-arch.cab) from the previously created temporary folder to another temporary folder. For example, type the following command at the command prompt, and then press ENTER:
   Expand.exe Path_To_CAB_File -F:* Path_To_TemporaryFolder2
   Note In Windows XP or in Windows Server 2003, this command may generate an error. If you receive an error message, use the version of the Expand.exe tool that is included in the Windows OPK or in the Windows AIK to extract the files
3. Copy the following files from the "Path_To_TemporaryFolder2 \x86_microsoft-windows-setup-component" folder that you created in step 2 to the Installation_Point \Sources folder:
   • actionqueue.dll
   • diager.dll
   • diagnostic.dll
   • setup.exe
   • spprgrss.dll
   • w32uiimg.dll
   • w32uires.dll
   • wdsutil.dll
   • win32ui.dll
   • winsetup.dll
   Note Do not copy any other files over onto the installation point even if the files have the same name. If you do this, Windows Setup may behave unpredictably.
4. Delete all temporary folders.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008 and Windows Vista file information note

The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.

Windows Server 2008 and Windows Vista, x86-based versions

Windows Server 2008, Itanium-based versions

Windows Server 2008 and Windows Vista, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about random computer name generation, visit the following Microsoft Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

Additional files for all supported Itanium-based versions of Windows Server 2008

Additional files for all supported x64-based versions of Windows Server 2008