Short answer:   working as expected.

"System state" backups include whatever Microsoft designates as part of "system 
state".
That doesn't mean it includes everything in c:\windows, or in c:\program files.
There seems to be no rhyme or reason to how Microsoft creates the "system 
state" list; they've never been very good or proactive about providing methods 
for customers to do successful system recoveries.
 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Steven Langdale
Sent: Wednesday, March 09, 2011 3:35 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Windows 2003 32bit whole system restore

Hello All, a quick systemstate restore question....

Our current backup process for Win2003 is to include the systemstate but 
EXCLUDE C:\windows  from the standard filesystem backup - this is under the 
assumption that the systemstate covers all that is needed in there (for a base 
system recovery at least)

In testing a system recovery (VMware environ) the systemstate and C: restore 
work fine but after a reboot there is no network and no mouse - but the 
keyboard works :)

If we do another backup of the donor with the C:\windows INCLUDED, then do a 
systemstate & C: restore (in that order), all works perfectly after a reboot.

So, was my understanding of the systemstate backup not correct i.e. is this 
working as designed, or do I have an issue?

Client is  5.5.3.0.

Thanks

Steven