Skip to main content

NAV 2013 R2 Windows Client & Web Client with NavUserPassword - Configuring the Credential Type on the Microsoft Dynamics NAV Clients

Hi all,

This is Fourth & Last post in this series. Please make sure that you have read all the previous post before you start reading this post.

All the post related to this series can be found in Introduction Post.

So Let's see what we need to do the configuration on Clients.

Windows / RTC Client -

I will explain this you all in a separate post, as of now just follow the steps as shown below -

1. Navigate to C:\Users\<UserName>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\71

2. Copy the File ClientUserSetting to say D Drive.

3. Open the copied file and do changes for these parameters as shown below.

Port No. - New Service Port No (in my case 10046)
Server Instance - New Service Name (in my case TESTNAVUsername)
Client Service Credential Type - NAVUSerPassword.
DnsIdentity - Certificate Name (in my case NAV2013R2)
UnknownSpnHint - New Serivce URL (in my case localhost:10046/TestUsername/Service)

4. Save the File.

5. Create a Shortcut of NAV 2013 R2 Windows Client on Desktop and Naviagte to its properties.

6. You will see below URL in the Target Property of Shortcut.
"C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe"

7. Append this with the address of settings file that you have updated in step 3.
"C:\Program Files (x86)\Microsoft Dynamics NAV\71\RoleTailored Client\Microsoft.Dynamics.Nav.Client.exe" -settings:"d:\ClientUserSettings.config"

*In my case i saved the setting file with same name in D Drive.

8.Hit Apply and ok.

9. Run the windows client, if all the steps are performed correctly you should end up with a window as shown below.

10. Enter UserName and Password created in Post 3 and here we go.

we have successfully configured Windows Client with NAVUSerPassword.

Web Client -

1. Navigate to C:\inetpub\wwwroot\DynamicsNAV71

2. Open the Web.config file.

3. We need to change following things in web.config , as shown below-

a. authentication mode with Client Services (Default - Windows).
b. ServerInstance (As we have configured to a different service).
c. ClientServicesCredentialType (Default - Windows).
d. ClientServicesPort (As we have configured to a different Port).
e. UnknownSpnHint (URL for service to connect).
f. DnsIdentity (Require a value for authentication for other than windows).

4. Save the File.

5. Run the web client from start menu, if all the steps are performed correctly you should end up with a window as shown below.

10. Enter UserName and Password created in Post 3.

we have configured Web Client with NAVUSerPassword.

In Next post we will see the detailed explanation for ClientUserSettings file that we have changed for RTC Client.

Saurav Dhyani


Popular posts from this blog

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.