RKSID15033-Windows 10 File Server or

Terminal Setup
Categories: HKS Knowledge, Aloha
HKS Knowledge ,Radiant Systems Radiant Service Partners ,RDS QSR
Available
Aloha Channel Partners and Direct Clients ,Radiant Systems -
To:
Entertainment All NCR Internal
Version: 1.0
Document
Published
Status:
Published
04/07/2017
date:
Author: hks admin

Type

Informational

CreatedByFirstName

Bill

CreatedByLastName

Seale

Created Date

2016-09-12 14:43:43

UpdatedByFirstName

Bill

UpdatedByLastName

Seale

UpdatedDate

2017-02-17 12:18:07
Description

Windows 10 File Server or Terminal Setup

Content

Perform the following to configure the Microsoft Windows 10 operating system (32 bit
and 64 bit OS) to function as a file server or terminal for the Aloha POS system.

The information in this document will assist you in enabling the Aloha POS system to
function, but you should also review the Reseller Aloha Base Server Creation Checklist
in RKS ID 11780 in order to assist you in implementing the proper data security
measures or obtain the Image Builder tool from Radiant Update. This tool when used can
set all Windows settings and policies for you. See the attached zip file for details on
every setting that is changed using Image Builder.

Refer to RKSID 14205 for additional information when using 64-bit Windows.

Windows Installation

Install Windows on the file server using standard configuration options. All of the
configuration changes required by the Aloha POS system will occur after the installation.

RAL Installation

Windows 10 requires the use of RAL version 16.3.5.19 or higher.

Orderpoint

Windows 10 requires the use of Orderpoint version 15.1.3.68 or higher and the
NCRDisplayVerification utility version 2.1.9.1.

Network

Configure the workgroup name the same on all terminals and the file server. This name is
arbitrary as long as it is consistent throughout the Aloha application software.

The file server and terminals are generally configured as a workgroup rather than a
domain in order to ensure that the terminal can operate in the absence of a domain
controller. However, some users will apply a domain to a NIC on the file server that is
designated for external and non-Aloha communication, and then configure a second NIC
on the file server (for communication with Aloha POS terminals) as a workgroup.

You can use static or dynamic IP addresses, but if you use the latter, ensure that the
terminals are able to function in the case of a network failure with no DHCP server.
You must select 'Enable NetBIOS over TCP/IP' in the advanced properties of the network
protocol used by the Aloha POS system.

Ensure that TCP/IP version 6 is not enabled on the network binding used by the Aloha
POS system.

Edit the NIC's power management properties to ensure that 'Allow the computer to turn
off this device to save power' is not enabled.

Ensure that the network binding used by the Aloha POS system is at the top of the
binding order list. This is accessed by opening the Network and Sharing Center and
clicking Change Adaptor Settings. Press Alt to access the Advanced drop-down menu,
and select Advanced Settings.

TCP/IP Media Sense

Windows 10 uses Media Sense with TCP/IP to determine whether the network card is in
a link state. If the computer is removed from the network or the network becomes
disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application
software.

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems
that may require the reinstallation of the operating system. Use this tool at your own risk.

New registry entries described in this document are enclosed in quotation marks. Please
ignore these quotation marks when adding the entry in the Windows Registry. All
Registry entries are case sensitive.

1. To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.
2. Path out
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.
3. Verify the DisableDHCPMediaSense value exists in the folder. If it does, double-click
it and change Value Data to '1'. If it does not exist, choose Edit/New/DWORD Value and
name the key ' DisableDHCPMediaSense '. Then double-click the entry and change
Value Data to '1'.
4. Select Registry/Exit to exit the Windows Registry Editor.
5. Restart Windows.

Media Sense provides the ability to connect to networks with different DHCP options in
one Windows session without the need to release and renew the IP configuration by using
IPCONFIG.EXE. If you disable Media Sense, no new IP configuration information is
obtained when you connect to a new network unless you restart the computer, or you
release and renew the IP configuration by using IPCONFIG.EXE.
Refer to Microsoft Knowledge Base document Q239924 for more information on Media
Sense.

Disabling TCP/IP Version 6 (IPv6)

In order to disable IPv6, open the Windows Registry Editor, path out
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/TCPIP6/Parameters,
create a new DWORD value labeled DisabledComponents if it does not exist. Type 0xff
to disable all IPv6 components except the IPv6 loopback interface. This value also
configures Windows to prefer using IPv4 over IPv6 by changing entries in the prefix
policy table.

Disable Simple File Sharing

Disable simple file sharing in Control Panel/All Control Panel Items/Folder

Options/View/Use Sharing Wizard.

File Sharing

The Aloha application software requires a network share labeled BOOTDRV that enables
read and write capabilities to the Aloha application software file server and FOH
terminals. This share needs to be applied to the root folder or drive in which the Aloha
folder resides. If the Aloha application software resides in C:\ALOHA, share C:\ as
BOOTDRV. If it resides in D:\ALOHA, share D:\ as BOOTDRV. If you created a special
folder for the Aloha application software, share the special folder as BOOTDRV. For
example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.

The installation application should create the share for you, but if you plan to share only a
folder as BOOTDRV, then you need to create the folder prior to installing the Aloha POS
system.

Disable Microsoft Data Execution Prevention

You must disable Microsoft Data Execution Prevention (DEP) on the file server. To do
this, right-click on the short-cut to the command prompt and select 'Run as administrator'.
Run the following command from the command prompt:

Bcdedit.exe /set nx AlwaysOff

Processor Priority

Configure the processor priority to 'Background services' by accessing the System

Properties and clicking Advanced/(Performance) Settings/Advanced.
Disable Client Side Caching

Windows enables Client-Side-Caching (CSC) by default. This results in Windows

dedicating a lot of processing time to caching of network files in a local folder, which can
slow down the Aloha POS system and possibly result in a fatal error. Perform the
following to permanently disable CSC in Windows:

1. To open the Windows Registry Editor, execute REGEDIT from the Run window, and
click OK.
2. Select Yes in the User Account Control confirmation window, if presented.
3. Path out HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CSC.
4. Verify the Start value exists in the folder. If it does, double-click it and change Value
Data to '4'.
5. Select Registry/Exit to exit the Windows Registry Editor.
6. Restart Windows.

Adjust User Account Control Settings

Since the Aloha POS system does not support User Account Control, you must configure
it to Never Notify in Control Panel/All Control Panel Items/Action Center/Change User
Account Control settings.

File Caching

The Aloha POS system uses files for some alerts and communications, such as refreshes
(Stop file) and EDC (.req and .ans files). Windows 7 has a default caching configuration
that that can delay discovery of these files. Perform the following on all Windows 7 PCs
that are part of the Aloha POS system:

1. Open Windows Registry Editor using Start/Run/Regedit.

2. Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation
\Parameters.
3. Add new DWORD entries (via Edit/New/DWORD) for the following names and
assign a value of 0. If the names already exist, change the values to 0.

FileInfoCacheLifetime
FileNotFoundCacheLifetime
DirectoryCacheLifetime

Beginning in Aloha POS versions 6.7.37 (and higher) and 12.3.5 (and higher), the
Ctlsvr.exe will automatically add/change these values on the file server and
Iber.exe/Iberqs.exe will add/change these values on FOH terminals.

Disable Windows 'Application has stopped working' Prompt

There are times when the Aloha POS is busy and Windows mistakes this as the
application has stopped working. This will result in Windows to gray out the application
and prompt with options to check online for a solution, close the program, or debug the
program. You should perform the following to disable this on PCs running Aloha,
especially the FOH:

1. To open the Windows Registry Editor, execute REGEDIT from the Run window, and
click OK.
2. Select Yes in the User Account Control confirmation window, if presented.
3. Path out HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows
Error Reporting.
4. Add a new DWORD entry (via Edit/New/DWORD) for DontShowUI and assign a
value of 1. If the name already exists, change the values to 1.
5. Select Registry/Exit to exit the Windows Registry Editor.
6. Restart Windows.

Install Aloha Software

(The minimum supported Aloha version for Windows 10 is 12.3)

Prior to installing the Aloha POS software, restart the computer after making the changes
explained in this document.

Install the Aloha POS software on the file server using the .msi file on the installation
CD.

Adding Users to the BOOTDRV Share

Edit your BOOTDRV share to ensure that the proper users have read/write access to the
contents BOOTDRV share.

Firewall

By default, the Windows built-in firewall will not allow the FOH terminals to interact
with the file server. In this case, you must either disable the Windows firewall if you are
using a third-party or external fire wall, or you must configure the Windows firewall to
allow the proper access.

Mixing Windows 10 with Windows XP PCs

If the site is mixing Windows XP PCs with Windows 7 PCs, then you must perform the
following on the Windows 10 PCs in order to ensure network access from the Windows
XP PCs:

1. Using the Windows Registry Editor, set

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\netbt\Parame
ters\UseNewSmb to a value of zero.
 2. In the local security policies (Secpol.msc), set Local Policies/Security
Options/'Network security: LAN manager authentication level' to 'Send LM
&NTLM - use NTLMv2 session security if negotiated'.

Keywords

windows 10 windows ten windows10 microsoft windows 10 32 bit 64 bit RAL

Orderpoint NCRDisplayVerification

Attachment

Win10 Server Build.zip