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 |
|
Last Modified 1/1/2007
Once the IRM is installed, configured and tested, hyperlinks need to be added to access the IRM on the marketing website. These links enable a guest, travel agent, group, wholesaler or vacation rental owner to easily make reservations and access other IRM functions. Links to the IRM can be added to various locations on your marketing web site.
Links to the IRM can have any wording, such as "Make a reservation now" or "Owner Login" and should appear in multiple locations on the marketing web site. Buttons, text, graphics, etc. can be used to enhance the appearance of the links. This document explains the various linking options and is intended for someone familiar with HTML programming and hyperlinks. RDP support does not provide HTML training. The following issues are critical regarding linking.
| Critical Issue | Explanation |
|---|---|
| Update the IRM to Version 2.332 or higher! |
11/7/2007 - There have been a number of important fixes to the IRM. The links in this page assume you have IRM version 2.332 or higher. See "IRM Update Page". |
| Do Not Modify IRM ASP Pages | The IRM consists of a series of ASP pages that contain programming code. Do not modify any IRM ASP pages in any way. Modification of ASP pages is cause for termination of the RDP support contract. |
| Start a New Browser Window | It is critical that the link from the marketing
web site to the IRM always start a new browser window, using the JavaScript
"window.open" function. Do not use the HTML tag
option "target=blank". See "Start
a New Browser Window" below.
Warning: Do not put the IRM into an HTML Frame. It will not work. Always link to a completely new browser window that only has the IRM. |
| Eliminate the Back button and Toolbars on Browser | The "Back" and "Forward" buttons on browsers were designed many years ago for "static" websites, where the pages did not change. These buttons redisplay the pages based on the information stored on the users computer, not the current information on the website. As a result, these buttons do not work with the IRM, or any other "dynamic" web application and must be removed from the guests browser. See "Eliminate the Back button and Toolbar on Browser" below. |
| Decide on IRM starting Page | It is possible to link from the marketing web site to the IRM to different starting points. For example, a travel agent or owner can link directly to the login page, while a guest can link directly to a list of available rooms. See: "Starting Page in IRM available for Linking" below. |
| Duplicate Session Warning |
Under some conditions when a guest attempts to start the IRM from a link on your marketing website they may receive a "Session running" warning. See KI0059 to eliminate this problem. |
The diagram below shows the data flow when a guest starts with your marketing website and then links to the IRM.
| Data Flow From Marketing Website to IRM |
|---|
|
|
It is critical that all links from the marketing web site to any start page in the IRM always launch a new browser window. This provides the guest two browser windows, one with your marketing site, and the other with the IRM. If the guest closes the IRM, your marketing site is still on the screen which allows the guest to easily go back and forth between your marketing site and the IRM. The following link starts RDP's demonstration IRM in a new window AND removes the back/forward buttons in the browser and should be used as a model by your website designers for all links to the IRM:
Sample link using new browser without back and forward buttons: Make a new Reservation in RDP's IRM Demonstration System.
Please also review Linking Options from Your Marketing Website to the IRM.
Warning: Do not put the IRM into an HTML Frame. It will not work. Always link to a completely new browser window that only has the IRM.
The "Back" and "Forward" buttons on browsers were designed many years ago for "static" websites. Static sites do not change. These buttons redisplay the pages based on the information stored on the user's computer; not the current information on the website. As a result, these buttons do not work with the IRM, or any other "dynamic" web application, because they attempt to display "old data". To understand this concept, lets look at an example:
The solution to this problem is:
The combination of these two steps provides the guest two browser windows, one with your marketing site
and one for the IRM, without the "back and forward" buttons. If the guest closes the IRM, your marketing site
is
still on the screen. This allows the guest to easily go back and forth between the marketing site and
the IRM.
The following link starts RDP's demonstration IRM in a new window AND
removes the back/forward buttons in the browser and should be used as a model by your website
designers for all links to the IRM:
Sample Link from Marketing site to IRM with a new browser without back & Forward buttons: Make a new Reservation in RDP's IRM Demonstration System"
Please also review Linking Options from Your Marketing Website to the IRM.
| Procedures for eliminating the Back and Forward buttons from the Guest Browser | |
|---|---|
| Warning: These steps are designed for use by someone familiar with HTML programming and JavaScript. | |
| Insert JavaScript on each page on the marketing site that links to the IRM | Insert the following JavaScript onto each page on the marketing website
that contains a link to the IRM: <script language=javascript> |
| Use the following link & start a new Browser with each link |
<a href='javascript:StartIRM("Link")'> The word "Link" above should be replaced with the normal IRM link option. See Linking options from your marketing website to the IRM |
| Sample
Link
Using New Browser & |
To see a sample of what the browser will look like without the back button and tool bars click on the link below. |
It is possible to link from the marketing website to the IRM to different starting points as described below. Regardless of what starting point is used, it is critical to always:
The combination of these two steps provides the guest two browser windows, one with your marketing site, the other with the IRM, without the "back and forward" buttons. If the guest closes the IRM, your marketing site will still be on the screen. This allows the guest to easily go back and forth between the marketing site and the IRM.
| IRM Starting Point | Explanation |
|---|---|
| Access Type | The Access Type screen allows entry to the IRM for all reservation categories. The user must then select a reservation category, which can include: paying guests, travel agents, groups, wholesalers, brochure requests, and vacation rental owners. |
| Link to Login Screen | The IRM can also make reservations for returning guests, travel agents, groups, wholesalers and vacation rental owners. It is possible to bypass the Access Type screen and link directly to the Login screen. |
| Link to Date Entry | Many RDP customers would prefer to skip the Access Type page and take paying guests directly to the Date Entry screen and then show all room types or room numbers that are available for those dates. |
| Link Directly to Available Room Types or Room Numbers | It is possible to collect the arrival date and departure date using a form on your marketing website and then link directly to the available room numbers or room types in the IRM. This bypasses both the IRM access type screen and the date entry screen. This feature is designed for customers using the IRM to make reservations either by room type (inventory reservations) or room number (pre-assign reservations). To implement this feature requires someone familiar with HTML forms and programming to create a form on your marketing website to collect the arrival date, departure date, and other information. |
| Link to Specific Room Type or Room Number | It is also possible to link to a specific room type (Inventory reservations) or room number. For example, you could put a complete description of your "Penthouse Suites" on your marketing web site, and then add a link for "Check availability for penthouse suites". Or, for our vacation rental customer, you may have a complete description of each rental unit on your marketing site and wish to link add a link for "Check availability of this unit number". |
| Linking to Multiple RDP Databases from one IRM Server | Many RDP customers have more than one RDP
database. It is possible to use one IRM server to access
multiple RDP databases, provided the IRM server and the data server are
connected locally to the same hub or switch. It is not possible to
connect the IRM to a data server that is remotely connected, such as over a
T1 line. See
IRM
Hardware Requirements.
For example, one RDP customer manages 8 different properties, which include 5 hotels, 2 condo-hotels, and a timeshare resort. This customer has a data center with two data servers (four RDP databases on each data server) and one IRM server, all at the same location. The properties connect to the data center with Microsoft Terminal Services. In this example the one IRM server can make reservations for all 8 properties which reside on two different data servers. |
| Link to Specific Property Code in one RDP Database |
Many RDP customers divide a single data directory into specific property codes, which are set up using menu 98, option 090, table "R2 - Property Code Definition". For example, a vacation rental operation may manage 20 units in the "Wildflower" building as property code WF and 30 in the Eagle Mountain building as property code EM. All 50 room numbers are in one RDP data directory, which is RDP01. When making reservation the guest can select any property code, such as WF and then all available room numbers of that property code are displayed. It is possible to link directly from your marketing website to a specific RDP data directory, with the default property code already set. For example, you may want to put a description and pictures of the Wildflower building on your marketing web site, and then include a link for "Make a reservation for Wildflower Condos". |
Link to RDP Database and Property Code |
Some RDP customers have an environment where they have multiple RDP data directories AND they use property codes to separate unit numbers in each data directory. It is possible to link to a specific RDP data directory AND a specific property code in that data directory: |
The IRM can be used with or without a SSL Certificate for secure access (see "Installation of SSL Certificate"). Lets look at a few terms:
| Term | Explanation |
|---|---|
| IRM Server | The IRM server is the Windows 2000/2003 server where RDP's Internet Reservation Module (IRM) software is installed. See "IRM Overview". |
| RDP Data Server | The RDP data server holds all data and is accessed by the IRM server, as well as all workstations. See "RDP Hardware Overview" |
| Internal IP Address | The IRM server and RDP data server will both have Internal IP addresses, which are behind the firewall and are used to communicate between the IRM and the data server. For RDP's demonstration IRM server, the internal IP address is: 192.168.43.7 |
| Use External IP Address of IRM if no SSL Certificate and use http in link | The IRM needs an external IP address, which can be accessed
outside your firewall. For RDP's demonstration IRM server, the
external address is 65.38.150.7. The firewall must be configured to
receive Internet TCP/IP packets on the external address (65.38.150.7) and
re-direct them to the internal address of the IRM server,
192.168.43.7. Note: see "Firewall
Ports to Open". When linking from your marketing site to the IRM server, if you are not using a SSL certificate, always use the external IP address of the IRM server in the link, such as: http://65.38.150.7/irm, which is the RDP test IRM server. |
| Use SSL Certificate name if
SSL Installed
Link with http, not https |
If a SSL certificate is purchased, it will have a
name. For RDP's demonstration IRM server, the name is
"IRM.Resortdata.com", which is set at the DNS level to the
external address of the IRM server, in this example, 65.38.150.7.
When using a SSL certificate, the link from the marketing web site to the
IRM must always use the certificate name, such as http://irm.resortdata.com/IRM,
which is the RDP test IRM server.
Warning: Always use HTTP (port 80) in the link and not HTTPS (port 443) when linking to the IRM. This significantly improves the IRM performance when checking availability, which does not require a data encryption. The IRM will automatically switch to secure mode (port 443) when moving to the data entry page that includes the guest credit card number. |
To hyperlink from the marketing website to the IRM access type page use the following links, depending on if a SSL certificate is installed or not. The samples below are for RDP test IRM server:
| Security Type | Link to use | Notes |
|---|---|---|
| No SSL Installed | http://65.38.150.7/irm | Replace the IP address with the external IP address of your IRM server |
| SSL Installed | http://irm.resortdata.com/IRM | Replace "irm.resortdata.com" with your SSL Name. Note: Use http, not https in the link. The IRM will shift to https when needed automatically |
With both links above the IRM uses the default data directory set in c:\Inetpub\wwwroot\IRM\IRMPath.txt for locating the RDP Data Server. See Using Multiple RDP databases with one IRM Server. A sample of the Access Type page is below
The link below is an example of using a button to link from the marketing web site to the IRM. If you click on the button below it will take you to the demonstration IRM at RDP. The link on the button is: http://irm.resortdata.com/IRM. You could also put on your marketing site, Make Reservation Now.
Many RDP customers would prefer to skip the access type page and take paying guests directly to the date entry screen and then show all room types or room numbers that are available for those dates. This can be accomplished with the links below:
|
Category |
Link to Use |
|---|---|
| New Guest Reservation if guest is allowed to select a particular room number (pre-assign reservations) | http://irm.resortdata.com/irm/Rooms1.asp |
| New Guest Reservation when guest selects a room type only (Inventory reservations) or if using the IRM to pick a room type and then automatically assign a room number. | http://irm.resortdata.com/irm/RoomType1.asp |
| Warning: For all links above if you are not using a SSL certificate, replace the "irm.resortdata.com" with the external IP address of the IRM server. If using a SSL certificate, then replace irm.resortdata.com with your SSL name. Note: Use http, not https in the link in all cases. The IRM will shift to https when needed automatically. | |
It is possible to collect the arrival date and departure date using a form on your marketing website and then link directly to the available room numbers or room types in the IRM. This bypasses both the IRM access type screen and the date entry screen. This feature is designed for customers using the IRM to make reservations either by room type (inventory reservations) or room number (pre-assign reservations). To implement this feature requires someone familiar with HTML forms and programming to create a form on your marketing website to collect the arrival date, departure date, and other information.
The IRM can also make reservations for returning guests, travel agents, groups, wholesalers and vacation rental owners. It is possible to bypass the Access Type screen and link directly to the Login screen.
|
Category |
Link to Use |
|---|---|
| Existing Guest Login | http://irm.resortdata.com/irm/AccessID.asp?AccessType=Guest |
| Travel Agent Login | http://irm.resortdata.com/irm/AccessID.asp?AccessType=Agent |
| Group/Wholesaler Login | http://irm.resortdata.com/irm/AccessID.asp?AccessType=Group |
| Owner Login | http://irm.resortdata.com/irm/AccessID.asp?AccessType=Owner |
| Brochure Request | http://irm.resortdata.com/irm/AccessID.asp?AccessType=Brochure |
| Warning: For all links above if you are not using a SSL certificate replace the "irm.resortdata.com" with the external IP address of the IRM server. If using a SSL certificate, then replace irm.resortdata.com with your SSL name. Note: Use http, not https in the link in all cases. The IRM will shift to https when needed automatically. | |
It is also possible to link to a specific room type (Inventory reservations) or room number. For example, you could put a complete description of your "Penthouse Suites" on your marketing web site, and then add a link for "Check availability for penthouse suites". Or, for our vacation rental customer, you may have a complete description of each rental unit on your marketing site and wish to link add a link for "Check availability of this unit number".
|
Category |
Link to Use |
|---|---|
| Link Direct to room type (unit type1B in this example) | http://irm.resortdata.com/irm/RoomDetail.asp?Type=1B |
| Link direct to Room Number (room 721 in this example) | http://irm.resortdata.com/irm/Calendar.asp?Room=721 |
| For all links above if you are not using a SSL certificate replace the "irm.resortdata.com" with the external IP address of the IRM server. If using a SSL certificate, then replace irm.resortdata.com with your SSL name. Note: Use http, not https in the link in all cases. The IRM will shift to https when needed automatically. | |
As an example of linking to a specific room number, see www.vailrealty.com. If you click on the link below for "book this unit now", it will take you to the demonstration IRM server at RDP, using the link: http://irm.resortdata.com/irm/Calendar.asp?Room=721
Note: This feature is designed for customers using the IRM to make reservations by unit type (inventory reservations). It does not work for customers who allow guests to select an available room number (pre-assign reservations).
The IRM can link to any of the three databases. Each database can have unique HTML screens for policies, room type descriptions, rates, etc. A sample link is below:
| Field | Explanation | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| http:// | Always start with http://, even if you are using a SSL certificate. The IRM will switch to SSL mode (port 443) when needed | ||||||||||||||||||||||||
| SSLNameorExternalIP/ | Put your SSL name (irm.resortdata.com) or external IP address (65.38.150.7) here. End with a "/" to separate the field. | ||||||||||||||||||||||||
| IRM/default.asp?IrmPath=// | Always place "IRM/default.asp?IrmPath=//" after the SSL name or IP address. Note: You must have two "//" after the "IRMPath"! | ||||||||||||||||||||||||
| dataservername/Path/Path | Put in the name of the RDP data server where the data for
this RDP data directory is stored. For example, if the RDP data
server is named "RDPData", and there is a shared folder RDPNT
on this data server, the path becomes:
RDPData/RDPNT/RDP/ |
||||||||||||||||||||||||
| &IRMResort=xx | The last part of the link is "&IRMResort=xx",
where "xx" is the data directory. In this example, the
"xx" will be one of:
|
||||||||||||||||||||||||
| &Country=yy | The IRM contains user defined
HTML files to customize the IRM, including your reservation policies,
unit type descriptions, pictures, etc. When using multiple RDP
databases with one IRM server it is possible to have different HTML
files for each data directory. These folders are found on the IRM
server in C:\Inetpub\wwwroot\IRM\ as follows:
|
||||||||||||||||||||||||
|
Sample Link1: http://IRM.Resortdata.com/irm/default.asp? The link above does not contain a data file path override or a UserHTML path override. It uses the default data paths. It will link to the IRM server based on the SSL security certificate IRM.Resortdata.com. It uses the data path found in the C:\Inetpub\wwwroot\IRM\IRMPath.txt file, which should be set to the RDP01 data directory. The user defined HTML files are found in the default "UserHTML" folder and the user text files are found in the default "UserText" folder on the IRM server in C:\Inetpub\wwwroot\IRM. |
|||||||||||||||||||||||||
|
Sample Link2: http://IRM.Resortdata.com/irm/default.asp?Irmpath=//RDPData/RDPNT/RDP&IRMResort=02&country=02 The link above will go to the IRM server based on the SSL security certificate IRM.Resortdata.com. It sets the default data server to "RDPData", to a folder on that server "RDPNT/RDP02". The "country=02" sets the path for the user defined HTML files to 02UserHtml and the user defined text files to "02UserText". |
|||||||||||||||||||||||||
|
Sample Link3: http://65.38.150.7/irm/default.asp?Irmpath=//RDPData/RDPNT/RDP&IRMResort=03&country=03 The link could be used if you did not have a SSL certificate. The link will go to the IRM server at the external IP address 65.38.150.7. It sets the default data server to "RDPData", to a folder on that server "\\RDPNT\RDP03". The "country=03" sets the path for the user defined HTML files to 03UserHtml and the user defined text files to "03UserText". |
|||||||||||||||||||||||||
Many RDP customers divide a single data directory into specific "property codes", which are set up using menu 98, option 090, table "R2 - Property Code Definition". For example, a vacation rental operation may manage 20 units in the "Wildflower" building as property code "WF" and and 30 in the "Eagle Mountain" building as property code "EM". All 50 room numbers are in in one RDP data directory, which is RDP01. When making reservation the guest can select any property code, such as "WF", and then all available room numbers of that property code are displayed.
It is possible to link directly from your marketing website to a specific RDP data directory, with the default property code already set. For example, you may want to put a description and pictures of the "Wildflower building" on your marketing website, and then include a link for "make a reservation for Wildflower Condos Now". This link would be formatted as follows:
|
Sample Link1: http://IRM.Resortdata.com/irm/default.asp?Propcode=WV The link above uses the default data path found in the C:\Inetpub\wwwroot\IRM\IRMPath.txt file, which should be set to the RDP01 data directory. The property code is set to "WV" (Wildflower in this example). The user defined HTML files are found in the default "UserHTML" folder and the user text files are found in the default "UserText" folder on the IRM server in C:\Inetpub\wwwroot\IRM. |
It is possible to turn off the ability for a guest to change the property code. On the IRM options page there is a checkbox in the reservation section for "Show property codes (Locations) on Room & Room Type Listing Page. If this is not checked the guest will only be able to view properties in the property code passed from the marketing website.
Some RDP customers have an environment where they have multiple RDP data directories AND they use property codes to separate unit numbers in each data directory. It is possible to link to a specific RDP data directory AND a specific property code in that data directory as follows:
|
http://IRM.Resortdata.com/irm/default.asp?Irmpath=//RDPData/RDPNT/RDP&IRMResort=02&PropCode=WV&Country=02 The link above will go to the IRM server based on the SSL security certificate IRM.Resortdata.com. It sets the default data server to "RDPData", to a folder on that server "RDPNT\RDP02". The property code is set to "WV" (Wildflower in this example). The "country=02" sets the path for the user defined HTML files to 02UserHtml and the user defined text files to "02UserText". Warning: When using Property codes AND the country=xx parameter to switch the UserHTML folder, all user defined files for all property codes, unit types, and unit numbers in the entire database found in the RDP02 directory. The "country" logic is "per data directory", not "per property code in a data directory". The relationship is as follows:
|
Under some conditions when a guest attempts to start the IRM from a link on your marketing website they may receive a "Session running" warning. See KI0059 for a variety of suggestions on how to eliminate this problem.
The following table explains the relationship of the RDP Data server, IRM server, workstations, and firewall.
| 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. |
Follow these instructions to add a hyperlink from your website that allows visitors to find Resort Data Processing's website. With this link, Internet users worldwide can discover additional information about the software used to manage your property. In return, RDP will list your property's website on our Customers on the World Wide Web page, so visitors to our website can easily find out more about your property.
|
|
The Internet Reservation Module (IRM) allows Internet guests to make reservations directly into the RDP system without involvement from the property’s reservation staff. This section provides links to instructions for configuring the IRM after the Windows 2000/2003 bridge server has been installed.
Remember to backup the C:\Inetpub directory every day on the IRM server to avoid losing important files and pictures. See Backup for more details.
| IRM Configuration Links | |
|---|---|
| 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 |
