SharePoint 2016 – MIM 2016: Full Sync does not export profile pictures to Active Directory
Consider the following scenario: You have SharePoint 2016 configured to import user profiles using Microsoft Identity Manager (MIM) 2016 as the External Identity Manager. You have configured MIM to import profile pictures from Active Directory (AD). After the pictures have been created in SharePoint, you decide to reverse the flow to export profile pictures from
SharePoint: Managed Metadata: The term is not a valid term
The main point of this post is to create awareness around the fact that you can use the CreateTerm PowerShell method on a TermSet object to create a new managed metadata term with a specified Term ID. You’ll have to read to the end to understand why that’s a big deal, and to see it
SharePoint – People Picker times out – Hybrid App Launcher issue
This was a really unique situation where a network problem for the Hybrid App Launcher caused People Picker to intermittently time out and display no results. Note: The two features are not directly related as you’ll see below. Let me explain: When you configure Hybrid OneDrive and Sites in SharePoint 2016, it adds an
SharePoint: MIM 2016 Export for SharePoint MA fails
Consider the following scenario: You have SharePoint 2016 set up to import user profiles from an External Identity Manager. We’ll say you’re using Microsoft Identity Manager (MIM) 2016 to import profiles from some 3rd party LDAP directory. The profiles should be imported as Trusted Provider type users (SAML-claims). You run a Sync, and everything goes
SharePoint: The Complete Guide to PortalSuperUserAccount and PortalSuperReaderAccount
What are the Super User and Super Reader accounts for? This is explained pretty well on Docs here: https://docs.microsoft.com/en-us/SharePoint/administration/configure-object-cache-user-accounts In general, they are used in the process of making SharePoint Publishing sites (any site using the publishing features) render quickly and efficiently. Please keep in mind that these accounts are not actually required to be
SharePoint 2016: Office documents prompt for authentication on anonymous site
Consider the following scenario: You have a SharePoint 2016 site that has been enabled for anonymous access. You have some Microsoft Office (Word, Excel, PowerPoint, etc) documents in a library that anonymous users also have access to. A user clicks on a (for example) Word document to open it. They receive a credential prompt,
SharePoint: Users forced to re-authenticate unexpectedly
This post covers the scenario where users log in via Trusted Provider / SAML-claims, (like ADFS, Ping, Okta, Site Minder, etc) and intermittently, they are redirected back to the login page to re-authenticate. There are a few pieces of information you need for a scenario like this (beyond normal scoping): 1. Output of Get-SPSecurityTokenServiceConfig from one