Re: duplicate AD in lab

did you read the:
http://support.microsoft.com/kb/263532
To start is simply install the Server than, use the backup set to restore
the DC to that new server, and set the BurFlags value to d4, than you can do
other verifrications explained on that article.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

--------------------------------------------------

"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:38B2E44E-5A74-4B82-B1FC-4B4FA4F4DD97@xxxxxxxxxxxxxxxx
Jorge,
I have been following MS KB 263532 although it's for windows 2000. Now, I
need to run in-place repair/upgrade. The problem is the option R is to
use
Recovery Console. So, once I selected R it goes to Recovery console
prompt.
Now, how can I start the repair or upgrade?

"Jorge Silva" wrote:

In both options the Schema partition comes along.

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

--------------------------------------------------

"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F2EC2F9-2E58-4C42-AA04-7EF089383368@xxxxxxxxxxxxxxxx
Jorge,
I know the 2nd option might be easier for me but it's not easy for me
unless I go through the change management control process. Plus, the
Lab
server IS different hardware (maybe that's why it keeps rebooting after
System Restore). So, I'm going to try the 1st option. Since I'm build
this
lab to test AD and Exchange for the production environment do you know
if
the Schema also can be restored with option 1?

"Jorge Silva" wrote:

Hi Chris
If you want to move to a different hardware check:
http://support.microsoft.com/kb/249694/en-us
http://support.microsoft.com/kb/263532/en-us

If you don't want to move to a different hardware:
You can duplicate by adding the VM directly to your Domain as DC, then
unplug that VM, and never connect that VM to the production
environment
again.
Manually remove that VM/DC from your production Environment, perform
metadata cleanup, also remove DNS entries, and any other references.
On the VM in the Lab, you should seize the roles to that VM, and on
that
VM
you can manually remove references to the Production Servers.(Make
sure
that
you never plug that VM again to your production environment, or could
end
up
with a corrupted forest)
To seize roles check
http://support.microsoft.com/kb/255504/en-us


--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

--------------------------------------------------

"Chris" <Chris@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CFE5BF17-4646-4F8C-B488-2974C0A5729F@xxxxxxxxxxxxxxxx
I want to set up a lab running the same AD as in our production. The
lab
is
in a isolated network, not connection to production. I backed up
(ntbackup)
System State from our of the production DC (not FSMO). Then
installed
a
new
Win2k3 server in the lab using the same name as the one System State
was
backed up. Then promote the new lab server as DC (FSMO) with the
same
domain
DNS name and Netbios name as production. Restored System State to
its
original location. After reboot the server came up with "Windows
server
2003" for a few seconds then reboot again. It just keeps rebooting.
F8
doesn't do anything.

So, how can I duplicate the production AD in a LAB? I also read an
article
saying restoring from System State won't restore Schema. I need
this
production AD in the lab to test AD and Exchange related tasks.

Can someone help? Is it possible to do so? If so, can someone
provide
how-to?

Thanks.








.

Relevant Pages

  • Re: Best Way for restoring AD in a test lab
    ... Well do a backup and restore following most of the procedures outlined. ... Just do a backup on a production dc. ... > DC to the test lab with the same Server Name and this is our DR process. ... >> Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Re: test environment windows 2003
    ... an authorative restore after the demote and system state restore. ... This document was prepared for the building of a copy of the production ... Remove the physical cable for the new pc and build the member server ... Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Windows 2003 and NT and XP Authentication of computer accounts [LAB ENVIRONMENT]
    ... I created a copy of our production Active Directory Windows 2003 ... Interim Mode to a lab environment. ... + Lab Contains - Wins, DNS, ISA server, XP/NT Workstations., ... computer account in its primary domain is missing or the password on ...
    (microsoft.public.windows.server.active_directory)
  • Database restore, both from same and different server
    ... Production WSS is working, but a web part has a memory leak. ... production to a development server. ... I've had all kinds of problems trying to restore this ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Test lab: DC Promotion and removal process
    ... I now need to move this DC into the test lab and this is where I get lost. ... system state restore processes and have been able to successfully restore ... system state to another server, log in, and have full access to all AD ...
    (microsoft.public.windows.server.active_directory)
Loading