Consider the following scenario: You set up Microsoft Identity Manager (MIM) 2016. You install the SharePoint Connector software and create a SharePoint Management Agent (MA). On the “Connectivity” page of the SharePoint MA, you attempt to create a connection to a SharePoint 2016 or 2019 farm using an HTTPS (SSL / TLS) address. The connection

As discussed in my previous posts about user profile cleanup for SharePoint 2013 and SharePoint 2016, when using Active Directory Import, the profile cleanup process is a bit more manual as compared to FIM Sync. It consists of three steps that need to be done periodically to keep things cleaned up: 1. Run a Full

Microsoft Identity manager (MIM) communicates with SharePoint via a web service, specifically, the “ProfileImportExportService” web service, located at http://YourCentralAdminSite/_vti_bin/ProfileImportExportService.asmx When there are problems with the synchronization, you should always look at what the MIM client (miisclient.exe) and the SharePoint ULS logs are saying, but sometimes there is a need to dig a little deeper and

  Consider the following scenario: Your users authenticate to SharePoint using “Trusted Provider” authentication. This is also known as SAML or WS-Fed authentication, typically provided by AD FS, Ping Federate, Okta, SiteMinder, etc. After SharePoint upgrade or security patching, users are no longer able to authenticate. They may see a “Server Error in ‘/’ Application”

  This is similar to a previous blog post I wrote. However, we’ve since found a few customers that have done something similar with Windows authentication. We’ve seen this a few times now. It seems to most commonly occur when Admins are setting up a new User Profile Service app using Active Directory Import (AD

  As far as I know, nothing much has changed regarding profile cleanup in SharePoint 2019 as compared to SharePoint 2016. See that post: SharePoint: The complete guide to user profile cleanup – Part 4 – 2016       This is part 5 in a series. You can find other parts here: SharePoint: The

This one may be a bit of a one-off. As far as I can tell, it’s only happened once in the history of SharePoint. However, that also means that documentation on this problem is non-existent, and if happened once, it could happen again.   Note: This is only valid for SharePoint 2010 and SharePoint 2013