So let’s say we take the registry key for our Communicator x86 (Communicator x64 not available) and run it on an x86 system.
The overall process is basically the same as what Office Communications Server does, but with added flexibility of easily customizing some of the timing of the different events.
Common causes of the red exclamation point are missed calls/instant messages, Outlook integration errors, address book synchronization errors, or not having a correct Autodiscover record.
There are a couple of things to try that might fix the problem: "Address Book Synchronization Error" If you have no idea what ABS is, then it’s probably a good thing because you’ve likely never encountered this error.
For those who have seen the error, it’s probably extremely frustrating because its error description will tell you to contact your system administrator.
NOTE: Depending on the Windows Explorer settings, the SIP profile folder may be hidden, if you are unable to navigate to the path listed for your version of the Skype for Business or Lync client you will need to set Windows Explorer to Peter is an Exchange specialist with over 15 years of experience with Exchange Server and certified Microsoft Certified Master (MCM) and Microsoft Certified Solutions Master (MCSM) on Exchange Server.
He has been awarded the Microsoft MVP award, every year since 2007.
And yes, these blog entries also talk about a registry entry you can create called Gal Download Initial Delay and creating a Dword set to 0 in order to force Communicator to do an instant update.