AD migration time limit?

didgemaster

didgemaster

didgemaster

Associate
Joined
11 Aug 2003
Posts
1,233
Location
Taunton, Somerset
Hi all

we are still running Windows 2000 server and AD!

We are having to upgrade and for some reason the guys at the top have decided to go to 2003

Now I have read that it is best to go to 2003 and then to 2003 RC2

However I have been talking to a senior colleague who seems to have got hold of the idea that there is a 60 day limit from when you introduce the first domain controller until the 2000 domain controllers stop functioning

This could cause an issue as we have many servers and several child domains.

After running Forest prep and the domain prep on the primary domain we will the run domain prep on each child domain when this has been done then we will be able to introduce our first windows 2003 DC - has anyone heard of this 60 day limit because I've not found it anywhere on the web.
 
Sounds like he's talking about the tombstone lifetime... although this is only relevant if you simply turn off your 2000 DCs (which obviously you wouldn't).

As long as you keep the Forest functional level at 2000 and the Domain function level at 2000 mixed or native you shouldn't have a problem.

If you are buying licenses new, it would be silly not to look into Server 2008...
 
Last edited:
I thought that myself

So when the Forest and Domain have both been 2003 prepared then there is no time limit on how long we can run 2000 2003 along side each other assuming we keep the functional level at 2000 and domain functional level at 2000 mixed/native of course
 
didgemaster said:
I thought that myself

So when the Forest and Domain have both been 2003 prepared then there is no time limit on how long we can run 2000 2003 along side each other assuming we keep the functional level at 2000 and domain functional level at 2000 mixed/native of course
Click to expand...

Yes, I've never heard of a time limit and they will happily run alongside each other.

This link might be worth a poke, some other links at the bottom too. Not sure if the Exchange 2000 section is relevant to yourself though:

http://www.petri.co.il/windows_2003_adprep.htm
 
OK

I asked him again why there is a sixty day limit and he says the problem is to do with DNS scavenging (currently set to 60 days)

I need to learn more about this and why it will effect a domain in a "transitional state"
 
That sounds like nonsense as we have a 2000 domain, running at 2000 forest/domain level and it has no 2000 DC's left and has been 2003, 2003 R2 and now 2008 prep'd and has been running for about a year like that.

In fact that domain no longer has a server on it older than 2003.
 
Sounds like he doesn't know what he's talking about.

Just keep everything running at 2000 functional level until you've upgraded all your DC's, then start changing the functional level up.

DNS Scavenging should have no effect really.. plus I imagine you will you be migrating your DNS servers too? Scavenging will actually help you because it will remove SRV records after the scavenging period has elapsed for DC's which no longer exist (else clients will still think the DC is available for use).
 
brainchylde said:
Sounds like he doesn't know what he's talking about.

Just keep everything running at 2000 functional level until you've upgraded all your DC's, then start changing the functional level up.

DNS Scavenging should have no effect really.. plus I imagine you will you be migrating your DNS servers too? Scavenging will actually help you because it will remove SRV records after the scavenging period has elapsed for DC's which no longer exist (else clients will still think the DC is available for use).
Click to expand...

Our DNS is integrated with AD
 
There's no problem running it in mixed mode for any length of time, most of our customers are in this situation for a period of years.

Get the servers up to 2003, then change it to native mode. You can start transitioning to 2008 / R2 from there.
 
You must log in or register to reply here.
Back
Top Bottom