Skip to main content

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.

Start, Stop & Restart Service - 

  • Start Service - Start-NAVServerInstance -ServerInstance BC210
  • Stop Service - Stop-NAVServerInstance -ServerInstance BC210
  • Restart Service - Restart-NAVServerInstance -ServerInstance BC210
Parameters Details - 
  • BC210 - Service Name

Set Service Account - 
  • Set User to Network Account - Set-NAVServerInstance -ServerInstance BC210 -ServiceAccount NetworkService -Start
  • Set User Account - Set-NAVServerInstance -ServerInstance BC210 -ServiceAccount User -ServiceAccountCredential (Get-Credential -message 'Enter User Password') -Start
Parameters Details - 
  • Service Name - BC210
  • Service Account - NetworkService / User

Create New Server Instance -
  • New-NAVServerInstance -ServerInstance BC210 -ClientServicesCredentialType Windows -DatabaseName "Demo Database BC (21-0)" -DatabaseServer localhost -ManagementServicesPort 9045 -ClientServicesPort 9046 -DeveloperServicesPort 9049 -ODataServicesPort 9048 -SOAPServicesPort 9047
Parameters Details - 
  • Service Name - BC210
  • ClientServicesCredentialType  - Windows, UserNamePassword, UserName, ACS ...
  • DatabaseName  - SQL Database Name.
  • DatabaseServer - SQL Server Name.
  • ManagementServicesPort, ClientServicesPort , DeveloperServicesPort,  ODataServicesPort & SOAPServicesPort - 5 ports needed for each service.
Get Parameters on Server Instance - 
  • Get-NAVServerConfiguration -ServerInstance bc210 -KeyName DatabaseName
Parameters Details - 
  • Service Name - BC210
  • KeyName - Property Name you want to Change.
Set Parameter on Server Instance - 
  • Set-NAVServerConfiguration -ServerInstance BC210 -KeyName DatabaseName -KeyValue "Demo Database BC (21-0)"
Parameters Details - 
  • Service Name - BC210
  • KeyName - Property Name you want to Change.
  • KeyValue - Property Value that you want to Set.
If you utilize panel to do other stuff not listed above, please add a comment to this article.

Hope you learned something from this article.

Saurav Dhyani


Post a Comment

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.