Skip to main content

NAV2013 & Later - How to Change Service Parameters Using Powershell.

Hi All,

I received a query from a friend about setting properties of the service instance using powershell for NAV 2013 R2.

Let's see how we can set those properties using powershell.

Open and Load NAV Cmdlets in Powershell window.
** How to open and Load NAV Cmdlets in powershell.

For Changing any property in the service instance there is a cmdlet called as Set-NAVServerConfiguration, as shown below.





The Cmdlets require Following fields as Input -

1. -ServerInstance - Specifies the name of a Microsoft Dynamics NAV Server instance.
2. -KeyName - The configuration key name.
3. -KeyValue - The configuration key value.

We all know the first parameters (service name) and some of us know / think that we know second and third parameter too :).

Let's see how we can find second and Third Parameter exact Value.

a) Navigate to C:\Program Files\Microsoft Dynamics NAV\70\Service (in case of NAV 2013)
a) Navigate to C:\Program Files\Microsoft Dynamics NAV\71\Service (in case of NAV 2013 R2)
a) Navigate to C:\Program Files\Microsoft Dynamics NAV\80\Service (in case of NAV 2015)

b) Open CustomSettings.config file in NotePad. It will be something as shown below.



c) The Highlighted Parts in Green are KeyName & in Red are KeyValue that we need for our Cmdlets.

Suppose i want to set SOAP web services to Disabled then my KeyName and KeyValue will be -

KeyName - SOAPServicesEnabled
KeyValue - FALSE.

Let's try to input that on powershell to my Service Instance BlankService.



Here is my Powershell window.



Let's Run the Cmdlet.



It Says that i need to Restart the Service. For that i will use the cmdlet Set-NAVServerInstance as shown below.




Let's check the Service Instance.



So i need to use two cmdlets to change any service configuration as listed below -
-----------------------------------------------------------------------------------------------------
#Replace all <<>> With Actual Values
Set-NAVServerConfiguration -KeyName <<KeyName>> -ServerInstance <<ServiceName>> -KeyValue <<KeyValue>>
Set-NAVServerInstance -ServerInstance <<ServiceName>> -Restart
-----------------------------------------------------------------------------------------------------

Hope you find the article useful and Your comments are welcome.

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype

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.