Page 1 of 5. Rental Network Software Corp., Rental Management Software v9.0 (R90) Release Notes. Topics Covered:

Transcription

1 Rental Network Software Corp., Rental Management Software v9.0 (R90) Release Notes Topics Covered: 1. Supported Configurations 2. Terminal Server 3. MDAC 2.7 Compatibility 4. Installing the application for multiple users on one machine 5. Server Install 6. R90.ini File Settings 7. Date/Time Synchronization 8. Microsoft SQL 2000 Server Database 9. Optional (MSDE 2000) Microsoft Data Engine 10. Database Security 11. Microsoft Internet Explorer Microsoft Word 2000 and Outlook Launcher Setup 14. Required Backup Strategy 15. Uninstalling RNS R Supported Configurations a. Operating System. The R90 client installation is intended for a Microsoft Windows 2000 (SP4 or higher) or Windows XP (SP1 or Higher) computer. Optionally, it may be installed on a Microsoft Windows 98SE, 98ME or NT4 (requires SP6a) clients today, however proper operation cannot be guaranteed with R90. i. Note: Microsoft will officially End-Of-Life (EOL) Windows NT 3.5, Windows 95, and Windows 3.x at the end of Windows 98, Win98Second Edition (Win98SE), and NT 4.0, which are currently in the extended support phase, will enter a nonsupported phase after June 30, 2003 and will be EOL'd on June 30, b. Note: The RNS R90 should not be installed on computers with Microsoft SQL Server 2000 installed, nor should any other 3 rd party software package be installed on that machine. This practice permits the data server to be as dependable as possible. c. Internet Explorer. All clients listed above require Microsoft Internet Explorer (IE) 6.0 or higher installed with all current updates. d. Memory. Each client computer requires a minimum of 64mb installed, however it is recommended that 128mb to the (preferred) 256mb (or greater) be installed. e. Video Resolution. The application is optimized for a minimum resolution of 800x600, however 1024x768 is recommended. [Note that for proper 800x600 display with Windows XP Professional, the Auto-hide the task bar option should be enabled to prevent scroll bars within the application]. f. Processor. A Pentium or AMD class processor with a minimum rating of 500mhz is required. As a guideline, any processor of 750mhz or greater should provide a good foundation for the application. If your environment includes a Microsoft Terminal Server, the processor speed of the client computer is irrelevant, because the application is run from the Terminal Server. Page 1 of 5

2 g. Control Panel Regional Options Date (tab) the MM/DD/YY setting should be selected for the Short Date Format for proper operation. 2. Terminal Server a. Administrative Mode i. We recommended all Windows 2000/2003 Server installations include installing Terminal Services (TS) in remote administration mode, including data and web servers. This will allow management of these servers in your office, from your home or from our office. Since TS requires authentication and supports encryption, you can run it securely over the Internet. b. Application Installation on Terminal Server (TS) i. The RNS R90 application uses only one copy of the R90.ini file that is located in the application installation directory. This single file approach simplifies the management of paths for all users of the application but may provide a challenge for companies wishing to separate users report and merge output paths. This can be accomplished by creating sub-directories or folders under the default output paths. You can then apply user level permissions to these user paths if needed. ii. A Windows Security Group should be created in the domain for all users of the rental group that will access this application. That security group should then be assigned to the Power Users group on the Terminal Server. The use of the RNS Launcher is not used in TS installations. The shortcut placed in the Start Menu after the installation calls only the R90.exe rather than the calling the launcher with the R90.exe parameter. iv. Updating the application exe and dll s on TS is done via a batch file found on the installation CD, \Other\UpdateR90.bat. This file should be placed in the application installation directory. When an update to the application files is distributed by RNS, the files are placed in the TS s \\Server\Drive\Program Files\RNS\R90\Updates folder. With all users out of the application, the batch file (UpdateR90.bat) is run to unregister the dll s, copy the new files and reregister the files. All TS users may then resume use of the program. v. It is recommended to use the Windows XP, RDP Client for all clients connecting to a Terminal Server. This client is optimized further than the standard TS client software. It is a standard feature of Windows XP Pro and can be found in the Start Programs Accessories Communications Remote Desktop Connection. It can be downloaded free of charge from Microsoft s Windows XP vi. download site for a variety of Microsoft clients. It is important that all TS users choose Logoff when ending a TS Session. This method ends all running applications and ends the session and is the proper way to terminate the client connection. Typically, the Shutdown and Run menu items, and other administrative menus are not available to normal TS users. 3. MDAC 2.7 Compatibility a. The R90 client application installs the Microsoft Data Access Components (MDAC) 2.7. The MDAC 2.7 SP1 redistributable installer installs the same Data Access core components as Microsoft Windows XP SP1. This redistributable setup is supported on Windows 98, Windows ME, Windows NT 4.0 and Windows Due to issues with clustering, this release is currently NOT supported on SQL 7.0 Clustered Servers or SQL 6.5 Clustered Servers. 4. Installation the application for multiple users on one machine a. During the Setup.exe operation, a dialog will provide a default of true for Anyone who uses this computer (All Users). You may change this to Only for me (current user name), or you may customize the install with the following instructions: To install this application on any Windows 2000/XP computer that requires multiple users to access the application, you MUST be logged in with administrative privileges or as the machine 'Administrator', our testing was preformed with all users as members of the 'Power Users' group (or you may setup a custom security group for this application that allows the users access to the Windows system files). 5. Server Install a. The installation CD contains a directory Server Files. Our recommendation is to copy these files to a central server location, typically on a second volume of the database or SQL Server computer. The recommended default path to create and paste the folders and files would then be: D:\RNS\R90\. i. After the set of directories and files are pasted into this path, while they are still highlighted, right-click and choose Properties. On the dialog, uncheck the Read-Only option. A small dialog appears, choose the option that states: Apply changes to the selected items, subfolders and files. Page 2 of 5

3 ii. Now click OK to close all dialog boxes. In D:\RNS\R90\ReportTemplates, unzip the self-extracting file ReportTemplates.exe in this same folder. 6. R90.ini File Settings a. After running the installation, only minor manual changes are required to the R90.ini; i. Section [PREFERENCES] 1. Edit the parameter; Client=Outlook (default) if you want to use Outlook Express, edit this parameter to read; Client=Outlook Express. ii. Section [SERVERPATHS] 1. Edit each of the parameters to point to the UNC network location where these shared folders exist. By default, the ReportsOutputPath and MailmergeOutputPath are mapped to the users local install path giving them private storage. You may however, map these to a shared location on the data server. With Terminal Server installations by default all users will pointed to a shared location but may be mapped to a private location. A suggestion to make private storage locations would be to add a UserName folder in the output path (e.g)..\reportsoutputpath\bob. 2. Edit the end of the UnitImagesPath to change the..\unitimages.companydbname where CompanyDBName is an abbreviation for your company name. For Example,..\UnitImages.VIP 3. Edit the end of the WebSiteFiles to change the..\websitefiles.companydbname where CompanyDBName is an abbreviation for your company name. For Example,..\WebSiteFiles.VIP Section [SQLOLEDB] 1. Edit the parameter: DataSource=Server1 - Where you change the name of Server1 to the actual name of your MS SQL Server Computer. 2. Edit the parameter: InitialCatalog=R901_ Where you edit the name of RNS_R90 the actual name of your MS SQL Server database supplied by RNS. 7. Date/Time Synchronization a. It is imperative that all workstations on the network be Date/Time Synchronized. Typically, a Microsoft Windows 2000 Server configured as a Domain Controller (DC) will provide this ability. However, if there is no DC on the network this feature must be configured by your hardware support personnel. b. Time/Date stamps are written on every record during Add, Edits or Deletes. If the workstations are not Date/Time synchronized, records may be missed in some program features updates. 8. Microsoft SQL 2000 Server Database a. The R90 client application requires Microsoft SQL 2000 Server (SP2 or higher) databases which are supplied by RNS at the time of installation, however the engine or software product Microsoft SQL Server 2000 (or optionally MSDE 2000) are not supplied by RNS and are the customers responsibility to purchase, install, backup and support. b. The database required by the application is; i. RNS_R90 is the Initial Catalog name or the main DB for the application. In some cases it may named RNS_R90_xx where the xx is replaced with an abbreviation to represent the name of your company. c. RNS will provide an import file for the default SQL Server Users at installation. See Database Security below. d. The default settings for the database Options include; i. Recovery Model: simple ii. Settings: Auto Shrink = True Note that these settings permit restores from previous backups and manageable DB Lb log files. DB Log file recovery options are not supported by RNS personal, however some installations may desire this method of file recovery. The person responsible for your Microsoft SQL Server 2000 DB administration should be consulted. e. Typical installation combinations include; i. R90 Client(s) on a LAN connected to a Microsoft SQL 2000 Server or MSDE 2000 Server. ii. R90 Client(s) on a LAN or WAN connected to a Microsoft Windows 2000 Terminal Server. In this case, normally it is recommended that there be an additional separate Microsoft Windows 2000 Server running Microsoft SQL Server Note that With Terminal Server environments, a document may Page 3 of 5

4 be obtained from the RNS Support team pertaining to installation and operation Terminal Server for R90. f. In addition to MS SQL Server 2000 software, separate client CAL s (computer access licenses) must be purchased for connection to a Microsoft Windows 2000 server, Windows Terminal Server and SQL Server g. Periodically, RNS support personnel may require access to the SQL Enterprise Manager and RNS databases. The most efficient method of access is via the Windows 2000 Terminal Server Administrative Mode. Your hardware or software support person will be able to create this access with an account for RNS. Without this access, RNS may not be able to perform needed maintenance. 9. Optional (MSDE 2000) Microsoft Data Engine a. In a limited number of installations, the MSDE 2000 may suffice as the database server software. This provides a cost-effective solution as well as a 100% scaleable solution for the future because the databases may be migrated from MSDE 2000 to Microsoft SQL Server 2000 without modification. b. Microsoft has stated that while there are no user limits, MSDE 2000 is tuned for five clients or less, and that performance degrades beyond that number of connections. Because connections to the data engine produce very little overhead, the RNS general guideline or interpretation of this statement recommends no more than ten (10) connected users producing five concurrent active data connections. c. Because MSDE 2000 can be installed on any network server, a number of configurations are possible. Please discuss these options further with your RNS sales or support representative. d. MSDE 2000 supports databases up to 2 gigabytes (GB) in size. There is no provided interface to the data, however Microsoft Access 2000 (or higher) can create read-only views and query s of the data. MSDE 2000 also includes Osql.exe, a utility you can use to enter Transact-SQL statements, system procedures, and script files. Note that there is no RNS Support for use of these tools. e. Use of MSDE 2000 requires attention to backup procedures that must be addressed prior to use of the application. f. For further information, see Database Security a. RNS will provide a login and password for read-only access to the data. Read-write access is prohibited and will void your warranty and support of the product. b. If needed, you may purchase a tool like Microsoft Access 2000 (or greater) to provide a graphic user interface (UI) to the data. Typically, (read-only) views, query s and reports can created from the data. These however are advanced operations for experienced persons. c. RNS does not supply Microsoft Access 2000 nor is the use of these tools included in the RNS Annual Support plans. 11. Microsoft Internet Explorer 6.0 a. Microsoft IE 6 (or higher) Is required at the client for a variety of web or browser displays, including Unit Virtual Tours. 12. Microsoft Word 2000/XP and Outlook 2000/XP a. Microsoft Word 2000/XP is required to perform document merging between R90 and Microsoft Word 2000/XP. b. Microsoft Outlook 2000/XP. Either Microsoft Outlook or Outlook Express may be used as an client with the R90 Application. The choice is made in the R90.ini file located in the application installation directory. c. Note that while you may run the R90 application by itself on a LAN or in a Terminal Server session, to obtain full use of the application features, Microsoft Word 2000/XP and Outlook (Express) 2000/XP are also required to run in the client session. d. Separate client CAL s (computer access licenses) must be purchased for each connection to Microsoft Word 2000/XP and Microsoft Outlook 2000/XP. e. Optionally, one installation of Microsoft Access 2000 or greater may be of benefit. Please see the topic Database Security in this document. Page 4 of 5

5 13. Launcher Setup a. The R90 Launcher is a client utility that checks and updates the client program files at startup. While the program may be run by invoking R90.exe, when the Launcher is used, the LaunchR90.exe is run, which checks the client versions, and updates them if needed, then calls the (current) R90.exe application. b. The Launcher depends on the R90.ini file SERVERPATHS to work correctly. c. To configure the client to use the Launcher, edit the application shortcut(s) Target to read; [TBD Contact support@rental-network.com] 14. Required Backup Strategy a. You the customer are responsible for performing backups on the (R90) databases, templates and other files that are created or modified by you or anyone who uses or comes in contact with this application. b. At a minimum, daily backups of all files are required. It is recommended that these daily backups be stored for a period of at least two weeks before being overwritten. c. Backup hardware, software and media are not supplied by RNS. d. It is strongly suggested that after a backup plan and equipment have been implemented - a restore is performed to confirm that the correct files are included and that the operators are familiar with the procedures. e. RNS may require a copy of your current data to resolve a support issue. Because MS SQL Server databases with logs can easily exceed 1gb, conventional backup methods (floppy disk, zip drives and CD-RW media may not be sufficient to make complete backups. Because of the variety of tape backup formats, RNS will not accept this media format. RNS recommends the use of a CD-R or DVD-RW drive as an alternative backup method for storing data and transport for RNS review (if required). 15. Uninstalling RNS R90 a. The proper method of uninstalling the client application is by using the Control Panel, Add/Remove Programs, select the RNS Rental Management Software v9.0 and click Uninstall. b. All files, directories, shortcuts and most system components but not OS components are removed. However, if you have added files or directories manually, they will remain with the directory trees and must be removed manually after the uninstall has been completed. c. Application Registry settings are not removed automatically during the uninstall, but can be removed by navigating to HKEY_CURRENT_USER\Software\VB and VBA Program Settings\R90. Select the R90 key and delete the key, to delete the key and sub keys. RNS Support can be contacted at support@rental-network.com. Last updated 8/7/2003 Reference: R90-13F Copyright Rental Network Software Corp., 2003 Page 5 of 5