Skip to main content

Installing LS Central - POS on local machine

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 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"?>
<configuration>
  <appSettings>
    <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;" />
  </appSettings>
</configuration>

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.

<Nav>
              <Title>POS</Title>
              <ExePath>C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\140\RoleTailored Client\Microsoft.Dynamics.Nav.Client.x86.exe</ExePath>
              <Username />
              <Password />
              <Domain />
              <NetLogin>false</NetLogin>
              <WaitForExit>true</WaitForExit>
              <Company>TEST</Company>
              <Object>
                <Type>Page</Type>
                <Id>99008950</Id>
                <Name>EPOS Main</Name>
              </Object>
              <ServiceTierList>
                <ServiceTier>
                  <Name>BC140</Name>
                  <Port>7046</Port>
                  <Host>YOUR SERVER URL</Host>
                </ServiceTier>
              </ServiceTierList>
              <WindowMode>Fullscreen</WindowMode>
</Nav>

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


Conclusion:

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 😉






Comments

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: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant 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

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe