Endpoint Protection

Updated SEP to 12.1.6.1a build to allow install on Windows 10 Enterprise LTSB evaluation. After it was installed, the client never appeared in SEPM. In looking at the client, it looks like the firewall exceptions for Symantec Antivirus weren't created. SMC and SNAC were created. I've tried both the full and reduced size installs. I can manually add the RTVScan entries, but shouldn't those entries be added by the install, like it did for SMC/SNAC? Is this why it's not showing up in SEPM?

RTVScan does not exist in 12.1 so there would be no exceptons for it.

Should have nothing to do with why it's not reporting. Post the sylink log to see what's going on. All comms happen over tcp 8014

I'm having trouble generating the sylink log. Windows 10 won't let me modify the registry. I'll get the log posted for you asap.

You can also run the symhelp tool to troubleshoot

Troubleshooting computer issues with the Symantec Help support tool

It's a DNS issue, specifically the system is unable to ping the server by name. The help tool was also unable to contact the server by name, but it was able to find the server using the FQDN. I'm sure this issue is related to the unique network setup I have currently, but it brings up another question. The tool obviously found the server by using the FQDN vs. NETBIOS name of the server. Why doesn't SEP do the same, and is there a way to get it to look for the server by FQDN?

May be this document will be usefull

https://support.symantec.com/en_US/article.TECH103175.html

 

 

I've set the Managment list already to specify the FQDN and the IP address of the SEPM server already. When I deploy the client to the Windows 10 system, I pick the container that has that management list assigned. Once the client is installed, the Symantec Help tool reports the NETBIOS name fails but the FQDN succeeds. The management list is assigning IP address and FQDN, so what the client sees isn't what the server list is set for.