Endpoint Protection

My SEPM server is running on a Windows Server 2012 R2 box.  I'm trying to do a push install to some new Windows 10 laptops that I have.  I go through the wizard, it finds the laptop on the network, I put in the credentials and it shows the push completed and was successful.  However, when I go to that machine symantec is not installed on that machine at all, doesn't show up in add/remove programs, doesn't show up in C:\Program Files (x86)\Symantec, etc.  Domain firewall is disabled, etc.  I've tried building a package with comm settings in SEPM and manually installing it on the client.  When I do that the client installs, but under Troubleshooting > Server connection status it says:

Status:  Not connected

Error:  Http error 500

It does show that it attempted to connect to the SEPM server so it clearly knows who the SEPM server is, but shows it was never successful.  Any ideas at all?  SEPM server is running 14.1 and trying to push out install pack 14.1.  Again, this only happens on Windows 10 machines.  All other Win 7 and 8 boxes work just fine.

Thanks in advance

Can you run a full Symdiag on one of these clients directly on the client after a failed push?

How to collect full support logs for Support with the SymDiag utility

This is all that it shows.  I've checked and those ports are allowed it says

I should add that the above screenshot is on a computer I maually installed 14.2.1031.0100 and attempted to import the comm settings for the SEPM server.  It still shows the HTTP error 500 as stated in my original question

And I should also add that my SEPM is still running 14.0 and NOT 14.2

Exactly which version of SEPM are you running 14.0 or 14.0.1 ?

Also which version of Windows 10 is on the laptops ? If new 1809 ?

From here

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

do you not need at least SEPM 14.0.1 ?

The SEP client compatibility is detailed here

https://support.symantec.com/en_US/article.TECH235706.htm

I have a similar issue but with SEPM 12.1.6 MP10, which as I see should be compatible with Windows 10 1803

https://www.symantec.com/connect/forums/sepm-can-not-remote-push-windows-10-1803-client-client-not-showing-sepm-manager-group?list_context_id=3377631

Thumbs up to the above responses!

I must admit, it all sounds rather odd.  The progress bar you're seeing in the Client Deployment Wizard only tracks the SEPM's ability to copy the installation files across and make registry changes.  It does not track the install of SEP itself.

This means it can take a little while for it to install, and that the SEPM's progress bar hitting 100% is not indication of a successful install, only of a successful push.

This article on Push Deployments (https://www.symantec.com/docs/TECH164327) recommends checking out the SEP_INST and MSI Logs to investigate instances when the push works but the install fails.  It links through to the below article (which should still be applicable in 14.*):

https://www.symantec.com/docs/TECH164067

On the machines on which you have manually installed SEP, please follow the below article on troubleshooting Client to Manager Comms:

https://www.symantec.com/docs/TECH105894

I also personally find the secars test quite handy:

https://www.symantec.com/docs/TECH102682

It's also worth noting that the 500 Error may just be indication that the Preferred Group (in your Sylink file) is Blocking New Clients:

https://www.symantec.com/docs/TECH208894

For more in-depth troubleshooting, you're going to need to enable logging in 14.2's Comms Module:

https://www.symantec.com/docs/TECH250061

Sorry for the late response.  I updated the SEPM to version 14.2 MP1 and immediately the version 14 clients started communicating with the SEPM.  Thanks!