Hi everyone, we’re back for another blog! This time around I’d like to step you through setting up a new Web Client instance for Dynamics NAV. If you’re ever in the situation where you have access to the Desktop or ClickOnce Client but the Web Client was not setup for whatever reason, this will guide you through it and it’s very easy to get it setup.
Setting up a new Web Client instance really only takes 5 minutes, but you’ll need access to the following:
- Windows PowerShell ISE and the ability to run it as an administrator
- Dynamics NAV application server (where the service is running from) and where IIS (Internet Information Services) is installed which it normally is by default on a server
- Optionally – you may also need access to the firewall on the application server to let the Client Services port through.
Once you setup a new Web Client Instance, you can then connect to NAV through the Web, Tablet and Phone (depending on what version you are on).
- First off, log into the application server where your Dynamics NAV service is running from and run PowerShell ISE as an administrator.
If you’re unsure what the application server is, if you log into NAV and go to Select Server, you’ll see the application server name there.
- When PowerShell ISE opens, you’ll want to navigate to the NAVAdminTool which is installed on the application server when NAV is installed. If you haven’t used PowerShell before then just as a forewarning, in my opinion you should only use PowerShell to administer things that you can’t do inside NAV. Anything you can do in NAV you should do so and not through PowerShell. By default it will be installed:
- Now from here press F5 and then press Refresh in the Commands window on the right hand side. You should then see a list of commands loaded into the window.
- Select New-NAVWebServerInstance
- Fill in the parameters about the service you want to create a Web Instance for. Required fields:
Server – enter in the application server name here. If you don’t know this, open NAV and open Select Server but in the majority of cases it will be the same server as you are currently logged into so you can find it by going to Windows Explorer.
Server Instance – enter the NAV service name you want to create a Web Instance for.
Web Service Instance – Give this new Web Instance a name, normal to give it the same name as the NAV service instance.
Client Service Credential Type – This must be the same as the Credential Type for the NAV service so if you don’t know it, open the NAV Administration Tool and you’ll find that in the General tab of that service.
Client Services Port – enter in the Client Service Port from that service, you can find it from the NAV Administration Tool or if you open NAV you’ll see the port number when you go to Select Server
Company – This is the default company that will open. If you are using 2017 onwards then you can change the company directly in the Web Client otherwise, you may wish to create multiple links going to different companies.
- Press Run. You’ll see the script will run successfully and it will say Completed at the bottom.
- When this happens, open IIS.
- Drill into the nodes and you’ll see your newly created Web Service Instance here, go us!
- From here you can press Browse on the right hand side to test it out. At this point may wish to allow the Client Service Port through the Windows Firewall so that users connecting through the Web Client on a Terminal Server on the domain can access it. If you need users to access this on a machine off the domain (like a tablet or phone) then allow it through the main firewall (e.g. on Azure, etc.)
Ok so that’s it, a quick one this week but it’s useful to know how to setup a new Web Service Instance, especially as it doesn’t take too long and it can be very useful to know in case it was missed during the installation and setup process!
See you next time.