J
Jeff Hauff
Hey, this past weekend I had an interesting experience. During preps for
upgrading from a 2000 domain to a 2003 domain, the DC was running a full
backup when something happened and caused the controller to crash and not
restart.
To make a long story short, I found this utility called UMOVE from
www.utools.com. This allowed my to put the old drive into another 2000
server and do an emergency move of the AD info to the new computer and it
did not make a single change to the orig hard drive. It moved everything
necessary to bring up the new server as a domain controller and the work
stations didn't know the difference.
It did have some trouble moving the DHCP scopes but those were easily
rebuilt.
Anyhow I just thought I would pass this on to those that may have similar
situations.
By the way, after doing the postmortum on the orig drive, it appears that
the services file was the cause. It grew to large for the system to be able
to boot it. Not sure why yet but thats the file that caused it to not boot.
A restore of an earlier version allowed it to boot and there are KB's on the
file being too large to load.
Have fun,
Jeff
upgrading from a 2000 domain to a 2003 domain, the DC was running a full
backup when something happened and caused the controller to crash and not
restart.
To make a long story short, I found this utility called UMOVE from
www.utools.com. This allowed my to put the old drive into another 2000
server and do an emergency move of the AD info to the new computer and it
did not make a single change to the orig hard drive. It moved everything
necessary to bring up the new server as a domain controller and the work
stations didn't know the difference.
It did have some trouble moving the DHCP scopes but those were easily
rebuilt.
Anyhow I just thought I would pass this on to those that may have similar
situations.
By the way, after doing the postmortum on the orig drive, it appears that
the services file was the cause. It grew to large for the system to be able
to boot it. Not sure why yet but thats the file that caused it to not boot.
A restore of an earlier version allowed it to boot and there are KB's on the
file being too large to load.
Have fun,
Jeff