Microsoft Dynamics Retail Management System 2.0 Cumulative Update 5

  • Article

This download contains Cumulative Update 5 (CU5) for Microsoft Dynamics Retail Management System (RMS) 2.0

Important Notice to Customers

We recommend that you contact your Microsoft Dynamics Partner before you install feature packs, service packs, or hotfixes. It is important to verify that your environment is compatible with the installation. A feature pack, service pack, hotfix, or download may cause interoperability issues with customizations and third-party products that work with your Microsoft Dynamics solution.

Why "Cumulative Update 5"?

Microsoft Dynamics is standardizing the naming of all service updates to “Cumulative Update.” To be consistent with the rest of Microsoft Dynamics, this update for Microsoft Dynamics RMS 2.0 is Cumulative Update 5 rather than Service Pack 5. This name is also more descriptive as the update is truly cumulative: it can be installed directly over RTM (or any subsequent release) and includes all changes made since the original release.

Overview

Microsoft Dynamics RMS 2.0 Cumulative Update 5 (CU5) is cumulative and contains all hotfixes that were released after Feature Pack 2 (FP2).

New Features

Cumulative Update 5 includes the following new features:

  • Integration with Microsoft Dynamics Online Payment Services. This integration provides up-to-date access to Microsoft Dynamics Online services and, through the Payment Services software development kit, provides new customization options for partners and payment processors who want additional payment options.
    Note The previous Microsoft Dynamics Online integration (sometimes referred to as "version 1") no longer appears as an option on the EDC tab of the Configuration dialog box in Store Operations Administrator. If you have been using that option, your settings will be preserved in the registry and you can continue to do so. However, we strongly encourage you to move to the latest integration, which has been validated against the latest PCI Payment Application Data Security Standard. For more information about how to update your system, see "Integrating EDC software" in Store Operations Administrator Online Help.
  • In support of current industry standards, Store Operations now sends reversals instead of refunds for voids of debit purchase and return transactions and for transactions that time out.
  • Store Operations now rejects payment processing connections that do not use strong ciphers (128 bits or higher).
    Notes
    • This change was implemented as part of our validation against version 2.0 of the Payment Card Industry (PCI) Payment Application Data Security Standard and our effort to keep Microsoft Dynamics RMS PCI compliant.
    • Changes to your environment might be necessary to maintain PCI compliance in your organization. For more information, see the most up-to-date PCI Data Security Standard for merchants and see the latest version of the Microsoft Dynamics RMS Implementation Guide for PCI Compliance, available in the Cumulative Update 5 Downloads section.

Changed Functionality

Cumulative Update 5 includes the following changes in functionality:

  • The "-q" switch introduced in hotfix rollup 2735491 for suppression of warning messages in Headquarters Client has been added to Headquarters Server, Voucher Server, and Voucher Client. To suppress warning messages for these programs, change the shortcut for the program so that it looks something like this (with the path adjusted for your system and with the correct executable name):

    "C:\Program Files (x86)\Microsoft Retail Management System\Headquarters\HQServer" –q

  • The following obsolete payment options have been removed from the EDC tab of the Configuration dialog box in Store Operations Administrator.

    • PC-Charge
    • ICVerify
    • Atomic Authorizer
    • WinTI / European EF

Note These integrations have not been PCI validated and are no longer supported by Microsoft. Customers who wish to continue using these options can do so by explicitly setting the registry key for these integrations to True. The registry key is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Retail Management System\Store Operations\POSUser\EDC\<Payment Option>

  • The behavior of Style 251: Update Inventory – Item Prices worksheet has been updated. The Cost and Profit Margin columns have been made read only to prevent costs set by the store manager from being inadvertently overwritten.
  • The Original PO number has been added to the PO receipt in Headquarters Manager and Store Operations Manager.
  • The item list in both Store Operations Manager and Headquarters Manager opens with active items shown by default. As before, if you make another selection in the list, this selection is preserved through the session.

Other Improvements

Cumulative Update 5 includes fixes for the following issues:

  • You receive the following error message when you process debit transactions:
    "Connection error: Authorization response contained NAK or ENQ. Please try again. None = 0, Source = "
  • You receive an error when you try to settle credit or debit transactions that were voided in Terminal Offline mode.
  • When you export a new store database from Headquarters with Microsoft SQL Server 2012, the centrally maintained data is not populated and the store ID is incorrect.
  • You receive the following run-time error message when you try to approve a Style 251: Update Inventory – Item Prices worksheet that is missing a date field:
    "Run-time error '-2147217887 (80040e21)': Multiple-step operation generated errors. Check each status value."
  • Incorrect opening amounts are shown in the Inventory Valuation report.
  • Deadlock issues can occur when you tender transactions or work on purchase orders on multiple registers, or when you run reports on one machine while transactions are being processed on other registers.
  • The Help button in the Top Cashier report in Headquarters Manager does not work as expected.
  • Matrix item component costs are not updated correctly when new matrix items are created.

PCI Compliance

The Microsoft Dynamics RMS Implementation Guide for PCI Compliance has been updated for the release of Cumulative Update 5, contains requirements that must be met in all new deployments, and is available for download in the Cumulative Update 5 Downloads section.

The requirements in this guide must be followed to implement Microsoft Dynamics RMS in a manner that is compliant with the Payment Card Industry (PCI) Data Security Standard version 2.0.

The requirements in this guide represent best practices that should be followed even if you are not required to comply with the PCI Data Security Standard.

This guide is intended for Microsoft Dynamics Certified Partners who are deploying Microsoft Dynamics RMS in a retail organization where electronic credit card and debit card payments are accepted and where Microsoft Dynamics RMS is used as the payment application. As a payment application, Microsoft Dynamics RMS is subject to the PCI Payment Application Data Security Standard (PA-DSS). The contents of this guide reflect that standard.

Legal Terms and Conditions

Acceptance of a given payment application by the PCI Security Standards Council, LLC (PCI SSC) only applies to the specific version of that payment application that was reviewed by a PA-QSA and subsequently accepted by PCI SSC (the “Accepted Version”). If any aspect of a payment application or version thereof is different from that which was reviewed by the PA-QSA and accepted by PCI SSC – even if the different payment application or version (the “Alternate Version”) conforms to the basic product description of the Accepted Version – then the Alternate Version should not be considered accepted by PCI SSC, nor promoted as accepted by PCI SSC.

No vendor or other third party may refer to a payment application as “PCI Approved” or “PCI SSC Approved”, and no vendor or other third party may otherwise state or imply that PCI SSC has, in whole or part, accepted or approved any aspect of a vendor or its services or payment applications, except to the extent and subject to the terms and restrictions expressly set forth in a written agreement with PCI SSC, or in a PA-DSS letter of acceptance provided by PCI SSC. All other references to PCI SSC’s approval or acceptance of a payment application or version thereof are strictly and actively prohibited by PCI SSC.

When granted, PCI SSC acceptance is provided to ensure certain security and operational characteristics important to the achievement of PCI SSC’s goals, but such acceptance does not under any circumstances include or imply any endorsement or warranty regarding the payment application vendor or the functionality, quality, or performance of the payment application or any other product or service. PCI SSC does not warrant any products or services provided by third parties. PCI SSC acceptance does not, under any circumstances, include or imply any product warranties from PCI SSC, including, without limitation, any implied warranties of merchantability, fitness for purpose or noninfringement, all of which are expressly disclaimed by PCI SSC. All rights and remedies regarding products and services that have received acceptance from PCI SSC, shall be provided by the party providing such products or services, and not by PCI SSC or any payment brands.

System Requirements and Prerequisites

System Requirements

The System Requirements document for Microsoft Dynamics RMS 2.0 was reviewed for Microsoft Dynamics RMS Cumulative Update 5 and is available for download in the Cumulative Update 5 Downloads section.

The system requirements listed in this document apply to Microsoft Dynamics RMS 2.0 Cumulative Update 5 (CU5) or later. Earlier versions of Microsoft Dynamics RMS 2.0 do not support some of the operating systems and versions of Microsoft SQL Server® that are listed in the document.

Prerequisites

Before you install this cumulative update:

  • You must have installed Microsoft Dynamics RMS 2.0.
  • Make sure that there are no registers in Terminal Offline Mode.
  • Print a Z report on every register with an open sales batch, and then shut down all register computers except the database computer.
  • Settle all outstanding credit card and debit card transactions. Failure to settle transactions could lead to lost revenues.
  • If an integrated accounting application is being used, all available batches must be posted.
  • Make backups of any customized reports, labels, receipt templates, and purchase order formats.
  • Back up all Microsoft Dynamics RMS databases (Store Operations and Headquarters) and name them "Pre-CU5" or something similar to note that they are backups that were made before upgrading to Cumulative Update 5.
  • Stop communication between Headquarters Server and Headquarters Client and Voucher Server and Voucher Client.

Note - The database will be modified during the upgrade and cannot be reverted. For more information, see the "Upgrade the Database" steps in the Installation section on this page.

Installation

Cumulative Update Information

Important Notes

  • Cumulative Update 5 can be applied to all builds of Microsoft Dynamics RMS 2.0 including RTM.
  • Make sure that the cumulative update is installed on all computers before you use ANY Microsoft Dynamics RMS program. Environments that are only partially updated have not been tested and are not supported.
  • The changes in Microsoft Dynamics RMS 2.0 Service Pack 2 included changes to password policy management are part of this update. For more information, see the Microsoft Dynamics RMS Implementation Guide for PCI Compliance download in the Support Information section later on this page.

The cumulative update must be installed on all computers where any of the following programs are installed:

  • Store Operations POS
  • Store Operations Manager
  • Store Operations Administrator
  • Headquarters Manager
  • Headquarters Administrator
  • Headquarters Server
  • Headquarters Client
  • Voucher Server
  • Voucher Client

Cumulative Update information for Headquarters​​

Before you install this cumulative update, we recommend that you stop communication between Headquarters Server and Headquarters Client and Voucher Server and Voucher Client. You must do this at each store, on the computer where Headquarters Client and Voucher Client are installed.

To stop communications, exit both Headquarters Client and Voucher Client at each store.

After the cumulative update is installed and the databases have been upgraded at all stores and at the head office, you can resume regular data uploads.

How to Install the Cumulative Update

Install the cumulative update at a time when no activity will occur, such as when all stores are closed.

To download and install Cumulative Update 5, follow these steps:

  1. Close all Microsoft Dynamics RMS programs.

  2. If you are running a Windows® operating system with User Account Control (UAC) enabled, log on with a Windows user account that has administrator credentials.

  3. Download the "Retail2.0-KB2887502.zip" file and save it in a folder on your computer’s hard disk.
    Note– If the Microsoft File Transfer Manager window does not automatically display, make sure that you have installed the ActiveX control. To install the ActiveX control make sure that you have pop-up windows enabled for this site. Download the File & Exchange System FAQ.

  4. Double-click the downloaded file, click Extract all files, and then follow the installation instructions.

  5. In the folder where you saved the extracted files, take one of the following actions:

    • If you are running a Windows operating system with UAC enabled, right-click the "Retail2.0-KB2887502.exe" file, click Run as administrator, and then provide administrator credentials. The cumulative update installer will guide you through the rest of the installation.
    • For all other Windows operating systems, double-click the "Retail2.0-KB2887502.exe" file. The cumulative update installer will guide you through the rest of the installation.

  6. The updated Help files for CU5 are not installed by default. Instead, you can download these individually from the Cumulative Update 5 Downloads section. Copy them into the appropriate Headquarters or Store Operations installation folders, overwriting the files that are already there. You may need to have administrator credentials in order to complete this step.

    • A.) These files should be copied to the Store Operations installation folder:
      • Store Operations Administrator Online Help.chm
      • Store Operations.chm
      • msrmspaymentconnector.chm
    • B.) This file should be copied to the Headquarters installation folder:
      • Headquarters Online Help.chm

    Note The Help button in the Dynamics Payment Connector dialog box (accessed from the EDC tab in the Configuration dialog box in Store Operations Administrator) does not open the Help file unless you have downloaded the msrmspaymentconnector.chm Help file as described above.

  7. Repeat steps 1-6 to install the cumulative update on all other computers where Headquarters or Store Operations programs are installed.

Important Notes

  • You must install the cumulative update on all computers where Headquarters or Store Operations programs are installed.
  • Regardless of which release of Microsoft SQL Server you are using, you must install the Microsoft SQL Server 2012 programs that are included in the cumulative update installer. If you do not install these programs, Microsoft Dynamics RMS will not work properly.

Verify the Cumulative Update Is Installed

To verify that the cumulative update is installed, follow these steps:

  1. Start any Microsoft Dynamics RMS program.
  2. On the Help menu, click About Program Name.
  3. If the version number shown is 2.0.2000, the cumulative update was installed successfully.

Upgrade the Database

Important Notes

  • If you have not already done this, use Store Operations Administrator or Headquarters Administrator to make a backup of the database. After a database is upgraded, it cannot be reverted back. Therefore, a backup will be required if you have to uninstall the cumulative update for any reason.
  • After you have successfully applied Cumulative Update 5 and have upgraded the databases, you will have to re-create all the Terminal Offline databases.

To upgrade the database, follow these steps:

  1. On the File menu in Store Operations Administrator or Headquarters Administrator, click Connect.
  2. Specify your credentials, select the database that you want to upgrade, and then click OK.
  3. On the Database menu, click Upgrade.
  4. In the Upgrade database to version box, select 2.06.
  5. Click OK.
  6. Make a backup of all your databases and label them "Post-CU5" or something similar to note that the backups were made directly after you applied Cumulative Update 5, and before you start to process new transactions.

Cumulative Update 5 Downloads

The following table provides the download thinks to all Microsoft Dynamics® 2.0 CU5 deliverables:

Deliverable Version File Download File Type (Size)
Microsoft Dynamics RMS 2.0 CU5 Readme November 2013 Readme_RMS_CU5.txt txt (12 KB)
Microsoft Dynamics RMS 2.0 CU5 System Requirements November ​2013 System Requirements.pdf pdf (399 KB)
Microsoft Dynamics RMS CU5 Implementation Guide for PCI Compliance November 2013 PCI Implementation Guide RMS CU5.pdf pdf (919 KB)
Microsoft Dynamics RMS 2.0 CU5 2.0.2000 Retail2.0-KB2887502.zip zip (33.5 MB)
Microsoft Dynamics RMS 2.0 CU5 Help files November 2013 RMS_CU5_Help_files.zip zip (5.43 MB)

Support Information

For technical support questions, contact your partner or direct your questions to the Support for Business hub: https://serviceshub.microsoft.com/supportforbusiness/create

CustomerSource Help and How-To Resources

To access the downloadable material within this content as previously found on CustomerSource, users will need to have the same customer account access. Click here to view more information.