Skip to main content

Symantec endpoint protection deployment fails


Deploying Symantec Endpoint Protection or SEP 14 on remote computers will fail if Firewall or services on remote computer is not properly set.

Deploying SEP version 14 to computers running Windows 8.1 will not install successfully.

If ICMPV4 is not allowed on the firewall will also cause fail deployment.

Even though ICMPV4 is enabled and allowed on the firewall and the deployment still fails.

If unable to deploy SEP 14 to remote computers running Windows 8.1, either do manual installation, send a link to user and ask them to install if user has a local admin password.

Of course, if trying to install to multiple computers remote deployment is the best way to do.

It's efficient, faster and user productivity is not disturbed.

One solution for this issue, is to enable "remoteregistry" service on the remote computers.

To enable "remoteregistry" on remote computers, open an elevated command prompt and enter the domain credentials.

Type:
C:\>sc \\James_PC_001 config remoteregistry start= auto

[SC] ChangeServiceConfig SUCCESS -- this message will be shown if the command is successful.

Next step,

C:\>sc \\sg0103 start remoteregistry 

If the command is successful a message will be displayed, success command will have this output: WIN32_EXIT_CODE    : 0  (0x0)

Once the two steps above has been done, try deploying again SEP 14 to the remote computer.

If everything goes well, deployment will be successful.

Once SEP 14 has been deployed successfully, then you need to be fair to the user.

Disable or revert back the status of the remote registry to disable.

C:\>sc \\James_PC_001 config remoteregistry start= disabled

Above command will disable the remoteregistry service.

To verify, type:
C:\>sc \\James_PC_001 stop remoteregistry 

It will show that the service is not started.

The method mentioned above also works for Windows 10 clients.

If everything is set, firewall settings verified okay. Remote registry service is not running, reboot a couple of times but still fail.

Try setting a static IP, of course don't use the IP Address that was auto set  by the DHCP.  What I mean if DHCP gives the machine 192.168.1.10, try setting up a static IP like 192.168.1.111 or any IP Address not the same with the lease IP Address from DHCP.

After setting up the static IP  try deploying again.

Above method will not work only for Symantec but for any application software that requires remote registry service to be enabled.


Cheers..hope it saves some time trying to figure out why SEP 14 cannot be deployed.




Comments

  1. Endpoint Protection is a security software suite, which consists of anti-malware, intrusion prevention and firewall features for server and desktop computers.

    ReplyDelete

Post a Comment

Popular posts from this blog

Notepad++ convert multiple lines to a single line and vice versa

Notepad++ is an awesome text editing tool, it can accept regex to process the text data. If the data is in a “.csv” format or comma separated values which is basically just a text file that can either be opened using a text editor, excel or even word. Notepad++ can process the contents of the file using regex. Example if the data has multiple rows or lines, and what is needed is to convert the whole lines of data into a single line. Notepad++ can easily do it using regex. However, if the data is on a single line and it needs to be converted into multiple lines or rows then regex can also be used for this case. Here’s an example on how to convert multiple rows or lines into a single line. Example data: Multiple rows, just a sample data. Press Ctrl+H, and  on "Find what" type: [\r\n]+ and on "Replace with" type with: , (white space) --white space is needed if need to have a space in between the data. See image below, "Regular Expression" must be se

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample Outpu