Install LDAPCP in your SharePoint farm


SharePoint (especially 2019) has unaddressed reliability issues when deploying farm solutions on farms with multiple servers.
The more servers the farm has, the bigger the risk that deployment fails. To mitigate this, cmdlet Install-SPSolution can be run with -Local on each server, but it requires more operations.
This page will guide you through the steps to install LDAPCP in a safe and reliable way.

Deploy the solution

Execute the following steps:

  • Download the latest version of LDAPCP.wsp.

  • Install and deploy the solution, using either the simple or the safe method:

    • Simple method: Recommended for single-server farms only:
    # Run this script on the server running central administration, in a new PowerShell process
    Add-SPSolution -LiteralPath "C:\Data\LDAPCP.wsp"
    # Wait for some time (until solution is actually added)
    # Then run Install-SPSolution (without -Local) to deploy solution globally (on all servers that run service "Microsoft SharePoint Foundation Web Application"):
    Install-SPSolution -Identity "LDAPCP.wsp" -GACDeployment
    • Safe method: Recommended for production environments with multiple servers:
        Deploy "LDAPCP.wsp" in a reliable way, to address reliability issues that may occur when deploying solutions in SharePoint (especially 2019) (and especially if there are many servers):
        Run this script on ALL SharePoint servers running the service "Microsoft SharePoint Foundation Web Application" and/or the central administration, sequentially (not in parallel), starting with the server running the central administration.
        The script does not require any modification, you only need to set the variable $packagefullpath with the path to the solution file (used only on the 1st server)
    # To use this script, you only need to edit the variable $packagefullpath below
    $claimsprovider = "LDAPCP"
    $packagefullpath = "C:\Data\$claimsprovider.wsp"
    $packageName = "$claimsprovider.wsp"
    # Perform checks on the local server to detect and prevent potential problems
    # Check 1: Install-SPSolution will fail if claims provider is already installed on the current server
    if ($null -ne (Get-SPClaimProvider -Identity $claimsprovider -ErrorAction SilentlyContinue)) {
        Write-Error "Cannot continue because current server already has claims provider $claimsprovider, which will cause an error when running Install-SPSolution."
        throw ("Cannot continue because current server already has claims provider $claimsprovider, which will cause an error when running Install-SPSolution.")
        Get-SPClaimProvider| ?{$_.DisplayName -like $claimsprovider}| Remove-SPClaimProvider
    # Check 2: Install-SPSolution will fail if any feature in the WSP solution is already installed on the current server
    if ($null -ne (Get-SPFeature| ?{$_.DisplayName -like "$claimsprovider*"})) {
        Write-Error "Cannot continue because current server already has features of $claimsprovider, Visit to fix this."
        throw ("Cannot continue because current server already has features of $claimsprovider, Visit to fix this.")
    Write-Host "All checks passed on this server, continuing..."
    # Add the solution if it's not already present in the farm (only the 1st server will actually do this)
    if ($null -eq (Get-SPSolution -Identity $packageName -ErrorAction SilentlyContinue)) {
        Write-Host "Adding solution $packageName to the farm..."
        Add-SPSolution -LiteralPath $packagefullpath
    $count = 0
    while (($count -lt 20) -and ($null -eq $solution))
        Write-Host "Waiting for the solution $packageName to be available..."
        Start-Sleep -Seconds 5
        $solution = Get-SPSolution -Identity $packageName
    if ($null -eq $solution) {
        Write-Error "Solution $packageName could not be found in the farm."
        throw ("Solution $packageName could not be found in the farm.")
    # Always wait at least 5 seconds to avoid that Install-SPSolution does not actually trigger deployment
    Start-Sleep -Seconds 5
    Write-Host "Deploying solution $packageName on the local server..."
    # Set -local in Install-SPSolution to deploy the bits on this server only and prevent reliability issues in SharePoint
    Install-SPSolution -Identity $packageName -GACDeployment -Local
  • Visit central administration > System Settings > Manage farm solutions: Confirm the solution is “Globally deployed”.

Finalize the installation

This step is very important and applies to all SharePoint servers which do NOT run the service “Microsoft SharePoint Foundation Web Application” and/or the central administration.

For each of those servers, complete the steps below to manually add/update ldapcp.dll in the GAC:

  • Use 7-zip to extract ldapcp.dll from LDAPCP.wsp

  • Run the script below to add ldapcp.dll to the GAC:

    [System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a") | Out-Null
    $publish = New-Object System.EnterpriseServices.Internal.Publish
        # Method Publish.GacRemove() removes the assembly from the GAC if it exists (it is needed for update scenarios)
        $existingAssembly = [System.Reflection.Assembly]::Load("ldapcp, Version=, Culture=neutral, PublicKeyToken=80be731bc1a1a740").Location
        Write-Host "Assembly $existingAssembly successfully removed."
    } catch {}
    # Add the assembly to the GAC
    Write-Host "Assembly was successfully added to the GAC."
  • Restart the IIS service and the SharePoint timer service (SPTimerV4):
    Restart-Service W3SVC; Restart-Service SPTimerV4

Enable the claims provider

To be enabled, LDAPCP must be associated with the SPTrustedLoginProvider which stores the configuration of the trust with the trusted STS:

$trust = Get-SPTrustedIdentityTokenIssuer "SPTRUST NAME"
$trust.ClaimProviderName = "LDAPCP"

You can now configure LDAPCP.

Edit this page on GitHub