I searched around and found two different approaches to creating 32-bit System DSN’s on a 64-bit box. One was using powershell to load registry keys, the other used GPO Client Side Preferences to define User DSN’s which creates the 64-bit DSN and a 32-bit equivalent.
The thing is, I actually prefer using GPO’s for settings instead of scripting them. Also, I want to be able to update DSN’s without having users logging off and back on.
For simplicity I create and test the 32-bit System DSN on the 64-bit box using the 32-bit ODBC Admin, %systemroot%\SysWOW64\odbcad32.exe.
Then I load up the GPMC, create or edit my policy and go to Computer Settings > Preferences > Registry.
Right Click on Registry and create a New Collection Item.
If you use this GPO to create only System DSN registry keys you can simply type in a logical name for the DSN. In my case, I named my collection 32-bit System DSN’s because I have several other registry entries in my GPO.
Right-click on your newly created Collection Item, and select New > Registry Wizard. Assuming you manually created the 32-bit DSN on the same box as you are running the GPMC, simply click Next.
Now go to HKLM > Software > Wow6432Node > ODBC > ODBC.INI
Here you should find any 32-bit System DSN’s you have created. Click the one you want to create using the GPO and select all the settings within the selected key. Click Finish.
Now you will have a new Collection Item, “Registry Wizard Values” within the one you created (the one I named “32-bit System DSN’s”) . You should rename this to something that makes sense to you.
Now, all you need to do, is apply this GPO to all 64-bit servers or client computers that require the 32-bit System DSN.