Internet Reservation Module (IRM) - RDP Installation Steps

Contact RDP Support to Install the IRM

This document provides the steps for installing the Internet Reservation Module (IRM) on a Windows 2000 or Windows 2003 server.  The document is intended for use by RDP Support.  Please do not attempt to install the IRM without contacting RDP support at 970-845-7108.

Checklist for IRM Installation

The following topics are covered in this document. The table below can be used as an installation checklist

Verify RDP-DOS is Current or Update

Prior to installing the IRM Module, verify the customers' version of RDP-DOS. If the customer is not on the current revision please update using the following steps : Updating RDP-DOS

Verify Correct IRM Hardware Installation

The IRM is designed to exchange a great deal of information with the data server, such as rates and availability.  This communication cannot function reliably without the proper hardware installation of the IRM Bridge and Data Server.  Please collect the following information:

Test Terminal Services with Remote Desktop

It is critical that RDP support is able to connect to the IRM Server and Data server using Microsoft's "Terminal Services", which is provided at no charge with Windows 2000 and 2003 server. The testing procedure is as follows:

1. Use Remote Desktop Connection to connect to the IRM Bridge server.  An external IP address on port 3389 must be re-directed through the firewall to the IRM server.  
2. Login to the domain as "Administrator".  NOTE: The administrator password is required by RDP Support to install the IRM.  An "equivalent account" cannot be used, since often these "equivalent accounts" are not set up correctly and are not truly "equivalent" to administrator.
3. From the IRM, use Remote Desktop connection to connect to the Data Server. The internal address of the data server should be used.  Again. Login as "Administrator".  If the remote desktop client is not installed on the IRM bridge, it can be installed by running setup.exe from the following folder:

C:\Windows\System32\clients\tsclient\Win32\Setup.exe

Verify Internet Information Services (IIS) installed

Verify that IIS (Internet Information Services) and the SMTP Mail Server are installed on the IRM Bridge as follows:

1. Select Start | Settings | Control Panel | Administrator Tools | Internet Information Services
2. If Internet Information Services (IIS) is installed it should start and appear similar to the below.   The left hand side in the sample below shows that their is a default website installed and a default SMTP server.  If these are not installed, see IRM Installation Document - Customer Steps.  Also see Installation of SMTP Server.
   

• Also see Installation, Configuration and Troubleshooting of Outgoing SMTP Email Server.

Installation and Configuring of SMTP Mail Server on IRM Bridge

The IRM is designed to send Email confirmations to guests using the Microsoft SMTP mail server, which is provided at no charge with Windows 2000/2003 server.   It is not possible to use another SMTP server, such as Microsoft Exchange.  Once the SMTP server is installed on the IRM bridge, it must be configured.  See Installation of SMTP Server.

Installing the Pervasive Client on the IRM Bridge

The IRM should be used with Pervasive version 8.6 or higher.  It may be possible to get the IRM to work with Pervasive Version 7.94.  If not, the customer must upgrade to Pervasive 8.6.  To install the Pervasive client on the IRM bridge computer with the following steps:

1. Verify the Pervasive Version on the Server.  See How to Verify the Version of Pervasive Engines (Servers)
2. Select Start, Run, and browse to the following file:  \\Dataservername\PVSW\Clients\Win\Setup.exe.  Do NOT use a "mapped drive" for the install. By using the dataservername Pervasive correctly uses DNS.  If you install Pervasive using a mapped drive letter, the RDP-DOS product will work, but not the IRM.
3. Make sure Pervasive tests complete correctly.  If they do not complete, do not continue with the Installation of the IRM. 
4. After successful installation of the Pervasive Client, it is critical to reboot the IRM Server, even if not prompted to reboot.  
5. After reboot, change the Pervasive Registry Security with the steps in the next section.

Changing Pervasive Terminal Services Security

Change Pervasive Registry Security for Power User Group

RDP support frequently connects to the IRM bridge using Remote Desktop Connection (Terminal Services).   By default any changes made to the Pervasive database via Remote Desktop Connection are not saved.   It is essential to perform the steps in "Pervasive Terminal Services Security for IRM Bridge".

The Pervasive database uses various Keys in the Microsoft Registry to store values for communication with the data server. After re-booting the IRM Bridge Server, the following registry key must be edited using REGEDT32 so that the anonymous IIS user can properly access Pervasive.   Click Start | Run  and enter Regedt32.. Maximize KEY_Users | .Default Right click the .DEFAULT key || Permissions. Highlight the "Power User" group and add a checkmark to the "Full Control" box and apply the changes.

Download and Run IRM Install Program

Download and run the latest IRM installation program as follows:  

1. Login to the IRM bridge as Administrator
2. Create an IRMSETUP directory on the local C: drive. Open Windows Explorer | Highlight C:| Select File | New | Folder 
3. Start Internet Explorer and navigate to www.resortdata.com.
4. Select "customer support" in the header, and then "updates" from the IRM column in Web-Based Support Options.  You can also download the update by clicking here.
5. Follow the instructions on the download page.  Be sure to save the installation file to the folder C:\IRMSETUP.
6. Run the install program and take all defaults

Set File Path from IRM to Data Server in IRMPATH.TXT

1. Login to the IRM bridge as Administrator
2. Select Start | Run | Notepad.  Enter the path to the RDP data server in the form:   \\dataservername\RDPNT\RDP\RDP01. 
   
3.  For example if the data server has the name "Data", with a shared folder "RDPNT", the path becomes: \\Data\RDPNT\RDP\RDP01\
   
4. In Notepad, select "File - Save as".  The file must be saved with the name "IRMPATH.TXT" to the following folder :
   
   C:\Inetpub\wwwroot\IRM\IRMPATH.TXT

Note: there are many ways to create a txt file and save it to the IRM folder however with heightened security in Win2000/2003  "rights" may not follow the file and cause a variety of security issues. Please follow the steps above when saving the IRMPath.txt file directly to C:\Inetpub\wwwroot\irm folder. 

Change Anonymous User Password For IRM and IIS

The IRM needs a user name and password to authenticate within the IRM bridge server and also to access the data server.  Create an "IRM" user as follows:

1. Add RDP-IRM user to the IRM Bridge Server 
2. Add RDP-IRM user to "Power users" group on the IRM Bridge Server
3. Change Internet Information Services (IIS) to use the RDP-IRM user
4. Add the RDP-IRM user to the data server 
5. Add RDP-IRM user to "RDP" group on the IRM Bridge Server

Each of these steps is explained below.

(1) Add RDP-IRM user to the IRM Bridge Server 

The RDP-IRM user account must first be created on the IRM bridge server as follows:

1. Login to the IRM bridge as Administrator
2. Start | Settings | Control Panel | Administrative Tools | Computer Management
3. Expand "Local Users and Groups", then right click on Users and select " New User "
4. Enter a new user, "RDP-IRM", as follows:   Any password can be used, such as 123456.  The screen should appear similar to the following.  Click "Create" and then "Close".
   

(1a) When the Data Server is NOT a Domain Controller

Perform all the steps we normally do on the IRM server, which include adding the RDP-IRM user as a LOCAL user on the IRM server with Computer Manager and making the RDP-IRM user a member of the LOCAL Power user group. 

Just make sure to NEVER use a "domain user" as the user name in IIS. ie, we just use the local user RDP-IRM, with password 123456

(2) Add RDP-IRM user to "Power Users" Group on the IRM Bridge Server

The RDP-IRM user must be added to the "Power Users" group on the IRM bridge server to allow this user to access all required files and registry entries on the IRM and data Server, as follows: 

1. Login to the IRM bridge as Administrator
2. Start | Settings | Control Panel | Administrative Tools | Computer Management
3. Expand "Local Users and Groups", and expand " Groups ".  
4. Right click on the Power Users group and select properties and then " Add ". Make sure the "From this location" shows as the name of the local IRM computer, not the DOMAIN.  The goal is to add the local user RDP-IRM to the local power user group on the IRM server.  In the example below, the name of the IRM computer is "WEB172".  
5. Choose Advanced | Find Now | Highlight the "RDP-IRM " user | Choose OK  and save.
   

(3) Change Internet Information Services (IIS) to use the IRM user

1. Login to the IRM bridge as Administrator
2. Start | Settings | Control Panel | Administrative Tools | Internet Information Services
3. Expand | Computer name | Web Sites | Default Web Sites | IRM
4. Right Click IRM, left click properties, left click Directory Security tab
5. Click "edit" under "authentication and access control"  The User Name and Password appear.  Change the user name to "IRM" and the correct password used before for the IRM user, such as 123456.  Warning:   It is critical to use the LOCAL IRM user as the user name (ie, just "IRM"). Do not use the "domain" RDP. 
   

(4) Add the IRM user to the data server 

The IRM user needs access to the Data Server to search for rates and availability, store reservations, etc.  The exact steps to perform this task will be different depending on what type of data server is in use, and if Active Directory is installed. The steps below apply to a Windows 2000 data Server with Active Directory installed.

1. Login to the RDP data server as administrator.  This can be done by sitting in front of the server, or by using Remote Desktop connection to connect from the IRM server to the Data Server.
2. Start | Settings | Control Panel | Administrative Tools | Active Directory Users & Computers
3. Right Click "Users" and select " New " | "User" 
4. Enter a new user, "RDP-IRM", as follows:
   
   
5. Choose " Next ", enter the same RDP-IRM password as before.. Check the boxes " User cannot change password " and "Password never expires" .
6. Select Finish.

(4a) When the Data Server is NOT a Domain Controller

Normally the Data Server is a Domain Controller, and we use Active Directory to add the RDP-IRM user. However, when the data server is NOT a Domain Controller, we want to use COMPUTER MANAGER from the data server to add the user, just like we would on the IRM. IE:

1.  Use Computer Manager and add a LOCAL USER RDP-IRM. (do NOT add a "domain user").   Make the password 123456 (same as on IRM)
2.  Use Windows Explorer to add the LOCAL USER RDP-IRM to have full security rights to the \RDPNT folder AND the PVSW  folder. It is critical to give full rights to BOTH. 
3.  Use Windows Explorer to add the LOCAL USER RDP-IRM to have full SHARING rights to the \RDPNT folder and the PVSW folder. 
   
   Note: You have to give BOTH security and Permission rights to the RDP-IRM user for BOTH the \RDPNT folder and the \PVSW folder on the data server. 

 (5) Add IRM user to "RDP" group on the Data  Server

The new user, IRM, that was added to Computer Management on the IRM server must now be added to the RDP security group on the Data Server with the following steps.  For additional information please see:  Windows 2000/2003 Data Server Installation Document

1. Login to the RDP data server as administrator.  This can be done by sitting in front of the server, or by using Remote Desktop connection to connect from the IRM server to the Data Server.
2. Start | Settings | Control Panel | Administrative Tools | Active Directory Users & Computers
3. Click " Users " in the left and then right click the "RDP" group and select Properties.  
4. Click the "Members" tab and then click the "Add" button.  Enter the name "IRM" to add and save.

How the " separate"  Domain Controller Step-up Works in the IRM

HOW DOES THIS SETUP WORK?
With the setup above the IRM can now communicate with the Data server using "peer-to-peer". The domain security is not used at all. IE:

1. On the IRM, IIS has a local user RDP-IRM, with password 123456. This is used to access local files on the IRM, as we do normally.
2. When the IRM wants to authenticate to the data server, it passes the user name RDP-IRM and password 123456 to the Data Server DIRECTLY (peer-to-peer). The Data Server finds this user name and password in its LOCAL security database and grants access.
3. The Data Server looks at the Permissions and Share rights to the RDPNT folder and finds the local RDP-IRM user has rights and allows access. 
   

STEPS FOR DOMAIN CONTROLLER

Do NOTHING on the Domain Controller. We do not even have to have the RDP-IRM user in the domain AT ALL. The IRM will now communicate with the data server "peer-to-peer".

Additional Configuration for Windows 2003

Before the IRM will start there are a few additional configuration changes that must be made if the IRM is running on a Windows 2003 server, as follows:

1. Activate Windows 2003 IIS Web Service Extensions
2. Win 2003 - Change Default Application Pool Identity = Local SYSTEM
3. Activate Remote Desktop (Terminal Services)
4. Disable Restrictive Internet Security:

(1) Activate Windows 2003 IIS Web Service Extensions

If the IRM bridge server is using Windows 2003 certain Web Service Extensions must be activated for the IRM to function.  Proceed as follows:

1. Login to the IRM bridge as Administrator
2. Select | Start | Settings | Control Panel | Administrative Tools | Internet Information Services (IIs)
3. Expand the default computer name and then expand "Web Service Extensions".  You must allow":

• Allow: = Active Server Pages
• Allow =  Server Side Includes
• ASP.Net (allowed by Default)

(2) Win 2003 - Change Default Application Pool Identity = Local SYSTEM

Applications in Microsoft IIS run in application pool.  The setting for the "Default Application Pool" has to be changed for the IRM access all required files and registry entries on the IRM bridge, as follows:

1. Login to the IRM bridge as Administrator
2. Select | Start | Programs | Control Panel | Administrative Tools | Internet Information Services (IIS)
3. Expand the default computer name and then expand  "Application Pools". 
4. Right Click the "Default Application Pool" and select Properties and then the " Identity " tab.  
5. The default identity is "Network Service".   Use the drop down to change this to "Local system" and select apply.  Note:  You must use local SYSTEM, not local SERVICE.
6. Enter "YES" to the warning from IIS manager.  The IRM requires Local System ability because it accesses another data server using Pervasive.  The screen should appear similar to the following when complete:
   

 (3) Activate Remote Desktop (Terminal Services)

With Windows 2003,  Microsoft renamed "Terminal Services in Remote Administrative mode" to "Remote Desktop for Administration", which is installed by default.  However, it must be activated after installation. To enable Terminal Services on a 2003 server:

1. Login to the IRM bridge as Administrator
2. Right Click My Computer | Properties | Remote
3. Make sure there the checkbox for "Allow users to connect remotely to this computer" is checked

(4) Disable Restrictive Internet Security

Windows 2003 has additional security for the web browser by default, which can cause problems with the IRM monitor and other utilities.  To disable Restrictive Internet Security:

1. Login to the IRM bridge as Administrator
2. Select Start | Settings | Control Panel | Add/Remove Programs | Add/Remove Windows Components
3. Uncheck " Internet Explorer Enhanced Security Configuration. 

Troubleshooting the Internet Reservation Module (IRM)

Troubleshooting the IRM is difficult because there are a wide variety of possible problems.  Please see "IRM Troubleshooting Overview"

Testing and Troubleshooting the IRM with IRMTOOLS.HTM

It is critical to test and troubleshoot the IRM with RDP's "IRMTOOLS.HTM" program.  Please see: "Testing and Troubleshooting the IRM with IRMTOOLS.HTM

Using RDP-DOS and RDPWin from the IRM Bridge    

RDP's legacy DOS based system (RDP-DOS) and windows based system (RDPWin) can both be installed and used from the IRM bridge.  These are installed normally.  See "Windows 2000/2003 Data Server Installation Document"

IRM Troubleshooting Links