|
||||||||||||||||||||||
Added: 03/12/14 | ||||||||||||||||||||||
RDPWin Version 4
|
||||||||||||||||||||||
| ||||||||||||||||||||||
1. Review RDPWin 4 Requirements | ||||||||||||||||||||||
| ||||||||||||||||||||||
2. Administrator Password |
||||||||||||||||||||||
|
||||||||||||||||||||||
3. Update Crystal Reports |
||||||||||||||||||||||
|
||||||||||||||||||||||
4. IRM.Net Changes |
||||||||||||||||||||||
IRM.Net Version 4 has been enhanced to support the latest browsers and future browser changes. If you are using a custom theme the following changes will need to be planned for. If a default theme is in use, none of these changes will apply. RDP will make sure the IRM.Net will take a reservation after the upgrade. However, a web developer may need to make changes to your custom theme. RDP will provide directions to the web developer.
|
||||||||||||||||||||||
5. GDS Changes |
||||||||||||||||||||||
Reservations with credit card information entered into RDP from a
GDS channel must have the card information tokenized prior to entering
RDP. The tokenization occurs using Shift4's 4Res product.
This requires white listing the RDP data server's IP address with
Shift4. Shift4 will assist with this. |
||||||||||||||||||||||
6. Upgrade Call Accounting and POS RDPDos Interfaces |
||||||||||||||||||||||
RDPWin Version 4 does not support the old RDPDos POS and Call
Accounting Interfaces. If you are currently using either of
these interfaces, they must be updated to the new RDPWin Interfaces
4.0 prior to installing RDPWin Version 4. RDPWin Interfaces
4.0 will work with the RDPWin Version 3 product. |
||||||||||||||||||||||
7. Purchase Credit Card Devices |
||||||||||||||||||||||
In order to make credit card numbers as secure as possible, RDP is
required to encrypt the credit card number outside the RDP system using
a stand alone device. We can no longer have a customer type a credit
card number into RDPWin using the workstation keyboard, or use an old
style card swipe to bring the number into RDP. These new devices must be
purchased from RDP or your Processor, because they have to be "injected" with special
firmware that allows the device to communicate with the Gateway and your
processor. Contact Rita Gale at 970-845-1143 or Camille Fowler at 970-845- 1144 for more information. |
||||||||||||||||||||||
|
||||||||||||||||||||||
Day of RDPWin 4 Upgrade |
||||||||||||||||||||||
1. Run ReportsUsers will be out of RDP for up to 8 hours. Print reports such as folios, reg cards, housekeeping schedule, room status, arrivals, departures, etc. |
||||||||||||||||||||||
2. Verify the RDP Data Backup |
||||||||||||||||||||||
It is critical to verify that the back-up of RDP Data directories
prior to Version 4 upgrade is good. |
||||||||||||||||||||||
3. Release Credit Card Authorizations on In-House Reservations | ||||||||||||||||||||||
Prior to upgrading to RDPWin4 it is critical to release all credit card authorizations in RDPWin3. Since the authorization was originally taken using a different gateway/processor, it will no longer be possible to release in RDPWin4. This process should take place immediately before the version 4 upgrade. You may release authorization one of two ways.
4. Locate New Credit Card DevicesLocate the new credit card device readers. Do not connect the M130s or SREDKeys into the usb ports on the workstations until instructed by the RDP tech. Remove the old credit card device readers. 5. Convert Credit Card Numbers to TokensBefore a credit card payment can be taken in RDPWin, all credit card numbers must be converted to tokens.
6. Secure all Archived RDP BackupsThe version 4 upgrade of RDPWin will convert credit card numbers to tokens and/or delete unused credit cards. However, it is the customers responsibility to secure and delete all archived directories on the RDP Data server where credit card numbers may exist after the version 4 upgrade. RDP support will help to identify archived directories, but cannot guarantee that all directories will be discovered.
| ||||||||||||||||||||||
|