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

Article translations Article translations
Article ID: 970485 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

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.

CAUSE

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

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Actionqueue.dll6.0.6001.22421167,93628-Apr-200915:35x86
Audit.exe6.0.6001.2242152,73628-Apr-200913:21x86
Diager.dll6.0.6001.2242131,23228-Apr-200915:42x86
Diagnostic.dll6.0.6001.22421122,36828-Apr-200915:42x86
Oobeldr.exe6.0.6001.2242142,49628-Apr-200913:21x86
Setup.cfgNot Applicable2,71101-Apr-200919:28Not Applicable
Setup.exe6.0.6001.22421192,58428-Apr-200916:42x86
Spprgrss.dll6.0.6001.2242154,27228-Apr-200915:42x86
Sysprep.exe6.0.6001.2242194,72028-Apr-200913:21x86
W32uiimg.dll6.0.6001.224212,928,64028-Apr-200915:42x86
W32uires.dll6.0.6001.22421266,75228-Apr-200915:42x86
Wdsutil.dll6.0.6001.2242147,61628-Apr-200915:42x86
Win32ui.dll6.0.6001.22421417,28028-Apr-200915:42x86
Windeploy.exe6.0.6001.2242162,97628-Apr-200913:21x86
Winsetup.dll6.0.6001.224211,470,97628-Apr-200915:42x86
Actionqueue.dll6.0.6002.22123167,93628-Apr-200915:29x86
Audit.exe6.0.6002.2212352,73628-Apr-200913:06x86
Diager.dll6.0.6002.2212331,23228-Apr-200913:07x86
Diagnostic.dll6.0.6002.22123122,36828-Apr-200913:07x86
Oobeldr.exe6.0.6002.2212342,49628-Apr-200913:06x86
Setup.cfgNot Applicable2,71104-Apr-200905:54Not Applicable
Setup.exe6.0.6002.22123194,00828-Apr-200916:10x86
Spprgrss.dll6.0.6002.2212354,27228-Apr-200913:06x86
Sysprep.exe6.0.6002.2212394,72028-Apr-200913:06x86
W32uiimg.dll6.0.6002.221232,928,64028-Apr-200915:31x86
W32uires.dll6.0.6002.22123266,75228-Apr-200913:06x86
Wdsutil.dll6.0.6002.2212347,61628-Apr-200913:05x86
Win32ui.dll6.0.6002.22123417,28028-Apr-200915:31x86
Windeploy.exe6.0.6002.2212362,97628-Apr-200913:06x86
Winsetup.dll6.0.6002.221231,470,97628-Apr-200915:31x86
Windows Server 2008, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Actionqueue.dll6.0.6001.22421437,24828-Apr-200915:39IA-64
Audit.exe6.0.6001.22421135,16828-Apr-200913:25IA-64
Diager.dll6.0.6001.2242187,55228-Apr-200915:45IA-64
Diagnostic.dll6.0.6001.22421292,86428-Apr-200915:45IA-64
Oobeldr.exe6.0.6001.22421103,42428-Apr-200913:25IA-64
Setup.cfgNot Applicable2,71101-Apr-200917:21Not Applicable
Setup.exe6.0.6001.22421318,43228-Apr-200916:26IA-64
Spprgrss.dll6.0.6001.22421100,35228-Apr-200915:45IA-64
Sysprep.exe6.0.6001.22421193,53628-Apr-200913:25IA-64
W32uiimg.dll6.0.6001.224212,928,12828-Apr-200913:25IA-64
W32uires.dll6.0.6001.22421266,24028-Apr-200913:25IA-64
Wdsutil.dll6.0.6001.22421107,52028-Apr-200915:45IA-64
Win32ui.dll6.0.6001.224211,068,03228-Apr-200915:45IA-64
Windeploy.exe6.0.6001.22421136,70428-Apr-200913:25IA-64
Winsetup.dll6.0.6001.224213,483,13628-Apr-200915:45IA-64
Actionqueue.dll6.0.6002.22123437,24828-Apr-200915:22IA-64
Audit.exe6.0.6002.22123135,16828-Apr-200913:07IA-64
Diager.dll6.0.6002.2212387,55228-Apr-200915:27IA-64
Diagnostic.dll6.0.6002.22123292,86428-Apr-200915:27IA-64
Oobeldr.exe6.0.6002.22123103,42428-Apr-200913:07IA-64
Setup.cfgNot Applicable2,71103-Apr-200921:28Not Applicable
Setup.exe6.0.6002.22123318,44028-Apr-200916:03IA-64
Spprgrss.dll6.0.6002.22123100,35228-Apr-200915:27IA-64
Sysprep.exe6.0.6002.22123193,53628-Apr-200913:07IA-64
W32uiimg.dll6.0.6002.221232,928,12828-Apr-200913:07IA-64
W32uires.dll6.0.6002.22123266,24028-Apr-200913:07IA-64
Wdsutil.dll6.0.6002.22123107,52028-Apr-200915:27IA-64
Win32ui.dll6.0.6002.221231,068,03228-Apr-200915:27IA-64
Windeploy.exe6.0.6002.22123136,70428-Apr-200913:07IA-64
Winsetup.dll6.0.6002.221233,483,13628-Apr-200915:27IA-64
Windows Server 2008 and Windows Vista, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Actionqueue.dll6.0.6001.22421200,70428-Apr-200915:47x64
Audit.exe6.0.6001.2242164,00028-Apr-200913:36x64
Diager.dll6.0.6001.2242138,91228-Apr-200915:52x64
Diagnostic.dll6.0.6001.22421146,43228-Apr-200915:52x64
Oobeldr.exe6.0.6001.2242148,12828-Apr-200913:36x64
Setup.cfgNot Applicable2,71101-Apr-200917:21Not Applicable
Setup.exe6.0.6001.22421209,49628-Apr-200916:42x64
Spprgrss.dll6.0.6001.2242154,78428-Apr-200915:52x64
Sysprep.exe6.0.6001.22421108,03228-Apr-200913:36x64
W32uiimg.dll6.0.6001.224212,928,12828-Apr-200913:35x64
W32uires.dll6.0.6001.22421266,24028-Apr-200913:35x64
Wdsutil.dll6.0.6001.2242156,32028-Apr-200915:52x64
Win32ui.dll6.0.6001.22421573,95228-Apr-200915:52x64
Windeploy.exe6.0.6001.2242176,80028-Apr-200913:36x64
Winsetup.dll6.0.6001.224211,866,75228-Apr-200915:52x64
Actionqueue.dll6.0.6002.22123200,70428-Apr-200915:13x64
Audit.exe6.0.6002.2212364,00028-Apr-200913:04x64
Diager.dll6.0.6002.2212338,91228-Apr-200915:17x64
Diagnostic.dll6.0.6002.22123146,43228-Apr-200915:17x64
Oobeldr.exe6.0.6002.2212348,12828-Apr-200913:04x64
Setup.cfgNot Applicable2,71103-Apr-200921:28Not Applicable
Setup.exe6.0.6002.22123210,92028-Apr-200916:02x64
Spprgrss.dll6.0.6002.2212354,78428-Apr-200915:17x64
Sysprep.exe6.0.6002.22123108,03228-Apr-200913:04x64
W32uiimg.dll6.0.6002.221232,928,12828-Apr-200913:04x64
W32uires.dll6.0.6002.22123266,24028-Apr-200913:04x64
Wdsutil.dll6.0.6002.2212356,32028-Apr-200915:17x64
Win32ui.dll6.0.6002.22123573,95228-Apr-200915:17x64
Windeploy.exe6.0.6002.2212376,80028-Apr-200913:04x64
Winsetup.dll6.0.6002.221231,866,75228-Apr-200915:17x64

STATUS

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

MORE INFORMATION

For more information about random computer name generation, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc749460.aspx
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Package_for_kb970485_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42129-Apr-200911:45Not Applicable
Package_for_kb970485_sc_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69029-Apr-200911:45Not Applicable
Package_for_kb970485_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,70129-Apr-200911:45Not Applicable
Package_for_kb970485_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42529-Apr-200911:45Not Applicable
Package_for_kb970485_server_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,69429-Apr-200911:45Not Applicable
Package_for_kb970485_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,71329-Apr-200911:45Not Applicable
X86_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6001.22421_none_32a1813dc66f310f.manifestNot Applicable27,02728-Apr-200919:44Not Applicable
X86_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6002.22123_none_3489f3b9c393b8e1.manifestNot Applicable27,02728-Apr-200917:12Not Applicable
Additional files for all supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Ia64_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6001.22421_none_32a32533c66d3a0b.manifestNot Applicable27,06028-Apr-200917:10Not Applicable
Ia64_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6002.22123_none_348b97afc391c1dd.manifestNot Applicable27,06028-Apr-200916:33Not Applicable
Package_for_kb970485_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42529-Apr-200911:45Not Applicable
Package_for_kb970485_sc_1~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,52929-Apr-200911:45Not Applicable
Package_for_kb970485_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,70629-Apr-200911:45Not Applicable
Package_for_kb970485_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42929-Apr-200911:45Not Applicable
Package_for_kb970485_server_1~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,53329-Apr-200911:45Not Applicable
Package_for_kb970485_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,71729-Apr-200911:45Not Applicable
Additional files for all supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6001.22421_none_8ec01cc17ecca245.manifestNot Applicable27,09328-Apr-200917:35Not Applicable
Amd64_microsoft-windows-setup-component_31bf3856ad364e35_6.0.6002.22123_none_90a88f3d7bf12a17.manifestNot Applicable27,09328-Apr-200917:14Not Applicable
Package_for_kb970485_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42929-Apr-200911:45Not Applicable
Package_for_kb970485_sc_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,70229-Apr-200911:45Not Applicable
Package_for_kb970485_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,71129-Apr-200911:45Not Applicable
Package_for_kb970485_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43329-Apr-200911:45Not Applicable
Package_for_kb970485_server_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,70629-Apr-200911:45Not Applicable
Package_for_kb970485_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,72329-Apr-200911:45Not Applicable

Properties

Article ID: 970485 - Last Review: October 7, 2011 - Revision: 2.0
APPLIES TO
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Standard without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Vista Enterprise 64-bit Edition
  • Windows Vista Home Basic 64-bit Edition
  • Windows Vista Home Premium 64-bit Edition
  • Windows Vista Ultimate 64-bit Edition
  • Windows Vista Business
  • Windows Vista Business 64-bit Edition
  • Windows Vista Enterprise
  • Windows Vista Home Basic
  • Windows Vista Home Premium
  • Windows Vista Ultimate
Keywords: 
kbautohotfix kbexpertiseadvanced kbfix kbsurveynew kbqfe KB970485

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com