Use the ModifyGroup procedure of the Managed Active Directory namespace to modify a group in Active Directory.
This procedure expects to be called with impersonate="1". The procedure impersonates the caller.
<request> <procedure> <execute namespace="Managed Active Directory" procedure="ModifyGroup"> <executeData> <group>LDAP:// CN=myGroup1,DC=contoso,DC=com</group> <groupType>UNIVERSAL SECURITY</groupType> <description>Describes the modified group</description> <properties> </properties> <preferredDomainController>myPrimaryDC.contoso.com</preferredDomainController> </executeData> </execute> </procedure> </request>
The following input is valid for this request:
Use the <group> element to specify the Lightweight Directory Access Protocol (LDAP) path of the group.
<group>LDAP://LDAP path of the group</group>
By using the <groupType> element, you can specify the type of group that you want to modify.
The different group types are:
A global security group can contain users, groups, and computers from its own domain as members. Global security groups can be granted rights and permissions for resources in any domain in the forest.
A local security group can be granted rights and permissions on only resources on the computer on which the group is created. Local groups can have any user accounts that are local to the computer as members, as well as users, groups, and computers from a domain to which the computer belongs.
A universal security group can contain users, groups, and computers from any domain in its forest as members. Universal security groups can be granted rights and permissions on resources in any domain in the forest.
This information is optional. If you do not specify a group type, the value defaults to GLOBAL SECURITY.
<groupType>GLOBAL SECURITY|LOCAL SECURITY|UNIVERSAL SECURITY</groupType>
By using the <description> element, you can specify an optional new description for the group. This information is optional.
<description>new description for the group</description>
By using the <preferredDomainController> element, you can specify the domain controller that you want to use for this request. Using a single preferred domain controller eliminates replication delays that arise between multiple controllers. This information is optional.
<preferredDomainController>your domain controller</preferredDomainController>
The response to this procedure does not contain significant data.