Share via

SharePoint 2019 On Prem doesn't read connected AD users in the poeple picker

SanderO 1 Reputation point
2020-08-12T14:00:50.657+00:00

Hi everyone,

We have installed a new and fresh install of SharePoint 2019 on prem on a local server. We imported the active directory and created a new teams site.

The issue we are facing is that the people picker in the team site doesn't read any AD user, only local users. This is blocking us from adding users to the security groups (site members, site owners, site readers) and with that sharing the site within the organization.

What we already did is:

  1. Make sure the user profiles are read in the User Profile Service Application
  2. Configured the synchronization connection

Are there more settings we need to trigger, to enable the poeple picker reading AD users?

We spend a lot of time on this already (with quite a bit of SharePoint knowledge) but can't seem to tackle this.

Any help would be very much appreciated!

Kind regards,

Sander

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,271 questions
SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,863 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. MichaelHan-MSFT 18,021 Reputation points
    2020-08-13T03:09:51.017+00:00

    As Trevor said, the people picker is not related to UPS Sync. please check the following:

    1.In you Central Administration site, does the people picker work for AD users?

    2.You could run the below script (the attachment) to add your domain to the web application's people picker. This is written by Trevor: powershell-for-people-picker-properties

    script.txt

  2. SanderO 1 Reputation point
    2020-09-03T07:09:25.703+00:00

    Re-installing SharePoint actually fixed it, but it was because sharepoint wasn't installed with an admin account and due to that someone in IT went in and started to change ownerships which corrupted the system I guess.