migrating from windows 2000 to 2003 server

[arcserve2000]

I am currently running windows 2000 AD w/a domain name for example, corp.xyz.com.

I am migrating to a windows 2003 server which would be on a new server and would have a new server name and domain name (abc.com). Would i need to move anything from windows 2000 server, like any settings? I am assuming i would have a new dns on the 2003 server. What else do i need to worry about or move from the 2000. Do i have to run ad prep/forest/domain?

Another thing is that i have a child domain which is in the 2000 AD domain (abc.corp.xyz.com). How would this effect the child domain do i have move that over to 2003 as well or do i have to reinitialize it....how does this work...please advise...

 

[pagy]

Have a poke through these

Upgrading from Windows 2000 Server to Windows Server 2003

http://www.microsoft.com/windowsserver2003/upgrading/w2k/default.mspx

How to upgrade Windows 2000 domain controllers to Windows Server 2003

http://support.microsoft.com/kb/325379

Common Mistakes When Upgrading a Windows 2000 Domain To a Windows 2003 Domain

http://support.microsoft.com/kb/555040

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[arcserve2000]

do i need to run the domain/ad/forest prep still if i am not moving anything from 2000 to 2003 besides the fsmo roles and global catalog. Dns would be newly created on the 2003 server considering i will using a new domain name??

 

[pagy]

Do you actually want a new forest or do you just want to upgrade your existing one to windows 2003????


Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[arcserve2000]

Let me tell you exactly what i want to do

Currently we are running Win2000 AD Domain, which has the PDC and backup which is named corp.xyz.com. We also have 2000 child AD domain which is named child.corp.xyz.com.

The 2000 PDC is on a real old server. We want to build 2003 AD domain on a new server..it will be a new forest, domain and server name. We are not keeping anything same, it will be as you are building a new domain. These 2 domains will run parallel to each other. The new domain say it would be names for ex. (pdc.abc.com)

From the 2000 server do we need to move anything besides the Global Catalog and FSMO roles? Does forest/domain prep still need to run on the 2000 server? We do have some entries of other domain names in the DNS on the 2000 server. ON the 2003 do i need to create a new DNS and recreate the DNS entries that are on the 2000 server?

Also, the child domain how would this be affected. How would that communicate w/the new forest considering it's in the 2000 domain (child.corp.xyz.com). We want it to be added to the 2003 domain as (child.abc.com).

If you have any other questions let me know

 

[arcserve2000]

One other thing, we are also currently running exchange 5.5, is it compatible with windows2003 the new domain we want to create??

 

[pagy]

From the 2000 server do we need to move anything besides the Global Catalog and FSMO roles? Does forest/domain prep still need to run on the 2000 server?

You would not need to do this as you are building a new domain in a new forest, it will have it's own GCs and FSMO roles will be on the first DC in the new forest you are building
Adprep would not need to be run on the 2000 DC as you are not upgrading that to 2003, you are building a new forest.

ON the 2003 do i need to create a new DNS and recreate the DNS entries that are on the 2000 server?

Assuming you will have your first DC in your new forest handling your DNS then a DNS zone will be created on your new DC in your new forest, if you have specific DNS entries that you require then you would need to add them to DNS on your new DC



Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[pagy]

Also, the child domain how would this be affected. How would that communicate w/the new forest considering it's in the 2000 domain (child.corp.xyz.com). We want it to be added to the 2003 domain as (child.abc.com).

It would not communicate by default with the new forest, you would need to set up a trust.

Is this new forest a replacement for what you already have or is it in addition and to be used for another purpose to your existing AD infrastructure????

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[arcserve2000]

it would be a replacement of the 2000 domain. So all we need to do is create a trust between the 2003 and child domain we currently have. Nothing needs to be done on the child domain then?


Would exchange 5.5 work with 2003 AD?

I forgot to mention we are also running an NT domain at the same time. All of our users log into the NT domain. Once we create the 2003 domain we would gradually move users over to the new domain. But instead of point the a/c for exchange to the NT domain side, will it work w/the new 2003 domain?

The 2000 child domain that we have is currently being used for terminal servcies, no a/c's on the 2000 parent domain.

 

[pagy]

Ok, let me make sure I understand. You have an NT4.0 domain that has your user accounts in it? Your w2k domain forest root has no accounts in it at all and the child domain has terminal servers in it?? So it sounds to me like the 2000 AD is pretty much a resource forest

So once you build your new 2003 AD what will become of the 2000 domain, will it stay in place for terminal services??

To the best of my knowledge Exchange 5.5 cannot run on Windows 2003 servers, it can run in an 2003 AD environment but would need to be on a windows 2000 server and you would need to use the active directory connector. If this is incorrect I'm sure someone with more exchange knowledge than I will correct me

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[ahhgeez]

If you are upgrading from a Windows 2000 to Windows 2003 R2 you have to run adprep /forestprep and run adprep /domainprep on the Windows 2000 domain controllers. Use the adprep from the Windows 2003 R2 CD 2 \cmpnents\R2 folder. That will take you to Schema Version 31. Get yourself a new box and install Windows 2003 R2 and create a new domain. Whats the reason why your changing the domain name? Just curious. Here is book you should pick-up and go straight to chapter 15.

Active Directory, 3rd Edition
By Robbie Allen, Alistair G. Lowe-Norris, Joe Richards
...............................................
Publisher: O'Reilly
Pub Date: January 2006
Print ISBN-10: 0-596-10173-2
Print ISBN-13: 978-0-59-610173-2

 

[pagy]

ahhgeez,

It would seem though that arcserve2000 is not upgrading any 2000 domains to 2003, rather the NT domain is being replaced by a new windows 20003 domain. At least that is what I think arcserve2000 means but I could be wrong

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[arcserve2000]

ONce we have a new 2003 domain. I would like to kill the 2 DC's on the 2000 side, staying up w/the new dc's in 2003. The child we still want intact, but would need to talk to the 2003 domain instead. I know we can establish a trust, but once we bring down the 2000 domain dc's, how would the child domain be effected or would it not? The child domain has a AD DC with accounts/group policies on it.

Do we need redo the child domain as well b/c it was a child domain for the 2000 dc's?

Right, NT domain is being replaced w/the 2003 domain.

 

[pagy]

You could not bring down the parent domain dcs and leave the child domain intact.

What you could do is use the active directory migration tool (ADMT) to migrate user and computer accounts from the child domain to your new forest, you could either have a OU in the new forest representing the migrated objects from the child domain or build a new child domain in the new forest to migrate them to.
You could also use ADMT to migrate your user and computer accounts from the NT domain.

Paul
MCSE


"Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe."
Albert Einstein

 

[arcserve2000]

That sucks..can't bring down the 2000 DC's b/c of the child domain. If i say migrated the OU from the child domain to the new 2003 server that would mean i would need to redo all my terminal servers to be added as the child domain in the new 2003 domain. All profiles are on the TSE servers.

Say if i create a new child domain server in the 2003 forest and move the OU from the 2000 child domain to the new 2003 child domain created. How would the 2000 child domain servers communicate w/the new 2003 child? There are profiles for users on each of the terminal servers in the 2000 side. Would i have to add it to the new 2003 domain instead?

Does the 2003 server CD have the AD Mail connector on it or is on the exchange 2003 CD?

 

[arcserve2000]

I have w/2000 server installed w/exchange server 5.5 running on it and its connected to the NT domain as you know.

I want exchange 5.5 server to work with 2003 a/c's once i move user gradually from NT to 2003 domain. If i have a user in the 2003 AD, would i be able to point the a/c on the exchange server to the 2003 domain.

How would this work..do i need to install some sort of mail connector in order for exchange to communicate w/AD?