NCR Command Center v19.2 Technical Overview—DFW05

1 Command Center Architecture 1. The support technician has access to valuable information about the file servers and terminals at multiple sites, to provide fast, superior support to customers. 2. The hosted Command Center server acts as the central point of contact for both the technician s computer, and the BOH file server at each site. 3. If a firewall is present at a site, Command Center does not require complex firewall configurations be-cause it uses standard ports, through which most firewalls allow access. 4. The BOH file server at each site always talks to the hosted Command Center server because Command Center communication is outbound from the site. Command Center uses Transport Layer Security (TLS) and Secure Shell (SSH2) encryption and protocol tech-nologies, which promotes secure com-munication.

2 5. Through Passive Virtual Network Com-puting (PVNC), which is activated only when needed by an authenticated user, the technician has direct access to the terminals at each site without the need to first access the BOH file server. Key Features and Benefits CMC allows you to: Monitor information at multiple sites, enabling you to stay on top of potential hardware and software concerns before they become an issue at a store. This keeps your customers focused on their guests. Provide the strictest remote connection security, through multi-factor authentication. There are typically two components to multi-factor authentication; something you know, and something you have. The username/password provides the something you know component, and the system checks to make sure you have the appropriate credentials, which is the something you have.

3 Stay aware of possible violations and security weaknesses at a store, through the use of automated dashboard alerts. Alerts can help you maintain a compliant POS system. Provide automatic CMC updates to ensure each site is on the current version with no manual intervention required. System Requirements Client Computer: .NET Framework Site File Server: .NET Framework Windows 7/ Windows 10 / Windows Server 2012 R2 or Server 2016 4 GB of RAM 100 MB free hard disk space Site Terminals: .NET Framework Windows Embedded POSR eady 7/ Windows 7 / Win-dows 10 2 GB RAM 100 Mb free hard disk space You can retrieve manufacturer, serial number, model code, and odometer information from a Radiant terminal only, with a P15xx driver ( or later) installed.

4 Click Contact us to email the CMC support team with questions, issues, enhancement suggestions, and more. NCR Command Center Technical Overview DFW05 Last Updated: July 7, 2020 Quick Reference Guide What is Command Center ? NCR Command Center (CMC) is a dynamic support tool that offers enhanced security and simplicity to the remote site support process. With CMC, you have an enterprise-level dashboard view of the servers and terminals at every site you support. You can quickly check the health of multiple computers, perform queries, transfer files, receive alerts, and more, without the need to take control of any computer at the store. This means customers are left to run their business with minimal interruption.

5 Page 2 Command Center File Structure BOH/Server: C:\Program Files (x86)\NCR\CMC Runs Command Center Agent service. Contains siteID and configuration options that control store-side application behavior, includ-ing Gateway= On . Contains Industry configuration . Used to PVNC into BOH and terminals. Manual start service needed for remote control. C:\Program Files (x86)\NCR\CMC\Logs Contains update information. CMC appends any new log information to the existing file. CMC log file. A new file is created for each business day, and kept for 14 days. Web ordering log file. A new file is created for each business day, and kept for 14 days. FOH/Terminals: C:\Program Files (x86)\NCR\CMC Contains siteID, BOH IP address, and configuration options that control how the store-side application behaves, including Gateway= Off Contains Industry configuration .

6 C:\Program Files (x86)\NCR\CMC\Logs Contains update information. Command Center appends any new log information to the existing file. Command Center log file. Easy Client Installation on the Technician s Computer You can use CMC on any computer with .NET Framework installed. To install CMC on a technician computer: 1. Send an email to: to obtain a user account. You will receive a response email with tempo-rary credentials and download links. 2. Download the client application from: Easy Firewall Setup For core CMC operations, the site needs outbound access on ports 443 and 80 for the following URL s: PVNC requires outbound access on ports 22 or 80 on the follow-ing URL: CMC will configure the Windows Firewall to allow exceptions for and Refer to Page 3 for more infor-mation.

7 Easy Installation at a Site CMC installs through a single executable file run on the file serv-er or main computer at a site. To install CMC at a site: 1. Download the file from: The zip file contains the file you will use to install CMC on the main computer at each store. 2. Right-click the file, select Run As Administra-tor to install Command Center (CMCA gent) on the main site computer (installer must have administrator rights). installs the Command Center Agent service and required components into the C:\Program Files (x86)\NCR\CMC folder. It also installs PVNC as a manual start service. Optional parameters for BOH/FileServer/Gateway: /SiteID nnnnn /Industry <Industry name> /ForceAlohaRestart /Uninstall For aloha sites, the CMC components are pulled down to each terminal at End-of-Day or the next refresh through the BIN synchronization process.

8 For other sites, run the on each node. parameters for FOH/Node/Terminal: /SiteID nnnnn /IP <BOH computer name or IP address> /NodeID /NodeName Command Center Technical Overview DFW05 Command Center Site configuration Command Center offers several custom configuration options for site management. The file, typically found at C:\Program Files (x86)\NCR\CMC controls machine/site configuration . This file follows XML formatting rules. All entries are optional and not required. Refer to Command Center Performing Manual Site configuration QRG for full configuration options. Unit Number (BOH): <unitNumber value= 9999 /> Changes the Unit Number value shown in the Store Manager display. Numeric value only.

9 Only affects BOH. Site Information (BOH): <siteInfo enterpriseId= xyz99 site-Name= Sample Site phone= 999-111-1234 phone2= 999-111-5678 address1= 123 Main St. address2= City, ST 12345 open-Time= 0400 /> Changes site information displayed on the Store Summary display. All fields are optional. Only affects BOH. Terminal ID (FOH): <nodeConfig id= 1 name= TermName /> Changes the Terminal ID and allows you to change how the terminal name appears in the Site Page 3 Command Center Technical Overview DFW05 Command Center Site Operations For core CMC operations, the site needs outbound access on ports 443 and 80 (port 8050 can be substituted for 80) for the following URL: ( ) All external Command Center communications are en-crypted.

10 Configure port 8050 if using SPI on port 80. PVNC requires outbound access on either port 22 or port 80 for the following URL: ( ) Online Ordering products ( aloha Online, Mobile pay, etc.) require outbound access on port 8082 for the following IP: ( ) Whitelisting If you are using a whitelisting application, make the following exceptions for proper installation and operation: (before CMCA gent ) Certificate Validation CMCA gent and CMCSvcWatcher are digitally signed applications and require the site certificate to be validated with prior to connecting to the datacen-ter. For certificate validation, the site needs outbound access on port 80(tcp) for the following IP addresses: The above GoDaddy IP addresses resolve to Only one IP address is required at a site, but the correct IP address depends on the site loca-tion.