How to update Emergency Repair Disk information from the command line in Win2k?

[Spin]

In WinNT, one can run the following command to update Emergency Repair Disk
information to the local hard disk:

Rdisk /s-

What is the Win2K equivalent command to do this?

--

 

[Steve Parry [MVP]]

You can backup your reg and create the ERD by going to;
Programs|Accessories|System Tools|Backup, then choose ERD, then if
you check the box for "Also backup....", then the reg will also be
backed up to %windir%\repair\RegBack
leaving the
%windir%\repair\
directory files intact as original installation.

quick question Dave, how do you achieve this if you have a
laptop without a floppy drive ?

 

[Dave Patrick]

A couple of ways would be to backup the system state or use regback.exe from
the resource kit.

 

[Dave Patrick]

Interesting ... so I suppose that overwrites the original as installed
backups in;
%windir%\regback

I'm wondering what the recovery console does with this.

 

[Steve Parry]

Interesting ... so I suppose that overwrites the original as installed
backups in;
%windir%\regback

I'm wondering what the recovery console does with this.

yes it appears to

--
Steve Parry

http://www.gwynfryn.co.uk

http://wrexhamseals.tripod.com

 

[Ricardo M. Urbano - W2K/NT4 MVP]

Steve, I was shocked at the omission of rdisk in W2K too, when I first
made the move and I tried the same thing you did, but I quickly noticed
that running the ERD from ntbackup vs. rdisk updated different files in
%SystemRoot%\repair.

I decided then that I couldn't count on the NT4 rdisk since I presumed
that the W2K recovery process worked differently than that of NT4.

Instead, the best compromise I have found is to schedule a SystemState
backup and then a batch that runs right after it to copy the contents of
%SystemRoot%\repair\regback to %SystemRoot%\repair.

I've actually never had to resort to it yet, so I don't know if it will
work the same, but I felt more comfortable w/ that than using rdisk or
nothing at all!

 

[Steve Parry]

Steve, I was shocked at the omission of rdisk in W2K too, when I first
made the move and I tried the same thing you did, but I quickly
noticed that running the ERD from ntbackup vs. rdisk updated
different files in %SystemRoot%\repair.

I decided then that I couldn't count on the NT4 rdisk since I presumed
that the W2K recovery process worked differently than that of NT4.

Instead, the best compromise I have found is to schedule a SystemState
backup and then a batch that runs right after it to copy the contents
of %SystemRoot%\repair\regback to %SystemRoot%\repair.

I've actually never had to resort to it yet, so I don't know if it
will work the same, but I felt more comfortable w/ that than using
rdisk or nothing at all!

thanks for the input Ricardo .. I'll check it out ... thanks

--
Steve Parry

http://www.gwynfryn.co.uk

http://wrexhamseals.tripod.com

 

[Ricardo M. Urbano - W2K/NT4 MVP]

Wasn't aware of it, that's why ;->

When I switched over, I posted in this NG essentially asking the same
thing: WHERE'S RDISK?!?!?!

The thread covered many things, but not regback. Does its backup work
w/ the recovery process and/or can I just restore these backups from the
Recovery Console?? I'll look into it.

The way I look at it, though, w/ the SystemState b/u, I also get the
added benefit of a backup of the system32 folder.

All my W2K servers and workstations run a SystemState once a month. The
entire repair folder is then copied up to a network share, and then the
regback folder is copied to repair. I save my bkf file in the regback
folder, but exclude it in the copy to the repair folder.

Ricardo,
If all you wanted was the registry backup, why not use regback.exe from the
resource kit?

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

Steve, I was shocked at the omission of rdisk in W2K too, when I first
made the move and I tried the same thing you did, but I quickly noticed
that running the ERD from ntbackup vs. rdisk updated different files in
%SystemRoot%\repair.

I decided then that I couldn't count on the NT4 rdisk since I presumed
that the W2K recovery process worked differently than that of NT4.

Instead, the best compromise I have found is to schedule a SystemState
backup and then a batch that runs right after it to copy the contents of
%SystemRoot%\repair\regback to %SystemRoot%\repair.

I've actually never had to resort to it yet, so I don't know if it will
work the same, but I felt more comfortable w/ that than using rdisk or
nothing at all!

Steve Parry wrote:

 

[Ricardo M. Urbano - W2K/NT4 MVP]

Kewl! Thanks a bunch!

Yepper; recovery console, parallel install, ntfsdospro, or possibly others.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

Assuming you can boot, or do you mean from the Recovery Console??

 

[Spin]

So gentlemen, is there any command-line way to update the Repair Disk
information anymore at all?

--

Kewl! Thanks a bunch!

Yepper; recovery console, parallel install, ntfsdospro, or possibly others.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

Assuming you can boot, or do you mean from the Recovery Console??

 

[Dave Patrick]

Probably about all of your options were touched on somewhere in this thread.

 

[Spin]

I'm now looking for a good command-line script which will back up the system
state data to a central server. Since system state data covers System32
files and Repair folder files.

--

Probably about all of your options were touched on somewhere in this thread.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

So gentlemen, is there any command-line way to update the Repair Disk
information anymore at all?

 

[Spin]

Guys, all I need is a one-liner batch script to back up the system state
data. Somebody, please tell me what that is.

--

Or you could just schedule it.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

I'm now looking for a good command-line script which will back up the system
state data to a central server. Since system state data covers System32
files and Repair folder files.

 

[Enkidu]

Use NTBackup and schedule it to run at a certain time.

NTBackup will backup the system state. That's what I think Dave meant.

If you want to use a script, look here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314844

Cheers,

Cliff

Guys, all I need is a one-liner batch script to back up the system state
data. Somebody, please tell me what that is.

--

Or you could just schedule it.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

I'm now looking for a good command-line script which will back up the system
state data to a central server. Since system state data covers System32
files and Repair folder files.

 

[Jerold Schulman]

Guys, all I need is a one-liner batch script to back up the system state
data. Somebody, please tell me what that is.

See tip 2500 in the 'Tips & Tricks' at http://www.jsiinc.com

Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com