Tweet
I've got a situation where I've delegated controls to the Helpdesk guys, but they are getting errors when trying to perform functions through Hyena.
They've been given essentially all access in the delegated controls Wizard. But if they even right click and go to properties, it gives them 'Unable to access RAS information for user xxxx' but then they click OK and it opens up the properties.
To create an account, they get that same error, plus "Unable to save Active Directory Data. Access is denied. Extended error --- LDAP Provider : 00002098: SecError: DSID-03150BB9 prob 4003, (INSUFF_ACCESS_RIGHTS), data 0"
Eventually they are able to get through the process, even with the errors. However, if the same users just pull up Active Directory Users and Computers, they can do anything they want to the profiles that they were given permissions to without any errors at all. The errors only pop up when using Hyena.
I've dug and dug, and haven't found a solution for this. There were mentions of this same error, but in most cases they were tied to Exchange. Currently we don't use Exchange so this wouldn't apply to us. We are on a 2008 R2 domain.
Any help would be greatly appreciated because I just can't get around the errors
They've been given essentially all access in the delegated controls Wizard. But if they even right click and go to properties, it gives them 'Unable to access RAS information for user xxxx' but then they click OK and it opens up the properties.
To create an account, they get that same error, plus "Unable to save Active Directory Data. Access is denied. Extended error --- LDAP Provider : 00002098: SecError: DSID-03150BB9 prob 4003, (INSUFF_ACCESS_RIGHTS), data 0"
Eventually they are able to get through the process, even with the errors. However, if the same users just pull up Active Directory Users and Computers, they can do anything they want to the profiles that they were given permissions to without any errors at all. The errors only pop up when using Hyena.
I've dug and dug, and haven't found a solution for this. There were mentions of this same error, but in most cases they were tied to Exchange. Currently we don't use Exchange so this wouldn't apply to us. We are on a 2008 R2 domain.
Any help would be greatly appreciated because I just can't get around the errors
Comment