Endpoint Protection

I am having an issue with pushing out SEP to new clients, in that during the deployment wizard, the client login using Domain Admin accounts is no longer working.

This was working correctly for the last couple of weeks, however now I am getting a message stating that the login to <hostname (IP Address)> failed,  The client could not be installed on remote computer.

A couple of other things that I have noticed.  When I Browse Network, nothing is being displayed now.  Used to show all items on same VLAN as server.

When I search network using IP address range for a VLAN, only the IP address of the hosts are being returned, this use to show the Hostname and IP.

The only thing that has changed is that the server was restarted.  SEP was installed on the SEPM server, and I believe that the firewall on the SEPM server is blocking this authentication, but can't prove this.

Anybody have any ideas ?? Please

Is the remote registry service running on the clients?

Preparing Windows and Mac computers for remote deployment

What OS type are you pushing to?

Have you tried temporarily disabling the fw to prove it?

Hi Brian

trying to push out to a combination of XP 32bit, and W7 64bit.

I have tried disabling the firewall on the SEPM server & AD server, but still not able to browse the network, or authenticate clients.

Is there anything blocking on the client end?

No Nothing is showing.

I uninstalled SEP from the SEPM server.

This is now allowing me to do all of the above, searching for clients and authenticating.  So I am therefore assuming that the root cause of this issue is with the installation of SEP and its associated firewall etc on the SEPM server.

Any ideas as to the optimal installation of SEP on the SEPM server, or does the SEPM server even need to have SEP installed.

The SEPM server needs a SEP client. The only other thing I can think of is to check the traffic log on the SEP client on the SEPM. Perhaps you're going to need to add firewall rules to allow this traffic.

Thanks for comments  Issue is now sorted.  It turns out that the SEP version that was installed on the SEPM server was a client version of SEP and not a server version.  Whenever I installed the correct version, all is working correctly