Sign in with Microsoft
Sign in or create an account.
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.


This article describes the Microsoft SharePoint 2010 Indexing Connector for Documentum issue that is fixed in the SharePoint 2010 Indexing Connector for Documentum hotfix package that is dated December 14, 2010.


Issues that this hotfix package fixes

This hotfix package provides supports for Documentum Trusted Content Services (TCS) in SharePoint 2010 Indexing Connector for Documentum when you perform a crawl on a documentum content server.


Improvements that are included in the hotfix package

  • This hotfix provides support for TCS "Access Restriction" Access Control List (ACL) features to Documentum users.
    When SharePoint 2010 Indexing Connector for Documentum translates Documentum ACL to NT ACL, the TCS ACL "Access Restriction" access permission is recognized and translated. Therefore, in SharePoint search results, you cannot see documents on which you are assigned with "Access Restriction" access permission.

    Note During the crawl process, "Required Group" access permission and "Required Group Set" access permission are not translated to NT ACL.

  • The TCS ACLs are extracted into SharePoint crawled properties.
    In order to enable the security trimming solution, this hotfix extracts the following TCS ACLs into SharePoint crawled properties that correspond to the Documentum objects crawled.


    Crawled Property

    Content Format

    Access Restriction


    DCTM User/Group\\ DCTM user/group\\DCTM user/group\\

    Required Group


    DCTM Group\\ DCTM group\\DCTM group\\

    Required Group Set


    DCTM Group\\ DCTM group\\DCTM group\\


    • In the RTM version of Indexing Connector for Documentum, the Documentum standard ACL access permission is extracted into crawled property DocumentumACL.

    • Extracting crawled properties for Docmentum ACLs are optional during the crawl process. If you want them to be crawled, an administrator should use the following command together with the command switch PersistDCTMACL in Documentum Connector:


    • The format that describes a Documentum user or group in these crawled properties is still kept same.




      User from "None" for "LDAP"


      "U" means user.
      dm_owner(represents the owner of the document) will be translated to the real user ID.
      dm_world(represents everyone) will be kept

      User from "Inline Password"


      "U" means user.
      dm_world(represents everyone) will be kept.



      "G" means group.

  • A special user permission "superuser" is available.
    If a user is assigned for the "superuser" user permission, the user can see all objects in the repository. Additionally the "superuser" user permission overrides all the other standard ACL access permissions and TCS ACL access permissions.


    • The "superuser" user permission is added into the managed crawled property DocumentumACL for every crawled object. In DocumentumACL, the "superuser" is treated as a group. The format of the "superuser" is as following:

      "Inline Password\G\RepositoryName\superuser"
    • The indexing connector treats the "superuser" as a special group. For every crawled object, the "superuser" user permission is translated into NT ACL access permission according to the mapping that is specified in DCTMConfig.xml.

    • In order to configure the indexing connector to map "superuser" user permission to a certain NT user account or a certain NT group account, an administrator should add the following code example under <Shared> element of theDCTMConfig.xml file that is located under the %Program Files%\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\SearchConnectors\Documentum path.


      The <SuperuserMapping> element is an optional element that takes effect both inĀ UserMappingTable mode and SameAccountNameĀ mode. Additionally, if you have several Documentum content servers, all the user accounts that have "superuser" permission are mapped to same NT account.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


To install this hotfix, you must have SharePoint 2010 Indexing Connector for Documentum installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the SharePoint search service before and after you apply the hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information

File name

File version

File size










Microsoft Windows Installer .msp file information

File name

File version

File size





Not Applicable




Not Applicable

After the hotfix is installed, the global version of this hotfix has the file attributes, or a later version of the file attributes, that are listed in the following table:


File name

File version

File size











For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!