Title here
Summary here
Update
Important
LDAPCP Classic is deprecated. Migrating to LDAPCP SE is safe and easy.
Update the solution
Important
Always start a new PowerShell process to ensure using up to date persisted objects and avoid nasty errors.
Bear in mind that additional steps are required on SharePoint servers which do not run the service ‘Microsoft SharePoint Foundation Web Application’.
On the server running the central administration:
- Start a SharePoint management shell and run
Update-SPSolution:
# This will start a timer job that will deploy the update on SharePoint servers. Central administration will restart during the process
Update-SPSolution -GACDeployment -Identity "LDAPCP.wsp" -LiteralPath "F:\Data\Dev\LDAPCP.wsp"- Visit central administration > System Settings > Manage farm solutions: Wait until solution status shows “Deployed”.
Important
Be patient, cmdlet Update-SPSolution triggers a one-time timer job on the SharePoint servers and this may take a minute or 2.
If status shows “Error”, restart the SharePoint timer service on servers where depployment failed, start a new PowerShell process and run Update-SPSolution again.
Finalize the update
Update-SPSolution updates the bits only on the servers running the service “Microsoft SharePoint Foundation Web Application”, but LDAPCP must be updated on all SharePoint servers.
To complete the update, follow the steps described in the section “Finalize the installation” in the install page.
Breaking changes
Version 10 is a major update that has breaking changes. Updating to v10 (or newer) will reset claim type configuration list, and all customization made to that list will be lost.