Active Directory user objects such as "mDBUseDefaults" may have corrupt values, preventing a synchronization in Enterprise Vault for Exchange.

Article:TECH48899  |  Created: 2007-01-16  |  Updated: 2007-01-16  |  Article URL http://www.symantec.com/docs/TECH48899
Article Type
Technical Solution

Product(s)

Environment

Issue



Active Directory user objects such as "mDBUseDefaults" may have corrupt values, preventing a synchronization in Enterprise Vault for Exchange.

Error



Synchronization Failed

Solution





Synchronization of Active Directory users in Enterprise Vault (EV) may fail due to Active Directory user attributes values being corrupt.

Active Directory users may have corrupt or missing values. The values may be corrupt after a Microsoft Exchange migration from Exchange 5.5 to Exchange 2003.

An Active Directory object and values of the objects can be listed by using the Microsoft LDP which is a utility that is located on the Microsoft Windows operating system CD.

These instructions will only perform a read on the Active Directory database.

Information Required

The location of the user in Active Directory will need to be identified. Record the OU location of the user as follows:


1. Install the system tools from the OS CD "<CD_PATH>\support\tools\"

2. Run the MSI to install the support tools. (Suptools.msi)

3. The support tools will install under "<drive>\program files\support tools\"

4. Execute the LDP application by double clicking on LDP.EXE.(Name of executable: ldp.exe)

5. Click on "Connections" then "Connect". Leave the server box blank then click "OK".

6. Click on "Connections" then choose "Bind" leave the user and password blank. Click "OK" to accept the settings.

7. Click on "View" then click on "Tree". Click "OK" to accept the settings.

A screen similar to the one below will be displayed. (Figure 1)

Figure 1
 


Expand the OU (Organizational Unit) in the left screen by click on the "+" sign. Find the user under the OU that the user is located by double clicking on each OU. Double-click on the user and the LDP utility will return the AD attributes and values of the user including the Exchange properties. (Figure 2)

Figure 2
 


The  "mDBUseDefaults" setting relates to the user's default Microsoft Exchange store settings. EV has to detect a "True" or a "False" value from the "mDBUseDefaults"  attribute. If the  "mDBUseDefaults"  value is in error in active directory, then EV will fail on a manual/automatic synchronization of the user.

Note: Running a manual synchronization on the user will return an error message on the screen indicating that the user was NOT synchronized successfully.  


Possible reason for the problem

After a migration from Exchange 5.5 to Exchange 2003 the "mDBUseDefaults" value may be set to a "0" or a "1". The vault should be set to "True" or "False."

Resolution:

The value of the "mDBUseDefaults" can be changed to "True" or "False" by following the procedure listed below:

1. Open "Active Directory Users and Computers" that is supplied with Microsoft Exchange.

2. Click on the "Exchange General Tab"

3. Click on the "Storage Limits box"

4. In the "Storage Limits" and "Deleted Items Retention" frame a check box will exist.

5. If the box is unchecked then check the boxes and click "Apply". This will force a change to the "mDBUseDefaults" value. Uncheck the box and click "Apply" so the user object will be set back to the original state.

NOTE: Run step 5 in the opposite direction if the box is checked. The idea is to force changes to the AD object.

6. Check the user object with LDP.EXE and verify that the "mDBUseDefaults" value is correct. (Set to "True" or "False")

7. Run a manual synchronization on the user and the synchronization process will return a message box to the screen indicating the status of the synchronization. The synchronization should be successful.

Supplemental note:

Information on the synchronization process can be gathered by running a Dtrace on the "Archive" process. Reference the related technical articles.








Legacy ID



284892


Article URL http://www.symantec.com/docs/TECH48899


Terms of use for this information are found in Legal Notices