Re: Domain Controller cannot boot up after restoring the system st

Tech-Archive recommends: Fix windows errors by optimizing your registry


It was sheer, pure luck that you were able to port a server installation to
a different box. This method worked well with Win9x and with WinNT but it
fails in most cases with all versions starting with Win2000.


"Bobson" <Bobson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:20F833A7-CB44-47F4-B7F9-7EE2DA5192A9@xxxxxxxxxxxxxxxx
Hi Pegasus,

Thank you for the advise.

In fact, I did the same on my pure Windows DNS server before. That method
worked while I restore the DNS on a different hardware box. So I thought
it
would be the same as I can do this on the domain controller...

Anyway or any tools I can "migrate" or "restore" the system state on a
different box?

Too bad if I really cannot test out the system state here...

Bobson

"Pegasus [MVP]" wrote:


"Bobson" <Bobson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:356ACB83-7A18-428C-8D63-86589273B7E5@xxxxxxxxxxxxxxxx
Hi everyone,

Thank you for your help in advanced.

I do this to try to validate my backup. Here is what I did.

There is a domain controoler I backup from. C drive has the OS System
partition and D drive has the Sysvol and NTDS directories.

I use the system state backup from the domain controller and restore it
on
a
different box by using Windows backup program (the one comes with the
OS).
It
did not work. The server keeps rebooting.

I thought...hmmm....maybe the System States does not specically tell
the
original sysvol and ntds is on D drive. So I restore the two folders on
the
test box first before I restore the system state. But the result is the
same.

I would like to ask what step I missed in order to restore the test box
to
run as the domain controller? What should I do in order to restore the
domain
controller correctly?

Thank you very much for your help!

Bobson

The Windows installation process takes into account the hardware on which
you're working. The installation is therefore specific for this
particular
machine and cannot be ported to another machine. If you want to test your
System State backup (which is an excellent idea!) then you should use a
different set of disks which temporarily replace the real disks on your
DC.





.

Relevant Pages

  • Re: Disaster Recovery - Virtualized environment
    ... Starting an Active Directory domain controller whose operating system resides in a virtualized hosting environment such as Microsoft Virtual PC, ... Starting an Active Directory domain controller that is located on a volume where the disk subsystem loads using previously saved images of the operating system without requiring a system state restoration of Active Directory. ... The only supported way to roll back the contents of Active Directory or the local state of an Active Directory domain controller is to use an Active Directory-aware backup and restoration utility to restore a system state backup that originated from the same operating system installation and the same physical or virtual computer that is being restored. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDSUTIL Authorative Restore Error: Error 8000ffff parsing inp
    ... you promoted a DC using the normal process (dcpromo) and then you're ... trying to restore the AD using a old Backup system state for that DC, ... Your DC will assume that system state backup as ...
    (microsoft.public.windows.server.active_directory)
  • Re: domain controller image
    ... a system state backup is the supported way to restore AD and prevent's the USN rollback. ... revert back to the snapshot then boot into the AD ...
    (microsoft.public.windows.server.active_directory)
  • Re: Restoring AD from System State
    ... You said use the /ADV when "promoting a new DC and wish to use a system state backup to populate the DS". ... This is a real restore, not an addition of another DC to my forest. ... When running dcpromo /adv, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Removable Storage Service Missing on SBS 2003
    ... The offered fix is to restore a recent system state backup. ... Then restore your system state, then if all is well, make a fresh backup. ... I restarted the server thinking that it was just a glitch, ...
    (microsoft.public.windows.server.sbs)