My intention of this post is to show you how to setup the mobile client when using a Windows 8.1 PC or laptop with Dynamics NAV installed in the 3-tier on one computer configuration. The NAV Team Blog post How to get Microsoft Dynamics NAV for tablets to connect using a self-signed certificate covers how to connect but you must complete a step that is shown in the last comment to fix a loop back issue if using non-server windows.
You need to have Dynamics NAV 2015 already installed with the web client working and be able to connect. If you need to install NAV, then you can look here to the Installation and Configuration Walkthroughs. To verify the web client is ready please test the connection by opening a browser and going to the URL http://<machine name>:8080/DynamicsNAV80/WebClient/ . The URL you use should be similar if you used the default settings when you installed NAV. In my case, 7mz8g12 (this is important later for creating the certificate) is my machine name so my URL is http://7mz8g12:8080/DynamicsNAV80/WebClient/
You can also see the tablet URL by just adding tablet.aspx to the end of the Web Client URL :8080/DynamicsNAV80/WebClient/tablet.aspx”>
Once NAV have been verified, download the mobile client from windows store. Go to the Store and search for
You should be brought to a page similar to this:
Click Install and follow the dialogs if this is the first time you are using the store.
You can also ignore:
The app will work with a mouse and keyboard for non-touch enabled pc and laptops.
Once you have the app installed you are ready to create the certificate and enable SSL for the NAV tablet app.
1. Create self-signed certificate (These steps are copied from the NAV Team blog post listed above)
a. Download and save the PowerShell script from:
b. Open a PowerShell prompt with the option Run As Administrator. I like to use Powershell ISE (C:\Windows\System32\WindowsPowerShell\v1.0\powershell_ise.exe) since there is so much more going on with NAV and Powershell in current versions.
i. Go to the directory where you saved the New-SelfSignedCertificateEx.ps1 file and run the following commands:
1. cd <file location>
2. Import-Module .\New-SelfSignedCertificateEx.ps1
ii. Then run the following command (hint: Use the IP address of your computer instead of machine name when creating the certificate, that way you can connect an external tablet to you NAV server):
As you can see I used only 7mz8g12 (or if IP then 192.168.1.3 for me) for what they call <your site name>
2. Manage the certificate:
a. Open the mmc.exe.
b. Go to the File menu, and then choose Add/Remove Snap-in…+
c. Select Certificates.
d. Choose Add.
e. Select the computer account.
f. Choose Next.
g. Finish and then OK.
h. Locate and copy the certificate you just created in the personal/certificates folder.
i. Copy the certificate and Paste the certificate into the Trusted Root Certification Authorities/Certificates folder.
3. Enable https
a. Here is the official guide:
i. Walkthrough: Configuring Web Services to Use SSL (SOAP and OData)
b. Open IIS Manager
i. Find NAV 2015 Web Client
ii. Click on Edit Site -> Bindings…
iii. Then click Add…
iv. Once in the Add Site Binding dialog select the Type to https and then select the certificate you created.
I have found the IP one more useful:
c. Click OK and the certificate should be set.
4. Fix the loopback issue:
a. This part is key for using a non-server pc.
b. If you prefer command line then you can run the following command in Powershell:
CheckNetIsolation.exe LoopbackExempt -a -n=”microsoft.dynamicsnav_8wekyb3d8bbwe”
c. Use Fiddler – The free web debugging proxy for the visual approach:
i. Open Fiddler
ii. Select Win8 Config
iii. Make sure the checkbox is checked next to Dynamics NAV if you ran the Powershell command. If you didn’t, check the box now.
You can test the NAV app connection by entering in the following URL:
If everything is correct then you should see:
If you would like to connect an android and/or iOS device then please complete the steps listed in the How to get Microsoft Dynamics NAV for tablets to connect using a self-signedcertificate.
For more information, feel free to reach out to me at