Re: AD Restore disaster please help.........
- From: "jx" <mc@xxxxxxxxxxx>
- Date: Wed, 8 Nov 2006 11:45:58 -0500
There are some good articles on MS regarding doing the SSR on dissimilar
hardware.
Usually the problem that occurs on dissimilar hardware is regarding the HAL
and physical component drivers. Try to restore only the software registry
hive in System State when you are try to do SSR, this may help.
http://support.microsoft.com/kb/263532
HTH
"Zeno" <momo2804@xxxxxxxxx> wrote in message
news:1162993476.068259.218210@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi There.........
I'd like to get some help and advice please...............
Our AD environment consists of a Win2k3 R2 Forest, with Root domain
companyname.com and a child domain au.companyname.com, with 2 DC's on
the root and two in the child.
For the last two days I've been trying to do a restore of the system
state backup from the Root DC (which has all FSMO roles) and a DC from
the child (RID, PDC, Infra).
Unfortunately the hardware which I'm doing the restore is different
which only makes things worse.
The steps I've been taking is as follows:
1. Do standard Win2k3 R2 Svr install
2. Do a restore of the system state backup for Root DC with advanced
options replace files and all files are restore to original path.
3. Follow instructions from MS document for DC restore to different
hardware, set burflag "d4", update the reg keys for the "process
startup".
4. The test environment DCs have exactly the same address as the
original.
5. With hardware and everything being different need to do a Win2k3
system repair with Win2k3 CD. Reregister the dns records.
After all that is done the first problem we come across is cannot lauch
any of the default AD admin tools from the administrative menu eg.
users and computers, DNS, sites and services etc. The only way to get
these consoles is via the MMC and add the console to the MMC viewer.
This occurs on the Root DC.
Then we do a restore of the child DC and the behaviour is exactly the
same with the same problems as the Root DC. So we follow the same
procedure.
Then after all that when we try to do a replication its gone things
like it cannot find the root DC domain or RPC Server unavailable.. Then
when we try to cleanup the metadata for the additional DC that was on
the root and child using ntdutils we get errors saying it can't
actually find sites, servers, but can find the domains. I can connect
to the DC using ntdutils but can't do things such as clean up the
metadata.
Can anyone help me with some suggestions....... it seems the major
problem is the root and child DC's can ping each other after the
restore with DNS working but can't do replication and in some instances
the netlogon service can't start..............
many many thanks...........
.
- References:
- AD Restore disaster please help.........
- From: Zeno
- AD Restore disaster please help.........
- Prev by Date: Re: LDAPS
- Next by Date: Re: Importing Data into Active Directory?
- Previous by thread: AD Restore disaster please help.........
- Next by thread: Domain Controller fault tolerance
- Index(es):
Relevant Pages
|
