I had a Windows 2008 server that I was attempting to install the Symantec Endpoint client on, but the client would not install, and the following message was left in the event log: Symantec Endpoint Protection (SEP) Installation fails with the following error “Symantec Endpoint Protection has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.” I rebooted the server and then tried to install the client again, but the same error would appear. Ssd Easy Rider Software Definition there.
The other Web-based application runs on Apache Tomcat, which is installed automatically. Symantec Endpoint Protection Manager includes an embedded. SQL server and database, and the Symantec Endpoint Protection Manager Console. You can install the embedded SQL server and database automatically, or you can. On the database selection screen, click Microsoft SQL Server database and then click Next. You can select the embedded database with a custom configuration. Check with your SQL database administrator to confirm whether or not the automatic database maintenance tasks should be enabled. When installing SEPM, and choosing to store your data in SQL Server (2005, 2008 or 2008 R2), you will often receive Error 11501. The normal folderol is to enable TCP/IP and restart SQL. This is great if you're using the Default Instance. However, if you use a named instance (e.g. “SUPPORT SEPM”), the. 72 thoughts on “ How to fix issue with Symantec Endpoint client not installing due to a required reboot. ” Ron at 8:07 am. Thanks your fix worked great.
I found that there was a registry entry that was giving me grief with the install, and here are the instructions that I used to fix the problem. • Navigate to: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control SessionManager PendingFileRenameOperations • Back up the registry key • Delete the registry key • Install the software without restarting the computer first (Restarting the computer may result in the registry key being placed back in the registry before installation.) • Restore the registry key from the backup location. NOTE: If you are running Windows Vista look for this key – HKEY_LOCAL_MACHINE SYSTEM Current ControlSet001 ControlSessionManager PendingFileRenameOperations * Thanks to Bill for this Windows Vista suggestion. This entry was posted in, and tagged, on. Post navigation.
↓ • craig whitey I have Windows Vista Home Premium 64-bit. I ran into this problem trying to load Symantec Enpoint Protection v for 64-bit. I had deinstalled the previous version of SEP and rebooted before trying to load new version but still had this problem. Could not find any registry key values as described above. In my search on the web found someone that mentioned this problem being associated with Logitech webcam software.
Deinstalled the Logitech webcam and the Symantec load was then successful. ↓ • Jadie Great thing is, it works. Less than great thing is I still can’t push SEP from the SEP Management Server to my Windows Server 2008R2 and have a successful install. I spent a few hours on the phone with a rather rude Tech Support individual at Symantec, who walked me through a number of steps to get SEP pushed out.