Set-CsUserReplicatorConfiguration -Identity global -ADDomainNamingContextList Remove domain Use the following commands: # Add domains If there are some domains that you don’t want to replicate to the Lync Address Book, use the ADDomainNamingContextList parameter (Set-CsUserReplicatorConfiguration) to add only the domains you want to synchronize. After changing the AbAttribute table, make sure you run Update-CSAddressBook to regenerate the address book.īy default all domains that are found will be replicated and will be replicated alphabetically from A to Z. For more information regarding the attributes and flags see: Administering the Address Book Service, Lync 2013. You can control the AbAttribute table by using the ABSConfig.exe tool ( Lync 2013 Resource Kit).
![outlook and skype for business not syncing outlook and skype for business not syncing](https://i.ytimg.com/vi/99t-zICnMo4/maxresdefault.jpg)
This flag determines what happens with translation between AD and the AbUserEntry table or, if a certain AD attribute is present, to include or exclude the user from adding it to the AbUserEntry table. With each attribute a flag is also present. If this table is empty the User Replicator will skip the AbUserEntry filling process (no users in the Lync Address Book). What kind of data is placed in the column is defined by the entries in the AbAttribute table. The table AbUserEntry is used to store this information and it contains two colums, one for the UserGUID and one for all the UserData. This information is retrieved from AD by the User Replicator and placed in the user database into the RTCab database. I don't get why they can't change a friggin name, but they can't (or rather, WON'T).Information about your Users, Contacts and Groups is stored in Active Directory (AD). There is no cmdlet to modify it, no xml file to change, nothing. Microsoft holds the keys because they own the server. Unfortunately there is NO way whatsoever for an admin to change the Favorites contact group name. As long as users don't mind ignoring the S4B client's favorites group and using the "Pinned Contacts" group for all their favorites, no harm no foul. It's crap that we even have to do this, but the workaround works. ALL you have to do is create a new contacts group named "Pinned Contacts", add your desired contacts into that new group and - Voila! - your contacts show up in the VVX phone's "Favorites Group" and on your home screen shortcuts.
Outlook and skype for business not syncing update#
They repeatedly told me I had to go back to Polycom to have them update their firmware. This is an issue strictly for Polycom/Skype For Business Online users. I had to do ALL of this research on my own, Microsoft was no help.
![outlook and skype for business not syncing outlook and skype for business not syncing](http://injelea-blog.de/wp-content/uploads/2015/07/Skype4B_Meeting_06_Outlook_Neues_Meeting_Link.jpg)
3 out of 10 of my users, all created within 15 minutes, are set for "Pinned Contacts", while the other 7 are "pinnedGroup".
![outlook and skype for business not syncing outlook and skype for business not syncing](https://www.moh10ly.com/wp-content/uploads/2020/06/image_thumb.png)
The other fun part of this is the decision to name the Favorites group "Pinned Contacts" or "pinnedGroup" appears to be arbitrary. Unfortunately, it appears they have NOT informed Polycom of this change, as the latest UC firmware (5.5.1) still does not recognize the S4B favorites - the VVX phones are looking for "Pinned Contacts". For some unknown reason (microsoft would NOT tell me) they started creating user profiles with the "Favorites" group being SOMETIMES represented by "pinnedGroup" and SOMETIMES by "Pinned Contacts". In the server's XML schema, "Other Contacts" is represented with a tilde "~", and "Favorites" is represented by "Pinned Contacts". User profiles, when they are created, have two contact groups made by default: "Other Contacts" and "Favorites". (THIS IS ASSUMING YOU HAVE AN ALL-CLOUD SOLUTION FROM MSFT) The issue is completely Microsoft's. To be honest, it's so simple (as a workaround) that I don't know why I didn't think of it earlier.įirst - a root cause analysis. After much consternation and back and forth with microsoft, I found the fix.