Only local groups can be created for member servers and Windows 2000 Professional.
To create a local group for a member server or computer running Windows 2000 Professional
-
Bind to the computer using the following rules:
-
Use an account with sufficient rights to access that computer.
-
Use the following binding string format using the WinNT provider, computer name, and an extra parameter to instruct ADSI that it is binding to a computer: "WinNT://<computer name>,<computer>".
The "<computer name>" parameter is the name of the computer groups to access.
In the binding string, the "<computer>" parameter instructs ADSI that it is binding to a computer. ADSI makes this data available to the WinNT provider's parser so that it can skip some ambiguity-resolution queries to determine what type of object you are binding to.
-
Bind to the IADsContainer interface.
-
-
Specify "localGroup" as the class using IADsContainer.Create to add the group.
[!Note]
If you specify "group" as the class, ADSI uses "localGroup". Do not specify the class as "globalGroup". Groups of class "globalGroup" cannot be created on member servers or a computer running Windows NT Workstation/Windows 2000 Professional. If you specify "globalGroup", IADsContainer.Create creates the group in the property cache, but IADs.SetInfo does not write the group to the security database and it does not return an error. -
Write the group to the computer security database using IADs.SetInfo.
Source: Microsoft Learn / Windows Win32 documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
