Updated: 10/13/08 SS per KW
Update: 6/11/08 Microsoft Windows Server 2003 and 2008 for 32 bit and 64-bit are supported by RDP. Call RDP Support at 970- 845-7108 with any hardware questions. Please see the current hardware requirements.
Note: RDP no longer supports Windows 95, 98, ME or 2000.
|IRM.Net and RDP Overview Links|
This document is intended for use by Certified Microsoft Installers and outlines the steps for installing the RDP system on a Windows 2003/2008 data server. The document is organized into the following sections.
RDP uses the Pervasive database, which is located on a data server. The
data server can use Windows Server or could be installed peer-to-peer on Microsoft
workstation platforms. The preferred operating system is Windows 2008.
Before starting the installation process, it is critical to verify if the proper
equipment is in place. Please
click here to review the RDP hardware requirements.
This document serves as an overview to the RDP Data Server installation process. It is designed for use by a Microsoft certified installer and is not intended as the sole reference for installing and configuring Windows Server and Pervasive.SQL.
RDP strongly recommends installing RDP as the only application on a Windows Server. Other applications (back-office accounting software, sales and marketing applications, etc.) should be installed on another server. This configuration guarantees maximum performance and reliability for the RDP property management software. It also eliminates the risk of application conflicts between RDP and the Pervasive.SQL database with other applications.
|Diagram of Data Server, IRM Server, and Workstations|
This document is not intended as a complete installation guide for Microsoft Windows Server. However, there are a number of prompts during the initial installation process that require the correct entry for the RDP system to function.
This document can be used to install an RDP Data server with Windows 2008 server. The installation steps are different as Microsoft made a variety of changes in Windows 2008.
If there is an existing Novell Server at the property, do not install the Novell Client, IPX/SPX, or the Novell Gateway on the new Windows Server. Any of these items will cause RDP software to not function correctly.
Make sure to install the file system as NTFS, which is required for various RDP functions to work correctly.
The computer name must follow the proper naming conventions for DNS. To keep things simple, RDP suggests naming the RDP data server "RDPDATA". Please call RDP support at 970-845-7108 for approval of any other name.
The administrator password is critical to Windows installation. Please follow the PCI suggested password practices. Please note that RDP support will require the administrator password to install the RDP system and for ongoing support.
Resort Data Processing (RDP) has fully integrated e-mail into RDPWin and the Internet Reservation Module (IRM). See: Installation and Configuration of Microsoft Internal Outgoing SMTP Mail Server.
Windows Server installation prompts for Network Settings. Assigning a static IP address to the RDP data server. When prompted for the networking settings:
Workstation network settings can be set automatically with DHCP or manually for
All workstations that access RDP must be on the same subnet. For example, if the RDP data server is assigned IP "192.168.43.2", then all workstations should have an IP in the range 192.168.43.3 to 192.168.43.255. The subnet for all workstations would be 255.255.255.0.
Windows Server installation will prompt for Workgroup or Computer domain. Answer as follows:
If you are not sure if there is another domain present at the property, select "workgroup." It is easy to join an existing domain at a later point.
After entering all the initial installation prompts as defined above, the Windows Server installation process continues. When this initial installation finishes, please complete the following tasks:
Almost all software shipped on CDs is outdated when you install it. There
are usually many bug fixes available from the vendor's website. After installing
Windows Server, please install all Microsoft service packs and critical updates.
The most efficient way to accomplish this goal is to connect the RDP Data Server
to the Internet and use Microsoft's Windows Update option.
It is important to install all service packs and critical updates available for Windows Server immediately, as RDP only tests our software on Windows Server with all service packs installed.
RDP requires anti-virus software to be installed on the data server. There are a wide variety of anti-virus products available.
Security with Windows Server is a very complex topic and there are many ways
to secure a server, including folder security, share permissions, domain policies,
local policies, users, groups, etc. RDP support personnel are not experts
on all security issues for Windows Server. We have outlined a security approach
in this document that works for our system. If you elect to deviate from the
suggestions in this document it is very easy to create incorrect security, permissions,
or policies that will prevent the RDP system from working and a complete reformat
of the data server may be required.
RDP's approach to security requires the presence of Microsoft Active Directory. The installation of Active Directory allows the creation of a domain to authenticate user logins and passwords as well as storing a list of valid users, groups, and additional security information.
If there is an existing Windows domain, the new RDP Data Server should be joined to this domain. This can be accomplished as follows:
The steps below apply to a installing active directory and creating a new domain for Windows 2003
To Install Active Directory on Windows Server:
Windows Server introduced the ability to have DNS server software installed to
resolve internal computer names, as well
as to resolve website addresses, such as "Yahoo.com". Names are resolved (translated
into IP addresses) by sending queries to the DNS software that is installed on the
Data Server. The computer industry uses the term "Server" to mean both
a physical computer and software. For example, for most RDP customers there
is only one physical computer that is called the "RDP Data Server". It also
runs run the "DNS Server" software and the "Pervasive Server" software. So
the "RDP Data Server" and the "DNS" server and potentially the DHCP server are all
the same physical computer.
The DNS server is a computer that stores domain name-to-IP address mapping records (DNS Forward Lookup Zones) and IP address-to-name (DNS Reverse Lookup Zones). DNS is essential to the correct function of a Windows Server. DNS was installed when the active directory creation wizard was run in the steps above. DNS must now be configured. If DNS is not properly configured, workstations, and the Internet Reservation Module (IRM) may
The steps below assume that there is not a pre-existing DNS server installed on another server. For those customers with an existing Windows DNS server already installed, the RDP Data server should be set to use the existing DNS server.
The information below is intended for Microsoft Certified computer professionals. RDP does not provide support on DNS Setup.
To function correctly the data server, IRM server, and all workstations need a full computer name (FCN). At Resort Data Processing our Domain is "RDP2003.Local". Therefore a give machine, such as the data server, has a FCN of "RDPData.RDP2003.Local". The IRM and Data Server use the FCN, which is stored in the local DNS server, to communicate.
When setting up a new forward DNS zone, the zone name should be separated by a period, such as "companyname.Local". Each computer then has a FCM of "Machinename.companyname.local". For each workstation to properly register with the internal DNS server, follow the steps below:
|Check Full Computer Name on data server, IRM, and all workstations|
Verify the full computer name of the data server, IRM server, and all workstations as follows:
|Change Full Computer Name if Needed|
|If you need to change the Full
Computer name, click the "More" button. A screen similar to the following
Confirm the following:
|Set the DNS suffix for the TCP/IP connection for
the Data Server, IRM Server, and all Workstations
You must also set the DNS suffix for the TCP/IP connection for the Data Server, IRM Server, and all Workstations as follows:
In the example below the "Preferred DNS Server" is the IP address of the INTERNAL DNS server, which is usually the RDP data server. It is critical to always use the internal DNS server as the Preferred DNS server for the RDP Data server, IRM server, and all RDP workstations for the RDP system to function correctly. An "Alternate DNS server" is not required, but if one is used it must also be an Internal DNS Server.
Click the "Advanced" button, and then click the "DNS" tab. A screen similar to the following should appear.
It is critical to:
|Test DNS with NSLOOKUP on the Data Server, IRM Server, and all Workstations|
After making all the changes above on the Data Server, IRM server, and each workstation, reboot each computer and test the DNS configuration with NSLOOKUP, a Microsoft utility, as follows:
|Verify Forward Lookup DNS of Data Server|
|First we want to verify the
Forward DNS lookup information for the RDP data server. At the ">"
prompt in NSLOOKUP, type in the name of the data server to verify the Forward
DNS Lookup information is correct. In the example below, the name
is "RDP2003A". NSLOOKUP will lookup this name in the forward lookup
table of the DNS server and return the internal IP address of that machine.
In the example below the internal IP address of the data server named "RDP2003a"
is "192.168.43.4". Verify that this is the correct IP address.
|Verify Reverse Lookup DNS of Data Server|
|Next we want to verify the
Reverse Lookup DNS information of the data server. At the ">"
prompt in NSLOOKUP, type in the IP address of the RDP Data Server
to verify the Reverse DNS Lookup information is correct. In the example
below, the IP address of 192.168.43.4 was entered.
The DNS Server RDP2003a.RDP2003.Local will lookup this IP address in its Reverse lookup table and return the full machine name of that internal IP address, which in this example, is RDP2003a.RDP2003.Local". Verify that this is the correct name for this IP address.
|Verify Forward Lookup DNS of Each Machine|
|Next we want
to verify the Forward Lookup DNS information of each computer. At
the ">" prompt in NSLOOKUP, type in the name of the computer to verify
the Forward DNS Lookup information is correct. In the example below,
the name is "GX112". NSLOOKUP will lookup this name in the forward
lookup table of the DNS server and return the internal IP address of that
machine. In the example below the DNS Server "RDP2003a.RDP2003.Local"
looked in its forward DNS lookup table to find the internal IP address of
the mahine GX112 as "192.168.43.57". Verify that this is the correct
|Verify Reverse Lookup DNS of Each Machine|
|Lastly we want to verify the
Reverse Lookup DNS information of each computer. At the ">" prompt
in NSLOOKUP, type in the IP address of the computer to verify the
Reverse DNS Lookup information is correct. In the example below, the
IP address of 192.168.43.57 was entered. The DNS Server RDP2003a.RDP2003.
Local will lookup this IP address in its Reverse lookup table and
return the full machine name of that internal IP address, which in this
example, is GX112.RDP2003.Local". Verify that this is the correct
name for this IP address.
RDP support requires access to the RDP Data 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 was installed earlier. For Windows 2003, you must activate Remote Desktop as follows: (Note: "Remote Desktop" in Windows 2003 is actually just "terminal services in Remote Administration mode" in Windows 2000...Microsoft just wanted to confuse everybody!)
Note: For both Windows 2003, 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. Please consult the Microsoft documentation for details.
The next step is to create RDP required users and groups in Active Directory.
The RDP system requires a specific folder structure. If any other structure is used, the system will not function correctly. Please follow the steps below:
|Step||Create and share the RDPNT Folder|
|Login as Administrator
on RDP Data Server
|Sit in front of the RDP Data Server and logon as the administrator. It is critical to make all initial security changes as administrator.|
|Start Windows Explorer||On the RDP Data Server, right click start and left click Explore. This starts Windows Explorer, which can also be found in the Accessories folder.|
|Create RDPNT Folder||
1. Highlight the local drive that is allocated for RDP, which is usually "C".
2. Select File | New | Folder Name the folder RDPNT.
3. The folder must have the name RDPNT.
|Create RDPNT/RDP Folder||
1. Highlight the new RDPNT folder, and select File | New | Folder and create a sub-folder "RDP".
2. The folder structure will appear as C:\RDPNT\RDP from the data server. When a network drive, such as F: is mapped to the shared RDPNT folder, the folder structure at the workstation appears as "F:\RDP".
Warning: Do NOT attempt to install RDP software in any folder other than the one described above. The folder structure must be \RDPNT\RDP, where RDPNT is created at the ROOT of a drive formatted with NTFS. Do NOT install RDP in any other folder, such as "C:\applications\RDPNT\RDP". If the directory structure is not followed, RDP updates will not install correctly.
|Assign RDP and
Full Control of RDPNT
The RDP security plan is to only allow members of the RDP group, or the Administrators group, to have access to the RDP System.
1. In Windows Explorer, right click the RDPNT folder (not the RDP sub-folder) and select Properties - Security.
2. Add the RDP group with full control of the RDPNT folder. Please note that full control is required, as RDP programs create files, delete files, rename files, etc.
Note: When the group RDP or Administrators is first added, they do not have full control. You must select the Full Control checkbox.
|Remove Users Group
From RDPNT Folder
|Windows 2003 has much tighter security be default than Windows 2000. The "users" group does not have full control of folders by default, but this group still has permission to "read & execute, list folders, and read". For proper RDP security, the "Users" group should be removed from the RDPNT folder.|
|Share the RDPNT Folder Add RDP Group and Administrators group
with Full Control of RDPNT Share
Workstations can only access the C:\RDPNT\RDP folder on the data server
if it is shared. To access the RDPNT folder when shared, Windows 2003 require
the proper security at both the folder level ("folder security") and the
property security at the share name level ("share permissions").
Pervasive.SQL Version 11 is the database used by RDP, and must be purchased from RDP. If you have not yet purchased Pervasive, please call RDP Sales. For details on Pervasive.SQL click here. The installation of Pervasive.SQL v11 process has four major steps, as follows:
The first step is to install the Pervasive.SQL Engine for Windows Server on the RDP Data Server with the following steps:
|Logon as Domain Administrator From Console - No Terminal Services||
The installation of Pervasive.SQL v11 must be performed from the RDP data server console.
|Close all Programs and Disable Virus Protection||Close or disable any virus protection software on the server as it may cause the installation to fail. If Microsoft Internet Information Services (IIS) is active it must be stopped. NOTE: Normally IIS should not be installed on the data server.|
|Install Pervasive.SQL Windows 2003 Server||Install Pervasive Server Version 11.|
|Test Network Communication & Relational Engine||Complete steps listed in Test the Active Installation.|
|Reboot Server - Even If Not Prompted To Do So||After installing the Pervasive Engine on a Server, shut down and reboot
the server, even if you are not prompted to reboot. Pervasive will
not function correctly until you shut down and
Complete steps for installing the Client or Workgroup.
|Finish Installation and Verify the Installation was Successful||Verify that the installation completed successfully. The text "You have successfully completed the Pervasive System Analyzer Wizard" should appear. If there were any problems encountered, and you purchased Pervasive from RDP, please open a ticket with RDP Support. Select "Finish". Pervasive should now be installed.|
|Check for Pervasive
|Click here to check for
Almost all software shipped on CD's is outdated when you install it. It is critical to install all Pervasive service packs BEFORE installing Pervasive on any workstations. Please call RDP Support at 970-845-7108 to determine if any service packs are required.
Pervasive.SQL uses RAM memory in the server to "Cache" system data. For
example, the first time reservations are displayed Pervasive has to read the data
from the hard disk drive on the data server. The second time the same information
is needed it is read from the RAM memory Cache. The single most important performance
factor for RDP is to have a Windows 2003 server with at least 2 gigabytes of total
memory, with 20% of this allocated to Pervasive cache. The cache should have
been set automatically, however, to verify this critical setting:
Warning: Before changing the Cache Allocation setting, please call RDP support at 970-845-7108. This is an absolutely critical setting. Performance can be destroyed if the setting is too high or too low. If memory is added or subtracted from the server, the cache allocation size must be adjusted.
By default pervasive installs communication protocols SPXII, TCP/IP and NETBIOS.
In order for RDP to function correctly, pervasive must be configured to use TCP/IP
only. It is critical that this step is performed before installing the Pervasive
client on work stations.
If installing PSQL V10 or higher, Clients you will not need to share this folder with all RDP Workstation users.
Prior to installing the Pervasive Client on all of the workstations, it is necessary to share the PVSW directory on the C drive of the RDP Data Server. This allows workstations to load the client installation files that are stored in c:\PVSW on the Data Server. To Share the PVSW folder, proceed as follows:
Note: It is not required to change the default security settings on the C:\PVSW folder, or the sharing permissions. The default is to give all domain users "read" access to the shared C:\PVSW, which is all that is required to install the Pervasive.SQL v11 client on a workstation.
The Pervasive.SQL client must be installed on each workstation using the RDP system directly. For remote clients, or thin clients connected via Terminal Services or Citrix, the Pervasive client must be installed on the Citrix Server, but not on the workstations connected to the Citrix Server. For details on using Citrix or Terminal Services with the RDP system, click here. To install the Pervasive.v10 client on a workstation directly connected, follow the steps below.
Before installing any workstation, verify that the Pervasive.SQL v11 engine and all service packs have been installed on the data server. Click here to check for service packs.
The Pervasive.SQL client installation, and RDP software, require workstations with Windows XP Professional. Windows 95, 98, ME, NT, 2000, or any other versions of Microsoft operating system should not be used and are not supported by RDP. RDP testing has determined that Windows XP Professional workstations are over 100 times more reliable that Windows 98, or older, operating systems.
Verify that each workstation can communicate with the network correctly before installing Pervasive.SQL v11:
In order to use the RDP system all workstations must be in the same domain as the data server. To change the domain on Windows XP:
When installing Pervasive.SQL on a workstation, it is essential to login as the network administrator, or as a user that has administrative rights to the local machine.
Close all programs running on the workstation. Also disable any virus protection software as it may cause the installation to fail. If for some reason Internet Information Services (IIS) is running on a workstation it must be stopped.
|Close all Programs and Disable Virus Protection||Close or disable any virus protection software on the workstation and disable virus protection.|
|Logon as Administrator
to a Given Workstation
|To start the Pervasive.SQL
client installation from a given workstation, right-click the Start button
and click "Explore" This starts Windows Explorer. In the left hand
panel expand the following:
|Prompts During Installation of Pervasive.SQL v10 for Windows 2003 Server||Select "Yes" if you agree
with the license agreement. Then enter the license key, and select
Next. Then select:
|Test Network Communication||
It is important to successfully complete all tests If any of the tests do not complete correctly, please call RDP support immediately, at 970-845-7108.
|Test Transactional Engine||The transactional engine as this is used extensively by RDP. Select "Next" to begin the transactional tests.|
|Test Relational Engine||Complete the Relational Engine Tests.|
|Reboot Server or Workstation - Even If Not Prompted to Reboot||After installing the Pervasive Engine on a given workstation, reboot the workstation even if you are not prompted to reboot. Pervasive will not function correctly until you shut down and reboot.|
|Finish Installation and Verify the Installation was Successful||Verify that the installation completed successfully. The text "You have successfully completed the Pervasive System Analyzer Wizard" should appear. If there were any problems encountered, and you purchased Pervasive from RDP, please call RDP support at 970-845-7108. Select "Finish". Pervasive should now be installed.|
The workstations can now be configured to start RDP with the steps in the next
RDP supports Windows XP Professional as a client operating system. This section serves as an overview of the Windows XP Professional installation process.
The same drive letter must be mapped to the Data Server folder RDPNT from all workstations with the following steps:
Each RDP workstation must have a unique station number. RDP uses station numbers to stores settings that are unique per workstation, such as screen colors. Use the following steps for setting a station number on a Windows XP Professional workstation.
Where "xx" is a number from 1-99. Remember, a different station number must be assigned to each Windows XP workstation.
RDPWin requires a minimum screen display of 1024 x 768
A batch file is used to start the RDP system, which can be created as follows:
A desktop shortcut should be put on each workstation that will access RDP, as follows:
With Windows 2000 and XP, Microsoft made a change that delays all DOS print jobs
by 15 seconds. To accelerate printing, every computer using any version of Windows
2000 or Windows XP will need the changes described below. This includes the Windows
2003 data server. If using Citrix or terminal services, the changes
must also be implemented on the Windows 2003 server running Citrix/Terminal Services,
as well as each workstation that uses the Windows 2000 or XP operating system.
WARNING: Using REGEDIT can cause serious damage to your operating system. Make sure to follow these steps exactly.
After installation of the data server, it is critical to test the performance. RDP has a test program (Utility RDP995 run on our demonstration data files) that should complete in 15 seconds or less. A customer recently purchased a new server, and this test program took 7 minutes, which is 28 times longer than it should! It turned out there was a problem with network card in this new machine. After replacing the card the test program completed in 8 seconds.
|Support Home||RDPWin4 & PCI Compliance||Enhancement Requests||Open A Web Support Ticket|
|Training||New Sales Website||Old Sales Website||Contact Us|