locked
User replication RRS feed

Answers

  • Hi channavera,

    You should look vor events like 30024.

    https://technet.microsoft.com/en-us/library/jj204680%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396

    With get-csManagementStoreRepplication, you can check that replication of your infrastructure is oh. Should be true for all server.

    https://technet.microsoft.com/en-us/library/gg415677(v=ocs.15).aspx


    best regards Holger Bunkradt Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com. Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Alice-Wang Wednesday, February 7, 2018 1:57 AM
    • Marked as answer by channavera Friday, February 9, 2018 3:54 AM
    Tuesday, February 6, 2018 8:19 AM
  • You might want to read https://blogs.technet.microsoft.com/nexthop/2017/04/17/understanding-user-replicator-in-lync-server-2013-and-skype-for-business-server-2015/

    If you don't see 30024, just filter the logs to LS User Services and LS User Replicator and see if there's a warning. 

    Examples #1:
    A SBA server didn't exist in any AD Site and this caused for User Replicator Initial Sync to connect to a Domain Controller in a different Continent, with poor network connectivity, eventually taking well over 6 hours to Synchronize, causing Front-End Service to be in Starting Mode for 6+ Hours. A simple AD Site configuration change caused the service to start in ~ 45 minutes when the initial Sync was interrupted, and the service was restarted. With Skype for Business Server 2015, the SkipFirstSyncAllowedDowntime parameter for Set-csUserReplicatorConfiguration would have been useful.  This is one of the many reason why we recommend not to configure the DomainControllerList parameter using Set-csUserReplicatorConfiguration

    Examples #2:
    In a particular case that I handled several months ago, we found that AD replication between sites was configured to occur only between 06:00 PM and 06:00 AM in 30 minute intervals. This caused users in a site to be able to communicate with a new hire almost immediately, while it took several hours ( up to 12 hours) for users on another site to view the newly created user. Once the AD replication interval was set to perform replication in 30 minute intervals, round the clock, we a newly created user was accessible in ~ 30+ minutes from both sites.

    • Marked as answer by channavera Friday, February 9, 2018 3:54 AM
    Tuesday, February 6, 2018 10:03 PM
  • Hi channavera,

    In order to the replication status, you can run the command in SFB management shell: Get-CsManagementStoreReplicationStatus, if the value of “Uptodate” is true, it indicates that the replication is completed.

    If the value is false, please run this command force replication:  Invoke-CsManagementStoreReplication


    Best Regards,
    Alice Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Alice-Wang Wednesday, February 7, 2018 8:52 AM
    • Marked as answer by channavera Friday, February 9, 2018 3:53 AM
    Wednesday, February 7, 2018 2:08 AM

All replies

  • Hi channavera,

    You should look vor events like 30024.

    https://technet.microsoft.com/en-us/library/jj204680%28v=ocs.15%29.aspx?f=255&MSPPError=-2147217396

    With get-csManagementStoreRepplication, you can check that replication of your infrastructure is oh. Should be true for all server.

    https://technet.microsoft.com/en-us/library/gg415677(v=ocs.15).aspx


    best regards Holger Bunkradt Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com. Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Alice-Wang Wednesday, February 7, 2018 1:57 AM
    • Marked as answer by channavera Friday, February 9, 2018 3:54 AM
    Tuesday, February 6, 2018 8:19 AM
  • You might want to read https://blogs.technet.microsoft.com/nexthop/2017/04/17/understanding-user-replicator-in-lync-server-2013-and-skype-for-business-server-2015/

    If you don't see 30024, just filter the logs to LS User Services and LS User Replicator and see if there's a warning. 

    Examples #1:
    A SBA server didn't exist in any AD Site and this caused for User Replicator Initial Sync to connect to a Domain Controller in a different Continent, with poor network connectivity, eventually taking well over 6 hours to Synchronize, causing Front-End Service to be in Starting Mode for 6+ Hours. A simple AD Site configuration change caused the service to start in ~ 45 minutes when the initial Sync was interrupted, and the service was restarted. With Skype for Business Server 2015, the SkipFirstSyncAllowedDowntime parameter for Set-csUserReplicatorConfiguration would have been useful.  This is one of the many reason why we recommend not to configure the DomainControllerList parameter using Set-csUserReplicatorConfiguration

    Examples #2:
    In a particular case that I handled several months ago, we found that AD replication between sites was configured to occur only between 06:00 PM and 06:00 AM in 30 minute intervals. This caused users in a site to be able to communicate with a new hire almost immediately, while it took several hours ( up to 12 hours) for users on another site to view the newly created user. Once the AD replication interval was set to perform replication in 30 minute intervals, round the clock, we a newly created user was accessible in ~ 30+ minutes from both sites.

    • Marked as answer by channavera Friday, February 9, 2018 3:54 AM
    Tuesday, February 6, 2018 10:03 PM
  • Hi channavera,

    In order to the replication status, you can run the command in SFB management shell: Get-CsManagementStoreReplicationStatus, if the value of “Uptodate” is true, it indicates that the replication is completed.

    If the value is false, please run this command force replication:  Invoke-CsManagementStoreReplication


    Best Regards,
    Alice Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Alice-Wang Wednesday, February 7, 2018 8:52 AM
    • Marked as answer by channavera Friday, February 9, 2018 3:53 AM
    Wednesday, February 7, 2018 2:08 AM
  • Thanks
    Friday, February 9, 2018 3:54 AM
  • thanks
    Friday, February 9, 2018 3:54 AM
  • You are welcome, I am glad the reply is helpful to you.


    Best Regards,
    Alice Wang


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, February 9, 2018 5:15 AM