General discussion

Locked

Non Admins with advanced rights

By Wayne B ·
We are using an application that interfaces with a Borland Database. On random but increasing occasions, when this program is launched by a new user or is updated through a dial up connection to the vendors server, our users receive a Blob Size error. Once this occurs, there is no way to allow access to the suppliers server without granting the user Domain Admin rights. The vendor states that this is an issue with NT and refuses to address this problem. We have uninstalled, removed all reference to the program, Sybase, and Borland in the registry, reinstalled and still get this error. It appears that the application requires some form of access to services, devices, or the registry that can't be accessed unless the logged on user has rights to make changes to these areas of the OS. Are there any ways to grant users this type of local access without granting them Domain Admin access. (Logging in to a local account with Admin rights is not an option either) Any ideas?

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Non Admins with advanced rights

by Nichomach In reply to Non Admins with advanced ...

Yes, and it's pretty easy. In the same way that Global groups or domain users can be integrated into local groups on a member server (or in a trusted domain), you can integrate global groups or domain users into local groups on individual workstations. Log in as a user with domain admin rights on an affected workstation. Launch the User Manager (yep, the local one, in Administrative Tools). Open the Administrators local group. Add. Now, it'll show you the list of local users on the station, but you can also click the drop down button and select the domain. You can then either drop individual users into the local Administrators group, or integrate a global group (like Domain Users, for example). If you don't want to traipse around all those workstation individually, fire up User Manager for Domains on your admin console, go to User menu, Select Domain and then type in \\<workstation name>, for whatever the workstation is called. This'll set the focus on the local accounts database for that workstation; you MUST use the backslashes in front of the name though, otherwise it'll look for a domain called <workstation name>. I hope this helps, and contact me if you've got any problems.

Collapse -

Non Admins with advanced rights

by Nichomach In reply to Non Admins with advanced ...

As an aside, Borland stuff is notorious for putting registry values in the wrong places. At a previous company, we used one of their development environments, and it wrote machine specific stuff to HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE, which is, frankly, crap. This meant that every person using that station had to have a fresh install done from CD in order to use it.

Collapse -

Non Admins with advanced rights

by Shanghai Sam In reply to Non Admins with advanced ...

Worked like a charm. I can't beleive I didn't thik of this. We have to do the same thing with an SQL server and local accounts on that system.

Thanks

Collapse -

Non Admins with advanced rights

by Wayne B In reply to Non Admins with advanced ...

This question was closed by the author

Back to Windows Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums