Invoke-Command -Session $session -ScriptBlock īy adding in a semicolon we can of course add a second line to our ScriptBlock and make the process a little more automated. The challenge i had was that on several clients it seemed Symantec had a different IdentifyingNumber (IN), which is the GUID used by Windows to identify the product.Īs there were only 7 client machines i did a lot more of this manually than perhaps i needed to.įirstly i found the right IdentifyingNumbe r from each PC. It is considered a best practice to use the application publishers own recommended uninstaller & utility when attempting to totally uninstall a. ![]() I already had the machines on the network configured for PowerShell Remoting, so connecting to them was not a challenge. There are various ways of course to execute a command on a remote machine, you can use PSTools’, PSExec for example, but i prefer to use PowerShell where i can. For more information, please refer to the official article: Client Settings - Endpoint Protection Hope my answer could help you. Then, deploy a package and program to uninstall the Endpoint Protection client. I did a lot of searching around for a reliable solution, most of which came back to using MSIEXEC from a command line. To uninstall the Endpoint Protection client, set the Manage Endpoint Protection client on client computers client setting to No. ![]() ![]() Recently, I was pushing out an upgrade to Symantec Endpoint. It was a small SEPM deployment, only 7 clients and a server but i was surprised to be reminded that SEPM has no ‘uninstall’ tool from their console. How-to Perform a Manual Uninstall of Symantec Endpoint Protection (SEP). Finally moving my last client from Symantec SEPM to Trend Micros WFBS Hosted platform.
0 Comments
Leave a Reply. |