Disable symantec5/24/2023 This will generate unique HardwareID's and sephwid.xml's for each client.īecause I have so many machines to fix this on (over 300) I was hoping to write a script that did this, as it would seem to be fairly straightforward, however I am having lots of issues disabling tamper protection from a script. Select the Tamper Protection Tab and enable.Turn On Tamper Protection by opening the client. Go to Start > Run and type SMC -Start and run.Go to Start > Run and type SMC -Stop and run.Delete any client that appears in the Symantec Protection Center.the folders will be located under C:\Program Data\\Symantec\Symantec Endpoint Protection\PersistedData\sephwid.xml In Windows XP and Windows 2003 systems C:\Documents and Settings\All Users\Application Data\Symantec Shared\PersistedData\sephwid.xml Then empty the Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC\SYLINK\SyLink\HardwareID="".Select the Tamper Protection Tab and disable.Go to Change Settings and select Client Management.Turn off Tamper Protection by opening the client.I am able to fix it manually by the following steps: All of the clients I have tested so far are able to communicate with our server as they have updated definitions, and report having successful connections, but no information can be read from SEPM. I did some research into this and it seems like it is a problem with the hardware ids on the clients being incorrect. The machines show up as we have our AD structure imported into SEPM, however the fields just say "client version unavailable," or something similiar. Recently we have finished upgrading all of our managed machines to SEP 12, and now that the upgrade is complete, I noticed that a large number of our clients in SEPM are not reporting client versions, definition versions, etc.
0 Comments
Leave a Reply. |