| Previous | Next |
| STATUS_NO_SUCH_USER | STATUS_NO_SUCH_GROUP |
STATUS_GROUP_EXISTS
Group creation conflicts with an existing group object
SAM distinguishes groups from aliases and users, and Active Directory also applies scope and type rules. A name collision should therefore be resolved by reading the existing object type, SID, scope, and ownership rather than assuming it is the group the provisioning operation intended.
Make group creation idempotent by comparing immutable identity and expected attributes. Do not silently attach permissions to an existing group with the same display name, especially across domains where similarly named groups have different SIDs.
What to inspect
- Query object class, SID, scope, and group type for the existing name.
- Compare the existing object with the desired provisioning record.
- Report a conflict when identity does not match instead of reusing the group.
References
- Microsoft Open Specifications: SAM Remote Protocol
- Microsoft Open Specifications: SAM server model
- Microsoft: NetGroupAdd
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.