MentalSolutions
asked on
ADMT error 8250 server is not operational during attempted migration
Im attempting to migrate a win2k3 server to a win2k3 SBS server using the MS ADMT tool
I have followed the documentation religeously however I get the above error when i try to run the migration. I believe the problem lies in the DNS and it is true that on the old win2k3 server the DNS was a bit of a mess. however if i try to ping olddomain.local I get the correct IP address (on the new server) and visa versa.
I have followed the documentation religeously however I get the above error when i try to run the migration. I believe the problem lies in the DNS and it is true that on the old win2k3 server the DNS was a bit of a mess. however if i try to ping olddomain.local I get the correct IP address (on the new server) and visa versa.
ASKER
oooh good idea - i will try that - the problem is the old server is an active server - so everytime i need to get it ready for the migration i have to take it out of active service - then (like tonight) if it dosent work i have to put it all back again - but i will try your suggestion tomorrow.
You should be able to make those changes without reboot/service interruption. At the least if you are concerned about that you can do the hosts file suggestion without risk.
Mike
Mike
ASKER
Yes I appreciate what you are saying, however if you follow the migration document to the letter there are quite a few steps that need to be taken which render the source server useless - such as
disconecting internet access
stopping the DHCP server on the source server
removing any external DNS forwarders from the source server DNS server
plus - naturally - all clients should be out of the system when you perform a Migration anyway
disconecting internet access
stopping the DHCP server on the source server
removing any external DNS forwarders from the source server DNS server
plus - naturally - all clients should be out of the system when you perform a Migration anyway
ASKER
I have tried everything you have suggested - unfortunately I still get the same error 8250 server is not operational
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Server 1 (old)
DNS 1 in TCP/IP properties: Itself (or the DNS for its domain)
DNS 2 in TCP/IP properties: The new server
Server 2 (new)
DNS 1 in TCP/IP properties: Itself
DNS 2 in TCP/IP propertise: The old server (or DNS for the "old" domain.
If these voth fail you might try static entries in the hosts file under c:\[windir]\system32\drive
Hoping this helps,
Mike