- REMOVAL STATUS 1603 REMOVING SYMANTEC ENDPOINT PROTECTION PATCH
- REMOVAL STATUS 1603 REMOVING SYMANTEC ENDPOINT PROTECTION UPGRADE
- REMOVAL STATUS 1603 REMOVING SYMANTEC ENDPOINT PROTECTION SOFTWARE
- REMOVAL STATUS 1603 REMOVING SYMANTEC ENDPOINT PROTECTION CODE
REMOVAL STATUS 1603 REMOVING SYMANTEC ENDPOINT PROTECTION PATCH
I seemed that the patch failed to apply and now windows has SEP listed in the installed programs list twice. The 32bit version of the patch applied without issue but when I applied the 64bit patch I ran into mayor issues after reboot. I was informed by a technician at DEECD that the bug was resolved in SEP 12.1 RU1 MP1. For more information on the bug visit the Symantec website. This was rather annoying as some of my servers have up to 4 network interfaces of which not all are used and need to remain disabled.
REMOVAL STATUS 1603 REMOVING SYMANTEC ENDPOINT PROTECTION UPGRADE
I installed the upgrade onto one of my Windows 2008 R2 servers at work and found a bug which enables all network interfaces, including disabled ones at boot. Our schools were recently informed to upgrade SEP 12.1 RU1 from SEP 11. The EPR tool is intended as a last resort tool.Within Department of Education and Early Childhood Development (DEECD) schools also known as Victorian Government schools we run Symantec Endpoint Protection (SEP) for our Anti-Virus program. McAfee does not recommend using the Endpoint Product Removal (EPR) tool as your primary method for uninstalling our products nor as a step in your upgrade process. In regards to this tool, we'd like to make you aware of the following KB and advise you to read it in full: You can find this in your product downloads under "Utilities and Connectors". One thing you may want to try - if this is only happening on one machine - is using our Endpoint Removal Tool to help you clean up the system. If you need assistance, please gather a MER from the machine in question and upload it to a new service request for review. With the error seen here you can search our knowledge base for known issues. The first entry you find shows you point of failure. If you do see 1603, then scroll back up to the top of the log file and search for “value 3” (the word value may be different depending on log language).“return code: 1603” (all MSI installation error codes are listed here, (v=vs.85).aspx)
REMOVAL STATUS 1603 REMOVING SYMANTEC ENDPOINT PROTECTION CODE
ThreatPreventionInstall.log and scroll to bottom, you will see the installation failure code i.e. Open the first installation related log i.e.Open the installation log location (see below) and sort files by date and time > look when installation was first attempted.You can also do this yourself - here is a short troubleshooting guide: To troubleshoot installation failures, we would need to look at the installation logs and see why the installation is failing. We would need to look at the installation logs locally. The failure message in ePO doesn't provide enough information for us to see why the installation is failing. It also has the capability to repair corrupt installations - so may be of use to yourself. With this information, you can plan and implement product upgrades efficiently throughout your environment. With EUA Package Creator you can create a custom deployment package that includes all products that need to be upgraded in a single, one-click deployment task via EUA Upgrade Automation. Similarly do you know what the installation fails with when you try to upgrade to a newer version?Īre you performing the upgrade via a regular product deployment task or via our EUA (Endpoint Upgrade Assistant)? In case you are unaware of our EUA Tool - This assistant will help you with your upgrade. It analyses the endpoints in your ePO environment, detects the supported McAfee products that are installed, and determines the minimum requirements for upgrading to current versions of the products.
REMOVAL STATUS 1603 REMOVING SYMANTEC ENDPOINT PROTECTION SOFTWARE
Hi do you see when you try to uninstall the software locally? Either via add/remove programs or via msi string (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432\Network Associates\ePolicy Orchestrator\Application Pluggins\END_?_10XX > there is a value for uninstall string)