The initial "root dispersion" was low (see above), indicating that the FE Server 'thought' that its local clock was pretty much synced with the DC clock - obviously it wasn't, but I'm not sure why this was the case. Check no shows that the Poll interval has risen to 11, so I guess this rises over a period of time if the client thinks that synchronisation is OK. Checking the "W32tm /query /status" again revealed the the Poll interval had changed from 15 to 10, ![]() I ran a "W32tm /resync" on the Lync FE, and over a period of time (about an hour), the synchronisation started coming back into line. All other member servers seemed to be synch correctlyĬ:\Windows\system32>W32tm /query /status Leap Indicator: 0(no warning) Stratum: 4 (secondary reference - syncd by (S)NTP) Precision: -6 (15.625ms per tick) Root Delay: 0.0686951s Root Dispersion: 0.1420435s ReferenceId: 0x892CACD1 (source IP: 111.111.111.111) Last Successful Sync Time: 09:14:46 Source: Poll Interval: 15 (32768s) The DC time was correct and syncing to a local NTP server, but the time difference was still large. This was over 2 minuets out from the DC's, however, when I checked the "W32tm /query /status", all looked OK - the Lync server was pointing to On coming across this thread this morning, I checked the time synchronisation on the FE (SE) server. Looks like you are already signed in on too many devices" From a users iPhone, I can see in the logs messages such as: "You've been disconnected because you're signed in to Lync in too many places"Īnd "We can't sign you in. Last night, clients were signed out of Lync (both mobile and desktop) with similar errors. Interestingly, I have just seen a similar issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |