Share via

How to Force User Replicator Regeneration

  • Article

If you are troubleshooting a User Replicator issue, here's an easy way to force User Replicator to run without have to restart any services on your Front-End server. 

To force User Replicator to run, you will need to make the change in WMI.

First you need to go to Start > Run > wbemtest

Click Connect
For the namespace, enter: root\cimv2
Click Connect

Next, click on Query.

Enter the following query:

Select * from MSFT_SIPUserReplicatorSetting

Double-click on the returned value.

Scroll down until you find the highlighted value.

To edit the property, click on Edit Property.  Change the value to TRUE.  When you are done, make sure to click on Save Property and Save Object.

 

In a couple of minutes you will see the following events in the Office Communications Server event log:

Event Type: Information
Event Source: OCS User Replicator
Event Category: (1009)
Event ID: 30027
Date:  4/25/2009
Time:  12:39:18 AM
User:  N/A
Computer: LAB-OCS2K7-FE
Description:
User Replicator has started initial synchronization of domain lab.deitterick.com (DN: DC=lab,DC=domain,DC=com) and the database. Initial synchronization occurs when Office Communications Server is started for the first time, or a regenerate operation is initiated.

Event Type: Information
Event Source: OCS User Replicator
Event Category: (1009)
Event ID: 30024
Date:  4/25/2009
Time:  12:39:18 AM
User:  N/A
Computer: LAB-OCS2K7-FE
Description:
User Replicator has completed initial synchronization of domain lab.deitterick.com (DN: DC=lab,DC=domain,DC=com) and the database.  Future synchronization for this domain will occur as changes are made in Active Directory.

Event Type: Information
Event Source: OCS User Replicator
Event Category: (1009)
Event ID: 30028
Date:  4/25/2009
Time:  12:39:18 AM
User:  N/A
Computer: LAB-OCS2K7-FE
Description:
Address book (AB) entries are populated successfully during UR initial cycle for domain lab.deitterick.com (DN: DC=lab,DC=domain,DC=com).

Number of objects examined :
72
Number of objects included :
10
Number of group objects excluded since they do not have a valid email attribute:
51
Number of objects excluded since they have "hide from AB" attribute set to 'TRUE':
1
Number of objects excluded since they have "exclude from AB" attribute:
0
Number of objects excluded since they do not have any of the required attributes:
10
Number of objects excluded since they do not have "include to AB" attribute:
0

 

Once you see these events in the event log, User Replicator successfully completed a pass of your environment.

Comments

  • Anonymous
    January 01, 2003
    HI, I DID THAT PROCESS MANNY TIME'S, AND I STILL HAVING PROBLEM WITH MY OCS....COULD YOU PLEASE HELP ME WITH THAT ISSUE?

  • Anonymous
    January 01, 2003
    my mail is jguzman_reyes@hotmail.com, if you could send me information about this problem i'll appreciate, because i have 3 weeks with this problem and rigth now is generating manny issues on my company...went i create a new user, they can't singing because the ocs cannot find the user in his own pool.

  • Anonymous
    September 20, 2010
    The comment has been removed

  • Anonymous
    October 15, 2010
    Using powershell: $userRG = gwmi -query "Select * from MSFT_SIPUserReplicatorSetting where backend = '(local)\rtc'" $userRG.RegenerateCookiesNow = $TRUE $userRG.put()