* Please don't suggest ghosting, normal file-backups, or reinstalling
Windows.
-Backups- Normal file backups have nothing to do with System State.
-Ghosting- the problem with ghosting is that the rollback of a ghost
rolls back user files as well, which we don't want. the advantage of
System State restore is that it preserves new user files. Ghosting
could only restore a prior System State, while preserving user files,
if the user files are stored on a hard disk separate from the
operating system. I don't have that luxury.
-Reinstalling- Reinstalling Windows is not an option, because it would
not include all my favorite software, user accounts, and preferred
config settings. Reinstalling Windows is time-consuming. If
reinstalling Windows was a smart solution to a minor corruption in the
OS caused by bad software or a virus, then Microsoft would not have
created System Restore.
* boot files (i need to find out exactly which ones)
* COM+ class registration database
* The registry
* Event logs
* System files (i need to find out exactly which ones)
* Windows File Protection files that are stored in \dllcache (all
of them?)
* IIS configuration files (i need to find out exactly which ones)
* Windows Management Instrumentation Database
* some weird system files with filename extensions from a long
list of "monitored extensions" (i need to find out exactly which ones)
* local user profiles.
I read about ntbackup, which is included on the Windows XP CD. It does
include a System State backup option. It is not officially supported
on Vista. It might work-- I have to experiment. Some caveats:
ntbackup requires the Removable Storage Management/ Removable Storage
Service feature to be enabled in Vista. This feature is not turned on
by default. To do this, go to Control Panel | Programs and Features |
Turn Windows features on or off, and select Removable Storage
Management.
==========
Must turn off "use Shadow Copy" in backup advanced options
==========
Differential restore points wont work on vista system files because
Vista seems to block ntbackup.exe and even administrators from
changing the archive attribute flag in the system32, Windows and other
security protected folders.
if i have to accomplish this manually, then i need to figure out how
to backup and restore all of the individual items normally included in
System State (list above).
For example, the COM+ class registration database. The Component
Services console (comexp.msc) does not have import/export function.
How then could one backup and restore the COM+ registration database?
Could one achieve this entire goal simply by ghosting just the Windows
System folder and Program Files folder?
One drawback of this method is that my Windows folder is 16 gigs and
my Programs folder is another gig, so that's a lot of storage space (4
DVD's). Still, if it works, it would probably be the easiest, simplest
solution.
>As many have complained about, Vista System Restore deletes old
>restore points to make way for new ones.
>
>We'd like a way to preserve restore points indefinitely, save them to
>removeable storage, and rollback anytime to any prior restore point.
>
>So, i'm exploring this. It cannot be done with Vista System Restore.
>How can it be done?
>
>Results of my research below.
-erunt holds the same complete system state that windows system
restore holds? I read it just backs up the registry.
-erunt backups expire after 30 days? I see nothing about expiration in
the helpfile. If you're using the optional autoback.exe daily backup
program, that keeps the last 30 days. Otherwise, I read that erunt
backups can be made whenever you want, stored wherever you, for as
long as you want, and restored whenever you want.
DIY System Restore With Saved History 
Linear Mode
