Migrated security group is being populated with already migrated but disabled users, even though domain pair is set to skip on disabled users. Disabled user is still a member of the group in the source domain. (4263570)

サポートと今すぐチャット

オンラインヘルプの参照
登録の完了

サインイン

価格設定をリクエスト

営業担当に連絡

戻る

フィードバックを送信しました

この記事は課題解決に役立ちましたか?

評価を選択

タイトル

Migrated security group is being populated with already migrated but disabled users, even though domain pair is set to skip on disabled users. Disabled user is still a member of the group in the source domain.
説明

What happens is the following situation:
- user and group were migrated and user became a member of the group in target domain properly
- source user was disabled
- target user was removed from the target group
- dirsync/linkresolver is re-populating target group with target user again even though the domain pair is set to skip on disabled objects
対策

Such behavior is by design because group itself is not a disabled object in the source domain. Yet, there's an unresolved link to migrated object in the source (user or group). LinkResolver will act on such link, find that link is corresponding to another migrated object in the ADLDS database and populated the target group accordingly.
To resolve the issue, it's not enough to disable the source user. Source user should be removed from the source group.
Defect ID

NBDR4

フィードバックを送信しました

この記事は課題解決に役立ちましたか?

評価を選択

Request a KB Article

推奨コンテンツ

製品：: Migration Manager for AD
8.15

トピック: Best Practices

記事の履歴：: 作成日： 2/10/2022
最終更新日： 5/7/2023

すべての記事を検索

製品を選択してください:

サービス向上のために、「Purpose of your Chat（チャットの目的）」を記入してください。

お客様の不具合に推奨されるソリューション

Migrated security group is being populated with already migrated but disabled users, even though domain pair is set to skip on disabled users. Disabled user is still a member of the group in the source domain. (4263570)

タイトル

説明

対策

Defect ID

Leave a Comment