Group policy to deploy 64 bit ODBC for new RDS Database

[tagteam]

I am building a new RDS server so that users can use office 365 access 64 bit because we have E3 licenses. I have updated the database to work with 64 bit and the database is working well.

However, I am trying to figure out the best way to deploy the 64 bit ODBC to each machine. Since it is 64 bit and the users have 32 bit office what is the best way to create an ODBC that can get deployed to them to work with the Access?

It seems that I need to set up the ODBC on the RDS Server (since that is where the application actually runs) but I tested a user and the remote calls to the sql server did not work and I had to create a 64 bit ODBC on his machine.



What is the best way to manage this?
Thanks

[tagteam]

Looks like I don't have to worry about the local machine. I had a messed up ODBC on the RDS Server that is why I was confused that it wasn't working and thought I need to do a local ODBC. I think if I just fix the one on the server everything will be fine.

[tagteam]

Well, I take that back. If i open the users database on the server i can connect to the tables fine. However, if I log in to the users computer and open the database there I can not access the sql server tables. I am not sure what to do because the user has 32bit office and the server is running 64 bit office and I don't want to have to create the ODBC connection on each machine so how can I get the users database to connect to the sql server?

[tagteam]

Drat the poor error reporting. It appears the issue was with permissions on the SQL server side. Sorry for not checking more fully first.