Endpoint Protection

I have a MR4 SEPM/SEP setup and yesterday noticed a client that was supposed to be managed by my primary server was now being managed by one of my replicated servers (this replicated server is priority 2 in my management server list).  I replaced the Sylink.xml file on the client and recycled the SMC service and it showed a green dot on my primary server.

It just happened again, the client is now reporting to my replicated server.  I opened the Sylink.xml file on the client and it has the correct servers listed along with their priorities.  This client is on a slow DSL link connect directly to our WAN.  Our main server's connection is two bonded T1's with high usage around this time.  Could the client be timing out to our main server?  I have other slow link clients being managed by my main server and I'm only seeing this problem with that one particular client.

hi,

check if this client machine can communicate to the SEPM ( set in priority 1) .

if it is unable to communicate then it fall on to another failover server ( priority 2).

Pete!

Hi,

Check that you also have the IP address of primary server in management server list if that is some DNS problem.

- Jukka

Thanks for the responses!  Yes, the client can communicate with the server and vice versa (like Start/run \\servername).  Keep in mind that the previous day when I replaced the sylink file, it was communicating with the primary server.  In fact, the primary server is the client's primary DNS server.

The server names and IP address are in the Server Management List.

Still scratching my head on this one.