Skip to content

Commit be7deb3

Browse files
Update Move-ADObject documentation
Added important note on cross-domain moves and group member limits.
1 parent 384fcd7 commit be7deb3

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docset/winserver2025-ps/ActiveDirectory/Move-ADObject.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -286,6 +286,9 @@ Specifies the Active Directory instance to use by providing the following value
286286
287287
Note: A cross-domain move requires a fully qualified server name and the use of the RID Master in both domains.
288288
289+
IMPORTANT: At the database level, a cross-domain move is treated like a object deletion in the source domain and object creatiion in the target domain. There is the case of a very large object, because there are many links on the object, for example a group with more than 5000 members. 5000 is a soft limit. You may be able to move groups with more members, but at some point you experience problems when moving such a group. The recommendation is to export and remove group members so the group has less than 5000 members. Then you can safely move the group to another domain and after that, re-add the exported members.
290+
References: [LDAP transaction limits](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/active-directory-domain-services-maximum-limits#maximum-number-of-accounts-per-ldap-transaction), [Link batch size limit](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/replication-failures-delete-active-directory-objects)
291+
289292
Domain name values:
290293
291294
- Fully qualified domain name (FQDN)

0 commit comments

Comments
 (0)