Windows 7 ODBC Administrator requires admin rights?

jonq

New Member
Joined
Apr 6, 2010
Messages
2
Hello,

I support a fleet of about 600 Windows XP machines that will soon be upgraded to Windows 7. We've begun limited testing and I've encountered the first problem related to the heightened user restrictions. A user cannot administrator ODBC settings without local admin rights. Is there any way around this? Our users are regularly adding/editing/deleting, ODBC data sources in order to create reports and queries from SQL databases, and making our users local admins is out of the question. Even when I make a user a Power User, it's still asking for an admin name and password.

This particular user is on Windows 7 Enterprise 64bit.
 
Solution
Upgrading from Windows XP to Windows 7 involves some changes in terms of user privileges and permissions, which can lead to issues like the one you're facing with ODBC settings. Here are some approaches you can consider to address this problem without making users local administrators:

1. Use Group Policy:​

  • You can use Group Policy to delegate specific administrative tasks like managing ODBC data sources to non-administrative users. This can be done through Group Policy Objects (GPOs) in Active Directory. You can grant permissions to specific registry keys or grant specific permissions on the ODBC-related files and folders.

    2. Custom Permissions:​

  • Set custom permissions on the registry keys that control...
Upgrading from Windows XP to Windows 7 involves some changes in terms of user privileges and permissions, which can lead to issues like the one you're facing with ODBC settings. Here are some approaches you can consider to address this problem without making users local administrators:

1. Use Group Policy:​

  • You can use Group Policy to delegate specific administrative tasks like managing ODBC data sources to non-administrative users. This can be done through Group Policy Objects (GPOs) in Active Directory. You can grant permissions to specific registry keys or grant specific permissions on the ODBC-related files and folders.

    2. Custom Permissions:​

  • Set custom permissions on the registry keys that control ODBC settings to allow specific non-administrator users to modify them. This may require some testing and tweaking to find the right balance between security and functionality.

    3. PowerShell or Command Line:​

  • You can automate the process of setting up ODBC data sources using PowerShell or command line scripts. Users can run these scripts without needing administrator rights. Just ensure that the scripts are properly structured to avoid security risks.

    4. Third-Party Tools:​

  • Consider using third-party tools that provide a more granular control over permissions related to ODBC settings. These tools can sometimes offer solutions that are not available through built-in Windows controls.

    5. Virtualize ODBC Configuration:​

  • One unconventional approach is to virtualize the ODBC settings part of the application that requires it. You can isolate this part so that it runs in an environment where it has the necessary permissions without giving users full local admin rights. It's essential to test any changes in a controlled environment before deploying them to your entire fleet. Additionally, ensure that any modifications are compliant with your organization's security policies and practices. By implementing one or a combination of these strategies, you should be able to provide your users with the necessary permissions to manage ODBC settings without compromising security by making them local administrators.
 
Solution