ODBC connections can be user (stored in user reg hive), system (stored in reg for all users) or file based.
So, on the client side, what type of ODBC data source is acceptable? Can the app reference a file ODBC DSN - dunno if that's acceptable security wise. Otherwise, does it need to be system wide or user specific? Either way, you can use your deployment tool to push it out. And TBH, why does it need to connect with "sa"? Surely another SQL Server identity can be created (even with the same privileges as "sa", and then reduced accordingly over time as the dev figures it out). You need to push back on this last part. From: [email protected] [mailto:[email protected]] On Behalf Of Gavin Wilby Sent: Monday, 27 October 2014 11:03 PM To: '[email protected]' Subject: [NTSysADM] Pushing out ODBC connections Hi, I have been asked by one of our Devs, to push out a ODBC connection to a database server. The issue is that is HAS to connect with the servers SA username and password... <sigh> I cant see how exactly how this can be pushed out by either a registry script or by GPP... anyone done this successfully? Gavin Wilby <random stuff snipped>
