Isolating a copy of Windows 2000 AD for lab upgrade to W2K3
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
Isolating a copy of Windows 2000 AD for lab upgrade to W2K3

 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration
Author Message
Gary
Guest
Posted: Thu Jan 13, 2005 3:45 am    Post subject: Isolating a copy of Windows 2000 AD for lab upgrade to W2K3 Reply with quote
We are wanting to test our migration to Windows 2003 in a lab environment
using a copy of our existing Windows 2000 AD database along with current FSMO
roles, site replication info, etc. so that we can do migration testing from
Windows 2000 to Windows 2003.

Can someone recommend the best way or steps to do this?

Thanks,

Gary
Back to top
Glenn L
Guest
Posted: Thu Jan 13, 2005 6:52 am    Post subject: Re: Isolating a copy of Windows 2000 AD for lab upgrade to W Reply with quote
You will get differing opinions on the 'best' way.

You basically have 3 options.

I will assume you have a single domain forest. More than one complicates
duplicating production into the lab, and may change which method is "best"

1)
Create a ghost image of a GC.
deploy the image onto an identical server in the lab.
log in and seize all FSMO roles it did not own.
perform a metadata cleanup for the non-existent production DCs using
KB216498

2)
Perform a system state backup of a GC.
restore the system state onto similiar hardware in the lab. There was a KB
on this...can't seem to find it now.
log into restored server and seize all FSMOs it did not own.
perform metadata cleanup for the non-existent production DCs using KB216498

3)
Bring in an additional GC into your domain. Once you have verified it is a
healthy replica, take it off the prod network and put it into the lab.
Seize all FSMOs.
perform metadata cleanup for the non-existent production DCs using KB216498
perform metadata cleanup of this new server in your production domain.


This last method is my preference for both single domain forests and
multidomain forests.
In multidomain forests, you would need (for this last method) to bring an
additonal DC into each domain in production prior to taking them into the
lab.
This last method also will not use existing DC names in the lab.


Regards,

--
Glenn L
CCNA, MCSE 2000/2003 + Security

"Gary" <Gary@discussions.microsoft.com> wrote in message
news:61621679-CB34-4BE4-A025-26C7394BE6C6@microsoft.com...
Quote:
We are wanting to test our migration to Windows 2003 in a lab environment
using a copy of our existing Windows 2000 AD database along with current
FSMO
roles, site replication info, etc. so that we can do migration testing
from
Windows 2000 to Windows 2003.

Can someone recommend the best way or steps to do this?

Thanks,

Gary
Back to top
Gary
Guest
Posted: Thu Jan 13, 2005 6:23 pm    Post subject: Re: Isolating a copy of Windows 2000 AD for lab upgrade to W Reply with quote
Glenn,

You are the man! Thanks for the suggestions, I will definitely review them.
If I follow suggestion 3, once I move the server into the lab I can just
remove it fom AD right and it will not appear as a DC in AD any longer
correct?

Gary

"Glenn L" wrote:

Quote:
You will get differing opinions on the 'best' way.

You basically have 3 options.

I will assume you have a single domain forest. More than one complicates
duplicating production into the lab, and may change which method is "best"

1)
Create a ghost image of a GC.
deploy the image onto an identical server in the lab.
log in and seize all FSMO roles it did not own.
perform a metadata cleanup for the non-existent production DCs using
KB216498

2)
Perform a system state backup of a GC.
restore the system state onto similiar hardware in the lab. There was a KB
on this...can't seem to find it now.
log into restored server and seize all FSMOs it did not own.
perform metadata cleanup for the non-existent production DCs using KB216498

3)
Bring in an additional GC into your domain. Once you have verified it is a
healthy replica, take it off the prod network and put it into the lab.
Seize all FSMOs.
perform metadata cleanup for the non-existent production DCs using KB216498
perform metadata cleanup of this new server in your production domain.


This last method is my preference for both single domain forests and
multidomain forests.
In multidomain forests, you would need (for this last method) to bring an
additonal DC into each domain in production prior to taking them into the
lab.
This last method also will not use existing DC names in the lab.


Regards,

--
Glenn L
CCNA, MCSE 2000/2003 + Security

"Gary" <Gary@discussions.microsoft.com> wrote in message
news:61621679-CB34-4BE4-A025-26C7394BE6C6@microsoft.com...
We are wanting to test our migration to Windows 2003 in a lab environment
using a copy of our existing Windows 2000 AD database along with current
FSMO
roles, site replication info, etc. so that we can do migration testing
from
Windows 2000 to Windows 2003.

Can someone recommend the best way or steps to do this?

Thanks,

Gary


Back to top
Glenn L
Guest
Posted: Thu Jan 13, 2005 10:39 pm    Post subject: Re: Isolating a copy of Windows 2000 AD for lab upgrade to W Reply with quote
you are correct.
follow KB216498 to delete the DC.


--
Glenn L
CCNA, MCSE 2000/2003 + Security

"Gary" <Gary@discussions.microsoft.com> wrote in message
news:3E1B2192-A5FA-4E79-B694-5ED5D5A940A7@microsoft.com...
Quote:
Glenn,

You are the man! Thanks for the suggestions, I will definitely review
them.
If I follow suggestion 3, once I move the server into the lab I can just
remove it fom AD right and it will not appear as a DC in AD any longer
correct?

Gary

"Glenn L" wrote:

You will get differing opinions on the 'best' way.

You basically have 3 options.

I will assume you have a single domain forest. More than one complicates
duplicating production into the lab, and may change which method is
"best"

1)
Create a ghost image of a GC.
deploy the image onto an identical server in the lab.
log in and seize all FSMO roles it did not own.
perform a metadata cleanup for the non-existent production DCs using
KB216498

2)
Perform a system state backup of a GC.
restore the system state onto similiar hardware in the lab. There was a
KB
on this...can't seem to find it now.
log into restored server and seize all FSMOs it did not own.
perform metadata cleanup for the non-existent production DCs using
KB216498

3)
Bring in an additional GC into your domain. Once you have verified it is
a
healthy replica, take it off the prod network and put it into the lab.
Seize all FSMOs.
perform metadata cleanup for the non-existent production DCs using
KB216498
perform metadata cleanup of this new server in your production domain.


This last method is my preference for both single domain forests and
multidomain forests.
In multidomain forests, you would need (for this last method) to bring an
additonal DC into each domain in production prior to taking them into the
lab.
This last method also will not use existing DC names in the lab.


Regards,

--
Glenn L
CCNA, MCSE 2000/2003 + Security

"Gary" <Gary@discussions.microsoft.com> wrote in message
news:61621679-CB34-4BE4-A025-26C7394BE6C6@microsoft.com...
We are wanting to test our migration to Windows 2003 in a lab
environment
using a copy of our existing Windows 2000 AD database along with
current
FSMO
roles, site replication info, etc. so that we can do migration testing
from
Windows 2000 to Windows 2003.

Can someone recommend the best way or steps to do this?

Thanks,

Gary


Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration All times are GMT
Page 1 of 1

 
 You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB