Forcing the Creation of Up-to-Date ERDs

Forcing the Creation of Up-to-Date ERDs
From Windows NT Troubleshooting by Kathy Ivens, Osborn McGraw-Hill, 1998

Unless your network is made up of the most phenomenally responsible users in the world, the computers on your network...

probably don't have a current ERD. You can force the creation of up-to-date ERD information for computers on your network with the Windows NT scheduler (the AT command).

The process involves several steps, and you can write a batch file (and schedule it with the AT command) that performs them all.

You'll need a share on the server (it should be a hidden share for safety) to hold the repair information for each computer, and you'll need a subdirectory in that share for each target computer for which you are keeping repair information.

For this example, the server share is named ERDShare$, and subdirectories under the share are created for each target workstation.

The AT command is AT<targetcomputer>01:00/interactive/every:M,T,W,Th,F,S,Su ServerNameERDShare$MakeERD.bat.

The contents of MakeERD.bat should be similar to this:

%windir%system32rdisk.exe /s-
net use x: /delete
net use x: ServerNameERDShare$/persistent:no
if not exist x:%targetname% md x:%targetname%
Copy %SystemRoot%repair*.* X:%targetname%*.*
net use x: /delete
exit
where %targetname% is the subdirectory for the target computer under the ERD share on the server. Keep in mind that the /s switch for rdisk tells the program to copy the SAM.

To create the actual ERD for a computer, just format a diskette on your server and copy the files from the %targetname% subdirectory.

There are a couple of things to be aware of before you rush to create this handy fuction:

  • Use full path names for all processes and steps.
  • Create a user (with administrative privileges) for this process and give that user a password that never expires.
  • Be sure the scheduler runs under the context of an administrative user.
  • Do not use the system account-it has no network access for copying files, and therefore the last step of the batch file will fail (the copy across the network to your server).

  • This was last published in November 1999

    Dig Deeper on iSCSI Management for Windows

    PRO+

    Content

    Find more PRO+ content and other member only offers, here.

    Start the conversation

    Send me notifications when other members comment.

    By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

    Please create a username to comment.

    -ADS BY GOOGLE

    SearchServerVirtualization

    SearchCloudComputing

    SearchExchange

    SearchSQLServer

    SearchWinIT

    SearchEnterpriseDesktop

    SearchVirtualDesktop

    Close