Internet Reservations (IRM) - Customer Installation Steps
This document covers basic steps for
the Internet Reservation Module (IRM) on a Windows 2000 or 2003 server. It is designed for use by a Microsoft Certified Installer and is not intended as the sole reference for installing and configuring
Windows 2003 Server. If you are
looking for the installation procedure for RDP's primary data server, please click here.
The IRM Bridge Server must be installed
exactly to the specifications in this document or you may have to re-install
Windows 2003 Server software. Follow
Complete all steps in the IRM
Install Windows 2003 per
the instructions below on the IRM server. NOTE: Windows 2003
"standard edition" is preferred, however Windows 2000 server can also
Verify that anti-virus software
is installed on all workstations, the IRM data server, and the RDP Data
server. It is critical to configure anti-virus software on all
computers to "not scan" network drives or performance of RDP may
be very slow. See "do not
allow anti-virus software to scan network drives".
When complete, call RDP support
at 970-845-7108 to schedule installation of the IRM software on the IRM
Bridge Server. See:
RDP Support Documentation for Installation of IRM
Adding Links From Your Marketing Website to the IRM
Once the IRM is installed, configured, and
tested, hyperlinks need to be added from your marketing website to the IRM.
These links enable guests, travel agents, groups,
wholesalers, and owners to easily make reservations and access other
IRM functions. The links can have any text such as "make a
reservation now" and should appear in multiple locations on the marketing
website. Use buttons, text, graphics, etc., to enhance the links.
See Adding Links from the Marketing
Website to the IRM.
IRM Bridge Server Dedicated to
requires installing IRM on a Windows 2003
Server dedicated to the IRM. All other network applications (back-office accounting software,
sales and marketing applications, etc.) should be installed on another server. This configuration
guarantees maximum performance and reliability. It also eliminates the
risk of application conflicts between RDP and/or the Pervasive.SQL database.
not make the IRM server a "domain controller", or install Active
Directory on the IRM Server.
RDP Data Server versus IRM
RDP's property management software is installed
on a Windows 2003 server that is referred to as the "Data
Server". For security reasons, the IRM is installed on a
separate Windows 2003, which is referred to as the "IRM Bridge
Server". When a guest, travel agent, group or owner access rates and
availability the IRM server accesses the data server. All IRM reservations as well as normal internal
reservations are stored immediately in
the same database on the data server.
The preferred operating system for both the data
server and the IRM Bridge Server is Windows 2003 standard edition.
However Windows 2000 may be used.
Firewall Required and Other Requirements
|Diagram of Data Server, IRM Server, and Workstations
Data Server Critical Installation Prompts
This document is not intended as a complete
installation guide for Microsoft Windows 2003. However there are a
number of prompts during the initial installation process of Windows
2003 that require the correct entry for the RDP system to function. The
information below summarizes these critical installation
Install only the TCP/IP protocol. If there is an existing Novell Server at
the property, do not install the Novell Client, IPX/SPX, or the Novell Gateway
on the IRM 2003 server, RDP Data server, or any workstation that access
RDP. Any of these items will cause RDP software to not function correctly.
prompted to format the drive, use the "complete format" mode, not the "quick
NTFS File System
the file system as "NTFS".
||The IRM server should have one,
and only one, partition, as the "C" drive. For example, if you have a 40GB disk
drive in the IRM server, you should end up with a "C" drive with a
size of 40GB, using NTFS.
If for some reason you must re-install
windows 2003 to correct mistakes made in a prior installation, RDP
requires completely removing the old installation first. Do NOT install a
"second instance" of Windows 2003. You should:
- Remove all partitions from the disk
- Reformatting the
drive with NTFS as one "C" drive
Install the server in a “Per Server”
licensing mode with the correct number of connections. RDP has not
tested the "per device or per user" mode of Windows 2003.
The computer name must follow the proper
naming conventions for DNS. To keep things simple, RDP
suggests naming the IRM Bridge Server "IRM". If you
elect to use any other name, problems may occur. Please call RDP support at 970-845-7108 for
approval for any other name.
administrator password on the IRM must be the same as the administrator password on the
Server. Please note that RDP support will require this password to install
and support the IRM and your data server.
Windows 2003 installation will prompt for Workgroup or Computer
domain. The IRM Bridge server must join the same domain as the RDP Data
Server. Choose " Make this computer a member of the domain "
If using a peer-to-peer environment, use "workgroup" and set
the IRM bridge computer to the same workgroup as the data server.
review the hardware requirements below. In particular, please note:
One, and only one network card in the Internet
Reservation Module (IRM) server, data server, and all workstations
A physical, separate firewall must be installed
The IRM and data server must be connected to the
The IRM and data server must be on the same
internal subnet (ie, 10.0.0.x)
A DMZ (De-militarized zone) cannot be installed
Settings - Use Manual Settings,
The firewall will route all internet traffic from the outside to the IRM
Bridge server. As a result the IRM server requires a static IP address,
not a DHCP assigned IP address, as follows:
||Assign a TCP/IP address to the IRM bridge that is in the same subnet
as the data server. For example, if the data server's IP address
is 10.0.0.1, then the IRM must be 10.0.0.x, where "x" can be
from 2 to 254. It is a requirement for the IRM to have the same
subnet as the data server.
||The subnet Mask should be 255.255.255.0
||The IRM Bridge Server requires a gateway
to communicate to the Internet. This is usually the IP
address of the Firewall.
| DNS Server
||The IRM bridge server communicates extensively with the data
server. The connection is made using a DNS server. The Preferred DNS server
for the IRM server and data server must be the same, and must be an
internal machine in the same subnet. For most RDP installations the data server is also the DNS server, in which case the
Preferred DNS server is the IP address of the RDP Data Server.
An internal DNS server is required for the
IRM to function correctly. For
information on configuration of a DNS server, see "RDP
Data Server Installation".
|Alternate DNS Server
||This can be left blank.
|One Network Card
||The IRM server can only have one network card, or communication with
the data server will not work.
Microsoft Service Packs and
Almost all software shipped on CD's is
outdated when you install it. There are usually many bug fixes and
service packs available from the vendors website. After installing Windows
2003, please install all Microsoft service packs and critical
updates to reduce the threat of hackers compromising your site. There is no charge from Microsoft for
service packs or critical updates.
Install IIS and SMTP - Do not
Install Front Page Extensions
The IRM requires the installation of Microsoft Internet Information Services
(IIS) and SMTP, both of which are included at no additional charge with Windows
2003 server. Follow these installation steps:
|With Windows 2003, IIS and SMTP
are not installed by default. After the initial installation of Windows
2003 is complete:
- Select | Start | Settings | Control
Panel | Administrative Tools | Manage your Server
- Select "add or remove a role for this
computer" and then Next.
- Select "Application Server IIS or
Do not put a check in "enable Front Page Extensions". They are not
needed and reduce performance.
Put a check in "Enable ASP.NET". RDP uses this technology.
Select Next several times to start the installation.
Repeat steps 1-3 and install the SMTP service
Do NOT install any additional
components other than those listed in these instructions.
Installing additional components or protocols may cause conflicts
within the Internet Reservation Module that can only be resolved by
re-installing the operating system and following these RDP
Configuration of SMTP Server
Email confirmations are sent from the IRM to guests and your system
administrator using the SMTP server installed on the IRM server. Port 25
must be open on the firewall to allow the outgoing email through your
firewall. See "Installation and Configuration of Microsoft Internal
Outgoing SMTP Mail Server"
E-Mail Related Topics
Terminal Services (Windows 2003 only)
RDP support requires access to the IRM Bridge Server for installation and ongoing support. Microsoft provides, at
no charge, a two-user license of their "Terminal Services"
product for this purpose. Terminal Services must be installed as follows:
Note: If there is a firewall at the
property you must open port 3389 for msrdp.tcp for Terminal Services to
connect to the data server.
|With Windows 2003,
Microsoft renamed "Terminal Services in
Remote Administrative mode" to "Remote Desktop for
Administration", which is installed by default. To
enable Terminal Services on a 2003 server:
click "My computer"
click the "Remote" tab
a check in the checkbox for "allow users to connect remotely to
RDP for Installation of IRM
basic configuration of the IRM Bridge Server is complete. If you have
purchased the recommended on-site IRM installation and training from RDP, please
call RDP Sales to schedule. RDP personnel will complete
the installation of the IRM.
RDP Support Documentation for Installation of IRM