I'm at a loss here and really frustrated...

I just want to know what's the best way to recover from a 2000/2003 server
that won't boot due to Windows corruption... and this is, of course, assuming
safe mode/directory services restore/last know good configuration all don't
work.

I know you can create an ERD for 2000 that contains information for
repairing or replacing corrupt or missing system files... and it can also
repair registry hives... is this an ideal recovery plan for a 2000 Server? 
Is this the only viable alternative to a reformat/reinstall?  I also know you
can do a Windows repair

Also... what about 2003 Servers?  They don't use ERDs; they use Automated
System Recovery (ASR).  I looked in to this and it seems that it does more
than create a standard ERD.  It creates an ASR media set that reformats and
recreates the system and boot partitions... which means any additional
partitions on the same disk will be deleted.  I don't like the sound of this
because it means you'd need to do a full restore of all non-system files in
order to bring the server back up to speed... isn't there a way to create an
ERD for a 2003 server that will look for and repair missing/corrupt system
files and registry hives that would be preventing it from booting?  ...or is
there another method of recovering Windows Server 2003  without having to do
a reformat/reinstall?

ANY HELP IS GREATLY APPRECIATED!!!  Thanks...

mike wrote:
<cut>> I just want to know what's the best way to recover from a
2000/2003 server
<cut>
Well is there any clue why the system won't boot, error messages beeps
or whatever? If you have no clue what is happening you can (assuming
it's not a RAID array) always place the disk in a working installation
and do file comparison and safe some files you like to have but can not
use the backup.
After that I am afraid you have to do a repair install, it gets the
system booting and safes most 3d party stuff but don't expect a stable
system, plan a clean reinstall right ahead.

But that is my experience ymmv.

Okay...

What you don't know is I don't currently have a 2000/2003 server that won't
boot due to Windows corruption.... I'm asking WHAT IF I had a server that
wouldn't boot... what would be the most ideal way of recovering Windows?

I'm trying to develop a recovery strategy for dealing with Windows
corruption, that's all.  Thanks.

Show quoteHide quote

mike wrote:
<cut>

My strategy for this kind of situation is:
Keeping as much as possible user/changing data on a separate partition
(in my case d:), set the dump & pagefile to a separate partition (in my
case s:( s stands for swap) I also use it for temp stuff).
Create a ghost boot disk/CD and dump the c partition on s and on a
network share.
Then I write on the disk/CD the location of the latest dump (do them
regular) and tape the disk/CD on the side of the case.

But that is when I only have limited resources, now that I have more
stuff I have user/changing data on a vss and backed them up with gf/f/s
scheme. Services are installed on multiple servers ( fail-over if
available) and are kicked on when the other system fails.
Of course my performance sucks when a server has more to do then
original planned but at least I still have my service available.

However now I am migrating almost my entire server systems onto a
virtual server concept and role out a service based infrastructure.

Restart a Windows 2003 server via scheduled task without no user is logged on
Disconnect Network Drive
Will using ASR delete all other partitions?
Stopping more than one loging
SERVER REBOOTS
W98 print server but no driver for W2K
Access to W2K server across WAN
Can't add http://*.windowsupdate.com in to trusted sites
Server 2003 & XP Home network share
How do I report bugs in Windows Server 2003?