In the SEPM client view - after a disaster recovery dry run - I have different behavior than expected. Not all clients are shoing as "online" and the clients themselves are missing their green dots. The few clients that have done a sylink.xml on do not show up in the manager after the fact. 

I've followed these instructions for creating the backups and performing the recovery. http://www.symantec.com/docs/TECH102333 In my case we did not want to restore from a backup database, but have the clients themselves repopulate it, to try to elimate issues with erroneous reporting.

I can see the time the clients last talked to the server, and they seem to connect, but not stay connected. Not sure what to think at this point. Running 11.0.73 on Windows 2008 R2.

Thanks in advance for your help!!

Have you tried manually replacing the sylink file?

You can can enable sylink logging to see whats going on

How to enable Sylink debugging for the Symantec Endpoint Protection 11.x and 12.1 client in the Windows Registry

Hello,

How many clients are facing the issues with?

What OS are these clients (in question) running on?

Could you please upload us the sylink.log from these client machines which would help us understand the root cause of the issue - 

How to enable Sylink debugging for the Symantec Endpoint Protection 11.x and 12.1 client in the Windows Registry

http://www.symantec.com/docs/TECH104758

Hope that helps!!

Did you restore the JKS file?

http://www.symantec.com/business/support/index?page=content&id=TECH102547

Afternoon - Manually replacing the sylink file unfortunately does not make the clients appear in the management console. All clients that I can see have the old sylink from the previous server. No issues before using the sylink to regain communications. The JKS file has been restored along with the Domain ID from the previous Server install. There is no continuity between OS versions and the client behavior. Our landscape consists of Professional versions of Windows from everything from XP to 8.1 (only a couple 8's and 8.1 machines) Most PCs running are XPs, Window 7's, along with several Windows 2008 & 2008 R2 machines. I would say the clients communicate briefly with the server, but either only a certain percentage stay, or only for a certain timeframe. I cannot get them all to show "online" at the same time. The last status change for every PC in the console is within the last hour though.

Can you post the sylink debug log file for review?

Now neither one of the servers is communicating well with the clients. I have been asked to concetrate on the older server and get it properly working again before moving on with the issue on the new one. Here is my sylink debug log file. I'm still having issues connecting new pcs using the sylink file to the server. An "update policy" command issued on the client side helps bring some of the clients back online but doesn't work for all. I've also been told this was unacceptable and that the server should be gaining the commucations by itslef without client intervention. Is there a way to force the clients to update their Policy not just the content and have them connect and appear online from the server?

Recap - I need to update the policy from the server, without intervention on the clients; is this possible and how?

Not all clients are communicating even after "update policy" on the tested pcs, or using the sylink.xml file.

I've attached the debug log. I have a much larger one going over several hours if there is no useful information from this one.

Thanks in advance for all your help and support!!!!

-Travis 

Attachment(s)

sylink_Nov182013-2.txt   199 KB 1 version