This can occur in one or more of the following circumstances:

• An AD filter exists in the RM Unify AD Sync Configuration Tool but no users match the filter.
• An AD filter container points at an OU that no longer exists in Active Directory, e. g. it has been deleted or renamed.
• The AD Sync database contains a large number of users, e.g. 5,000 and the following error is present in the AD Sync log file:
  "The InnerException message was 'Maximum number of items that can be serialised or deserialised in an object graph is '65536'".
• A user listed under an AD filter shares the same "rmCom2000-UsrMgr-UPN" AD attribute value as another user in Active Directory. This will be seen on CC4 sites. 

1. In the RM Unify AD Sync Configuration Tool, double-click the AD Filters node to display all AD filters.
2. Double-click the first AD filter.
3. Click the Users node. Users matching the filter will be listed in this node.
4. If the Users node is populated with users, do nothing.
5. If the Users node is empty, right-click the AD Filter and select Delete AD Filter.
6. Repeat steps 2-5 for each AD filter.
7. Wait five minutes and you should find that the Resync status will be returned to 'None scheduled'.

1. In the RM Unify AD Sync Configuration Tool, double-click the AD Filters node to display all AD filters.
2. Click the first AD filter.
3. In the 'Select the Active Directory' section, confirm that the path to the container is still valid.
4. Repeat these steps for each AD filter.
5. If you find an invalid path, you will need to reinstall RM Unify AD Sync with a clean database following the instructions in TEC5015612 in the Other Useful Articles section below.

1. On the AD Sync server, browse to C:\Program Files (x86)\RM\RM Unify AD Sync\LogFiles.
2. Using Notepad, check the three most recent .csv files for errors, including "The InnerException message was 'Maximum number of items that can be serialised or deserialised in an object graph is '65536'".
3. If errors are found, please contact RM Cloud Support for further assistance.

1. Log on to RM Unify as a Super Admin user.
   Important: If you have a multi-site AD Sync installation syncing from a shared AD, you must log on to your parent RM Unify establishment. If you are unsure whether your establishment is part of a parent/child cluster, please contact RM Support.
2. Select Management Console.
3. Select 'Sync users from AD'.
4. In the 'AD Sync Service Registration Code' section, click 'Change registration code'.
5. Note the new AD Sync Service Registration Code.
6. On the RM Unify AD Sync server, open the RM Unify AD Sync Configuration Tool.
7. Expand RM Unify Registrations.
8. Select your site, the 'Organisation code' and 'Registration code' fields should show on the right-hand side.
9. Enter the new registration code into the field.
10. Click Save, followed by the Register button. After a short pause, the Successful Registration window opens.
11. Click OK.

1. Download the 'findduplicates.txt' file from the Download section below.
2. Rename the file to FindDuplicates.ps1.
3. On a domain controller, open Windows Powershell ISE.
4. Click File, Open and select the FindDuplicates.ps1 file from step 2.
5. Click Open.
6. Click View, Show Script Pane.
7. Click Run Script from the toolbar (or select File, Run).
8. View the screen output. If the duplicates are shown, open the file:
   c:\RMUnifyDuplicates\RMCom2000Duplicates.txt.
9. Please contact RM Cloud Support for further help with ensuring the correct network user account is linked to the right RM Unify user.