- #SYMANTEC ENDPOINT PROTECTION 14 STAND ALONE CLIENT INSTALL#
- #SYMANTEC ENDPOINT PROTECTION 14 STAND ALONE CLIENT MANUAL#
- #SYMANTEC ENDPOINT PROTECTION 14 STAND ALONE CLIENT PASSWORD#
#SYMANTEC ENDPOINT PROTECTION 14 STAND ALONE CLIENT INSTALL#
We then deployed the uninstall via SCCM, now the unisntall does require a reboot, so we let SCCM handle that (90 minute countdown timer) and when it comes back online we hit it with a defender / firewall enablement script,ġ) Collection with query for any devices with SEP installed version less than | <- upgrade package is targeted at this collectionĢ) Collection with query for any devices with SEP installed version (this collection populates as the above package runs) | Uninstall targeted hereģ) Collection with query for no SEP products install | <- Defender enablement script targeted here The user is not forced to reboot SEP patiently waits for a reboot to enable the new version without a client. We have various versions of SEP in the estate ranging from 14.0 to 14.1, so we found wiht this new package, we could silently upgrade clients. On the SEP server, we created a package in the latest version that we were able to () and ensured that this new package belonged to a group in the SEPM heirarchy that did not require a password.
#SYMANTEC ENDPOINT PROTECTION 14 STAND ALONE CLIENT PASSWORD#
I didn't trust the SEP Server to be able to communicate a policy change to all clients, that the password was no longer required, I'm an SCCM guy so my trust lies there. So, anyone who comes across this post, this is how I did it.Īs stated by the commentor above, teh first stage was to get the clients to a state that they did not require a password. The ideal scenario would involve no interaction with the SEP central server.Īny tips or statemenmts that i've made that are incorrect. So i guess I'd like to know from your community, what is the best way to remove this product in a remote manner, under the above conditions.
Import Client Policy - I found allusions online to the ability to import a new client policy (IE: no password requirement) to a SEP client, however i haven't been able to find a command line for this, or if it applies to SEP 14 and above. However, I'm not sure if this applies to SEP 14, as the regkeys mentioned, don't exist on 14. This would be a suitable approach as it requires no interaction with the SEP central server. I found mention of a certain regkey, that when deleted, removes the password requirement from the uninstall. This is not suitable for a bulk uninstall.
#SYMANTEC ENDPOINT PROTECTION 14 STAND ALONE CLIENT MANUAL#
This appears to be a manual process, i'm unable to find any silent command parameters. The other alternative mentioned is to use CLEANWIPE. The new policy will not reach clients who are not connected via VPN The new policy will not reach 1800 clientsī. The documentation I've found mentions removing the password requirement to perform a standard uninstallĪ. There appears to be no mechanism to parse a password into the unisntall string.Ģ. Password Protected Clients -(i have the password)ġ.
I can only assume this means that 1800 devices are currently unmanaged. The other server is failing, the SEP Related services are unable to start. SEP Environment - There appears to be two main SEP Servers, one server has 1200 clients listed. So the use cases shouldn't be an issue, however I am running into the following issues Using SCCM's cloud gateway, I can easily hit all these scenarios to issue any required commands / uninstalls (the only requirement for Cloud Gateway is that the device has an internet connection). We 3 different scenarios ģ) Remote users who rarely / if ever connect to VPN (they work mostly using O365 and local applications) I'm looking to uninstall SEP 14.0 from approximatly 3,000 endpoints via SCCM, to switch over to Defender. I'm an SCCM SME and have inherited a job to remove SEP from the estate in order to switch over to Defender.
0 kommentar(er)
