Export (0) Print
Expand All
Expand Minimize

People Search relevance is not optimized when the Active Directory has errors in the manager reporting structure (SharePoint 2013)

SharePoint 2013
 

Applies to: SharePoint Server 2013, SharePoint Foundation 2013

Topic Last Modified: 2013-12-18

Summary: Learn how to resolve the SharePoint Health Analyzer rule "People Search relevance is not optimized when the Active Directory has errors in the manager reporting structure".

Rule Name:  People Search relevance is not optimized when the Active Directory has errors in the manager reporting structure.

Summary:  In Active Directory Domain Services (AD DS), only company leaders should have the Manager property set to NULL. If the Manager property is set to NULL for other users, people search relevance is reduced. To optimize people search relevance, explicitly specify company leaders. People search can then use this information to improve relevance.

Cause:  Company leaders have not been explicitly specified.

Resolution: Specify company leaders.
  1. Verify that you have the following memberships:

    • securityadmin fixed server role on the SQL Server instance.

    • db_owner fixed database role on all databases that are to be updated.

    • Administrators group on the server on which you are running the Windows PowerShell cmdlets.

    • Add memberships that are required beyond the minimums above.

    An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.

    NoteNote:
    If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about Windows PowerShell permissions, see Add-SPShellAdmin.
  2. Start the SharePoint 2013 Management Shell.

    • For Windows Server 2008 R2:

      • On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.

    • For Windows Server 2012:

      • On the Start screen, click SharePoint 2013 Management Shell.

        If SharePoint 2013 Management Shell is not on the Start screen:

      • Right-click Computer, click All apps, and then click SharePoint 2013 Management Shell.

    For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012.

  3. At the Windows PowerShell command prompt, type the following command:

    $upaProxy = Get-SPServiceApplicationProxy <AppID>
    

    where <AppID> is the GUID of the User Profile service application proxy. For more information, see Get-SPProfileLeader.

  4. Type the following command:

    Add-SPProfileLeader -ProfileServiceApplicationProxy $upaProxy -Name "<Domain\UserName>"
    

    where <Domain\UserName> is the user account that you want to add as a leader — for example, Contoso\Joe.Healy. For more information, see Add-SPProfileLeader.

  5. You are prompted to confirm. Type Y to confirm.

  6. Run a full crawl on the content source that contains the start address (URL) of the User Profile application. For more information, see Start, pause, resume, or stop a crawl (SharePoint Server 2010).

Repeat the commands to add more user accounts as company leaders.

For more information, see The *-SPProfileLeader Windows PowerShell cmdlets in SharePoint Server 2010 SP1 (http://go.microsoft.com/fwlink/p/?LinkId=226295).


Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft