arildb_
asked on
Permissions required to configure user's terminal services settings
Hi,
I'm trying to find out what permissinos are required in order to set the terminal services settings on other users. Currently the only way I have been able to do that is if the user I'm using to set the information is a domain admin. However, we need to be able to delegate that task to other users that are not domain admins.
I've tried "Account Operators", "Server Operators" and quite a few of the "User Rights" in the Domain Policy but to no avail.
The error I get is: "Could not load Terminal Services properties for this user because: Access is denied."
Any tips at all would be appreciated.
I'm trying to find out what permissinos are required in order to set the terminal services settings on other users. Currently the only way I have been able to do that is if the user I'm using to set the information is a domain admin. However, we need to be able to delegate that task to other users that are not domain admins.
I've tried "Account Operators", "Server Operators" and quite a few of the "User Rights" in the Domain Policy but to no avail.
The error I get is: "Could not load Terminal Services properties for this user because: Access is denied."
Any tips at all would be appreciated.
Didn't try this for Terminal Server Settings (do I understand correctly, that you mean those stored in AD?), but the Delegate Control Wizard should be able to assign the permission to any group/user you want.
ASKER
Well, I do mean those that you see through Users and Computers, but those settings arent stored as attributes in AD (or atleast I haven't found them). And I've already delegated full control on all types of objects to no avail (which makes sense if the data is stored outside AD). Even when accessing this programmatically you need to use a separate API (WTSxxx) to get/set the values since there is no way through ADSI.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You're right about that one. And actually the user I'm using does have read/write access to the attribute (even has full control on all objects under that OU) but it still doesn't work in this lab. I did the same test in our other lab and it worked like a charm så I guess there's something other that giving me the problem and maybe it's time to reinstall our development lab. Thanx, I'll give you the points, but right now EE fails when I try to do that.
ASKER