olisterr.tech | Blog on Dynamics 365 Business Apps, NAV / Business Central, Power Platform and Azure

Introduction: When you are using Business Central On-Premise, we might need to set up the Development Environment for AL Extension through Business Central Administration. In this blog, I will be sharing how to set up Development Environment connectivity on your local device and Business Central On-Premise hosted on a Server using UserPassword. Pre- requisites : Understanding of Authentication  Understanding of Business Central Administration VS Code AL Language Extension Business Central On-Premise Demonstration: 1. Set up Networking:  i. Enable Port through Inbound Port Rules in Azure: By default the Development Port required for Connectivity is disabled. Hence you will need to add the port in the Inbound Port Rules. ii. Enable Port through Inbound Port Rules in Advanced Firewall Settings: Add the port in the Inbound Port Rules in Firewall Settings. Add Inbound Port in Firewall 2. Set up Development Configuration in Business Central Administration: By default, Business Central Admini

Introduction: In this blog, I'm attempting to capture the LS Central - POS installation process on Local Machine. This blog has nothing to do LS Central - Server Setup for POS. LS Retail / LS Central - On Premise POS Pre- requisites : LS Central Installed on Server SSL Setup on LS Server (https://www.olisterr.tech/2020/03/how-to-setup-navuserpassword-with-ssl.html) LS - POS Installer Business Central - On Premise Installer Demonstration: Once your LS Retail / LS Central POS is setup on the main server. Just prior to Go-Live, you will actually have to install this POS on multiple systems and connect these POS to the main server with LS Retail / LS Central. 0.Preparation: Prior to actually installing Business Central On-Premise Windows Client, you need to make sure that you're able to ping the target with the correct Port number. For this I made use of PS-Ping tool.  PSPing - IP Address: Port If you're unable to PS-Ping the correct IP with Port number, simply check the Advan

07/10/2020 - Update on Self-Signed Certificate Setup Process for NAV / Business Central  As per my previous post on setting up NAVUserPassword here Reference:  https://community.dynamics.com/nav/b/dynamicsnavcloudfronts/posts/how-to-login-windows-client-and-web-client-using-navuserpassword-authentication-in-microsoft-dynamics-nav If you have created a Certificate using the above PowerShell command and it gives error while starting the NAV / BC Instance with the error as follows: ******************************************************* Server instance: DynamicsNAV100 Tenant:  <ii>The service MicrosoftDynamicsNavServer$DynamicsNAV100 failed to start. This could be caused by a configuration error. Detailed error information: System.ArgumentException: It is likely that certificate 'CN=navision.southeastasia.cloudapp.azure.com' may not have a private key that is capable of key exchange or the process may not have access rights for the private key. Please see inner exception for

Introduction: In this blog, I'm attempting to setup basic authentication like NavUserPassword for Business Central On-Premise. NavUserPassword is an authentication system, where each user have their own UserID and password which is configured inside Business Central itself. Pre- requisites : Microsoft Dynamics 365 Business Central On-Premise Domain for your VM Understanding of Credential Types in Business Central Demonstration: 1. Setup DNS in Azure VM: Go to your VM inside Azure to configure DNS. Click on Configure Put the URL as you need. 2.  Create a Webserver Instance for Business Central: New-NAVWebServerInstance to create a Web Server Instance Adding Web Server Instance with the name LS 3. Create a Self Signed Certificate or get an SSL from Domain provider: Run the PowerShell script to create a self signed certificate New Self-Signed Certificate New Self-Signed Certificate created After creation/installation of Certificate, righ