Remove
This article describes the steps to remove in order to successfully update EntraCP in your SharePoint farm.
Is it safe to (un)install or update EntraCP in my SharePoint farm?
Yes, as long as you follow the steps in the documentation, as the solution’s deployment type (ApplicationServer) means that:
- Deploying/retracting the solution only copies/removes the files on disk (it does not installs/removes the EntraCP features).
- The features are installed/removed with a specific step, which prevents conflicts.
- The files are deployed on truly all SharePoint servers.
The biggest risk is a misconfiguration in the assembly bindings, which could prevent SharePoint to run.
Do not just retract the solution
EntraCP features must be deactivated and uninstalled before the solution is retracted.
Update the trust configuration
Unfortunately, the only supported way to clear the property ClaimProviderName is to remove and recreate the SPTrustedIdentityTokenIssuer object.
Alternatively, this property can be reset using .NET reflection, but this is not supported and you do this at your own risks:
# Set private member m_ClaimProviderName to null. Note that using .NET reflection on SharePoint objects is not supported and you do this at your own risks
$trust = Get-SPTrustedIdentityTokenIssuer "<SPTRUST_NAME>"
$trust.GetType().GetField("m_ClaimProviderName", "NonPublic, Instance").SetValue($trust, $null)
$trust.Update()Uninstall EntraCP
Remove the assembly bindings
Steps order
This step must be completed on all SharePoint servers, after the solution was uninstalled.
- Open file
%systemroot%\Microsoft.NET\Framework64\v4.0.30319\Config\machine.configin a text editor. - Locate the XML node
<runtime>. - Delete the entire node with its children and replace it with
<runtime />. - Save the file
machine.config.