![]() ![]() ![]() 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. ).Uninstall() A successful uninstall will return a message that ends with 'ReturnValue: 0' Note: If you have password protected client uninstallation, you should disable it first and then run the script. $computers = “pc1”,”pc2”,”pc3”,”pc4”,”pc5”,”pc6”,”pc7” Run the following command: (Get-WmiObject -Class Win32Product -Filter 'Name'Symantec Endpoint Protection'' -ComputerName. 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. Then go to the command line and run C:\Program Files (x86)\Symantec\Symantec Endpoint Protection\smc.exe -stop. Unselect the box that says Protect Symantec security software from being tampered with or shut down. Click on Tamper Protection of Client Management Settings. ![]() I already had the machines on the network configured for PowerShell Remoting, so connecting to them was not a challenge. Click on Change Settings -> Configure Settings of Client Management. 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. ![]() I did a lot of searching around for a reliable solution, most of which came back to using MSIEXEC from a command line. 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. Finally moving my last client from Symantec SEPM to Trend Micros WFBS Hosted platform. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
May 2023
Categories |