Deselected containers not saved in User Profile Sync. Connection SharePoint 2019

LNM 1 Reputation point
2020-07-29T14:29:33.473+00:00

Hi,

I've set up an User Profile Synchronization Connection in SharePoint 2019. But I am unable to save deselected sub containers, after I save the Sync. Connection.

For example I have this container/OU structure:

  • Department A
    ○ Users
    § Employee A
    § Employee B
    § Employee C
    § Temporary contractors
    -Temporary Contractor A

When I deselect Temporary contractors after selecting Department A followed by saving the connection, this actually isn't saved. When I reopen the Sync. Connection and Populate the containers again I see the container Temporary contractors selected again.

The only way to save this situation is to do the following:

  1. Expand the Department A container.
  2. Select Employee A
  3. Select Employee B
  4. Select Employee C
  5. Click the Save button
    In this way I have my desired situation which is that the container Temporary contractors is not selected.

You can imagine that this situation is not user friendly and I honestly don't think that this is the way it is supposed to work.

Can someone clarify if this is a known error/bug?

Kind regards,

  • LNM

p.s. if needed I can provide screenshots

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,246 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,834 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Itch Sun-MSFT 2,556 Reputation points
    2020-07-30T08:58:30.813+00:00

    As far as I know, this seems to be a known annoying problem...😔

    You can view a few similar scenarios below:

    AD Import - Cannot deselect containers

    user profile sync from AD taking more accounts than it should...

    If the workaround you're finding right now doesn't satisfy you.

    I suggest you remove the old connection and create a new one.

    0 comments No comments