7.0 Migration Plan
From NewHaven Software Wiki
Contents |
Intro
This article describes the recommended minimum preparation and post-installation procedures you should follow to upgrade to CMS version 7.0. Please read through this document and any referenced documents before scheduling an installation appointment with our staff or attempting to upgrade to CMS 7.0 on your own.
Prep for 7.0 install
Important information to read to ensure you are prepared for the update and understand the differences in how CMS will work after the update.
- Confirm you meet hardware and operating system requirements – http://wiki.newhavensoftware.com/index.php/CMS_System_Requirements
- Specifically, no server or workstations are running Windows 2000. If you have XP machines, make sure they have been updated to service pack 3 (SP3).
- Reminder: NHS Explorer will be uninstalled as part of your 7.0 upgrade. If you need this utility, it can be downloaded from our updates site and reinstalled after your CMS 7.0 install.
- Read our 7.0 Release Notes – read AT LEAST up to "CMS Version 7.0 New Features List".
- Review the CMS PA-DSS Implementation Guide - This Word document can be downloaded our updates site. This document is intentionally left in a Word format so you may add to it to suit your company's policies and need for distribution. We have a video posted to provide an overview of the Implementation Guide - http://www.youtube.com/watch?v=_l98imtWirY
- Platinum customers should contact your Platinum Account Manager to schedule your desired conversion date.
- Silver and Gold customers should contact NewHaven Software Sales for 7.0 Upgrade purchase information.
It is important that you understand some of the significant changes that are taking place with this update, particularly with Employee passwords and permissions. Please contact NewHaven Software with any questions.
UPS Update
If you are using UPS Worldship and have not yet updated to Worldship 2010 (aka version 12) please do so before updating CMS to version 7.0. We will be providing new mapping files to facilitate changes in how UPS connects to your CMS database for keyed imports.
Day of install
Prerequisites for installing the update.
- Download your CMS 7.0 update - http://updates.newhavensoftware.com/
Also available when downloading your update are:
- NHS Explorer
- Your version 7 release code which you will need when installing
- Get everyone out of CMS or other programs that may connect to your CMS database.
- Backup and archive your database - This means rename the .db file after it has been created so it will not be overwritten by subsequent nightly backups CMS creates.
- Review YouTube video on the new version 7 installation process - http://www.youtube.com/watch?v=jMO59TIHjxs
Installation
- Server install - You must be logged in with local administrator rights and have everyone logged out of CMS. This update may take up to twice as long as a typical update. Please plan accordingly.
If you are moving CMS to a new server instead of just upgrading your existing server, please see these instructions.
Post installation
Steps to perform immediately after the update has completed and before anyone uses CMS.
- Follow the steps in our PCI Configuration Video. The steps are also outlined below.
- Login as PCI Admininstrator and set password
- Create other PCI Administrator employee account, one per user
- Configure employee permissions – there is no more "administrator" checkbox so you must assign what used to be admin rights to appropriate employees. See http://updates.newhavensoftware.com/v7release_notes.htm#5
- Disable System user (remove access and set password)
- Configure other PCI Admin settings
- Encryption turned on (if not already)
- Enable credit card masking
- Set data retention policy
- Change database passwords
- Apprise your staff of changes that affect them due to PCI requirements, changes in your company's policies or new settings/features in CMS. Here are some examples:
- Your data retention policy (and that credit cards numbers will be deleted after that period)
- Use of credit card masking (CMS only displays last 4 digits of a card number after processing/saving)
- Changes you may have made to employee permissions
- Operators should not put credit card numbers or CVC security codes in CMS notes fields or be written on paper
- Operators must not share their login credentials
- Educate your staff on the importance of PCI and credit card security. Share what you know with them and help them understand that the health of your business is at stake. Proper handling of credit card data must be top of mind for all employees.
UPS Worldship Users
We have provided new mapping files to facilitate changes in how UPS 2010 connects to your CMS database for keyed imports. These mapping files are CMSPackages.dat and CMSPackagesExport.dat and we installed into your \NewHaven Software folder where CMS.exe is installed. After you've updated to Worldship 2010 and CMS 7.0, you'll need to copy these two files into your c:\UPS\WSTD\ImpExp\Shipment\ directory replacing the existing files. We recommend renaming the existing files in that directory before copying in the new ones so you have them as a backup.
Also, if you've followed our PA-DSS Implementation Guide, you should have changed your database passwords (dbo and cmsuser) in CMS. Worldship uses the cmsuser credentials to connect to your database so be sure to update those in Worldship too. To do this, follow these steps in Worldship:
- Click Import/Export Data and select Create/Edit Map
- Choose CMSPackages and click the ODC Login button (right side of screen)
- Enter cmsuser and the password you selected for this user (leave the credentials for Shipment blank)
- Click OK and then OK again
Recommended but not required
- Workstations – Workstation updates are not required but you do want to copy over the new Help file from the server to the workstations after the server update is complete. The file is CMS.chm and can be found in the same directory where CMS.exe is installed. Copy this file to the local workstation, usually C:\NewHaven Software, replacing the old CMS.chm that is there.