Symantec endpoint client not updating

Their methods are low tech and highly effective: Last year, 71 percent of attacks began with spear phishing.

Although the number of organizations subject to targeted attacks is low, the risks posed are quite high.

The solution here is to delete your existing local Lync address book files and force the download of new ones from the server: I have seen this work many times in production deployments.

Read The Executive Summary A meteoric crypto currency market triggered a gold rush for cyber criminals.Detections of coin miners on endpoint computers increased by 8,500 percent in 2017, with Symantec logging 1.7 million in December alone.Four common problems and their solutions are listed below.1] The Persistent Message “” in the Lync Client When the Lync client is run for the first time it chooses a random time between 1 – 59 min to download the Lync address book (from the FE server).The ‘URL from Server’ gives the internal and external URLs of the address book service.

You can test the address book via the web service using the Test-Cs Address Book Service and Test-Cs Address Book Web Query cmdlet’s.

The random time is to prevent network storms if a lot of Lync clients are being deployed at the same time.

If you have had the Lync client running continuously at any time for more than 2 hours and this synchronization message is still displayed, there is likely an issue.

If you cannot map the Lync address book network share from more than one client and are running Symantec Antivirus, this is a possible cause.

This Microsoft KB article provides the details and the solution: Unable to access Shares “The specified network name is no longer available” when Symantec Endpoint Protection prior to 11.0.4202 (MR4-MP2) or Symantec Antivirus 10.2 are installed on a Windows 2003, 2008 or 2008 R2 Server.

network access), permissions, or address book configuration on the Lync server.