Hello,

I use "websearch only" for "addressbookavailability". This is working fine on all client.

I have a problem with changes in active directory. When we change for example "job title" of someone then the old "job title" stays present on lync client. When i do a reset of the client of a new installation the new "job title" is present.

Although we use "websearch only" for some changes it seems that the local address book of lync is still used.
Does someone know how i can force a lync client to also query active directory for this.
I know that the lync server updates every night but on many clients the local address book is not updated.

Regards

You still can force the Addressbook replication by running update-csuserdatabase and update-csadressbook. I suggest you delete the .slab files from Lync share web folder 0000000\000000 folder and then run above command. that will create brand new set of files. the delete the sip folder from client PC and then restart the client to force download the local copy. see if that fix your issue.

Hi Yarisken,

You can run Update-CsUserDataBase to force Back-End to re-read all the user-related information stored in Active Directory Domain Services.

Best regards,

Eric

You still can force the Addressbook replication by running update-csuserdatabase and update-csadressbook. I suggest you delete the .slab files from Lync share web folder 0000000\000000 folder and then run above command. that will create brand new set of files. the delete the sip folder from client PC and then restart the client to force download the local copy. see if that fix your issue.

Hi Yarisken,

You can run Update-CsUserDataBase to force Back-End to re-read all the user-related information stored in Active Directory Domain Services.

Best regards,

Eric

Hello Eric,

This is not working. The cache on the local computers is not updating.

You don't have to clean up the .slabs files al the time. And can you check whether the client can access the Addressbook services in FE server?. Can you try to access <a href="https://>FE">https://>FE Pool FQDN>:443/ABS/Handler and see if you can reach the server. You should get some response from the server. It shouldn't be "Page cannot be displayed"

You don't have to clean up the .slabs files al the time. And can you check whether the client can access the Addressbook services in FE server?. Can you try to access <a href="https://>FE">https://>FE Pool FQDN>:443/ABS/Handler and see if you can reach the server. You should get some response from the server. It shouldn't be "Page cannot be displayed"

Hi Yarisken,

Based on my understanding, if the GALcontacts.db and GALcontacts.db.idx files exist, the Lync client will always search the contacts from them first even the client policy is configured to websearchonly.

Best regards,

Eric

Hi Yarisken,

Based on my understanding, if the GALcontacts.db and GALcontacts.db.idx files exist, the Lync client will always search the contacts from them first even the client policy is configured to websearchonly.

Best regards,

Eric

Hi Yarisken,

Based on my understanding, if the GALcontacts.db and GALcontacts.db.idx files exist, the Lync client will always search the contacts from them first even the client policy is configured to websearchonly.

Best regards,

Eric

• Marked as answer by Eric_YangKModerator 1 hour 21 minutes ago

Hi Yarisken,

Based on my understanding, if the GALcontacts.db and GALcontacts.db.idx files exist, the Lync client will always search the contacts from them first even the client policy is configured to websearchonly.

Best regards,

Eric

• Marked as answer by Eric_YangKModerator 18 hours 5 minutes ago