Hi everyone (long time reader, sites been great on snagging tips for deployments)...

I'm looking at deploying some Oracle ODBC connections (datasources). I haven't had much luck using ODBCCONF.EXE, just wondering if anyone has has deployed this perhaps with script or registry? VBS isn't really an option for me due to security configurations on our endpoints...

thanks!
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi! why don`t you catch conenctions in the registry? and just include them in an ordinary MSI then roll it out. That`s simple task
Answered 10/14/2009 by: Scazy
Senior Yellow Belt

Please log in to comment
0
Just did one yesterday [;)], DSNs are just registry keys so you can put what you need in an msi.

System based DSN entries are under:
HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI
and
HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\ODBC Data Sources

User based DSNs are under (although I would stick to System ones if deploying them):
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI
and
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC Data Sources

Add one manually and look at the registry and you'll see what you need.

Cheers.
Toothman
Answered 10/14/2009 by: Toothman
Yellow Belt

Please log in to comment
0
I have experience doing this with Oracle, with thousands of users but, unless you are using Oracle, my suggestions won't help you. Please let me know if you are using Oracle and I can help. My method works without any 3rd party tools including the costly solutions provided by Oracle. Change/add/delete connection strings in one location and all workstations immediately have access without ever visiting the local workstations of those users, once a configuration file has been deployed. Requires an Oracle client (minimally). I know it works with all versions of Oracle since 8i even though Oracle doesn't support it... They'd rather sell you expensive tools.
Pat
Answered 10/15/2009 by: pmarshbu
Orange Belt

  • I would like to hear more about this Pat. Please elaborate.
Please log in to comment
0
thanks for the replies..

yes we are Using Oracle.
Answered 10/15/2009 by: ltd2007
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: Toothman

Just did one yesterday [;)], DSNs are just registry keys so you can put what you need in an msi.

System based DSN entries are under:
HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI
and
HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\ODBC Data Sources

User based DSNs are under (although I would stick to System ones if deploying them):
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI
and
HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC Data Sources

Add one manually and look at the registry and you'll see what you need.

Cheers.
Toothman


this seems to be working! thanks again...
Answered 10/15/2009 by: ltd2007
Senior Yellow Belt

Please log in to comment
0
I agree with Toothman's solutions in their entirety as I have also used that method at times however, if this is something you will need to do as a regular maintenance issue to modify your connection strings, I can share an easier way so that you will never have to reconfigure the local workstation connection strings (or registry) again, after initial setup, which also uses remote FileDSNs for the datasources. I had to perform extensive testing before implementing this. Just let me know if you are interested in this method and I'll be glad to help...Good Luck!
Pat
Answered 10/15/2009 by: pmarshbu
Orange Belt

Please log in to comment
0
I know some people like the registry way but I figure the ODBC tables are there for a reason, no?

Learning to use the existing tables will give you a deeper understanding of Windows Installer.

For example, one should NEVER use custom actions to apply permissions but use the LockPermissions table.
Answered 10/15/2009 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity