Knowledge Base
Knowledge Base
Knowledge Base
Knowledge Base
| Home | RDP Sales | Contact Us | Training |
|
| RDP Support | ||||
|
RDPWin Knowledge Base |
RDP-DOS Knowledge Base |
IRM and IRM.Net Knowledge Base |
Crystal Knowledge Base |
|
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 these steps:
Complete all steps in the IRM Installation Checklist.
Install Windows 2003 per the instructions below on the IRM server. NOTE: Windows 2003 "standard edition" is preferred, however Windows 2000 server can also be used.
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
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.
RDP 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.
Do not make the IRM server a "domain controller", or install Active Directory on the IRM Server.
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.
| Item | Explanation | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Anti-Virus Software | Anti-virus software should be installed on the RDP data server, IRM server, and all
workstations. It is critical to configure the auto-protected mode of
all anti-virus software to scan local drives only. If anti-virus
software is set to scan network drives, all network based software such as
RDP will run slowly. See Do Not Scan Network Drives with Anti-virus Software. |
||||||||||||||
| Router | A router connects your firewall to the Internet. For security reasons, it is critical to always connect the router to a firewall and not directly to a network card in any server or workstation. | ||||||||||||||
| Firewall | A firewall provides security when an internal network is connected to the Internet. The
firewall must be a physically separate device (a "stand alone" firewall).
RDP software does not work with firewall software installed on the RDP data server or the
IRM Bridge Server. The firewall must be capable of "address redirection."
For example, the external IP address of 65.38.150.5 will be redirected to the internal
address of the IRM server (10.0.0.4 in this example). See Linking Options From Your Marketing Website to the IRM and IRM.net. |
||||||||||||||
| Firewall Ports to Open DMZ setup for IRM Ports for Netmeeting |
A physical firewall is required to secure the IRM from viruses and other attacks. The
external IP address must be redirected to the internal address of the IRM Bridge for Ports 80,
443, and 3389. Additionally, the firewall must be open to allow outgoing e-mail from the
SMTP server installed on the IRM bridge on Port 25. Do not, under any conditions, assign
the external IP address directly to the IRM, as this creates a security loophole and also
prevents proper communication from the IRM to the data server.
|
||||||||||||||
| Switch or Hub | All workstations are connected to a hub or switch which must be a minimum of 100 megabits. The RDP data server and IRM bridge server must be connected to the same hub or switch. Ideally, all workstations that access RDP should be connected to the same hub or switch as the data server. Multiple hubs or switches may be installed for larger installations. Regardless of how many hubs or switches are used, all workstations that access the RDP data server must be on the same subnet. | ||||||||||||||
| Same Subnet and Domain |
The RDP data server, IRM bridge server, and all workstations that access RDP must be on the same subnet and in the same domain. For example, if the IP address assigned to the data server is 10.0.0.3, then the IRM bridge server and all workstations should have an internal IP address of 10.0.0.x, where x can range from 1-254. The "Subnet mask" on all computers would be 255.255.255.0. | ||||||||||||||
| One and Only One Network Card |
The RDP data server, IRM bridge server, and all workstations that access RDP should have one, and only one, network card. When more than one network card is installed, various communication problems result. | ||||||||||||||
| Workstations | RDP supports Windows XP Professional or Windows Vista workstations. | ||||||||||||||
| Data Server Domain Controller or Peer-to-Peer |
RDP is installed in a Windows 2003 "Active Directory"
environment or "Peer-to-Peer". For most
installations, the RDP Windows 2003 or 2008 data server also serves as the domain
controller. However, if there is already a Windows 2003 or 2008 domain
controller, the RDP data server can be a member server of the existing domain.
If there are other applications that require a Windows 2003 or 2008 server, RDP suggests placing them on another Windows 2003 or 2008 server, not the RDP data server or IRM bridge server. This maximizes performance and reduces conflicts. The RDP data server, IRM bridge server, and all workstations that access RDP must be members of the same domain. In peer-to-peer environments, they must all be part of the same workgroup. See Details on Installation of RDP 2003 Data Server Installation |
||||||||||||||
| IRM Server | The Internet Reservation Module
(IRM) is an optional product from RDP and requires
a separate Windows 2003 or 2008 server. This server is installed as a member
server to the domain that contains the RDP data server. In
peer-to-peer environments the IRM server must be in the same workgroup as
the Data Server. All rates,
availability, and reservations are stored on the data server. Do NOT
install active directory, or other applications, on the IRM Server.
Windows Small Business server or Windows XP Professional may not me used
for the IRM Server - it must use Windows 2003 or 2008 server. See IRM Server Installation. |
||||||||||||||
| IRM Security | Security with the IRM has proven excellent and is divided into the following areas:
|
||||||||||||||
| Outgoing SMTP E-mail Server Required |
RDP sends e-mails to guests, owners, groups, travel agents, and others from the IRM and
our RDPWin product. See Installation of Outgoing SMTP E-mail Server and RDP E-mail Marketing for more detail. |
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 prompts:
| Item | Explanation |
|---|---|
| TCP/IP Only | 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. |
| Use "Complete Format" | If prompted to format the drive, use the "complete format" mode, not the "quick format". |
| Use NTFS File System | Install the file system as "NTFS". |
| One Partition Only | 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. |
| Re-Install Operating System |
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:
|
|
Use "Per-Server" Licensing
|
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. |
| Computer Name Suggested - "IRM" | 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 |
The administrator password on the IRM must be the same as the administrator password on the RDP data Server. Please note that RDP support will require this password to install and support the IRM and your data server. |
| Join Existing Domain |
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. |
| One
Network Card
Physical Firewall Same Hub/Switch Same Subnet No DMZ |
Please review the hardware requirements below. In particular, please note:
|
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:
| TCP/IP Address | 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. |
|---|---|
| Subnet Mask | The subnet Mask should be 255.255.255.0 |
| Default Gateway | 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.
Warning: 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. |
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.
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:
| Windows 2003 |
|---|
With Windows 2003, IIS and SMTP
are not installed by default. After the initial installation of Windows
2003 is complete:
|
| Warning | 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 instructions. |
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"
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.
| Windows 2003 |
|---|
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:
|
The 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.
See: RDP Support Documentation for Installation of IRM
| Home | RDPWin | RDP-DOS | IRM/IRM.Net | Open A Web Support Ticket |
|---|---|---|---|---|
|
Version 2.xxx | Upgrade to RDPWin | Link to Marketing Site | Contact Us |
| Training | Vendor Interfaces | Troubleshooting | RDP Sales Website |
