Awsome , thanks for the reply cactus, very helpful.
There is a server-manager panel (located at https://server-name/server-manager) in which you can create groups and assing users to certain groups. This groups at their turn can be associated with ibay access and so on
One question about that. When I worked with Win2kServer you would create a user. Then you could add the user to multiple groups which had their own limits and permissions. Like say I want to create 3 users who all have admin powers, and 4 powerusers and the rest all just users, where are the settings to do such things? As far as I can tell from working with groups it's just grouping users together for email and i-bay purposes.
I just found out yesterday after experimenting a lot that you can use the group description to match them to the Windows groups. I have not fully tested everything but I created a group called "domain.admins" with the description "Domain Admins" and they were perfectly mapped to the Domain Admins group under Windows (the group name is arbitrarily, the description should be exactly as used in Windows). I guess this will also work for Power Users and other groups. Here is a list of the Windows Groups:
- System Operators (SID-removed) -> -1
- Replicators (SID-removed) -> -1
- Guests (SID-removed) -> -1
- Power Users (SID-removed) -> -1
- Domain Users (SID-removed) -> shared
- Print Operators (SID-removed) -> -1
- Administrators (SID-removed) -> -1
- Account Operators (SID-removed) -> -1
- Backup Operators (SID-removed) -> -1
- Users (SID-removed) -> -1
- Domain Admins (SID-removed) -> domain.admins
- Domain Guests (SID-removed) -> nobody
(I removed the SID's for security issues)
Behind the -> is the name of the mapped group as you (might have) created it in the server-manager. A value of -1 means no group or user mapped.
I don't know if it is possible for all this groups but the Domain Admins group seems to work OK
Be carefull though, as by default the Domain Admins group is mapped to the admin member by default, also don;t mess with the Domain Users as this group is managed by the server and all members created will be mapped but in this group and therefor automatically will be domain member.Please post your expereinces back to the forum, so we can all benefit (in case you try off course).
If you want to see if you maping worked correctly you can try this:
Log in as root user by SSH or at the console. With the following commands you will be able to retrieve data:
net groupmap list
will give you all the groups and there mapped user group
net rpc group MEMBERS "windows groupname/description" --user=admin
will list the members who are mapped to the group after you have entered the admin password, e.g.
net rpc group MEMBERS "Domain Admins" --user=admin