If you manage a Lync 2013 server, you probably have looked through event viewer to find this little bugger; Event 21054.<\/p>\n
You’ll notice this event is generated whenever the address book is updated with Update-CsAddressBook cmdlet or after the maintenacne that is run every day.<\/p>\n
The following is a sample of the event log information details:<\/p>\n
Users are not indexed in the database that should be.<\/p>\n
Expected indexed user count: 0<\/p>\n
Actual indexed user count: 136<\/p>\n
Cause: User replication issue.<\/p>\n
Resolution:<\/p>\n
Run Update-CsAddressBook to synchronize all accounts.<\/p>\n
How lovely, it didn’t resolve the issue. All googling will state run “debug-csaddressbookreplication” and if not indexed objects and Abandonded objects are 0 then…..
\nYou guessed it! MS favorite quote “You can safely ignore it.”
\nBetter yet MS fix this already!<\/p>\n
Jan 2018 Update<\/strong><\/em><\/p>\n I have no clue if this is still a problem, I generally don’t look in event viewer unless somethings broken. However if you are running Zenos, PRTG or some other monitoring software that ties into some windows servers event viewer, you’d have to filter it there.<\/p>\n","protected":false},"excerpt":{"rendered":" If you manage a Lync 2013 server, you probably have looked through event viewer to find this little bugger; Event 21054. You’ll notice this event is generated whenever the address book is updated with Update-CsAddressBook cmdlet or after the maintenacne that is run every day. The following is a sample of the event log information … <\/p>\n