Home RDP Sales Contact Us Training  
RDP Support      Call (970) 845-7108        Open a Web Support Incident
RDPWin
Knowledge Base		 RDP-DOS
Knowledge Base		 IRM and IRM.Net
Knowledge Base		 Crystal
Knowledge Base
         

Updated: 7/03/08 SS per KW

RDP Windows 2003 Data Server Installation

Update:  6/11/08 Microsoft Windows Server 2003 and 2008 for 32 bit are supported by RDP.  Feel free to call RDP Support at 970- 845-7108 with any hardware questions.  Please see the current hardware requirements.

Note:  Microsoft's Windows Server 2003 with SP1 x64-based version (released 10/11/2007) has not been tested by RDP and therefore is not supported.  RDPWin only supports Windows 2003 R2 Standard Edition and Server 2008 for 32-bit programs.  RDP no longer supports Windows 95, 98, ME, or 2000.

Links to RDP Data Server and Internet Reservation Module (IRM.net) documents

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 Windows 2003 Data Server
Configuration Overview

RDP uses the Pervasive database, which is located on a data server.  The data server can use Windows 2003 standard edition or 2008 32 bit server, or could be installed peer-to-peer on an XP Professional workstation.  The preferred operating system is Windows 2008, as it's faster than 2003.  Any new server purchased for a RDP Data Server or Internet Reservation Module Server should be Windows 2008 for 32 bits.  Existing customers with a Windows 2003 servers do not need to upgrade to 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 Windows 2003 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 a Windows 2003 Server and a Pervasive.SQL database.  If you are looking for the installation procedure for RDP's Internet Reservation Module, please click here.

RDP strongly recommends installing the property management software on a Windows 2003 or 2008 Server dedicated to running the RDP software.  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 for the RDP property management software.  It also eliminates the risk of application conflicts between RDP and/or the Pervasive.SQL database.

Diagram of Data Server,  IRM Server, and Workstations
Warning:  Microsoft Small Business Server can not be used for the Internet Reservation Module (IRM), because Small Business Server installs Microsoft Exchange which does not work with the IRM. 
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.

Ports Reason
25 E-mails are sent out to guests from the IRM bridge server using Port 25.  See Installation of Outgoing SMTP E-mail Server
80 Internet traffic (HTTP) is required for all IRM systems.
443  Secure Internet (HTTPs) is required if IRM has Security Certificate.
3389  Terminal services are required for RDP support to access server.
DMZ Only

1583
3351		 Some customers want to set up the IRM in a Demilitarized Zone (DMZ).  RDP uses the Pervasive.SQL database, which uses two TCP ports when communicating from the client to the server, which are: 1583 and 3351. These ports will have to be open on the firewall, as all other ports required by Microsoft for the Windows 2003 IRM server to communicate with the Windows 2003 Data Server. Please contact Microsoft for details on what ports are required.
522, 389
1503, 1720
1731		 Any workstation that connects to RDP with NetMeeting must open various ports.  For instructions on how to configure your firewall to allow workstations to connect to RDP using Net Meeting, see Microsoft article ID# 158623 How to Establish Net Meeting Connections Through a Firewall.
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 2000 Professional or Windows XP professional 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:

  1. A good firewall stops most intrusions.
  2. Microsoft security on the IRM server and data server is very strong.
  3. Anti-Virus software should be installed on the IRM server and must be set to NOT scan network drives.
  4. All credit card data is encrypted when sent to the guest using SSL technology.
  5. All sensitive data, such as credit card information, is stored on the data server and not the IRM.  If a hacker manages to get through the firewall and Microsoft security to the IRM server, they still have to get from the IRM server to the data server to retrieve data.
The IRM has been installed at over 300 sites over the last 10 years, and there has not yet been an instance of someone "hacking" into the Data Server from the IRM.  However, there is always a first time; and there is some security risk. The only way to prevent all theoretical security problems is to completely remove the IRM from the Internet.  Unfortunately this would also prevent all reservations!
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.

Windows 2003 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 subjects below summarize these critical installation prompts:

Windows 2003 Versus Windows 2008

This document can be used to install an RDP Data server with Windows 2003 server.  The installation steps are different as Microsoft made a variety of changes in Windows 2008.

Do Not Install Novell Netware Client or IPX/SPX

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 2003 server.  Any of these items will cause RDP software to not function correctly.  To move data from an older Novell Server, use a tape backup.  Or use a workstation with IPX/SPX to copy data from Novell to the workstation, and then from the workstation to the new Windows Data Server.

Use NTFS File System

Make sure to install the file system as "NTFS", which is required for various RDP functions to work correctly.  If prompted to format the drive, RDP suggests using the "complete format" mode, not the "quick format."

Reinstallation of Windows 2003

If for some reason you must reinstall windows 2003 to correct mistakes made in a prior installation, RDP requires completely removing the old installation by reformatting the drive with NTFS.  Never install more than one copy of Windows 2003 on the same server.

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 - "RDPDATA"

The computer name must follow the proper naming conventions for DNS.  To keep things simple, RDP suggests naming the RDP Data Server "RDPDATA".  If you elect to use any other name, problems may occur when printing or connecting workstations.  Please call RDP support at 970-845-7108 for approval of any other name.

Administrator Password

The administrator password is critical to Windows 2003 installation.  Microsoft has suggested password requirements and  RDP suggests you follow these.  Make sure to write down the password!  Please note that RDP support will require the administrator password to install the RDP system and for ongoing support.

Windows 2000 Components - Do Not Install IIS, FTP, SMTP, or Other Services

When Installing Windows 2000, there is a critical installation screen for "Windows 2000 Components."  This screen does not exist for Windows 2003 installation.  Use all the defaults for Windows 2000 Components, with the following exceptions:

Warning: Do not install Internet Services Manager (IIS), FTP, SMTP, or any other service or application on the RDP Data Server.  The performance of the RDP Data Server decreases and the possibility of crashes and data corruption increases as more applications are run on the same server.  For maximum performance and reliability all non-RDP applications, such as accounting, E-Mail, etc., should be installed on another server.  With each additional application, the possibility of conflicts and system crashes increase greatly.

Installation of Outgoing SMTP Server on the Data Server

Resort Data Processing (RDP) has fully integrated Email into our Windows .Net property management system, RDPWin and the Internet Reservation Module (IRM).   See:  Installation and Configuration of Microsoft Internal Outgoing SMTP Mail Server

Remote Desktop or Terminal Services in Administrative Mode

RDP support requires access to the RDP Data Server for installation and ongoing support.   Microsoft provides, at no charge, a two-user license of its "Terminal Services" product for this purpose. Terminal Services must be installed as follows:

Windows 2003 Windows 2000
Remote Desktop for Administration is installed by default.  There are no installation prompts required.  Note: In Windows 2003, Microsoft renamed "Terminal Services in Remote Administrative mode" to "Remote Desktop for Administration." During Installation of Windows 2000, Terminal Services in Remote Administration mode must be installed.  See "Windows 2000 Components" above.

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.  Please consult the Microsoft documentation for details.

Networking Settings - All Workstation in the SAME SUBNET

Windows 2003 prompts for Networking Settings. RDP suggests 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 each workstation. For smaller networks, RDP has found it easier to use manual network configuration for all workstations.  This avoids installation and configuration of a DHCP server.  Installation of DHCP is not explained in this document.

Whether using manual network settings or DHCP, all workstations that access RDP must be in the same sub-net.  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.1 to 192.168.43.255. The subnet for all workstations would be 255.255.255.0.

One Network Card Only in Data Server

Only one network card should be in the data server. The Pervasive Database does not work with more than one network card.  If more than one card exists on the motherboard it is critical to disable the additional cards.

Create a Domain

Windows 2003 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 a pre-existing domain at a later point.

Steps After Initial Installation of Windows 2003

After entering all the initial installation prompts as defined above, the Windows 2003 installation process continues.  When this initial installation finishes, please complete the following tasks:

Install All Microsoft Service Packs and Critical Updates

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 2003, 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 2003 immediately, as RDP only tests our software on Windows 2003 servers that have all service packs installed.  There is no charge from Microsoft for service packs or critical updates.

Install Anti-Virus Software

Viruses have become very commonplace and can cause catastrophic problems, including complete loss of all data.  RDP requires anti-virus software to be installed on the data server.  There are a wide variety of anti-virus products available.

Installation of Active Directory and Security

Security with Windows 2003 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 2003.  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 for Windows 2003, which is provided at no charge with Windows 2003.  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.

Join a Pre-Existing Windows 2003 Domain

If there is a pre-existing Windows 2003 domain, the new RDP Data Server should be joined to this domain, and become a "member server".  This can be accomplished as follows:

  1. Right click the "My Computer" Icon.
  2. Left click properties.
  3. Select the "Network Identification" tab.
  4. Select Properties.
  5. Select "Member of" and input the Domain.

Create a New Windows 2003 Domain and Install DNS

Most RDP customers do not have a pre-existing Windows 2003 domain and therefore need to create a new domain, with the RDP Data Server acting also as the Domain Controller and the DNS server.  The exact procedure is different for Windows 2003 as described below.

Warning:  Do not use a "single label domain name" (a name without a ".").  For example, the domain name "RDP2003" by itself will not allow DNS to function correctly.  A domain name of RDP2003.LOCAL will work.  If the name of a given workstation is "RDPData", the fully qualified domain name becomes "RDPData.RDP2003.LOCAL", which is a valid DNS name.  When creating the forward lookup zone for DNS, the name of the zone in this example would be "RDP2003.LOCAL".

Install Active Directory on Windows 2003:

The steps below apply to a installing active directory and creating a new domain for Windows 2003

  1. Click Start | Programs | Administrative Tools | Configure Your Server.
  2. On the server configuration screen, click Active Directory.
  3. Scroll to the bottom and select Start the Installation wizard.
  4. Select Next and Choose a Domain Controller for a new domain.
  5. Select "Create a New Domain Tree."
  6. Select "Create a New Forest of Domain Trees."
  7. You need a Domain Name, which is entered when prompted for the "DNS Name."  The domain name must be different from the computer name assigned to the RDP Data Server.  Keep the domain name simple, 8 characters or less, and add a ".Local" to the end.  For example, you could use "RDP.LOCAL" or "MYDOMAIN.LOCAL".  You must add the ".Local" to the end of the domain name.  Windows 2003 and XP operating systems use the full domain name (i.e., RDP.Local).  Do NOT use your "external website domain," such as "resortdata.com," for your domain name.
  8. Enter the Domain NetBios Name, which is the name entered in the previous step without the ".local".  For example, either "RDP" or "MYDOMAIN".  Old Windows ME/98/95 machines use the "NetBios" name.  Note:  All RDP workstations must run Windows XP Professional with all service packs installed.
  9. Take the defaults for Database location and Log location and click next.
  10. Take the default for SYSVOL location and click next.
  11. Click OK to the error message that the DNS server cannot be contacted at this time.  This is normal, since DNS is not installed yet.
  12. Select "Yes" and Install and configure DNS on this server.  If prompted for a DNS Forward lookup name, use the same name as the domain, such as "mydomain.local".
  13. Select the radio button for "Permission compatible with Windows 2003 servers only."  This is not the default - you must select this radio button.
  14. Enter  the administrator password and select next to start the Active Directory Installation.
  15. DNS will also be installed.  Do not select the "Skip DNS" option when prompted.
  16. When the active directory wizard is done, remove the CD and reboot the server when prompted.
  17. After reboot and login, the "Configure your server" screen may appear.   Uncheck the box for "Show this screen at startup" and close this window.
  18. DNS must now be configured - see " Configuration of a DNS Server" below.

Windows 2003 - Create Domain - Install DNS - Install DHCP

To Install Active Directory on Windows 2003:

  1. Click Start | Administrative Tools | Configure Your Server Wizard. Click "Next" to start the wizard.
  2. Select "Typical configuration for a first server" and select Next.   This will install Active Directory, DNS, and DHCP.
  3. You need an Active Directory Domain Name, which is different from the computer name assigned to the RDP Data Server.  Keep the domain name simple, eight characters or less, with a ".Local" to the end.  For example, you could use "RDP.LOCAL" or "MYDOMAIN.LOCAL".  You must keep the ".Local" to the end of the domain name.  Windows 2003 and XP operating systems use the full domain name (i.e., RDP.Local).  Do NOT use your "external website domain," such as "resortdata.com," as your domain name.  Select Next and the new active directory domain will be created.
  4. Enter the Domain NetBios Name, which is the name entered in the previous step without the ".local".  For example, either "RDP" or "MYDOMAIN".  Old Windows ME/98/95 machines use the "NetBios" name.  Note:  All RDP workstations must run Windows XP Professional with all service packs installed.
  5. The next screen involves "Forwarding DNS Queries."  If you have an internet connection, choose "Yes, Forward DNS Queries..." and enter the IP address of the external DNS server that the DNS server installed on your new Windows 2003 server will use to resolve domain name addresses.  This DNS address is normally provided by your Internet Service Provider (ISP).  With some firewalls, the IP address entered will be the IP of the firewall, since the firewall provides DNS. If you do not have an Internet connection, choose "do not forward DNS Queries."
  6. Select "Next" on the screens that follow to start the installation of Active Directory, DNS and DHCP.  The server will reboot when needed during this process.

Configure a DNS - Windows 2003

Windows 2003 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 2003 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 a pre-existing Windows 2003 DNS server already installed, the RDP Data server should be set to use the pre-existing DNS server.

Naming Convention for DNS Zone - Setting up each workstation

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:
  1. From a workstation, right click My Computer and left click properties.
  2. Click the "Computer Name" tab and then click the "change" button.  
  3. The full computer name appears below.  In this example, it is "GX112.RDP2003.Local".  The "RDP2003.Local" is also the DNS Zone Name
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 should appear. 

Confirm the following:
  1. The "Primary DNS Suffix of this computer" is set the the DNS Zone name, which in this example is "RDP2003.Local".
  2.  It is critical to check the box for "Change primary DNS suffix when domain membership changes".
  3. The NetBIOS computer name should be the computer name by itself, in this example GX112
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:

  1. Right-click "My Network Places" and left-click properties.
  2. Right-click the active network connection and left-click properties.    Warning: There should be one, and only one, network card installed in the data server, IRM server, and each workstation.  If there are more than one network card the computer is not supported by RDP.
  3. Highlight the Internet Protocol (TCP/IP) and right-click Properties.  If the IP address has been manually assigned to the computer (instead of from DHCP), a screen similar to the following should appear.

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:
  • Check the radio button for "Append primary and connection specific DNS suffixes"
  • Check the checkbox for "Append parent suffixes of the primary DNS suffix"
  • Make sure that the "DNS suffix for this connection" is set the DNS Zone name, in this example, "RDP2003.Local"   
  • Check the checkbox for "Register this connection's addresses in DNS"
  • Check the checkbox for "Use this connection's DNS suffix in DNS registration"
  • Reboot the computer after making all changes

DNS Forward Lookup Zones - Windows 2003 Only

  1. The DNS server was automatically configured correctly with Windows 2003. The steps below only apply to a Windows 2003 server.
  2. Windows 2003, click Start | Programs | Administrative Tools | DNS.
  3. The name of the server should appear in the left hand pane.  Highlight this name.
  4. Expand the "Forward Look up Zones" in the right hand panel.
  5. If a "." zone appears on the right, delete it.  This is an incorrect default zone that was created with some version of Windows 2003.  This may not appear with later versions of Windows 2003.
  6. Expand the ServerName.Local zone under Forward Lookup Zones.  If the server name is "RDPDATA, the name, there will be a folder in the right hand pane, "RDPData.local".  The IP address of the Data Server will display.
  7. Close DNS and restart the service.
  8. If you have an internet connection highlight the server name in the left hand panel and select the "action" tab and then "properties".  Select the "forwarders" tab, and then check the "Enable Forwarders" and add the IP Address of the External DNS server used to resolve domain names.  This DNS address is normally provided by your Internet Service Provider (ISP).  With some firewalls the IP address entered will be the IP of the firewall, since the firewall provides DNS.

DNS Reverse Lookup Zones - Windows 2003

  1. The steps below apply to creating a DNS Reverse Lookup zone for Windows 2003.
  2. Windows 2003 - Click Start | Programs | Administrative Tools |  DNS.
  3. Expand the "Reverse Lookup Zones."
  4. From the Action menu, select "New Zone", select Next and "Active Directory Integrated Zone."
  5. When prompted for the "network ID", enter the first 9 digits of the internal IP address of the Data Server.  For example, if the IP address of the data server is "192.168.43.2", then enter the network ID of "192.168.43".  This creates a reverse lookup zone for all IP addresses in the range 192.168.43.1 to 192.168.43.255.
  6. Select Finish and close DNS.
  7. Verify that the data server network settings are using the correct DNS server, as follows:

DNS Reverse Lookup Zones - Windows 2003

  1. The steps below apply to creating a DNS Reverse Lookup zone for Windows 2003.
  2. Windows 2003 - Click Start | Administrative Tools |  DNS.
  3. Expand the "Reverse Lookup Zones" in the left hand panel.  From the Action menu, select "New Zone."  Use the defaults, which are: Primary zone and Store the zone in Active Directory.
  4. For the "Active Directory Zone Replication Scope," use the default "to all domain controllers in the Active Directory domain" and select Next.
  5. When prompted for the "network ID," enter the first nine digits of the internal IP address of the Data Server.  For example, if the IP address of the data server is "192.168.43.2", then enter the network ID of "192.168.43".  This creates a reverse lookup zone for all IP addresses in the range 192.168.43.1 to 192.168.43.255.
  6. On the Dynamic Update screen, select the default "Allow only secure dynamic updates" and select Next.
  7. Select Finish and close DNS.
  8. Reboot the server.
  9. Test DNS with the steps below.
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:

  1. Select Start - Run and type CMD.
  2. In the command window, type "NSLOOKUP".  A screen similar to the following should appear.

    The "Default Server" should be the full computer name of the Internal DNS Server, which is usually the RDP Data server.  In this example, the Default DNS Server is "RDP2003a.RDP2003.Local'.  
  3. Also verify that the internal address of the Default DNS Server is correct.
Warning:  It is critical to use an INTERNAL Windows 2003 server as the primary DNS server for the RDP data server, IRM server, and all workstations.  It is not possible to use an EXTERNAL DNS server for this purpose.
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 IP address.
  • Repeat the steps above for the Data Server, IRM server, and all workstations
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.
  • Repeat the steps above for the Data Server, IRM server, and all workstations

Activate Remote Desktop

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!)

  1. Click Start | Control  Panels | System.
  2. Select the "Remote Tab."
  3. Put a check in the checkbox for "Allow user to connect remotely to this computer."
  4. Select "OK."

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.

Windows 2003 Users and Groups

The next step is to create RDP required users and groups in Active Directory.

Create an RDP Group - Windows 2003

  1. Windows 2003 - Select Start | Administrative Tools | Active Directory Users and Groups.
  2. Expand the computer name in the left panel.
  3. In the right panel, right click users and select "new" and "Group."
  4. Enter the Group Name as "RDP", using the default Group Scope=Global and Group Type is "Security."

Adding Users to the Domain
and as a Member of the RDP Group

  1. In Active Directory Users and Computer, Highlight Users |Action | New | Users.
  2. Enter the user's first and last name, login name, password.
  3. RDP recommends selecting the "User cannot change password" and "Password never expires" options, Save.  The new user is now added to the domain.
  4. Right Click the User Account and Select Properties and Member.
  5. Add the user to be a member of the RDP group.

Create and Share the RDPNT Folder

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 
Administrator Groups
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").

Turn on sharing as follows:

  1. Use Windows Explorer, right click the RDPNT folder, and select Properties and then select the Sharing tab.
  2. Select "Share this folder" with a share name of "RDPNT".   The share name must be RDPNT for the system to function correctly.
  3. Click the "Permissions" button.
  4. Add the RDP group and the Administrators group with full control.
    Click Apply & OK in order to save these changes correctly.
  5. Note: When the group RDP or Administrators is first added, they do not have full control.  You must select the Full Control checkbox.
  6. Remove the "Everyone" group from the sharing permission list.
  7. When complete, the RDPNT folder should be shared, with full control permissions to the RDP and Administrators groups.

Install Pervasive.SQL Version 10
for Windows 2003 Server

Pervasive.SQL Version 10 is the database used by RDP, and must be purchased from RDP.   If you have not yet purchased Pervasive, please call RDP Sales at 970-845-1140.   For details on Pervasive.SQL click here.  The installation of Pervasive.SQL v10 process has four major steps, as follows:

  1. First the Pervasive.SQL V10 Engine is installed on the Windows 2003 data server.
  2. All Service Packs for the Pervasive SQL.Version v10 Engine must be installed on the data server.
  3. The Pervasive PVSW folder must be shared on the data server.
  4. The Pervasive.SQL v10 client software must be installed on all workstations.

Install Pervasive.SQL v10 Engine
on Windows 2003 Data Server

The first step is to install the Pervasive.SQL v10 Engine for Windows 2003 on the Windows 2003 RDP Data Server with the following steps: 

Logon as Domain Administrator From Console - No Terminal Services The installation of Pervasive.SQL v10 must be performed from the Windows 2003 RDP Data Server console.

  • Do not use a workstation to install Pervasive - you must use the Data Server.
  • Do not install Pervasive Remotely using Terminal Services, or any other remote connection product.  An installation of Pervasive.SQL v10 done with Terminal Services will appear to work, but will not function properly after installation.
  • It is critical to logon to the RDP Data Server as the domain administrator during installation
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 10.
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 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 open a ticket with RDP Support.   Select "Finish".  Pervasive should now be installed.
Check for Pervasive
Service Packs		 Click here to check for service packs. 

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.

Configure Pervasive.SQL 10 Cache Allocation Settings on Data Server

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:

  1. Sit in front of the RDP Data Server and logon as the administrator.  It is critical to make all Pervasive changes as administrator.
  2. Select Start | Programs | Pervasive.SQL | Pervasive.SQL 9 Control Center.
  3. In the left hand panel, expand engines.   An Icon with the name of the Data Server should appear.  Right Click this Icon | Properties.
  4. Select | Performance Tuning | Cache Allocation Size.   The setting should be approximately 20% of total Ram Memory on the Server, to a maximum of 800,000,000 bytes.
  5. Close the Pervasive Control Center.  If any changes were made, you will be prompted to save the changes.  Do so.
  6. If any changes were made and saved, reboot the data server so these changes take effect.
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.

Configure Communication Protocols

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. 

  1. Sit in front of the RDP Data  Server and logon as the administrator.  It is critical to make all Pervasive changes as administrator
  2. Select Start | Programs | Pervasive.SQL | Pervasive.SQL v10 | Control Center.
  3. In the left hand panel, expand engines.   An Icon with the name of the Data Server should appear.  Right Click this Icon | Properties.
  4. Select | Communication protocols.
  5. Under Supported Protocols only TCP/IP should be checked.  Uncheck all other proctocols.  
  6. Click Apply | OK
  7. If any changes were made and saved, reboot the data server so these changes take effect.

PVSW V9 only - Security and Sharing of the PVSW Folder for Client Installations

If installing PSQL V10 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:

  1. Sit in front of the RDP Data Server and logon as the administrator.  It is critical to make all security changes as administrator.
  2. Use Windows Explorer, right click the PVSW folder, and select Properties and then select the Sharing tab.
  3. Select "Share this folder" with a share name of "PVSW." Do not change the share name - use the default of PVSW.
  4. Select OK.  A small hand should appear under the C:\PVSW folder to indicate it is shared.

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 v10 client on a workstation.

Installing Pervasive.SQL v10 on Each Workstation Client

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.

Verify Pervasive.SQL v10 and Any Service Packs
are Installed on Data Server

Before installing any workstation, verify that the Pervasive.SQL v10 engine and all service packs have been installed on the data server.  Click here to check for service packs.

Verify Workstation Operating System is Windows XP Professional

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.

Reformat and Reinstall Operating System If Novell Client Present

The RDP system, and Pervasive.SQL v10, work best in a "pure Windows 2003" environment using only TCP/IP.  This is the "default" environment if there are no other servers present.  If you have never installed any Novell software on any workstations, you can move on to the next step.

Many customers used to have, or still have, an old Novell Server.  Many workstations that used to access the Novell Server will have the IPX/SPX protocol installed and the Netware client.  Any version of the Novell Client for Netware, or the Microsoft Client for Netware, will cause the installation to fail.  The installation will also fail if any version of Pervasive has been previously installed on a workstation that also had the Netware client.

It is very difficult, if not impossible, to completely remove IPX/SPX, the Netware client, and previous installations of Pervasive client from a workstation.  As a result, RDP suggests a complete re-format and re-install of the operating system on any workstation that previously had any version of the Novell Client or Pervasive installed.

Verify Network Connection on Each Machine

Verify that each workstation can communicate with the network correctly before installing Pervasive.SQL v10:

  1. Each workstation needs a unique TCP/IP address in the same subnet as the Data Server.  For example, if the Data Server has an IP Address of 192.168.43.2, then all workstation must have IP addresses in the range 192.168.43.xxx.
  2. The Subnet Mask for each workstation should be 255.255.255.0.
  3. The DNS server for each workstation should be the same as DNS server used by the Data Server.  When DNS is installed on the Data Server, use the IP address of the data server as the DNS server IP address for each workstation.  IE, normally DNS is running on the data server, and if the IP address of the Data Server is 192.168.43.2, then the DNS server for all workstations should be 192.168.43.2.
  4. Each workstation should be a member of the same domain as the RDP Data server.

Join the Windows 2003 Active Directory Domain

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:

  1. Right click my Computer, Left Click Properties.
  2. Click the "Computer Name" tab.
  3. Click the "change" button, and then select the "domain" radio button.  Make sure the domain name is the same as the domain on the data server.   NOTE:  In order for a workstation to join the domain you must disconnect any network drives first.  You will also need the password for the domain administrator.
  4. Reboot the workstations. Make sure to login to the DOMAIN after reboot by selecting the "options" tab from the login screen.

Login with Administrative Rights to the Local Machine  

When installing Pervasive.SQL V8 on a workstation it is essential to login as the Network Administrator, or as a user that has administrative rights to the local machine.  It is absolutely critical to have administrative rights to local machine when installing Pervasive.SQL Version 8, and when running RDP software.

Close All Programs and Turn Off Virus Protection 

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.

Complete Pervasive Client Installation on All Workstations


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:

  • My Network Panels
  • Entire Network
  • Microsoft Windows Network
  • Domain name (the name of your domain)
  • Server name (the name of your data server)
  • PVSW
  • Clients
  • Win
  • Setup.exe
Warning:  Do not use the Pervasive Installation CD's to install client software, as the CD may be outdated.  Always install the Pervasive Client software with the steps above.
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:

  • Select to install PSQL V10 Server for Windows (32 bit)
  • Select "Complete"  as the installation type and click "Next".
  • It will give you a default location where the PSQL files will be saved  DO NOT CHANGE THE FOLDER
  • Click "Install" to begin the Installation.
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.
  1. Enter the target machine which is the "DataServer".  Do not browse to the Data Server either enter the IP address or the "Server Name".
  2. Click Advanced Settings | Select Use Only These Protocols | Select only TCP/IP.  All other protocols should be unchecked.
  3.  Click OK.
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.

Configuring Windows XP Professional Workstations to Start RDP DOS and WIN

The workstations can now be configured to start RDP with the steps in the next section.

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:

  1. Start Windows Explorer (Right-click Start, Click Explore).
  2. Expand My Network Places.
  3. Expand Entire Network.
  4. Expand the name of the Domain.
  5. Expand the Data Server Name.
  6. Highlight the RDPNT folder and right-click this folder.  Note:  You must map the RDPNT folder, not the RDP folder.
  7. Select "Map Network Drive".
  8. Enter the Drive letter "F" (you may use any drive letter, but all RDP workstations must map the same drive letter to the RDPNT folder).
  9. Make sure to put a check in the box for "Reconnect at logon" and select OK.
  10. Close Windows Explorer.

Setting a Station Number  

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.

  1. Select | Start | Control Panel | System.
  2. Select the "Advanced" tab.
  3. Select "Environmental Variables" button.
  4. In the "System Variables" area (not the "User variables" area) click the “New” button.  Enter:
Where "xx" is a number from 1-99.  Remember, a different station number must be assigned to each Windows XP workstation.

Set the Screen Display to 1024 x 768

 

RDPWin requires a minimum screen display of 1024 x 768

  1. Click you Start button on the Desktop->Settings->Control Panel->Display->Settings

  2. Change default display to 1024 x 768

  3. Click Apply

Verify that Microsoft.NET Framework 2.0 is installed on the workstation

  1. Right click Start->Explore

  2. Navigate to the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

  3. If you do not see this folder, there are only folders for V1.0.3705 and v1.1.4322 then you need to install >NET framework 2.0

  4. If not installed run a Microsoft Update or you will find the Dotnetfx2.exe in the RDPWIN Setup folder

Creating a RDP Batch File - Windows XP

A batch file is used to start the RDP system, which can be created as follows:

  1. Select Start-Run and enter "Command" and press OK.
  2. When the command prompt appears, enter "F:" and press <enter> (assuming you mapped the "F" drive to RDP).
  3. Type CD \RDP and press <Enter>.
  4. Type EDIT RDP2000.BAT.  Enter the commands as follows:
  5. Save with File, Exit, Save.

Create a Desktop Shortcut to Start RDP DOS

A desktop shortcut should be put on each workstation that will access RDP, as follows:

  1. Use the following steps for creating an RDP shortcut on the Windows XP desktop.
  2. Right click anywhere on the desktop and select | New | Shortcut.
  3. Enter the Location as F:\RDP\RDP2000.BAT (assuming you mapped drive "F") and click Next.
  4. Enter the Name of the shortcut as RDP and select Finish.
  5. Right-click the new Icon on the Desktop and select "Properties".
  6. Select the "Change Icon" button. If you get a warning that the RDP2000.BAT file contains no Icons, select "OK" to continue.
  7. Enter the file name for the Icon as F:\RDP\RDP1.ICO (assuming you mapped drive "F") and click OK twice.  The RDP Icon with a Skier should appear.
  8. Right click the new Icon on the desktop and select "Rename". Make the name "RDP".
  9. Click the Icon to test.

Install the RDPWIN Client

 

  1. Right Click on Start->Select Explore

  2. Browse to the mapped Drive:\RDPNT\RDP\RDPWIN Setup

  3. Double-click on RDPWINClient2.XXX.exe

  4. Accept the defaults until the executable file gives you the option to click finish

 

  1. On the Desktop Double-click on the RDPWin Icon to test login.

  2. You will be prompted to enter the path of \\Data Server Name\RDPNT\RDP\RDP01

  3. For your first login attempt the Login Name is - User is the login,  no password

Fix Slow Printing for All Windows 2000 and XP Professional Workstations

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.

  1. On the Windows 2003 or Windows XP machine where the printer is connected, click Start -> Run and type REGEDIT.
  2. Expand HKEY_LOCAL_MACHINE.
  3. In the header, click View and make sure to check "Tree and data".
  4. In the left pane, expand System -> CurrentControlSet -> Control -> WOW .
  5. In the right pane, there should be a key "LPT_timeout".  Double click this key.
  6. A prompt for a string with a default of "15" (seconds) will appear. Change this to 1 and click OK.
  7. Close REGEDIT.
  8. Start RDP and test to see if the local printer now prints faster by using the F2-Print function from the RDP Menu.

Testing Data Server Performance

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.

Existing RDP Customers - Converting From Novell or Windows NT

Many existing RDP customers are converting from an older Novell or Windows NT server to a new Windows 2003 Server.  The following issues should be considered:

Remove Novell Client with Workstation Reformat

If your site has previously used Novell with RDP, we suggest reformatting all existing workstations to completely remove all traces of Novell and the Pervasive Database client for Novell.  While in theory it may be possible to "uninstall" the Novell client, in practice this does not work very well and many problems persists.  Workstations that have been used in the past with RDP on a Novell server should be completely re-formatted, and Windows 2003 or XP professional installed.  Do NOT purchase an "upgrade" from Windows 95/98/ME/2000 to Windows 2003/XP, as these upgrades tend to not work.

Copy RDP Data From Old Novell Server to New Server

The RDP folder and sub-folders on the old Novell or Windows NT server has to be copied to the new Windows 2003 server.  RDP suggests using a workstation for this purpose, and use Windows Explorer on that workstation to copy the RDP folder from the OLD server to the RDPNT folder on the Windows 2003 server.  In no case should you install Novell Client Software on the new Windows 2003 data server.

Converting Files to Pervasive.SQL

After copying RDP data files from an old Novell Server, or any old server you must convert the Pervasive data files format as follows:

  1. This process will take between 10 minutes  and 12 hours, depending on the amount of data in the system  and the speed of workstation and server.
  2. Exit all users from the RDP system.  They must remain out of the system while the files are converted.
  3. Start RDP on the fastest workstation.  From menu 99, choose option 994, "Rebuild an RDP Data File"
  4. Select option "C" - Rebuild all Critical Files, and enter "Y" to continue.
  5. When RDP994 finishes, all workstations can re-enter RDP.
Home RDPWin RDP-DOS IRM/IRM.Net Preprinted Forms
Version 2.xxx Upgrade to RDPWin Link to Marketing Site Support: 970-845-7108
Training Vendor Interfaces Troubleshooting Sales: 970-845-1140