Article ID: 823735
Article Last Modified on 11/4/2007
APPLIES TO
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Datacenter Server
- Microsoft Windows 2000 Server
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Professional
SYMPTOMS
When you use Active Directory Migration Tool (ADMT) version 2 to migrate computer objects from a Microsoft Windows 2000 Server-based server to a Microsoft Windows Server 2003-based server, the Domain Name System (DNS) name of each computer object is used to resolve the IP address instead of the NetBIOS name, as expected. When you experience this problem, you may receive the following error messages:
The following information may be logged in the dispatch log:
CAUSE
If the dNSHostName attribute is defined on the computer object, the DNS name is used to resolve the IP address of the computer object. If the dNSHostName is not defined, the NetBIOS name is used to resolve the IP address. By default, all Windows 2000-and-later workstations have this attribute defined on the Active Directory computer object.
WORKAROUND
To work around this issue, clear the dNSHostName attribute from the computer accounts before you use ADMT to migrate your computer objects from a Windows 2000-based server to a Windows Server 2003-based server.
RESOLUTION
Windows Server 2003
Hotfix information
A supported hotfix is now 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 Windows Server 2003 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Mcsdispatcher.exe | 5.2.3790.72 | 111,104 | 29-Jul-2003 | 01:55 | x86 |
Note To install this hotfix on Windows 2000-based computers or on Windows XP-based computers that are running ADMT 2.0, extract the hotfix by using the /x switch. Next, copy Mcsdispatcher.exe to the ADMT install directory. For example, copy Mcsdispatcher.exe to C:\Program Files\Active Directory Migration Tool.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Keywords: kbbug kbfix kbqfe kbwinserv2003presp1fix kbhotfixserver KB823735
