Symantec in Schools

Change Managed Server

Change the Management Server

This script allows you to take a managed PC from one server to a different server.

The main issue will be if the current logged user can delete the "C:\Program Files\Symantec\Symantec Endpoint Protection\SyLink.xml" file or not.

@echo off

echo stopping Symantec End point
"c:\program files\symantec\symantec endpoint protection\smc.exe" -stop

echo deleting old link
dir "C:\Program Files\Symantec\Symantec Endpoint Protection\SyLink.xml"
del "C:\Program Files\Symantec\Symantec Endpoint Protection\SyLink.xml"
copy \\server\utilities\ai.net.nz\SyLink.xml "C:\Program Files\Symantec\Symantec Endpoint Protection\SyLink.xml"
dir "C:\Program Files\Symantec\Symantec Endpoint Protection\SyLink.xml"

echo Do you now have the new SyLink.xml file?
pause
echo starting Symantec End point
"c:\program files\symantec\symantec endpoint protection\smc.exe" -start
pause

Symantec for NZ Schools

https://fileshare.symantec.com/

User name : nzschools

Password 12/2010 : zXcv098&

Make Managed

This script is for when an existing system has had a SEPM installed and you want to update PCs to this new manager.

There are bound to be other ways to do this, but this is simple and easy and has worked for me.

Read more...

Getting updates during the holidays

Holidays are here, but let's not forget to keep your self protected during the holiday season.

Your Teachers Laptop, being at home for the next few, weeks will not be able to update it's self from the school server for virus protection.

SO

  1. To keep safe:
  2. At least one a week go to this site....
  3. http://www.symantec.com/business/security_response/definitions/download/detail.jsp?gid=savce
  4. You want to download and run the first UPDATE on this page:
  5. This is the one labeled: Symantec Endpoint Protection Client installations on Windows platforms (32-bit)
  6. Under the File Name click on the orange download link.
  7. You may be asked if you really want to do this, we do!
  8. Download this file.
  9. Run this file and answer yes as needed to update your Symantec End Point.

Read more...

Hit with a Virus

Actually more than one virus, but this is abouyt getting rid of an infection.

  • At times we are seeing symantec disabled and unable to run.
  • We see the Task Manager greyed out and unavailable.

Task Manager Greyed out:

  1. Start > Run,
  2. Type "gpedit.msc",
  3. Go User Configuration
  4. Then Administrative Templates
  5. System
  6. Ctrl + Alt + Del Options.
  7. Set Remove Task Manager to Disabled.
  8. Apply & Exit
  9. Task Manager now available.

Reinstalling Symantec

  1. Find a good copy of the setup.exe
  2. Generally I have copied from the Symantec Server to the File Server a copy of setup.exe
  3. In this case on the Symantec Update Server I have a setup.exe and used this.
  4. Right Click and click on Run as... (Installa as administrator)
  5. I have found that I could not install as the current user, even though I should be able to!
  6. Reboot and Symantec NOT THERE

http://www.symantec.com/connect/forums/microsoft-visual-c-runtime-error-sav-client-fails-start#comment-2572551

scram[wdk] you nailed it. Thank you for helping me fix this problem. Up until your post I was not aware of wbemtest so it took me awhile to figure out what to do with it.

For the sake of those you may have this problem in the future, here are the steps that corrected my issue:

• Go to a command prompt and run wbemtest
• Click the Connect button
• Replace root\default with root\securitycenter and click Connect
• You will be returned to the original screen, now click the Enum Classes button, leave the Superclass info box that appears as is (empty) and click OK
• On the Query Results screen, highlight AntivirusProduct and choose the Delete button.
• Close the Query windows and exit wbemtest
• Now either reinstall or repair Symantec Antivirus Corporate Edition

Interesting note, in my case when I re-entered the wbemtest after fixing my problem, the AntivirusProduct class no longer existed, even after a reboot. I can only guess this was a remnant of an older Symantec AV product or some other software package placed it there and it was causing a conflict with Symantec AV.

 

More Articles...