A. You can schedule an ERD creation using
at \\<machine name> <time> /interactive /every:M,T,W,Th,F %windir%\system32\rdisk /s-
It may be preferable to store the contents of this disk on a location at the server, so the following batch script could be used:
net use z: \\<server name>\temp /persistent:no
if not exist z:\%computername% md z:\%computername%
copy %windir%\repair\*.* z:\%computername%\
net use z: /delete
This would then be submitted as
at \\<machine name> <time> /interactive /every:M,T,W,Th,F \\<server>\<share>\ERD.BAT
You could also just put the call to ERD.BAT in the login script so the contents of the repair disk will be updated every time the user logs on.
If you notice that the setup.log file does not always get copied to the destination. Changing the attributes to -r -s -h before copying and changing them back after seems to make the difference.
A more supported method is to use a software product such as ERDisk from www.aelita.com.
Harlan Springett also submitted the following:
From each workstation, at staggered times, call this cmd script
on the remote computer (MachineNameExample1) using the scheduler
service and run the job under an administrator's account.
Create an ERD folder somewhere on 2 networked machines
and share the folder(s) as \\MachineNameExample#\ERD$
This cmd script would be at one of them and named ERD.cmd
Set the names of these 2 machines on the 'set=' lines for
the placement of the ERD copies.
echo Backing previous ERD set to \\%ERD_PREV%\ERD$\%computername%...<br>
xcopy \\%ERD_CURR%\ERD$\%computername% \\%ERD_PREV%\ERD$\%computername%\<br>
echo Updating local system ERD set...<br>
echo Backing current ERD set to \\%ERD_CURR%\ERD$\%computername%...<br>
xcopy %windir%\repair \\%ERD_CURR%\ERD$\%computername%\<br>