NCR Hospitality PA-DSS Implementation...

NCR Hospitality PA-DSS Implementation Guide

© 2012 NCR Quest Page

Highly Confidential - Distribution Restricted

i

Table of Contents

Table of Contents .................................................................................................................................... i Revision Information .............................................................................................................................. 2 Executive Summary ................................................................................................................................ 2

Assessor ............................................................................................................................................. 2 Application Summary ......................................................................................................................... 3 Typical Network Implementations ..................................................................................................... 3 Dataflow Diagram .............................................................................................................................. 5 Dataflow Diagram .............................................................................................................................. 7

Difference between PCI Compliance and PA-DSS Validation ................................................................. 8 The 12 Requirements of the PCI DSS: ................................................................................................ 8

Considerations for the Implementation of Payment Application in a PCI-Compliant Environment ...... 9 Sensitive Credit Card Data requires special handling......................................................................... 9 Remove Historical Credit Card Data ................................................................................................... 9 Set up Good Access Controls ........................................................................................................... 10 Properly Train and Monitor Admin Personnel ................................................................................. 11 Key Management Roles and Responsibilities ................................................................................... 11 PCI-Compliant Remote Access ......................................................................................................... 12 Use SSH, VPN, or SSL/TLS for encryption of administrative access .................................................. 12 Encrypt data transmitted from TCP/IP devices to the host ............................................................. 13 Log settings must be compliant ....................................................................................................... 13 PCI-Compliant Wireless settings ...................................................................................................... 14 PCI-Compliant Use of Email .............................................................................................................. 14 Network Segmentation .................................................................................................................... 14 Never store cardholder data on internet-accessible systems .......................................................... 15 Never store credit card data outside of the dedicated fields .......................................................... 15 PCI-Compliant Delivery of Updates .................................................................................................. 15

Maintain an Information Security Program .......................................................................................... 16 Application System Configuration ........................................................................................................ 17

Payment Application Initial Setup and Configuration ...................................................................... 17

© 2012 NCR Hospitality Page 2 |


Revision Information

Name Title Date of Update Summary of Changes Nick Wagnitz Senior Manager

– Quest Global Solutions

31 October 2008 Initial Draft

Nick Wagnitz Senior Manager – Quest Global Solutions

14 May 2010 Protobase log settings added.

Nick Wagnitz Senior Manager – Quest Global Solutions

12 November 2010 Added: - data encryption from TCP/IP devices to the host - correct entry of credit card data

Irina LeMaire Technical Writer – Quest Global Solutions

5 January 2012 Changed: Configuring Credit Cards Added: Quest Web Service Installation – Using Internet Information Service (IIS) Manager


10 January 2012 Added: SQL Server 2008 - Maintenance Plan


23 August 2012 Updated for v2.0.1.


11 October 2012 Updated Product names

Irina LeMaire Technical Writer – NCR Hospitality

12 October 2012 Removed duplicate information

Note: This PA-DSS Implementation Guide must be reviewed on a yearly basis. Updates should be tracked and reasonable accommodations should be made to distribute or make the updated guide available to users.

Executive Summary

NCR Venue Manager version 2.0.1 has been PA-DSS (Payment Application Data Security Standard) certified, with Payment Application. For the PA-DSS assessment, we worked with the following PCI SSC approved Payment Application Qualified Security Assessor (PAQSA):

Assessor

Coalfire Systems, Inc. 150 Nickerson Street Suite 106 Seattle, WA 98109 This document also explains the Payment Card Industry (PCI) initiative and the Payment Application Data Security Standard (PA-DSS) guidelines. The document then provides specific installation, configuration, and ongoing management best practices for using Payment Application as a PA-DSS validated Application operating in a PCI Compliant environment.



PCI Security Standards Council Reference Documents The following documents provide additional detail surrounding the PCI SSC and related security programs (PA-DSS, PCI DSS, etc):

Payment Applications Data Security Standard https://www.pcisecuritystandards.org/documents/pci_pa_dss.pdf

PCI DSS https://www.pcisecuritystandards.org/documents/pci_dss_v1-2.pdf

Open Web Application Security Project (OWASP) http://www.owasp.org

Application Summary

Name: NCR Venue Manager

Specific File Version Numbers:

NCR Venue Manager 2.0.1

Credit Card Server: Protobase 6.01.06 or greater

Back Office: NCR Venue Manager 2.0.1

Setup:

Operating Systems: Windows Server 2008, Windows 7, Windows Server 2003, Windows XP, Windows Vista

Code base DB engine: Microsoft SQL 2005 SP3 or higher, SQL 2008

Application Description: Back Office Solution to support Quest POS Terminals, along with providing a turn key solution for Hospitality Venues.

Application Environment

Application Target Clientele:

Hospitality Venues requiring multiple levels of POS functionality, including but not limited to the following modules:

- Stock Control

- Order Entry

- Suite Catering

- Vending

Typical Network Implementations

Important: For PA-DSS compliance all telnet support on all Quest TCP/IP terminals must be disabled. Private Networks:

https://www.pcisecuritystandards.org/documents/pci_pa_dss.pdf

https://www.pcisecuritystandards.org/documents/pci_dss_v1-2.pdf

http://www.owasp.org/





Dataflow Diagram



Public Networks:

Note: The terminals must support and have SSL encryption enabled in this configuration.

Note: The PB container against the POS Server is a 3rd Party Gateway ProtoBase, which authorizes transactions with the processor. Note: The POS Server and Quest Service Controller must have SSL encryption enabled in this configuration.



Dataflow Diagram



Difference between PCI Compliance and PA-DSS Validation

As a software vendor, our responsibility is to be “PA-DSS Validated.” We have performed an assessment and certification compliance review with our independent assessment firm, to ensure that our platform does conform to industry best practices when handling, managing and storing payment related information. PA-DSS is the standard against which Payment Application has been tested, assessed, and validated. PCI Compliance is then later obtained by the merchant, and is an assessment of your actual server (or hosting) environment. Obtaining “PCI Compliance” is the responsibility of the merchant and your hosting provider, working together, using PCI compliant server architecture with proper hardware and software configurations and access control procedures. The PA-DSS Validation is intended to ensure that the Payment Application will help you achieve and maintain PCI Compliance with respect to how Payment Application handles user accounts, passwords, encryption, and other payment data related information. The Payment Card Industry (PCI) has developed security standards for handling cardholder information in a published standard called the PCI Data Security Standard (DSS). The security requirements defined in the DSS apply to all members, merchants, and service providers that store, process or transmit cardholder data. The PCI DSS requirements apply to all system components within the payment application environment which is defined as any network device, host, or application included in, or connected to, a network segment where cardholder data is stored, processed or transmitted.

The 12 Requirements of the PCI DSS:

Build and Maintain a Secure Network 1. Install and maintain a firewall configuration to protect data 2. Do not use vendor-supplied defaults for system passwords and other security parameters Protect Cardholder Data 3. Protect Stored Data 4. Encrypt transmission of cardholder data and sensitive information across public networks Maintain a Vulnerability Management Program 5. Use and regularly update anti-virus software 6. Develop and maintain secure systems and applications Implement Strong Access Control Measures 7. Restrict access to data by business need-to-know 8. Assign a unique ID to each person with computer access 9. Restrict physical access to cardholder data Regularly Monitor and Test Networks 10. Track and monitor all access to network resources and cardholder data 11. Regularly test security systems and processes Maintain an Information Security Policy 12. Maintain a policy that addresses information security



Considerations for the Implementation of Payment Application in a PCI-Compliant Environment

The following areas must be considered for proper implementation in a PCI-Compliant environment.

Sensitive Credit Card Data requires special handling

Remove Historical Credit Card Data

Set up Good Access Controls

Properly Train and Monitor Admin Personnel

Key Management Roles and Responsibilities

PCI-Compliant Remote Access

Use SSH, VPN, or SSL/TLS for encryption of administrative access

Encrypt data transmitted from all TCP/IP devices to the host

Log settings must be compliant

PCI-Compliant Wireless settings

Data Transport Encryption

PCI-Compliant Use of Email

Network Segmentation

Never store cardholder data on internet-accessible systems

Never store credit card data outside of the dedicated fields

Use SSL for Secure Data Transmission

Delivery of Updates in a PCI Compliant Fashion

Sensitive Credit Card Data requires special handling

NCR Venue Manager does not, nor has it ever stored any sensitive authentication, mag stripe, card validation (values or codes) and pin or pin block data for any purpose (PA DSS 1.1.5.c). The following handling requirements are required if there is a need for handling sensitive credit card data:

Collect sensitive authentication only when needed to solve a specific problem.

Store such data only in specific, known locations with limited access.

Collect only the limited amount of data needed to solve a specific problem.

Encrypt sensitive authentication data while stored.

Securely delete such data immediately after use.

Remove Historical Credit Card Data

If clients are upgrading from previous version of NCR Venue Manager (prior to v 1.5.36.96 ) the following steps must be performed to ensure that any security sensitive data is removed (PA DSS 1.1.4.a).

1. Complete a full SQL backup of the current Database 2. Perform upgrade of software 3. Run database maintenance plan (see below) 4. Test functionality of software 5. Securely Delete all ATW and SLS files on a periodic basis, from all workstations running NCR

Venue Manager 6. Complete full SQL back up of Database 7. Destroy previous version of Database Back up files prior to software upgrade



Purging of Cardholder Data

All sensitive Credit Card data exceeding the customer-defined retention period must be purged. NCR Venue Manager includes capabilities to securely wipe sensitive cardholder data automatically (PA DSS 2.1). This is performed using a function built into the SQL Database referred to as the Shrink Job. This process is scheduled as part of the standard Maintenance Plan on any NCR Venue Manager database and performs the following tasks in direct relation to the removal of historical sensitive cardholder data:

1. The customer must define a retention period with business justification. Credit Card data in sales logs will be retained for that period.

2. Cardholder data exceeding the customer-defined retention period will be purged. 3. Clerk Security Activity logs are retained for at least 1 month. 4.

It is the customer’s responsibility to ensure that the above processes are running.

The users must also configure their operating system to prevent inadvertent capture or retention of cardholder data, such as system backup or restore points. This applies even if you do not store cardholder data.

Set up Good Access Controls

The PCI DSS requires that access to all systems in the payment processing environment be protected through use of unique users and complex passwords. Unique user accounts indicate that every account used is associated with an individual user and/or process with no use of generic group accounts used by more than one user or process. Additionally any default accounts provided with operating systems, databases and/or devices should be removed/disabled/renamed as possible, or at least should have PCI DSS compliant complex passwords and should not be used. Examples of default administrator accounts include “administrator” (Windows systems), “sa” (SQL/MSDE), and “root” (UNIX/Linux). During the installation process, the NCR Venue Manager software creates a default user called quest_backoffice and quest_security password. Changing installation settings outside of this guide for these users will result in a non-compliance with the PCI DSS. As per the PCI standard, NCR Venue Manager:

Assigns unique IDs for user accounts

Uses password as a method of identification. The PCI standard requires the following password complexity for compliance (often referred to as using “strong passwords”):

Passwords must be at least 7 characters

Passwords must include both numeric and alphabetic characters

Passwords must be changed at least every 90 days

New passwords cannot be the same as the last 4 passwords PCI user account requirements beyond uniqueness and password complexity are listed below:



If an incorrect password is provided 6 times the account should be locked out

Account lock out duration should be at least 30 min. (or until an administrator resets it)

Sessions idle for more than 15 minutes should require re-entry of username and password to reactivate the session.

Do not use group, shared, or generic user accounts These same account and password criteria must also be applied to any applications or databases included in payment processing to be PCI compliant (PA DSS 3.2). NCR Venue Manager, as tested to in our PA-DSS audit, meets, or exceeds these requirements. For information on how to change the authentication directions please see Understanding Clerk Security. NCR Venue Manager must require unique usernames and complex passwords for all administrative access and for all access to cardholder data. [Note: These password controls are not intended to apply to employees who only have access to one card number at a time to facilitate a single transaction. These controls are applicable for access by employees with administrative capabilities, for access to servers with cardholder data, and for access controlled by the application.] Control access, via unique username and PCI DSS-compliant complex passwords, to any PCs, servers, and databases with payment applications and cardholder data. NCR Venue Manager requires unique usernames and complex passwords for administrative access.

Do not use administrative accounts for application logins (e.g. don’t use the “sa” account for application access to the database).

Assign strong passwords to these default accounts (even if they won’t be used), and then disable or do not use the accounts.

Assign strong application and system passwords whenever possible.

Create PCI DSS-compliant complex passwords to access the payment application, per PCI Data Security Standard 8.5.8 through 8.5.15

Control access, via unique username and PCI DSS-compliant complex passwords, to any PCs, servers, and databases with payment applications and cardholder data.

Properly Train and Monitor Admin Personnel

It is your responsibility to institute proper personnel management techniques for allowing admin user access to credit cards, site data, etc. You can control whether each individual admin user can see the full credit card number, or only last 4 characters of the Card Number. In most systems, security breach is the result of unethical personnel. So pay special attention to whom you trust into your admin site and who you allow to view full decrypted payment information.

Key Management Roles and Responsibilities

All Credit Card information is securely encrypted within NCR Venue Manager using Encryption Keys. These keys are dynamically created and no cryptographic material is stored. The Vendor does not have the ability nor requires to update these encryption keys. As part of normal operations, you will also need to train and ensure that the Super Admin personnel understand, accept and perform duties in their role as Encryption Key custodians. As a custodian, they



are responsible for the safeguarding of these chosen keys, and for performing routine updates to the keys as a normal course of business, defined periodically herein. Super Admin users/Key Custodians should fully familiarize themselves with PCI compliance guidelines, as those will contain the most relevant and accurate security procedures in addition to Payment Application specific guidelines in this document.

PCI-Compliant Remote Access

The PCI standard requires that if employees, administrators, or vendors are granted remote access to the payment processing environment; access should be authenticated using a two-factor authentication mechanism (username/ password and an additional authentication item such as a token or certificate) (PA DSS 10.2). Our default application for remote support is Go To Assist, however in those situations where this is not available please ensure the following precautions are taken. In the case of vendor remote access accounts, in addition to the standard access controls, vendor accounts should only be active while access is required to provide service. Access rights should include only the access rights required for the service rendered, and should be robustly audited. If users and hosts within the payment application environment may need to use third-party remote access software such as Remote Desktop (RDP)/Terminal Server, pcAnywhere, etc. to access other hosts within the payment processing environment, special care must be taken. In order to be compliant, every such session must be encrypted with at least 128-bit encryption (in addition to satisfying the requirement for two-factor authentication required for users connecting from outside the payment processing environment). For RDP/Terminal Services this means using the high encryption setting on the server, and for pcAnywhere it means using symmetric or public key options for encryption. Additionally, the PCI user account and password requirements will apply to these access methods as well. When requesting support from a vendor, reseller, or integrator, customers must take the following precautions:

Change default settings (such as usernames and passwords) on remote access software (e.g. VNC)

Allow connections only from specific IP and/or MAC addresses

Use strong passwords for logins in accordance with PCI DSS 8.1, 8.3, and 8.5.8-8.5.15

The remote access session is securely encrypted per PCI DSS 4.1

Enable account lockouts after a certain number of failed login attempts, per PCI DSS 8.5.13

Require that remote access take place over a VPN as opposed to allowing connections directly from the internet

Enable logging for auditing purposes

Access to customer passwords is restricted to an authorized reseller/integrator or application vendor support personnel

Customer passwords are established according to PCI DSS 8.1, 8.2, 8.4, and 8.5 requirements.

Use SSH, VPN, or SSL/TLS for encryption of administrative access

SSH, VPN, or SSL/TLS should be used when accessing SQL Server 2005/2008 via a non-console application. NCR Venue Manager does not allow non-console administration.



Encrypt data transmitted from TCP/IP devices to the host

Configure all TCP/IP communication from terminals directly or via an ECM to encrypt data transmitted to the host.

Log settings must be compliant

NCR Venue Manager has PA-DSS compliant logging enabled by default. This logging is not configurable and may not be disabled. Disabling or subverting the logging function of NCR Venue Manager in any way will result in non-compliance with PCI DSS. NCR Venue Manager Logging is performed in 4 areas they are as follows:

1. ATW Files – These files record transactional and communication messaging from the POS Terminals to the Back Office POSServer or COMMS Server. ATW file is valid for POSServer, while the COMMS Service stores it in the Database. Credit Card information, including Credit Card number may be included in these files, however if present will be masked in accordance with specifications.

2. CCDLL.ATW – These files are used primarily as a resource for support tracking / issues discovery. Credit Card information, including Credit Card number may be included in these files, however if present will be masked in accordance with specifications.

3. Security Logging – within the NCR Venue Manager database we log any activity that will occur using a complex password. This will include but not limited to the following activities:

a. Creating a new complex password b. Logging into a module using the complex password c. Modifying a password for a complex password d. Failed Attempts of logging into modules

4. Credit Card Table – A table within the SQL Database retains Credit Card transaction specific data for the processor. This table includes both masked and encrypted fields.

In Protobase, Log files are configurable. To satisfy PCI compliance and increase security of their Credit Card data, the users must enable the Unique ID in lieu of Accnt # in API option in the Settings tab of the Location Information dialogue. By selecting this option you will ensure that the system will assign a Unique ID to each account, and will pass that ID in the output response instead of the full account number (PA DSS 4.1.b).

NCR Venue Manager v2.0.1 facilitates centralized logging

NCR Venue Manager facilitates centralized logging with all security logging stored within the SQL database. You can use SQL Server Import and Export Wizard to export this data into Excel spreadsheets.

Services and Protocols

NCR Venue Manager does not require the use of any insecure services or protocols. Here are the services and protocols that NCR Venue Manager does require:

HTTPS

SSL



PCI-Compliant Wireless settings

For wireless networks transmitting cardholder data or connected to the cardholder data environment, you must use industry best practices (for example, IEEE 802.11i) to implement strong encryption for authentication and transmission (PA DSS 6.2.b).

For all wireless implementations, use WPA/WPA2.

o Perimeter firewalls are installed between any wireless network and the cardholder data environment (PCI DSS 1.2.3); and

o These firewalls deny or appropriately control any traffic from the wireless environment into the cardholder data environment (PCI DSS 1.2.3); and

o All wireless networks implement strong encryption (e.g. AES) (PCI DSS 2.1.1); and

o Wireless encryption keys must be changed from their default value (PCI DSS 2.1.1); and

o Wireless encryption keys are changed anytime someone with knowledge of the keys leaves the company (PCI DSS 2.1.1); and

o Wireless encryption keys are changed anytime someone with knowledge of the keys changes positions (PCI DSS 2.1.1); and

o Default SNMP community strings on wireless devices were changed (PCI DSS 2.1.1 / PA DSS 6.1.f); and

o Default passwords/passphrases on access points were changed (PCI DSS 2.1.1); and

o Firmware on wireless devices is updated to support strong encryption for authentication and transmission over wireless networks (e.g. WPA/WPA2) (PCI DSS 2.1.1); and

o Other security-related wireless vendor defaults, if applicable, are changed (PCI DSS 2.1.1)

PCI-Compliant Use of Email

NCR Venue Manager does not have functionality for sending of PANs via email, instant messenger or chat programs. Whilst NCR Venue Manager is capable of e-mailing reporting information this PAN / Complete Credit Card information is not able to be produced and e-mailed.

Network Segmentation

The PCI DSS requires that firewall services be used (with NAT or PAT) to segment network segments into logical security domains based on the environmental needs for internet access. Traditionally, this corresponds to the creation of at least a DMZ and a trusted network segment where only authorized, business-justified traffic from the DMZ is allowed to connect to the trusted segment. No direct incoming internet traffic to the trusted application environment can be allowed. Additionally, outbound internet access from the trusted segment must be limited to required and justified ports and services.

Refer to the standardized Network diagram for an understanding of the flow of encrypted data associated with NCR Venue Manager.



Never store cardholder data on internet-accessible systems

Never store cardholder data on Internet-accessible systems (e.g. web server and database server must not be on same server) (PA DSS 9.1.b).

Never store credit card data outside of the dedicated fields

Some areas of the NCR Venue Manager software (e.g. Suite Catering and Tags) require manual data entry for Credit Cards. Train your personnel to enter sensitive Credit Card data into the dedicated fields only. For example, the Credit Card number should never be entered into the Card Name, Notes or any other Text field.

PCI-Compliant Delivery of Updates

NCR Venue Manager will be updated from time to time in conjunction with approval from the customer directly. All upgrades are performed by NCR Hospitality staff that have been trained with this process. On the notification of any release of the NCR Venue Manager application, or at least annually, the QA Coordinator or delegate must complete a review of NCR Venue Manager PA-DSS implementation Guide. This will be in conjunction with a complete review of the PA-DSS Requirements. As a development company, we keep abreast of the relevant security concerns and vulnerabilities in our area of development and expertise. Our development and testing process will address any security concerns and are reviewed regularly. Once we identify a relevant vulnerability, we work to develop and test a patch that helps protect NCR Venue Manager against the specific, new vulnerability. We attempt to publish a patch within 10 days of the identification of the vulnerability. We will then contact vendors and dealers to encourage them to install the patch. Typically, merchants are expected to respond quickly to and install available patches within 30 days. We do deliver software and/or updates via remote access to customer networks. For receiving updates via remote access, we recommend that merchants:

Use a personal firewall product if computer is connected via VPN or other high-speed connection, to secure these “always-on” connections, per PCI Data Security Standard 1.3.10.

Use 2-factor authentication for remote access.

Use secure modem use, per PCI Data Security Standard 12.3: 12.3 Develop usage policies for critical employee-facing technologies (such as modems and wireless) to define proper use of these technologies for all employees and contractors. Ensure these usage policies require the following: 12.3.1 Explicit management approval 12.3.2 Authentication for use of the technology 12.3.3 List of all such devices and personnel with access 12.3.4 Labeling of devices with owner, contact information, and purpose 12.3.5 Acceptable uses of the technologies 12.3.6 Acceptable network locations for the technologies 12.3.7 List of company-approved products 12.3.8 Automatic disconnect of modem sessions after a specific period of inactivity 12.3.9 Activation of modems for vendors only when needed by vendors, with immediate deactivation after use



12.3.10 When accessing cardholder data remotely via modem, prohibition of storage of cardholder data onto local hard drives, floppy disks, or other external media. Prohibition of cut-and-paste and print functions during remote access.

Maintain an Information Security Program

In addition to the preceding security recommendations, a comprehensive approach to assessing and maintaining the security compliance of the payment application environment is necessary to protect the organization and sensitive cardholder data. The following is a very basic plan every merchant/service provider should adopt in developing and implementing a security policy and program:

Read the PCI DSS in full and perform a security gap analysis. Identify any gaps between existing practices in your organization and those outlined by the PCI requirements.

Once the gaps are identified, determine the steps to close the gaps and protect cardholder data. Changes could mean adding new technologies to shore up firewall and perimeter controls, or increasing the logging and archiving procedures associated with transaction data.

Create an action plan for on-going compliance and assessment.

Implement, monitor and maintain the plan. Compliance is not a one-time event. Regardless of merchant or service provider level, all entities should complete annual self-assessments using the PCI Self Assessment Questionnaire.

Call in outside experts as needed.



Application System Configuration

Below are the operating systems and dependent application patch levels and configurations supported and tested for continued PCI DSS compliance.

All latest updates and hot-fixes should be tested and applied. The operating systems that are currently available include:

o Windows XP Professional with SP 3 o Windows Server 2003 SP 4 o Windows Vista. o Windows 7 o Windows Server 2008

512 MB of RAM minimum, 2GB or higher recommended for Payment Application

1 GB of available hard-disk space

TCP/IP network connectivity

SQL Server 2005 SP3 or higher / SQL Server 2008. All latest updates and hot-fixes should be tested and applied.

Payment Application Initial Setup and Configuration

Installing the Payment Application

Installing NCR Venue Manager

Installing NCR Venue Manager on the Server

Please read the NCR Venue Manager Minimum Requirements before following these steps. If you have any questions or concerns as to whether the PC is suitable for this install, please contact [email protected].

1. Download the application from the source provided by NCR Hospitality.

2. Close all other application running on your PC.

3. In the installation folder, open Setup.exe. The Install Shield Wizard will launch to guide you through the installation process. Select Accept the terms of the license agreement, then click Next.

4. Enter the User Name and the Organization for which this installation is taking place, then select Next.

5. Specify the Destination Folder for this install. By Default, NCR Venue Manager will install in the folder below: C:\Program Files\Quest POS\NCR Venue Manager However this path can be changed by the user if required. Click Next to move through to the next screen.

6. When prompted in the Setup Type dialogue, select the Server option, then click Next.

mailto:[email protected]



This option will install NCR Venue Manager, install SQL Server 2005 Express, establish a database connection, then install and setup Quest Mirror. Click Next.

7. A confirmation screen will open. Please ensure that the Destination Folder and the Install Type are correct. If required, click Back to change these settings. If all is correct, click Install to begin the process. This installation process may take several minutes.

8. At the Install Shield Wizard Completed screen, select Finish. The SQL Server Launch installation will begin. This program will guide you through the process of creating and setting up a connection to an NCR Quest database. Click Next.

9. At the Options screen, select the default Database option to create a new database on the local PC. Click Next.

10. If the system detects a version of SQL on the destination computer, it will prompt you to select an Instance from the drop-down list in the Setup dialogue box. If you don't have SQL installed the program will prompt you to enter a sa password for installing Microsoft .NET Framework and SQL Server 2005 Express. To see what constitutes a strong password, press the Strong Password Requirements button. Once the program has accepted the password, press the Install SQL Server 2005 Express button. The installation process may take several minutes.

11. When both Microsoft .NET Framework and SQL Server 2005 Express are installed, click Next.

12. On the Database screen, enter the Database Name. There must not be any spaces in the name, e.g. QVM_SmithHotel.

13. Create and confirm a quest_backoffice password. This password will allow you to connect to the database.

14. Create and confirm a quest_security password. This strong password is required to allow you to access credit card information on the database. If necessary, check the Strong Password Requirements. Click Next.

15. The database will be created and patched to the latest script. Click Finish.

16. Restart the PC once the installation process has completed.

17. Once the PC has rebooted, you can start working with NCR Venue Manager (ensuring that you load NCR Venue Manager Mirror.exe).

18. When opening NCR Venue Manager for the first time, using v1.5.152 or greater, an SDelete License Agreement will open. This is a system requirement relating to credit card security. Select Agree.



Installing NCR Venue Manager on a Workstation

Before installing a Workstation, make sure that NCR Venue Manager and SQL Server applications are installed on the Server.

1. Download the application from the source provided by NCR Hospitality.

2. Close all other application running on your PC.

3. In the installation folder, open Setup.exe. The Install Shield Wizard will launch to guide you through the installation process. Select Accept the terms of the license agreement, then click Next.

4. Enter the User Name and the Organization for which this installation is taking place, then select Next.

5. Specify the Destination Folder for this install. By Default, NCR Venue Manager will install in the folder below: C:\Program Files\Quest POS\NCR Venue Manager However this path can be changed by the user if required. Click Next to move through to the next screen.

6. When prompted in the Setup Type dialogue, select the Workstation option, then click Next. This option will install NCR Venue Manager, establish a connection to a database, and setup Quest Mirror.

7. A confirmation screen will open. Please ensure that the Destination Folder and the Setup Type are correct. If required, click Back to change these settings. If all is correct, click Install. The installation process may take several minutes.

8. At the Install Shield Wizard Completed screen, click Finish. The SQL Server Launch installation will begin. This program will guide you through the process of creating and setting up a connection to an NCR Quest database. Click Next.

9. At the Setup screen, enter the details of the database to which you want to connect. Enter the name of the Server (or select from the drop-down list). The Username field will be populated with quest_backoffice.

10. Enter the password for the database access. Select the Database from the drop-down list.

11. Select the master directory from which you want to mirror the files by clicking on the ellipsis next to the Master Directory field, and browsing for the file. Click Next.

12. Click Finish.



13. Restart the PC once the installation process has completed.

14. Once the PC has rebooted, you can start working with NCR Venue Manager (ensuring that you load NCR Venue Manager Mirror.exe).

15. When opening NCR Venue Manager for the first time, using v1.5.152 or greater, an SDelete License Agreement will open. This is a system requirement relating to credit card security. Select Agree.

Additional SQL settings (recommended)

To complete the installation process we recommend that you change the Max Degree of Parallelism setting in the SQL server. By default, this setting is zero, which means SQL Server can use as many processors as it wants to distribute a query. Sometimes, SQL Server can run into a problem by excessive distribution of queries. To avoid this, we recommend setting this value to half or less of the available processors.

1. Open the SQL Server Management Studio.

2. Open the Server Properties > Advanced.



3. If the setting of Max Degree of Parallelism is zero, click OK to close the Properties window.

4. Run the script below, where the N value is half or less of the available processors.

sp_configure 'show advanced options', 1;

GO

RECONFIGURE WITH OVERRIDE;

GO

sp_configure 'max degree of parallelism', N;

GO

RECONFIGURE WITH OVERRIDE;

GO

5. Check the Advanced settings again and make sure that the Max Degree of Parallelism setting has changed to the N value.

6. Exit the SQL Server Management Studio.

System Clerk

NOTE: The System Clerk password by default is 2311, however it is a requirement that after the initial installation this password is changed. To do this go to the System Dialog, then the Other Tab, and enter the old password, enter a new unique password, and re confirm the new password.

Addressing Inadvertent Capture of PAN

Disable System Restore Settings

Disabling System Restore – Windows 7

1. Right-click on Computer.

2. Select Properties.

3. Select the System Protection tab.



4. Click Configure.

5. Select Turn off system protection.

6. Click Apply.

7. Click OK to shut the System Protection window.

8. Click OK again to shut the System Properties window.

9. Reboot the computer.

Encrypt the System PageFile.sys

Encrypting PageFile.sys – Windows 7

* Please note that in order to perform this operation the hard disk must be formatted using NTFS. 1. Click on the Windows Start button and in the search box type in “cmd”.

2. Right-click on cmd.exe and select Run as Administrator.

3. To Encrypt the Pagefile type the following command:” fsutil behavior set EncryptPagingFile

1”.



4. To verify configuration type the following command: “fsutil behavior query

EncryptPagingFile”.

5. If encryption is enabled EncryptPagingFile = 1 should appear

6. In the event you need to disable PageFile encryption type the following command: “fsutil

behavior set EncryptPagingFile 0”.

7. To verify configuration type the following command: “fsutil behavior query

EncryptPagingFile”.

8. If encryption is disabled “EncryptPagingFile = 0” should appear.

Clear the System Pagefile.sys on shutdown

Windows has the ability to clear the Pagefile.sys upon system shutdown. This will purge all temporary data from the pagefile.sys (temporary data may include system and application passwords, cardholder data (PAN/Track), etc.). NOTE: Enabling this feature may increase windows shutdown time.

1. Click on the Windows Start button and in the search box type in “regedit”.



2. Right-click on regedit.exe and select Run as Administrator.

3. Navigate to HKLM \ System \ CurrentControlSet \ Control \ Session Manager \ Memory

Management.

4. Change the value from “0” to “1”.

5. Click OK and close Regedit.

6. If the value does not exist, add the following:

1. Value Name: ClearPageFileAtShutdown

2. Value Type: REG_DWORD

3. Value: 1

Disable System Management of Pagefile.sys

Disabling System Management of PageFile.sys – Windows 7

1. Right-click on Computer.

2. Select Properties.

3. Select the Advanced tab.



4. Under Performance, click on the Settings button.

5. Go to the Advanced tab.

6. Under Virtual Memory, click Change.



7. Un-flag the Automatically manage page file size for all drives checkbox.

8. Flag Custom Size.

9. Enter the following for the size selections:

o Initial Size – as a good rule of thumb, the size should be equivalent to the amount of

memory in the system.

o Maximum Size – as a good rule of thumb, the size should be equivalent to 2x the

amount of memory in the system.

10. Click OK, OK, and OK.

11. Reboot your computer when prompted.

Disable Windows Error Reporting

Disabling Windows Error Reporting – Windows 7

1. Open the Control Panel.

2. Open the Action Center.

3. Click on Change Action Center Settings.



4. Click Problem Reporting Settings.

5. Flag Never Check for Solutions.



Configuring Credit Cards in POSServer

About POSServer Credit Cards tab

Accessing the Credit Cards tab

About POSServer Credit Cards tab

In compliance with the PCI requirements, only users with Admin permissions can view and modify Credit Card settings in POSServer. When configuring Credit Cards in POSServer, remember that the Credit Card settings in your NCR Quest Manager software will override the settings in the POSServer.

Accessing the Credit Cards tab

1. Open the POSServer application.

2. Click on the Properties button in the top right corner of the main page. The Properties dialogue will open.



3. Select the Credit Cards tab in the Properties dialogue.

4. When prompted, enter your Clerk ID and your Complex Password. This will be the same Complex Password you use in the Back Office software. If you have logged on successfully, the system will display the Credit Cards tab. If you don't have a Complex Password, refer to the Understanding Clerk Security chapter.

5. Flag the Enable credit card verification and the Notify SQL Cashup dialog checkboxes if you need the software to perform Credit Card verification.

6. Select the appropriate option for local approval from the drop-down list.

7. Enter the maximum amount for local approval.

8. From the S/W drop-down list, select Protobase.

9. Enter the Approval delay in seconds.

10. Enter the Protobase Gateway IP and Gateway Port.

11. Enter the Chain Code and the Source IP Address. Leave these fields blank unless instructed otherwise by Protobase.

12. Item Code is a definable field that the system sends to the Protobase software. Usually, it is defined as the number 1. If the Protobase software requires a different code, please contact Protobase.

13. Item Text is a definable field that the system sends to the Protobase software. Usually, it is defined as the word SALE. If the Protobase software requires a different text, please contact Protobase.



Configuring Credit Cards in Quest Service Controller

About Quest Service Controller Credit Cards tab

Credit Cards Settings

About Quest Service Controller Credit Cards tab

In compliance with the PCI requirements, only users with Admin permissions can view and modify Credit Card settings in Quest Service Controller. When configuring Credit Cards in Quest Service Controller, remember that the Credit Card settings in your NCR Quest Manager software will override the settings in the Quest Service Controller.

Credit Cards Settings

1. Open the Quest Service Controller application.



2. Select the Credit Cards tab.

3. When prompted, enter your Clerk ID and your Complex Password. This will be the same Complex Password you use in the Back Office software. If you have logged on successfully, the system will display the Credit Cards tab. If you don't have a Complex Password, refer to the Clerk Security Feature document in your NCR Quest Manager Manual.

4. From the S/W drop-down list, select Protobase.

5. Enter the Protobase Gateway IP and Gateway Port.

6. Enter the Chain Code and the Source IP Address. Leave these fields blank unless instructed otherwise by Protobase.

7. Item Code is a definable field that the system sends to the Protobase software. Usually, it is defined as the number 1. If the Protobase software requires a different code, please contact Protobase.

8. Item Text is a definable field that the system sends to the Protobase software. Usually, it is defined as the word SALE. If the Protobase software requires a different text, please contact Protobase.

9. Enter the Approval delay in seconds.

10. Configure the Local approval option by selecting The Local Approval option from the drop-down list. This feature allows your software to issue local Authorisations to Credit Cards under a certain amount. Use this feature with extreme caution. The system will validate the credit card number and expiry data, but will not be able to validate if the card is active or if there is sufficient funds. Hence may result in revenue loss.

11. Enter the maximum amount for local approval. Use this feature with extreme caution. The higher your Maximum local approval, the greater the liability you are accepting.

Please refer to the Credit Cards Setup document for more information.



Configuring the Fusebox Settings within Departments - NCR Venue Manager

Configuring Fusebox Settings

1. In the Organization module, open the Departments tab.

2. Open the Department you want to modify.

3. Open the Other tab. You will note the Fusebox Settings for Protobase group of fields.

4. Enter Chain Code and Location Name / Source IP Address. Both values are supplied by Protobase.

5. Press OK to save changes and exit the Department dialogue.



NCR Venue Manager – Conducting Test Transactions

1. After successfully defining your credit card set up and terminal allocation, it is required that a number of transactions are performed for testing purposes.

2. At a POS Terminal please ensure the following transaction are performed and validated within both the NCR Venue Manager software, and the Gateway Software.

a. Cash Sale

b. Credit Card sale using a swipe card

c. Credit Card sales using a manual entry of number and expiry

d. Refund Cash Sale

e. Refund Credit Card Sale using manual entry

f. Credit Card Authorisation

g. Credit Card sales with Tip included



Understanding Clerk Security

About the Clerk Security feature

About Simple Passwords

About Complex Passwords

About Administrator Privileges

About the Clerk Security feature

Clerks have always been a central part of the NCR Quest Manager suite of software, and they can be used not only to track and log sales at the terminal, but with the introduction of the Clerk Security features listed below, far greater control has been placed on how and who has permission to access the secure areas of the software such as Sales Browser.

The introduction of the Clerk Security feature has resulted in a number of significant changes, which will be covered in the document below, and include the following:

The creation of three types of Clerk passwords / levels of privilege - "Simple", a "Complex", and "Administrator".

Clerk Type Hierarchies. These provide a way in which clerks who belong to a higher Hierarchy, such as Site Administrator, can Add or Modify the details of clerks who belong to lower Hierarchies.

Clerks can now be assigned quest_security rights, allowing them to view and modify Credit Card data within various areas of the software.

About Simple Passwords

Simple Passwords are those that are configured for a clerk and are used when logging on at the Terminal, logging on to various areas of the software, such as CashRoom and Reports and can still be used to log onto the Clerk module when required.

NOTE: If logging into the Clerk module with a Simple Password, you will no longer have the ability to Add a new Clerk, or view the Clerk Types tab.

***This can only be done if you log into the Clerk module using your Complex password and have been assigned Administrative privileges.

Configuring a Simple Password for a Clerk

1. From within your NCR Quest Manager software, select the Clerk button from the toolbar at the left of screen.

2. When prompted, enter your Clerk ID and Simple Password to gain access to the Clerk module.

3. Within the grid listing of clerks, select the Clerk to which you wish to assign a password. Double-click on this entry or select the Modify button to display the Add/Modify Clerk dialogue.

4. In the password field, enter the Simple Password that will be assigned to the selected Clerk. Once configured, select OK to save changes to the return to the main Clerks grid.



NOTE: You can only View or Edit passwords for clerks who have been configured with a hierarchy ID greater than yours.

About Complex Passwords

Complex passwords are configured for clerks who will require access to the Credit Card data that is stored within the secure areas of the software such as Sales Browser. If a clerk has not been configured with a Complex password, and attempts to access the Credit Card data in these areas, they will be met with a message notifying them that they do not possess sufficient access rights.

In NCR Quest Manager, Complex, or Strong Password is defined as follows:



NOTE: The process of assigning Complex Passwords to individual clerks can be performed only by clerks who have been assigned Administrator privileges (see below), or who have access to the quest_security password.

Configuring a Complex Password for a Clerk


2. When prompted, enter your Clerk ID and Simple Password or Complex Password to gain access to the Clerk module.

3. Expand the Advanced Options Panel at the left of screen to display the available Wizards, "Clerk Swap" and "Security".

4. From the grid listing of clerks, locate the Clerk to which a Complex Password will be assigned. Highlight this Clerk using your cursor and select the Security Wizard from the Advanced Options Panel.

5. If you have used your simple Password to access the Clerk module, you will be prompted at this point to enter either your Administrator Password, or if this is unknown, the quest_security password. This quest_security password is that which was configured previously for the quest_security database user, and needs to be entered exactly as it was initially entered. If the quest_security password is being used to enter the Clerk Security Wizard, be sure to select the Use Quest Security Password checkbox. Select OK to proceed with the Wizard.

6. The Clerk Security Wizard will display the current Security status of the selected Clerk. In the instance below, our clerk- Ron Master has not yet been configured with a Complex Password, allowing him access to the secure areas of the software.



7. Select the Security Enabled checkbox to activate the clerks security status. You will be prompted to enter and confirm the password that will now become the Complex password for this clerk. Once the password has been entered in the Confirm field, select your Tab key to determine if the password is valid. This password will be required when they attempt to view Credit Card details in the secure areas of the NCR Quest Manager software.

8. If the password meets the required criteria, the OK button will become available and select this to proceed with the Clerk Security wizard.



9. The selected Clerk will now have been configured with a Complex password, and this password will have to be reset each 90 days. The expiry date of the configured password will be listed in the "Password Change Required" field.

10. Once all details have been configured for this clerk, select the Finish button to complete the Wizard.

About Administrator Privileges

Administrator Privileges relate to the ability to Add and Modify Clerks, Clerk Types and Credit Card data within the back office software. Typically, this access would be issued to the Site Administrators, and Supervisors within a venue.

Even once a clerk has been assigned Administrator rights within the software, they still will only be able to View and Modify Clerk Types that have been configured with a Hierarchy ID which is greater than the Hierarchy ID to which they have been assigned.

For example, John Smith, a HR Manager (a Hierarchy ID of 3) within Site X, has been given Administrator Privileges within the database. When John logs into the Clerk module, he is able to see only Clerk Types with a Hierarchy ID of 3 and greater.

NOTE: Only clerks which have been assigned Administrator privileges can assign Administrative access to other clerks with equal or lesser hierarchy.

Configuring Administrator privileges for a Clerk


2. When prompted, enter your Clerk ID and Simple Password or Complex password to gain access to the Clerk module.

3. Expand the Advanced Options Panel at the left of screen to display the available Wizards, "Clerk Swap" and "Security".



4. From the grid listing of clerks, locate the Clerk to which a Complex Password will be assigned. Highlight this Clerk using your cursor and select the Security Wizard from the Advanced Options Panel.

5. If you used your Simple password to access the Clerk module, you will be prompted to enter either an Administrator Password, or if this is not known, the quest_security password. This quest_security password is that which was configured previously for the quest_security database user, and needs to be entered exactly as it was initially entered. If the quest_security password is being used to enter the Clerk Security Wizard, be sure to select the Use Quest Security Password checkbox. Select OK to proceed with the Wizard.

6. The Clerk Security Wizard will display the current Security status of the selected Clerk. In the instance below, our clerk- Ron Master has not yet been configured with a Complex Password, allowing him access to the secure areas of the software.

7. Select the Security Enabled checkbox to activate the clerks security status. You will be prompted to enter and confirm the password that will now become the Complex password for this clerk. Once the password has been entered in the Confirm field, select your Tab key to determine if the password is valid. This password must be unique to this clerk only, and will be required when they attempt to view Credit Card details in the secure areas of the NCR Venue Manager software. NOTE: This password must be longer that 7 characters and must contain a combination of letters and numbers.



8. If the password meets the required criteria, the OK button will become available and select this to proceed with the Clerk Security wizard.

9. The selected Clerk will now have been configured with a Complex password, and this password will have to be reset each 90 days. The expiry date of the configured password will be listed in the "Password Change Required" field.

10. If you wish to configure this clerk with Administrator Access (Administrator Privileges), select the appropriate checkbox. Once this checkbox is flagged, they will be able to use the password which has been configured in this dialogue to access the secure areas of the software. If the password requires changing, or becomes expired, use the Change Password button.

11. Select the Finish button to complete the Security wizard process.



Exporting Clerk Security Log with SQL Server Import and Export Wizard

1. Click on the Windows Start button.

2. Select the All Programs > Microsoft SQL Server 2008.

3. Run Import and Export Data (32-bit) as an Administrator. The SQL Server Import and Export Wizard will open.

4. From the Welcome page click Next.

5. Leave the default Data source or choose a different one from the drop-down list.

6. From the drop-down list, select the Server name.

7. Click on the Refresh button and select the required database from the drop-down list.

8. Click Next.



9. On the Choose a Destination page, select Microsoft Excel as the Destination.

10. Browse to the Excel file path.

11. Click Next.

12. On the Specify Table Copy or Query page, select the Copy data from one or more tables or views option.

13. Click Next.

14. On the Select Source Tables and Views flag the tblClerkSecurityLog source.

15. Click Next.



16. The Review Data Type Mapping page will open.

17. Click Next.



18. On the Save and Run Package page, flag the Run immediately option.

19. Click Next.

20. To complete the Wizard, click Finish. The program will execute the export.

21. If the execution has been successful, the wizard will display the grid as follows.

22. Click Close.

23. The destination Excel file should now contain the exported data.



Credit Card Security Features (PCI Compliance)

NCR Venue Manager's Security Features

About the Security Password for the quest_security Database User

Configuring the Security Password for the quest_security Database User

NCR Venue Manager's Security Features



- A new tab "Database User" found in the Quest Service Manager application which allows the user to configure a unique password for the quest_security user

- Masking of Credit Card data numbers and expiry dates within various dialogues and reports

- Clerk Security Wizard found in Advanced Options Panel of the Clerk dialogue once the Security password has been configured

About the Security Password for the quest_security Database User

Upon applying the Upgrade to your NCR Quest Manger server, to ensure you are PCI Compliant you must first configure a password for the new quest_security database user.

Once configured, this user will have the ability to assign special permissions to individual clerks which will allow them to access the Credit Card data which will be hidden from clerks who have not been given permission. As a general rule, such permission would only be given to the staff that a site determines as being trustworthy and responsible enough to handle such confidential data, and this should be considered prior to assigning the Security password explained further in this document.

NOTE: The creation of the quest_security user can take place either via the Quest Service Manager (by following the steps listed below), or if a quest_security user does not exist for the database, one will be created when running the Upgrade Wizard.

If you do not wish to create a quest_security user during the Upgrade process, select the "Skip creation of quest_security user" checkbox.



Configuring the Security Password for the quest_security Database User

1. Right -click on the Quest Service Manager icon located in the System Tray of your Server. Select the Open Quest Service Manager option to display the dialogue on screen

2. Once open on your machine, select the Database User tab. You will need to enter the name of the database Server, and the sa password that has been configured for the database to which you wish to connect.

NOTE: It is imperative that you enter the sa password for this database in order to be able to further configure the quest_security database user.

3. Once you have entered the Name/IP address of the database server, and the sa password, select the Refresh button to populate the list of databases

4. Select the applicable database from the list followed by the "Click to test the connection" button.

If all details have been entered successfully, you will be met with the following screen,



which indicates that a unique password for the quest_security Database User has not been configured for this database previously

5. Select the Create quest_security user button to begin the process of assigning a unique password to this database user

6. You will be prompted at this stage to enter a "Strong" password for the quest_security user. If you are unsure of what constitutes a Strong password, select the Strong Password Requirements button and a dialogue will be presented to you on screen containing the following information

NOTE: Please ensure that the password that you enter is easily remembered, as this will be required when assigning Credit Card security permissions to individual clerks within your NCR Venue Manager database



7. Once you have entered a "Strong" password in the Password field, select Confirm to ensure that the password you have entered meets the requirements stipulated above. If successful, you will be met with the following message- "Quest Service Manager has detected that your database user configuration is valid"

NOTE: The process of assigning a password to the quest_security user needs only to take place once, and the process should not be required in the future.

8. Best practices for the management of the password control of the quest_security user should include the enforcement of the password policy with the SQL properties.



9. From the SQL Server Management Studio application, using the tree view on the left of the application, navigate to the Security Node, expand this and expand the Logins Node.

10. Right click on the quest_security user and select the properties option.

11. Ensure the “Enforce Password Policy” and “Enforce Password Expiration” is enabled as shown following:

12. Select the OK button.

Adding clerk types - NCR Venue Manager

What are clerk types?

How to add a new clerk type in NCR Venue Manager

What are clerk types?

A Clerk Type is a level that is assigned to a clerk. The user can use this feature to define whether a particular type of Clerk is allowed to view specific areas in the software or edit specific information.

How to add a new clerk type in NCR Venue Manager

1. Open the Clerks module using your complex password.

2. Select the Clerk type tab.

3. Select the New button to add a new clerk type. An Add/Modify Clerk Type dialogue box will open.

4. Type in a Hierarchy ID number, or click on the blue arrow to generate a number automatically.



5. Enter the Description of the clerk type. This description would usually be the level of job position required from a clerk, e.g. Manager.

6. Select the Organization for the Clerk Type.

7. Select the required Job Code from the available options in the drop-down list.

8. Select the appropriate checkbox(es) for the POS Access Levels

9. In the Access Areas tab, flag the boxes to allow the clerk type access to these parts of the Back Office software that are relevant to their job. For example, the Manager may be the only Clerk Type that has access to reports, cashup, or stock control.

10. In the Reports tab, flag the checkboxes against the Reports you want to enable for this Clerk Type.

11. In Tag Types, flag the checkboxes which will allow the Clerk Type to use these Tag Types. A clerk tag type is automatically recognized by the terminal, when the clerk ID is entered. Any "member" number that is under 60,000 is automatically detected as being a clerk ID.

12. In the Department tab, select the departments in which this clerk type will be active.

13. In the Event Type tab, double-click on the individual Event Type to open the Add/Modify Clerk Type Event Type dialogue and enter the Start Time for the Clerk Type for this Event Type.

14. Click OK to save all the current Clerk Type settings and exit the dialogue box.

Using clerk access levels at the terminal

What are Access Levels

Setup of POS Access Levels in the software

Assigning POS Access Levels to Keys

Using the POS Access levels at the terminal

What are Access Levels?

Access levels provide restrictions for defined terminal functionality depending on how the keypad has been configured. These restrictions are assigned on an individual key type basis providing total flexibility across the whole system. An access level is assigned to a clerk type, which in turn is assigned to a clerk. When the clerk logs on at the terminal, the keypad that is assigned to that terminal knows whether that clerk has the required access level to perform the function selected, or whether it will require a different clerk type to perform the required function.

Access levels would typically be setup to suit a hierarchy of staffing levels, from Administrator, Manager, Supervisors etc, through to Casual staff and others with additional restrictions required at the terminal.

A total of 7 access levels can be set up in the software, so it is advised that there is careful planning of how these access levels might be used before starting to set these up.

The clerk functionality accessible at the terminal is completely dependent on the clerk type access levels. Restrictions can be enabled for any key type and are assigned at the keypad level in the back office software. This enables restrictions for key types such as credits, or deleted item keys.

At the terminal, if a clerk is currently logged on that does not have the access to this particular function type, the clerk with the access required can overwrite the current clerk that is logged on to perform this restricted function before the terminal returns to the original clerk that is logged on.



Access Levels can be broken into two areas - POS Access Levels and Software Access Permissions. POS Access Levels are referred to above, and restrict a clerk's functionality at the terminal.

Software Access Permissions gives the user the ability to restrict the areas of the software that are available to be seen by various clerk types. It may be necessary for example, for the Bottleshop Manager to be able to see and operate the Stock Module within the Back Office software so that he can enter stock takes and adjustments; however it is not necessary for him to have access to the Members dialogue as this could cause Privacy and Security issues.

Setup of POS Access Levels in the software

1. From the Clerks dialogue box, select the POS Access Levels tab.

2. Select New to add a new POS Access Level or Modify to modify an existing POS Access Level.

3. Select the Auto Generate button to assign the next available ID to this record, and enter a description for this access level, noting that there is a maximum of 7 POS Access Levels available within the software.

4. Click OK to save changes and exit the dialogue.

5. Select the Clerk Types tab and open the Clerk Type you want to modify.

6. Flag the checkboxes against the POS Access Levels you want to assign to this Clerk Type.

7. Click OK to save changes and exit the dialogue.

Assigning POS Access Levels to Keys

1. In the Keypads module open the keypad to which you want to add the key with limited access.



2. Assign the required key, or select an existing one.

3. In the Security selection list flag the access level(s) for this key.

4. Click OK to save the changes and exit the keypad.

Using the POS Access Levels at the terminal

1. Log on at the terminal.

2. Press the key for which you have configured the security access.

3. If the current clerk does not have the right POS Access, a No Access message will be displayed, along with a double beep from the terminal.

4. Log on at the terminal as a Clerk with the appropriate security access level.

5. Press the key again.

6. Log on as the original Clerk to finalize the sale.



Adding clerk data

Before entering clerks into the Back Office Software

How to add clerks into the Back Office Software

Before entering clerks, check to ensure the following is setup

Before entering clerks, configure the Administrator Privileges and quest_security Passwords. If you are intending to assign Vendors to Clerks, consider also configuring Vending Types before Clerks.

How to add a new clerk into the Back Office Software

1. Open the Clerks module using your complex password.

2. In the Clerks tab, click the New button to add a new clerk. An Add/Modify Clerk dialogue box will be displayed. NOTE: The New button will only be available if the Clerk who has logged into the Clerk module has been assigned Administrator privileges. Refer to Clerk Access for further information on how to configure these privileges.

3. Either manually enter in a clerk ID number, or select the blue arrow to generate a number automatically. This is the number that will be required to enter at the terminal when logging on / off, or clock in / out, plus additional security features that are required based on clerk type. This field must be numeric only. For this ID to be automatically detected as a clerk ID number, this number must be under 60,000. Note: If you are using a data entry method at the terminal other than the keypad for clerks, (e.g. magswipe, RF clerk readers) this ID number must match the device number.

4. Enter a Code if required. This can be the same number as the ID and used for referencing.

5. Enter the full name of the clerk in the Full Name field.

6. Enter the name in the Terminal Description field. A maximum of 16 characters will be displayed on the initial log on to the terminal. Other features that display the clerk name on the terminal (e.g. Table lists with Clerks) display less characters on the terminal again.

7. Select the required Clerk Type from the available options in the drop-down list.

8. Enter a password in the Password field. This field must be numeric only. Keep in mind that for any clerk type logged into NCR Venue Manager with full access, these passwords are visible unless they are not assigned to that clerk type (see Clerk Access).

9. Enter the Balance within the field if the Clerk is entitled to an allowance (e.g. Meal Allowance).

10. In the Details tab, enter the clerk Address Enter a Home and Other phone number Enter the clerk's Date of Birth



11. In the Time and Attendance tab, in the Job Override panel, enter the required Job Code and Pay Rate for the clerk, if this needs to be different from the default settings for that particular Clerk Type. This function would be used in a situation where the Clerk works shifts in several sections throughout the venue that may fall into different work categories.

12. In the Notes tab, enter any relevant notes.

13. If a Vendor Type has been added in the System, select one from the Vendor Type drop-down list, and enter a badge number if required for referencing purposes.

14. Click OK to save the changes and exit the Clerk dialogue box.

15. To add another clerk, click on the Continue button in the bottom left corner. This will save the current clerk setting, and open a fresh Add/Modify Clerk dialogue.

Accessing the ECM Web Configuration screen

About the ECM Web Configuration screen

Using the ECM Web Configuration screen

ECM configurations available for edit

About the ECM Web Configuration screen

The ECM Web Configuration screen will allow you to use an Internet browser to configure the ECM details Hyperterminal or serial cables which are not always available.

Using the ECM Web Configuration screen

For this method to work, make sure you have downloaded ECM firmware 2.40 or greater to the ECM you are configuring.

1. Open the Internet Explorer.

2. In the address window of the browser, enter http:// immediately followed by the IP address of the ECM.For example,http://10.0.0.64

3. The system will prompt you for a Username and Password. Enter them and press OK. By default, the Username will be Quest and the Password will be quest.

4. If you have logged on successfully, the browser will display the Current Details (Firmware Version, IP Address, etc) at the top of this page.

5. Change the configurations as required. When you change a configuration within any section of the web page, remember to press the Set button for this section before proceeding.



6. Press the Refresh Page button.

7. When the page reloads, check that all new configurations are correct.

8. Press the RESET ECM button at the bottom of the page.

ECM configurations available for edit

The ECM Configuration section

Name - you can change the name of the ECM, for example, to reflect the location of the ECM. This will allow you to identify the ECM in the back office software. The name should be a single word because the system will not accept spaces.

ECM Static IP Configuration

IP Address - the IP address of the ECM

IP netmask - the netmask of the local network

IP gateway - the gateway available to the device

DNS Server - the DNS Server address

DHCP setting when Host disconnects - select:

Static or DHCP

Keep or New

Seconds ECM will search for a DHCP server - enter the required value

Host Configuration

Search network for host - flag if you want the ECM to search the network for a Host



Fixed host or backup - flag to configure a specific Host

Host Address - the IP address of the server / Host

TCP Port - the TCP Port of the server / Host

Traffic to host Encrypted - the option allows you to encrypt the information transmitted from ECM to the Host. This feature is important for data security, and we recommend that you set it to Yes.

Yes (recommended) or No

Backup Host Configuration

Host Address - the IP address of the server / Host

TCP Port - the TCP Port of the server / Host

Traffic to host Encrypted - this option will be inactive in this section. It will be automatically configured to reflect the Host Configuration settings.

Proxy Configuration

Proxy IP Address - the IP Address of the Proxy Server

Proxy Port - the Port Address of the Proxy Server

Proxy User - the Username for accessing the Proxy Server

Proxy Password - the Password for accessing the Proxy Server

SQL Server 2005 - Maintenance Plan

About Maintenance Plans

Adding a Job

Adding a Maintenance Plan


Maintenance Plans can be used to create a workflow of the maintenance tasks required to make sure that your database performs well, is regularly backed up in case of system failure, and is checked for inconsistencies. Although the Maintenance Plan Wizard can be used for creating core Maintenance Plans, creating these plans manually gives you much more flexibility. In SQL Server 2005 Database



Engine, Maintenance Plans create a job that performs these maintenance tasks automatically at scheduled intervals.

To create or manage Maintenance Plans, you must be a member of the sysadmin (sa) fixed server role.

Adding a Job

Before creating your Maintenance Plan, it is recommended that you first create a SQL Server Agent Job to perform a regular SHRINK function to your database. The Shrink function removes additional log files that are no longer required; this function will also remove all Credit Card data from the database. This in no way will restrict the data shown in any reports.

1. Open the Microsoft SQL Server Management Studio. NOTE: Ensure you connect to the database server as a sysadmin user.

2. In the left hand side Object Explorer, expand a Server, and then expand SQL Server Agent - Jobs

3. Right-click on Jobs and select New Job

4. Define a Name for the Job - QUEST-Shrink. Leave the Owner of this job as default

5. Select from the drop down list, the Category that this job will be classified under Database Maintenance

6. Click on the Steps page in the left-hand panel, and click the New button

7. In the Step Name field, enter Shrink Database. Select the required database from the drop down field. In the Command field, enter execute main_shrinkdatabase Click OK



8. Then click the New button to add the second step to the job

9. This time in the Step Name field, enter Index Database. Select the same database. In the Command field enter execute main_reindexdatabase

10. Click OK



11. Click OK to save the New Job and to exit the dialogue




There are two ways to create a maintenance plan: you can create a plan using the Maintenance Plan Wizard (recommended), or you can create a plan using the Design Surface. The Wizard is best for creating basic Maintenance Plans, while creating a plan using the Design Surface allows you to utilize enhanced workflow.

Note: Maintenance Plans are only displayed if the user is connected using Windows Authentication. Object Explorer does not display Maintenance Plans if the user is connected using SQL Server Authentication.

1. Open the Microsoft SQL Server Management Studio. Ensure you connect to the database server as a sysadmin user

2. In the left hand side Object Explorer, expand a Server, and then expand Management

3. Right-click on Maintenance Plans and select the Maintenance Plan Wizard

4. Click Next



5. Enter a Name in the name field, and leave other settings as default. Click Next



6. Select the Maintenance Tasks to be performed with this maintenance plan. Flag on each of these tasks:

a. Check Database Integrity - A single database or multiple databases can then be selected for the Maintenance Task to apply to

b. Update Statistics - A single database or multiple databases can then be selected for the Maintenance Task to apply to. The object should be left default of Tables and Views

c. Clean Up History - This task will clean up and logs files older than the timeframe specified

d. Execute SQL Server Agent Job - This task will schedule any specific Jobs that have been created. This is where the QUEST - Shrink job can be scheduled to run as part of the Maintenance Plan

e. Back Up Database (Full) - A single database or multiple databases can be selected for the Maintenance Task to apply to. The database can be defined to back up to a Disk, Tape or HDD Then click Next

7. To select the Maintenance Task Order, highlight the task and use the Move Up / Move Down buttons to move the task to the correct position. That order must be:

a. Check Database Integrity

b. Back Up Database (Full)



c. Execute SQL Server Agent Job

d. Update Statistics

e. Clean Up History

8. When all the tasks are in order, click Next

9. To define the database(s), select from the drop down list. The Include indexes option will be flagged on by default

10. Click Next



11. To define the Back Up Database (Full) task, select the required database(s) from the drop down list

12. Define the folder where the backup will be located, by using the ellipsis. Other settings can be left as default. Click Next



13. Then select the SQL Server Agent Job created earlier: Quest - Shrink

14. Click Next



15. To define the Update Statistics task, select the required database(s) from the drop down list

16. Other settings can be left as default. Click Next



17. To define Cleanup History, leave the settings as default

18. Click Next

19. To create a schedule for the maintenance plan, click the Change button



20. To create a New Job Schedule, enter a Name in the name field

21. The Schedule type can remain as the default setting of Recurring

22. Set the Frequency to Daily

23. Set the Daily Frequency to occur at 4:00:00AM

24. Other settings can remain as default. Click OK

25. The schedule just created will be displayed in the Schedule field. To edit this further, click the Change button

26. Click Next



27. In the Report Options page, leave the settings as default

28. Select Next



29. To complete the Maintenance Plan Wizard, verify the choices made in the wizard. To make any changes on previous screens, use the Back button

30. Select Finish exit the wizard, and to execute the plan

SQL Server 2008 - Maintenance Plan


Adding a Job



Maintenance Plans can be used to create a workflow of the maintenance tasks required to make sure that your database performs well, is regularly backed up in case of system failure, and is checked for inconsistencies. Although the Maintenance Plan Wizard can be used for creating core Maintenance Plans, creating these plans manually gives you much more flexibility. In SQL Server 2008 Database Engine, Maintenance Plans create a job that performs these maintenance tasks automatically at scheduled intervals.



To create or manage Maintenance Plans, you must be a member of the sysadmin (sa) fixed server role.

Adding a Job

Before creating your Maintenance Plan, we recommend that you create a SQL Server Agent Job to perform a regular SHRINK function to your database. The Shrink function removes additional log files that are no longer required, in addition, this function will also remove any and all Credit Card data from the database. This in no way will restrict the data shown in any reports.

1. Open the Microsoft SQL Server Management Studio. NOTE: Ensure you connect to the database server as a sysadmin user.

2. In the left hand side Object Explorer, expand the Server for which you want to create a job.

3. Expand SQL Server Agent - Jobs.

4. Right-click on Jobs and select New Job.

5. Assign a Name for the Job. Use the name that best describes the job, e.g. MaintenancePlan. Leave the Owner of this job as default.

6. Select from the drop-down list, the Category that this job will be classified under Database Maintenance.

7. Click on the Steps page in the left-hand panel, and click the New button.

8. In the Step Name field, enter Shrink Database. Select the required database from the drop-down field. In the Command field, enter execute main_shrinkdatabase. Click OK.



9. Then click the New button to add the second step to the job.

10. This time in the Step Name field, enter Index Database. Select the same database. In the Command field enter execute main_reindexdatabase.



11. Without leaving the Job Step dialogue, open the Advanced page.

12. From the On Success Action drop-down list, select the Quit the job reporting success option.

13. Click OK.

14. Click OK to save the New Job and to exit the dialogue.




There are two ways to create a maintenance plan: you can create a plan using the Maintenance Plan Wizard (recommended), or you can create a plan using the Design Surface. The Wizard is best for creating basic Maintenance Plans, while creating a plan using the Design Surface allows you to utilize enhanced workflow.

Note: Maintenance Plans are only displayed if the user is connected using Windows Authentication. Object Explorer does not display Maintenance Plans if the user is connected using SQL Server Authentication.

1. Open the Microsoft SQL Server Management Studio. Ensure you connect to the database server as a sysadmin user.

2. In the left hand side Object Explorer, expand a Server, and then expand Management.

3. Right-click on Maintenance Plans and select the Maintenance Plan Wizard.

4. Click Next.



5. Enter a Name in the name field, and leave other settings as default.

6. To create a schedule for the maintenance plan, click the Change button.

7. To create a New Job Schedule, enter a Name in the name field.



8. The Schedule type can remain as the default setting of Recurring.

9. Set the Frequency to Daily.

10. Set the Daily Frequency to occur at 4:00:00AM.

11. Other settings can remain as default. Click OK.

12. Click Next.

13. Select the Maintenance Tasks to be performed with this maintenance plan. Flag on each of these tasks:

a. Check Database Integrity - This task performs internal consistency checks of the data and index pages within the database.

b. Update Statistics - ensures the query optimizer has up-to-date information about the distribution of data values in the tables. This allows the optimizer to make better judgments about data access strategies.

c. Clean Up History - deletes historical data about Backup and Restore, SQL Server Agent, and Maintenance Plan operations. This wizard allows you to specify the type and age of the data to be deleted.



d. Execute SQL Server Agent Job - This task allows you to select SQL Server Agent jobs to run as part of the maintenance plan.

e. Back Up Database (Full) - This task allows you to specify the source databases, destination files or tapes, and overwrite options for a full backup. Click Next.

14. To select the Maintenance Task Order, highlight the task and use the Move Up / Move Down buttons to move the task to the correct position. That order must be:

a. Check Database Integrity

b. Back Up Database (Full)

c. Execute SQL Server Agent Job

d. Update Statistics

e. Clean Up History

15. When all the tasks are in order, click Next.



16. To assign database(s) to Tasks, click on the down arrow next to the Databases field. The system will open a Databases selection dialogue with multiple options.

17. Select the required options.

18. Click Next.



19. To define the Update Statistics task, select the required database(s) from the drop-down list.

20. Other settings can be left as default. Click Next.

21. To define Cleanup History, leave the settings as default.

22. Click Next.



23. Then select the SQL Server Agent Job created earlier: Quest - Shrink.

24. Click Next.

25. To define the Back Up Database (Full) task, select the required database(s) from the drop-down list.

26. Define the folder where the backup will be located, by using the ellipsis. Other settings can be left as default.



Click Next.

27. In the Report Options page, leave the settings as default.

28. Click Next.



29. To complete the Maintenance Plan Wizard, verify the choices made in the wizard. To make any changes on previous screens, use the Back button.

30. Click Finish exit the wizard, and to execute the plan.

31. The system will display the Maintenance Plan Wizard Progress.



32. To view, save, copy or email the maintenance report, click on the Report button and select the required option from the drop-down list.

Quest Web Service Installation – Using IIS

1. Unzip the file Quest Web Service.zip to a location on your computer.

2. Go to Start-> Control Panel -> Administrative Tools -> Internet Information Services. Note: If your IIS is not installed you must install it before proceeding.

3. In IIS you will see a screen like below. Here you will now need to add the folder that you have just unzipped.



4. To add the directory to ISS, right click on the default website, go to new -> Virtual Directory.

5. A wizard will then pop up. Click Next.

6. In the Alias box that will appear next enter QuestWebService and click Next.



7. The next screen will prompt you to enter the directory. Browse to the location you unzipped the files to.

8. On the next screen click Next and then click Finish.

9. The tree will display the new web service.



10. Now you will need to check that the service works. Double-click the Services folder. Right-click on QuestMenu.asmx and go to browse. If installation has been successful the page for the web service will appear as below.

11. Now you will need to modify the web.config option in the SQL Setup application. Open the SQL Setup application in your product directory.



12. In the Web Configuration group of options, flag the Requires Secure Connection checkbox and press OK.

13. Click on the ellipsis button to browse to the web.config file.



14. Now you will need to enable SSL connection. To do this you may need to install iis60rkt.exe to install a temporary SSL certificate. If this is the case follow these instructions.

15. With the iis60 kit is installed go to Start -> Programs -> IIS Resources -> SelfSSL. When the command prompt comes up, type selfssl and hit enter. Hit y when prompted to.

16. Once this is done you can go back to IIS window and right click on the QuestMenu.asmx.

17. Go to file security and click edit.

18. Tick Require SSL check box and click ok to return to the main IIS window.



19. To confirm SSL is working right-click on QuestMenu.asmx and click Browse.

20. You will receive a message saying the page needs to use SSL. Add an “s” to the http in the address bar and hit enter.

21. You will receive a certificate warning. Click Continue.

22. You have finished setting up the Quest Web Service using SSL.

Quest Web Service Installation – Using Internet Information Service (IIS) Manager

1. Unzip the file Quest Web Service.zip to a location on your computer.

2. Go to Start-> Control Panel -> Administrative Tools -> Internet Information Service (IIS) Manager. Note: If your IIS is not installed you must install it before proceeding.

3. In IIS you will see a screen like below. Here you will now need to add the folder that you have just unzipped.



4. To add the directory to ISS, right-click on the default website, go to Add Virtual Directory.



5. A wizard will then pop up. Click Next.

6. In the Add Virtual Directory box that will appear next enter Quest WbService.

7. Browse to the Physical Path to the location you unzipped the files to.

8. Click OK.

9. Right-click on the new web service in the tree and select the Convert to Application option.

10. In the Add Application dialogue, click OK.



11. Now you will need to check that the service works. Double-click the Services folder and switch to Content View.

12. Right-click on QuestMenu.asmx and go to Switch to Features View.

13. In the Actions panel Click on the Browse*:80 (http) and the Browse:443 (https) links.

14. If installation has been successful the pages for the web service will appear as below.



15. Now you will need to modify the web.config option in the SQL Setup application. Open the SQL Setup application in your product directory.



16. In the Web Configuration group of options, flag the Requires Secure Connection checkbox and press OK.

17. Click on the ellipsis button to browse to the web.config file.



18. Now you will need to enable SSL connection. To do this you may need to install iis60rkt.exe to install a temporary SSL certificate. If this is the case follow these instructions.

19. With the iis60 kit is installed go to Start -> Programs -> IIS Resources -> SelfSSL -> SelfSSL. When the command prompt comes up, type selfssl and hit enter. Hit y when prompted to.

20. Return to IIS window and right-click on the QuestMenu.asmx.

21. Select the Switch to the Features View option.

22. In the Features list, right-click on the SSL Settings option and select Open Feature.

23. Flag the Require SSL checkbox and click Apply.



24. In the Actions panel Click on the Browse*:80 (http) and the Browse:443 (https) links. The pages for the web service will appear as below.



25. Click Continue to this website. The system will display Quest Menu.

Date post:	08-Jul-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times