If you
do that method then the DC that you have in the test environment will have a
different name to the ones in Production which may mean that when testing
solutions (is that why you are doing this?) you will have a different names and
stuff to worry about. We achieve what you are after here by performing a
restore to identical hardware in an air gapped network.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Murray
Sent: 16 January 2006 18:18
To: [email protected]
Subject: RE: [ActiveDir] AD Test Environment
Hi Frank
There's a suggestion on how to do this
here:
Tony
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frank Abagnale
Sent: Tuesday, 17 January 2006 4:07 a.m.
To: Active
Subject: [ActiveDir] AD Test Environment
Hi,
Single W2k3 Forest/domain
I am planning on building an exact like for like test environment.
My initial thought is to add a DC to the domain and then pull this off, do
a metadata cleanup in live to remove any traces of this DC.
I would like some advice on what steps I will need to take in order to
use this DC in the Test Environment.
Would I need to do anything with the legacy DC's which are no longer
available in AD, do I need to clean these up? I assume I will need to
seize the FSMO's....
I use AD Integrated DNS so this is covered, WINS is not too much of a
problem. I also need to think about Exchange & SUS updates...
Any experience of this would be great....
thanks
Frank
Yahoo! Photos – Showcase holiday pictures in hardcover
Photo Books. You design it and we’ll bind it!
This message has been scanned for viruses by MailControl
This email and any attached files are confidential and copyright protected. If you are not the addressee, any dissemination of this communication is strictly prohibited. Unless otherwise expressly agreed in writing, nothing stated in this communication shall be legally binding.
