After using Ghost,my DC crash!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Dear all
I got a big problem.
Yesterday I use Norton ghost to backup my DC,but when I restored the image
to another hard disk, I got a error message in the login screen.

It shows the lsass.exe system error,ask me to reboot into Directory recovery
mode to ceck event log.

I found some event IDs:3095,7023,7024,2005,1229 may cause this problem.

I don't know how to fix this problem,even though I switch to the original
disk, I still have the same situation. Please give me some suggestions.

Thanks a lot~~
 
In
Jerry said:
Dear all
I got a big problem.
Yesterday I use Norton ghost to backup my DC,but when I restored the
image to another hard disk, I got a error message in the login screen.

It shows the lsass.exe system error,ask me to reboot into Directory
recovery mode to ceck event log.

I found some event IDs:3095,7023,7024,2005,1229 may cause this
problem.

I don't know how to fix this problem,even though I switch to the
original disk, I still have the same situation. Please give me some
suggestions.

Thanks a lot~~
Click to expand...

Ghost is tricky with a DC or any operating system when moving it from one
hardware platform to another. Apparently whatever machine you moved it to,
the hardware is different enough where these errors occured. One example
that may apply here based on the errors you are getting (Netlogon and other
services failed) can be based on a different (newer) NIC that the operating
system does not have drivers for. At least you got lucky and got it to boot.
Check the NIC drivers and if you can, go into DSRM and update the drivers.
Look at any other hardware that didn't get installed.

As a trainer, I've used Ghost for years without problems, including on DCs,
but there are a bunch of things I must do prior to ghosting it to insure it
boots on other types of hardware, such as forcing the system to enumerate
any new hardware at boot, and copying all possible drivers of the new
machine onto it's C: drive so I don't have to go hunt down drivers, etc.

Worst comes to worse, you can always re-run Windows setup as an upgrade by
using an identical service pack integrated i386 source on the CD matching
the current service pack level. This way it refreshes the OS. It doesn't
take that long to do.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================
 
In
Jerry said:
Thanks for your great help!
Click to expand...

No problem Jerry.

For the next time to consider moving between hardware, I mentioned the
drivers being on the drive, etc, but here is one more thing I forgot to
mention. Check this article out on how to insure when you move it between
different IDE installations that you can do to force it to enumerate IDE
controllers:


314082 - You Receive a Stop 0x0000007B Error After You Move the Windows XP
System Disk to Another Computer [boot XP on different hardware]: (This is
the one I use for ghosting along with making sure VGA, NIC and Sound drivers
are on the C: drive prior to ghosting):
http://support.microsoft.com/?id=314082

(For using backup, not Ghost, to restore to other hardware):
249694 - How to Move a Windows 2000 Installation to Different Hardware:
http://support.microsoft.com/?id=249694

Ace
 
Guys, never ghost DCs - especially in production. If you do that, you'll
have a one-way USN mismatches, possible ghost objects, and security issues
because of a RID being allocated a second time, etc.

Check out Directory Services MVP Willem Kasdorp's excellent post on this
subject here:
-- http://web2.minasi.com/forum/topic.asp?TOPIC_ID=16357
 
In
Paul Williams said:
Guys, never ghost DCs - especially in production. If you do that,
you'll have a one-way USN mismatches, possible ghost objects, and
security issues because of a RID being allocated a second time, etc.

Check out Directory Services MVP Willem Kasdorp's excellent post on
this subject here:
-- http://web2.minasi.com/forum/topic.asp?TOPIC_ID=16357
Click to expand...

Paul, I realize that and would never ghost a prod DC. I used to use it with
classroom images, but specifically ONLY the instructor machine, which is the
forest root DC, PRIOR to installing the student child domain DCs and/or
member servers. This way I have a fresh start all the time and don't have to
deal with objects passed the tombstone, among a miriad of other issues. I've
been using Ghost in this fashion for classroom images for over 8 years,
including AD courses without any problems.

And Paul, I agree, as for production machines, the sytstem state should
ALWAYS be backed up and NOT ghosted.

Ace
 
Back
Top