Home	RDP Sales	Contact Us	Training
RDP Support		Open a Web Support Ticket
RDPWin Knowledge Base	RDP-DOS Knowledge Base	IRM and IRM.Net Knowledge Base	Crystal Knowledge Base

Index
Added 7/03/08 - SS/KW
Article ID#: KWin0071

Data Server Replacement

Follow the outline below when replacing the RDP Data Server to ensure a clean and accurate data transfer process.

When an RDP Support representative is needed to assist, please contact RDP Support to schedule the transfer of the new server.

RDP recommends that you configure your new server, copy the RDPNT folder over, and test to ensure everything is working correctly. Then schedule a "go live" date to bring the RDP data over.  This requires one to two hours of down-time for all RDP users.

Data Server Transfer Steps

1. Install 2003 Server as per the instructions in the following link to RDP support documentation.

2. Ensure that Active Directory setup is complete on the new server or if it is being hosted on another computer ensure the new server is part of the Active Directory Domain.

3. Ensure the following information has been reviewed and confirmed as working. This includes confirmation that the new server is part of the Domain and all users of RDP have full control to the RDPNT folder.
   

   • Installation of Active Directory and Security
   • Join a Pre-Existing Windows 2000/2003 Domain
   • Create a New Windows 2000/2003 Domain and Install DNS
   • Windows 2003 - Create Domain - Install DNS - Install DHCP
   • Create an RDP Group - Windows 2000 and 2003
   • Adding Users to the Domain and as a Member of the RDP Group (Windows 2000 and 2003)

4. All users in Active Directory using RDP should be part of the RDP User Group.  The group should have sharing rights and full control of the RDPNT folder on the New RDP data server.
   

   • Create an RDP Group - Windows 2000 and 2003
   • Adding Users to the Domain and as a Member of the RDP Group (Windows 2000 and 2003)

5. Install Pervasive on the server and ensure all RDP Computers including Interfaces and IRM are running on the same Pervasive version as the server.
   

   • PSQL Version 10 Installation Documentation
   •  PVSW Version 9 Installation Documentation
   •  Run the Pervasive System Analyzer tests on all machines to ensure Pervasive is connecting to the New Data Server.

6. Ensure all users are logged out of the RDP system on the old server.

7. Disconnect mapped RDPNT drives on all user workstations that are connected to the old data server.

8. Copy the entire RDPNT folder (including subfolders) over to the new server (place in the root C/D/E drive).  The folder should maintain the same naming structure (i.e., RDPNT).

9. Rename the RDPNT folder on the old server with an old name such as OLDRDPNT to ensure that no active users can reconnect to the old RDP data files.

10. Reconnect all mapped drives to the new server (using the same file path letter as the old data server (RDP recommends F or R drives). This will, in most cases, allow for RDP desktop shortcuts to be re-used.

11. On all Workstations using RDPWin, navigate to C:\Program Files\ResortDataProcessing\RDPWin and open the RDPWinPath.txt file. Ensure that the file path is mapped to your new data server: (i.e., \\DATAservername\RDPNT\RDP\RDP01). Save and Close.

12. Test all workstations by logging into RDP-DOS and RDPWin. Call RDPSupport when errors are received.
    The RDPWin Login screen should show the New Data server name in the server field (example below).
    

IRM Bridge Interface 

1. Log onto the IRM bridge machine.
2. Navigate to the C:\Inetpub\wwwroot\IRM\IRMpath.txt file. Ensure this file has the correct UNC path name to the new data server RDPNT folder.
   
3. Run the IRMTools.htm program to ensure all tests pass.

PBAdmin Interface

On the credit card bridge machine (the machine that has your PBAdmin tools such as "Start CC Engine" and "Stop CC Engine" icons):

If PBAdmin is less than version 6.0, follow these three steps.  If not, continue to Version 6.0 notes.

1. The Start CC and Stop CC engine shortcuts may need to be recreated.

2. Map the RDPNT drive on the Bridge machine to the new server. Use the same drive as the previous RDP data server whenever possible.

3. The Loadpb.bat and unloadpb.bat shortcuts should be recreated. Although the mapped drive may be the same, these files often do not load correctly unless the loadpb.bat and unloadpb.bat shortcuts are recreated and copied to the desktop.
   

If PBAdmin is Version 6.0, the following should be loaded on the credit card bridge machine using the local C drive:

1. From C:\SDC\PBASE type EDIT STARTPB.BAT or use Notepad to open C:\SDC\PBASE\STARTPB.BAT.
   

2. If RDP is on a different drive than F, change the drive letter on the three lines (shown above) that have f:\rdp\pb\pbfiles in them to the correct drive letter and save changes.

3. Run STARTPB.BAT, and make sure two windows are running minimized on the task bar. One is named "Protobase Comm Director," which is running PBDIRECT; the other is named "Protobase Filserver," which is running PBFSRV.

4. Run STOPPB.BAT, and verify both windows close.

5. If the Start CC engine and Stop CC engine utilities do not run correctly, right-click the Start/Stop CC engine shortcut, select Properties, and verify the path to the PB files is correct.
   

Call Accounting
POS and Other RDP Interfaces

1. Disconnect the mapped drive to the old data server RDPNT folder.

2. Re-map the same drive to the new data server – RDPNT folder.

3. Ensure the RDP-DOS Call Accounting, POS or other Interface icons on the desktop have the correct mapped drive to the new RDP Data server.

4. Log into the Interface using the correct interface login name and password to ensure a connection to the new data server.
   
   

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