Open TCP/IP properties by clicking on TCP/IP protocol, Open IP Address tab.

Scroll down to IPAll and make TCP Dynamics Port blank.

Enter your port number to TCP Port (1433 is most used SQL server port) apply the changes and click OK

Change SQL server and SQL server Browser Start mode to Automatic by going to their properties.

Our next step is to tell your system/server about which port to open for accepting the SQL connection

To do this first close servers Firewall (if don’t want to do this for security reasons, pass SQL server application to allow applications in Advance Firewall option) navigate to the advance option in firewall windows.

After successful installation of GP on server side we need to install GP clients on different systems and while installation we need to pass our server’s SQL server name and instance or we can pass server’s IP along with port number like (192.168.1.1, 1433 another way myserver\Sqlserver) format is first machine name\ server instance name) and need to pass SQL server authentication credentials.

After installation of GP, 2 tier client server architecture will be successfully implemented in such a way multiple clients will point to one server.

Post navigation

2 thoughts on “Deployment of Dynamics GP as multiple desktop clients”

Hi,
I’d like to point out that it is a very practice to use the IP address of the SQL server for your GP client deployment, as the GP user password is encrypted based on the SQL server name in the ODBC connection, and thus if you put in an IP address and need to change it sometimes in the future, you’re screwed and need to reset all the user’s password, not to speak of all the ODBC connection that need to be redone.. Usually, it is advised to stick with canonical server names like (SERVER\DYNAMICSGP). I even go further and suggest to use an ALIAS for the DNS entry, so you can move your SQL server to another instance without having to reset the GP user’s pwd and ODBC setup (like DYNAMICSGP\DYNAMICSGP). This allows also for quicker & easier switch the next time you upgrade to a new SQL server.
Have a great day.
@GP_Beat

PS: all the steps about port 1433 are usually not required within a regular GP client / server setup, unless your network policies are very tight and all ports locked down.