Skip to main content

NAV 2013 R2 Windows Client & Web Client with NavUserPassword - Installation of Security Certificates.

Hi all,

This is second post in this series. Please make sure that you have read the first post before you start reading this post.

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

I hope you would have finished all the steps as discussed in Post 1. Let's Move Ahead.

11. As of now if we check the certificate information we will find that its not trusted.
we now need to install the certificate & revocation list on the computer running Microsoft Dynamics NAV Server.


12. Open Mmc.exe from RUN menu.

13. From File Menu Select Add/Remove Snap-in.

14. From available snap-ins select certificates and click add.

15. Select Computer account, click next and then click finish.

16. From Left hand panel select Trusted Root Certificate Authorities and then select Certificates.

17. Right Click and Select All Tasks and then select Import.

18. Click Next, Locate the file in your folder.

19. Click Next, and Finish. You will find Certificate in the list.


20. Right Click and Select All Tasks and then select Import.

21. Click Next, Locate the file in your folder (Change the File Extension to .crl).

22. Click Next, and Finish.

23. Select the Trusted Root Certificate Authorities node, and then refresh the snap-in.

24. You will find Recovation List in a new Group.

To create and install a test certificate for the Microsoft Dynamics NAV Server computer -

1. At the command prompt, type the following command:

makecert -sk NAV2013R2 -iv NAV2013R2.pvk -n "CN=NAV2013R2" -ic NAV2013R2.cer -sr localmachine -ss my -sky exchange -pe NAV2013R2.cer

This command specifies the subject’s certificate name as NAV2013R2. You need this certificate name when you configure the Microsoft Dynamics NAV Windows client or Microsoft Dynamics NAV Web Server components.

2. When you are prompted, enter the password that you used to create the root CA.

Grant Access to the certificate’s private key to the service account for Microsoft Dynamics NAV Server -

25. Open Personal and select certificate Folder From Left Menu.

26. Right Click the certificate (in my case certificate name is NAV2013R2),choose All Tasks, and then choose Manage Private Keys.

27. In the Permissions for NavServiceCert private keys dialog box, choose Add.

28. In the Select Users, Computers, Service Accounts, or Groups dialog box, enter the name of the service account that is used by Microsoft Dynamics NAV Server By default, the service account is NETWORK SERVICE. Choose OK when done.

29. In the Permissions for NavServiceCert private keys dialog box, select the account, and then select the Allow check box next to Full Control. Choose OK when done.

30.Double Click the Certificate and goto Details Tab, select Thumbprint. Copy the value of Thumbprint Shown we will require it in next step.

My Thumbprint Value is =a6 fd 3e 7c 9c 82 ef 07 7a 1f 36 73 bc ee 8a bc e9 4c 03 cc


In Next Post we will see the changes that need to be done in Service Tier.

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.