Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
force ocs user replication ? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Before you try to test or verify any end user functionality, verify that the changes you made to enable users have been replicated by the Office Communications Server User Replicator. Replication has succeeded when you see event ID 30024 in the event log.

     

    How can I force the replication ?

    Thank you !

    Thursday, March 29, 2007 4:56 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually User Replicator is a variant of ADC (At least it was in LCS) that takes information from the AD and replicates it to SQL and the only way to force it was and may still be through WMI. It was done by setting the MSFT_SIPUserReplicatorSetting, RegenerateCookiesNow to True (I don't have access to my OCS test server here, so I can't verify the setting in OCS here - ping me if you can't find it)

     

    Usually the UserReplicator is really fast and it shouldn't be a problem in a test environment, but I have seen problems with it in large geographically dispersed enterprise installation, with slow lines and long replication times.

    Friday, March 30, 2007 3:42 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I use "replmon" utility to manualy replicate all server in forest.

     

    Mario.

    Thursday, March 29, 2007 8:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually User Replicator is a variant of ADC (At least it was in LCS) that takes information from the AD and replicates it to SQL and the only way to force it was and may still be through WMI. It was done by setting the MSFT_SIPUserReplicatorSetting, RegenerateCookiesNow to True (I don't have access to my OCS test server here, so I can't verify the setting in OCS here - ping me if you can't find it)

     

    Usually the UserReplicator is really fast and it shouldn't be a problem in a test environment, but I have seen problems with it in large geographically dispersed enterprise installation, with slow lines and long replication times.

    Friday, March 30, 2007 3:42 PM