Hi support-team,
it is indeed some kind of a permission problem. I added the privileged account to the domain admin group and in worked just fine.
I've created a workaround by adding the required permissions to the OU to the privileged user.
This is a new issue, however. All applications I know interpret users they cannot read as non-existent, so this might still be worth investing on your side.
The whole synchronization process crashes for any group where members are present to which the privileged user has no read-permission. For the purpose of synchronizing groups I'd say that those users can simply be ignored which I suppose was the case before one of the latest builds.
I cannot say exacly when the synchronization started failing because we only noticed it last friday. I can only say that this issue exists in build 9381 and 9400.
Thank you and best regards
Tobias