ODBC Connection

Not planned

Comments

2 comments

  • Shane Corellian

    This wouldn't be a good candidate for the Package Library since DSN connections require data that will change in each environment (such as server name, DSN name, etc.)

    I would suggest using a Command Step in PDQ Deploy and call odbcconf.exe on the target computer. I haven't tried it myself but this utility is available as a way to configure your ODBC DSNs via CLI. Here is the usage window showing the available parameters. (from a Windows 7 workstation)

    odbcconf_usage.png

     

    0
    Comment actions Permalink
  • Jayden Thorup

    I have found that if you export the odbc registry entries, and make sure to install the exact same odbc driver(s) as the entries, you can deploy these out quite easily. Once you figure out how one connection is structured, it is easy to duplicate or remove one or two connections. Just make sure your drivers have a silent install option or optionally roll the driver out with your windows image. https://kencenerelli.wordpress.com/2012/07/26/export-an-odbc-data-source-from-the-registry/

    0
    Comment actions Permalink

Post is closed for comments.