Exchange 2000 to 2003 Migration

Hello,

I am doing an exchange migration from exchange 2000 to 2003 enterprise
edition. I am actually doing a test migration where i have built an windows
2000 adv server with exchange 2000 server enterprise server and restored my
exchange database onto this offline server. This server has a new domain
(restore.local) and is totally seperate from my network. Then I installed
another server with windows 2003 enterprise and exchange 2003 enterprise
server and configured it to be a domain controller in my origional domain. I
let it sync with the other domain controllers so it had the latest copy of
ad, also it is a global catalog server. Then i connected it to a seperate
network where onely both servers can see each other. I have installed the
latest updates for exchange and windows on both servers. I have also created
hosts enteries in the hosts file in the windows 2003 box so i can ping the
fqdn of the windows 2000 box. Now when i start the migration wizard on the
windows 2003 and get to the point where it asks my for servername and
username and password, i give it the fqdn for server (server.restore.local)
and for user (restore.local/administrator) with the password and it gives me
an error of. "Unable to logon to the server. Please verify the server name,
port, account names, and password.' I have also tried adding the port 389
after the servername (server.restore.local:389) and that didnt work either.
Does anyone have any ideas??? I can also connect to either computers admin
shares using fqdn so i know they can see eachother fine and it proves that
name resolution is working fine.

Mike

Leif
Mon Mar 13 16:36:36 CST 2006

Hi,

Is it also a new domain you are migrating to in the production environment?
Instead of trying to migrate between two domain you should just do this (I
assume that you want to migrate to a new server in the same domain?)

http://www.msexchange.org/tutorials/Migrating-Exchange2000-Exchange-2003-Hardware.html

Leif


"Mike" <Mike@discussions.microsoft.com> wrote in message
news:2BE1DF94-C72D-4779-BF3D-F466080E4E72@microsoft.com...
> Hello,
>
> I am doing an exchange migration from exchange 2000 to 2003 enterprise
> edition. I am actually doing a test migration where i have built an
> windows
> 2000 adv server with exchange 2000 server enterprise server and restored
> my
> exchange database onto this offline server. This server has a new domain
> (restore.local) and is totally seperate from my network. Then I installed
> another server with windows 2003 enterprise and exchange 2003 enterprise
> server and configured it to be a domain controller in my origional domain.
> I
> let it sync with the other domain controllers so it had the latest copy of
> ad, also it is a global catalog server. Then i connected it to a seperate
> network where onely both servers can see each other. I have installed the
> latest updates for exchange and windows on both servers. I have also
> created
> hosts enteries in the hosts file in the windows 2003 box so i can ping the
> fqdn of the windows 2000 box. Now when i start the migration wizard on
> the
> windows 2003 and get to the point where it asks my for servername and
> username and password, i give it the fqdn for server
> (server.restore.local)
> and for user (restore.local/administrator) with the password and it gives
> me
> an error of. "Unable to logon to the server. Please verify the server
> name,
> port, account names, and password.' I have also tried adding the port 389
> after the servername (server.restore.local:389) and that didnt work
> either.
> Does anyone have any ideas??? I can also connect to either computers
> admin
> shares using fqdn so i know they can see eachother fine and it proves that
> name resolution is working fine.
>
> Mike

Mike
Mon Mar 13 21:34:56 CST 2006

The new domain is not in a production environment. I would like to migrate
instead of moving the mailboxes to minimize downtime and for testing
purposes. The migration wizard should work, I would just like to know why am
i getting this message "Unable to logon to the server. Please verify the
server name....." i am migrating from 1 domain to another though. Any
thoughts??


"Leif Pedersen [MVP]" wrote:

> Hi,
>
> Is it also a new domain you are migrating to in the production environment?
> Instead of trying to migrate between two domain you should just do this (I
> assume that you want to migrate to a new server in the same domain?)
>
> http://www.msexchange.org/tutorials/Migrating-Exchange2000-Exchange-2003-Hardware.html
>
> Leif
>
>
> "Mike" <Mike@discussions.microsoft.com> wrote in message
> news:2BE1DF94-C72D-4779-BF3D-F466080E4E72@microsoft.com...
> > Hello,
> >
> > I am doing an exchange migration from exchange 2000 to 2003 enterprise
> > edition. I am actually doing a test migration where i have built an
> > windows
> > 2000 adv server with exchange 2000 server enterprise server and restored
> > my
> > exchange database onto this offline server. This server has a new domain
> > (restore.local) and is totally seperate from my network. Then I installed
> > another server with windows 2003 enterprise and exchange 2003 enterprise
> > server and configured it to be a domain controller in my origional domain.
> > I
> > let it sync with the other domain controllers so it had the latest copy of
> > ad, also it is a global catalog server. Then i connected it to a seperate
> > network where onely both servers can see each other. I have installed the
> > latest updates for exchange and windows on both servers. I have also
> > created
> > hosts enteries in the hosts file in the windows 2003 box so i can ping the
> > fqdn of the windows 2000 box. Now when i start the migration wizard on
> > the
> > windows 2003 and get to the point where it asks my for servername and
> > username and password, i give it the fqdn for server
> > (server.restore.local)
> > and for user (restore.local/administrator) with the password and it gives
> > me
> > an error of. "Unable to logon to the server. Please verify the server
> > name,
> > port, account names, and password.' I have also tried adding the port 389
> > after the servername (server.restore.local:389) and that didnt work
> > either.
> > Does anyone have any ideas??? I can also connect to either computers
> > admin
> > shares using fqdn so i know they can see eachother fine and it proves that
> > name resolution is working fine.
> >
> > Mike
>
>
>