Skip to main content

Installing LS Central - POS on local machine


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


  • LS Central Installed on Server
  • SSL Setup on LS Server (
  • LS - POS Installer
  • Business Central - On Premise Installer


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.

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 Advanced Firewall Setting  in Inbound and Outbound Rules.

Inside Windows:
Inbound Port 7046
Inbound Rules - Port 7046

Outbound Port 7046
Outbound Rules - Port 7046

In Azure:
Inbound Port 7046
Inbound rules - Port 7046

Outbound Port 7046
Outbound Rules - Port 7046

1. Install NAV / Business Central Windows Client:
In Business Central On-Premise Installer, simply select the Windows Client and remove all other components.

Install the NAV / Business - On Premise Windows Client Component

Goto C:\Users\<YOUR USERNAME>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\140

You will find the ClientUserSetting.config file and change the parameters as marked

<?xml version="1.0" encoding="utf-8"?>
    <add key="Server" value="YOUR SERVER" />
    <add key="ClientServicesPort" value="7046" />
    <add key="ServerInstance" value="BC140" />
    <add key="TenantId" value="" />
    <add key="ClientServicesProtectionLevel" value="EncryptAndSign" />
    <add key="UrlHistory" value="localhost:7046/BC140" />
    <add key="ClientServicesCompressionThreshold" value="64" />
    <add key="ClientServicesChunkSize" value="28" />
    <add key="MaxNoOfXMLRecordsToSend" value="5000" />
    <add key="MaxImageSize" value="26214400" />
    <add key="ClientServicesCredentialType" value="NavUserPassword" />
    <add key="ACSUri" value="" />
    <add key="AllowNtlm" value="true" />
    <add key="ServicePrincipalNameRequired" value="False" />
    <add key="ServicesCertificateValidationEnabled" value="true" />
    <add key="DnsIdentity" value="" />
    <add key="HelpServer" value="" />
    <add key="HelpServerPort" value="0" />
    <add key="ProductName" value="" />
    <add key="TelemetryDeploymentType" value="" />
    <add key="TelemetryInstrumentationKey" value="" />
    <add key="UnknownSpnHint" value="(net.tcp://localhost:7046/BC140/Service)=NoSpn;(net.tcp://YOURSERVER:7046/BC140/Service)=NoSpn;" />

The result should be you getting access to Windows Client.
Windows Client

2. Install LS Retail / LS Central POS:
Simply install the LS Retail POS Setup just as you would on your server, and change the config file.
After this is done, head over to C:\Program Files (x86)\LS Retail\NAV\LSStart and find the file LSStart.exe.config File.
Replace the <Nav> section with and change the parameters as marked.

              <ExePath>C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\140\RoleTailored Client\Microsoft.Dynamics.Nav.Client.x86.exe</ExePath>
              <Username />
              <Password />
              <Domain />
                <Name>EPOS Main</Name>
                  <Host>YOUR SERVER URL</Host>

The final result will be that you will get access to LS Retail POS.
LS Retail POS

3. Access Web - POS:
This method is suitable for mobile devices such as Tablets, Phones or mini-computers.
Simply login into your Browser with the Web Client URL
Business Central - Web Client

Select the LS Retail Role

Once, you have selected the correct Role, automatically your Business Central session will refresh and will initiate LS Retail Web-POS
LS Retail - Web POS Initializing
LS Retail - Web POS - Login Screen

LS Retail - Web POS - Transactions


Although this might look like a complicated process, it is relatively easier than the SSO setup.
Just that you need to verify connectivity at each step. Overall the gist is you just install the client, modify configurations like IP and Port and Instance name and Credential Type and you're done.

I hope this helps 😉


Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

Business Central Environment Blinking after update to v20

Introduction: Business Central Updates after updating to version 20.x, there is a common problem which is observed. The Business Central environment starts blinking as per the video below - Pre- requisites : Business Central Online  v20 Demonstration: 1. Restart the Business Central Environment: Go to Business Central Admin Center > Select the Environment >Sessions > Restart Environment. 2. Ensure that your URL contains Tenant ID: When you login into the Business Central Environment, make sure that your links are in the following formats Sandbox :<SandboxEnvironmentName>/?sandbox=true Production :<ProductionEnvironmentName>/ If you URL like or any other format without Tenant ID, chances are that you will end up with the issue. Also, you can login through Admin Center URL -  Connect from URL in BC Admin Center 3. Check the status if the insta