We have a major issue today. I ran a script to change sylink.xml files on about 3000 systems that had communication issues. Now, most of these machines when rebooted come up with missing hal.dll errors. Here is the two scripts that I pushed form the Dell Management Console.
The Task first runs:
Echo Off
REM -- Script to change Syslink File within Symantec Endpoint Protection Client
REM -- Last modified April 22nd, 2010 by Kris Turner
Echo Checking for Syslink.txt file on local drive.
If Exist C:\Sylink\sylink.xml goto :End01
:Script
Echo Creating directory and copying files.
C:
mkdir C:\Sylink
CD C:\Sylink
copy \\dstmgtsvr\softwarelibrary\sylink\*.* "C:\Sylink"
Echo Now Running SylinkDrop.
SylinkDrop -silent -p ######## sylink.xml
goto :End02
:End01
Echo File sylink.xml exist.
goto :End02
:End02
Echo Script is complete.
Exit
Then it runs:
:DELETE
C:
del C:\SYLINK *.*/Q
rmdir C:\SYLINK
:End
Exit
I am not sure if the SYLINKDROP app would do anything to system32 files? I have never seen this before. Also, the 2nd script shouldn't be deleting any system files as well. Can someone verify that my theory is correct?
I have about 800 plus and counting systems coming back with the missing hal.dll file now.
Need help!!!!!!