Re: NT4 to win2k3
From: Bob Qin [MSFT] (bobqin_at_online.microsoft.com)
Date: 01/26/05
- Next message: stephany: "RE: ADMT and Clustered Servers"
- Previous message: Bob Qin [MSFT]: "RE: ADMT and Clustered Servers"
- In reply to: Upgrader: "Re: NT4 to win2k3"
- Next in thread: Upgrader: "Re: NT4 to win2k3"
- Reply: Upgrader: "Re: NT4 to win2k3"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 Jan 2005 12:42:19 GMT
Thanks for your reply .
Please verify the IP configuration on the client machine for DNS
resolution; it should be able to ping both domain controllers by FQDN.
Pinging by host name does not ensure DNS resolution because name resolution
may occur via WINS.
If all settings appear to be correct and the migration still fails, follow
these steps:
1) Log on to the client machine as administrator.
2) Right-click the network connection and choose properties.
3) Click on "Client for Microsoft Networks" and click the uninstall button.
4) Reboot the machine
5) Log back in to the client machine
6) On the properties of the network connection, click the install button
7) Under clients, choose Client for Microsoft Networks
8) Reboot the machine
Once the machine comes back up, attempt to migrate it again.
If ADMT still fails after removing and reinstalling the Client for
Microsoft Networks and File and Printer sharing, rename the computer and
retry ADMT.
In addition, please refer to the following document for other possible
causes.
The Active Directory Migration Tool displays a "RPC server is unavailable"
error message in Windows Small Business Server 2003
http://support.microsoft.com/default.aspx?scid=KB;EN-US;837366
Have a nice day!
Regards,
Bob Qin
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "Upgrader" <ucan.kissmyass@gmail.com>
Newsgroups: microsoft.public.windows.server.migration
Subject: Re: NT4 to win2k3
Date: 25 Jan 2005 09:41:24 -0800
Here is the error
005-01-25 12:40:29 Created account input file for remote agents:
DCTCache.031
2005-01-25 12:40:29 Installing agent on 1 servers
2005-01-25 12:40:29 The Active Directory Migration Tool Agent will be
installed on \\TORZIW01
2005-01-25 12:40:29 ERR2:7625 Unable to connect to \\TORZIW01\ADMIN$.
The machine might be down or its Server, Netlogon service might not be
started. rc=1722 The RPC server is unavailable.
2005-01-25 12:40:29 ERR2:7014 The Active Directory Migration Tool
Agent
Service on \\TORZIW01 did not start. See the application log on
\\TORZIW01 for details.
2005-01-25 12:40:30 All agents are installed. The dispatcher is
finished.
- Next message: stephany: "RE: ADMT and Clustered Servers"
- Previous message: Bob Qin [MSFT]: "RE: ADMT and Clustered Servers"
- In reply to: Upgrader: "Re: NT4 to win2k3"
- Next in thread: Upgrader: "Re: NT4 to win2k3"
- Reply: Upgrader: "Re: NT4 to win2k3"
- Messages sorted by: [ date ] [ thread ]