Initial Installation and Configuration

Windows Terminal Server with EbixONE Windows 2000 and Windows 2003 Server Initial Installation and Configuration IMPORTANT: The use of this document is intended to be a quick reference for a certified or trained network administrator or engineer. It is not a step by step selfhelp guide for installing or configuring the Windows Terminal Server or Terminal Client. DISCLAIMER: As always, Ebix makes every effort to verify that the information published in this document is accurate. Ebix reserves the right to modify or change the contents of this guide at any time, without any obligation to notify any person or entity of such changes. 9/26/2007 1 of 21

Table of Contents EbixONE System Requirements for Terminal Server... 3 EbixONE Setup Overview... 4 Install the Server OS and Configure the File Server... 5 Configure the File Server for EbixONE... 5 Add Terminal Server Role... 5 Option 1 Configure Your Server Wizard... 5 Option 2 Add/Remove Programs through the Control Panel... 5 Share the Terminal Server Client Setup Folder... 6 Install Applications on Server... 6 Microsoft Office 2000 or Office 2003.... 6 Install Pervasive.SQL V8 SP2... 6 Configure Pervasive.SQL V8 Server Settings... 7 Adding Users... 8 Setting Up EbixONE on Terminal Server... 9 Create EBIX folder... 9 Set Permissions for Group... 9 Create a Mapped Drive to Shared EBIXDATA Folder... 10 Install EbixONE Client on Terminal Server... 11 Creating ODBC DSN (Data Source Name)... 13 Install EbixONE Spell Checker... 17 Setting Up Terminal Client Workstations... 17 Remote Desktop Connection Wizard... 17 Connect to Remote Desktop Session... 17 Configure User Settings for EbixONE... 20 Copy ARIAL.TTF Font for PDF Creation... 21 Finalize Setup and Test Connection... 21 9/26/2007 2 of 21

EbixONE System Requirements for Terminal Server Microprocessor: Server Type: Hard Disk / Partitions: RAM: Network Adapter: Screen resolution OS/Database: Pentium 1 GHz or higher. While multiple microprocessors are not required, Terminal Services can take advantage of multiple microprocessors for increased performance. It is recommended that you install Terminal Services on a member server and not on a domain controller. The Terminal Server, EbixONE File Server, and Clients should all be on the same domain. Small Business Server installed on a domain controller is not supported. If the server is to be used as both the File Server and Terminal Server, then one or more hard disks with a minimum of three NTFS partitions should be setup. One for the Terminal Server OS, one for EbixONE and related file applications, and the third partition is for the page (swapped) file. The size of the partition for the virtual memory paging file is relative to amount of installed RAM. In any event, follow the recommended default page file size. RAM plays an very important role in performance using Terminal Services. The minimum recommendation is 512MB plus an additional 8MB to 10 MB for each user that will be connected. Additional 4 to 10 MB RAM for each user that runs third party applications such as Microsoft Word for word merge. Ebix recommends as much RAM as the computer can handle for best performance. See the Microsoft Hardware Compatibility list (HCL) for supported NICs. Having a high-performance network adapter is recommended especially if users access EbixONE on a separate file server. While Windows Server takes advantage of multiple adapters, Pervasive is known to have problems with some multiple adapter configurations. Because of this, ebix recommends using only one network adapter on the terminal server. 800x600 resolution with 256 colors. Windows 2003 Server SP1 on Pervasive.SQL V8 SP2 (version 8.6) or higher. Pervasive.SQL 2000i SP4 is supported by Ebix on Windows 2000 Terminal Server. Fax software - WinFax Pro is not supported on Terminal Server by Ebix. 9/26/2007 3 of 21

EbixONE Setup Overview The following overview assumes you are familiar with Terminal Services and have the knowledge to setup Terminal Services on the server and client workstations. EbixSupport provides Network support related to the installation and configuration of Pervasive and the EbixONE client. Network support does not include installing Terminal Services on the server or client workstations. The information provided covers the requirements of EbixONE and our recommended optimum configuration. Ebix does not support installation of Terminal Services on a server with existing applications already installed. The following documentation covers installing Terminal Server on the same hardware as the File Server. Installing Terminal Server on a second server is possible but performance would decrease and some of the instructions below are slightly different. Please contact EbixSupport before installing Terminal Server on a separate server so that we may provide any agency specific instructions. Install the Server OS (Windows 2000 or Windows 2003 Server) Configure the File Server and create shared Ebixdata folder. Add Terminal Server role Share Terminal Server Client Setup Folder Install programs to server Microsoft Office and Pervasive.SQL Server Add Group and select Users to access EbixONE through Terminal Server Setup sharing, Users, and mapped drive for EbixONE Setup EbixONE on Terminal Server and Install Install Terminal Services client (Remote Desktop) on each workstation Setup EbixONE on Terminal Clients copy.ini files and setup mapped drives 9/26/2007 4 of 21

Install the Server OS and Configure the File Server Install Windows 2000 Server or Windows 2003 Server. Equipment must meet minimum hardware requirements for EbixONE and Terminal Server. Installing the operating system is your responsibility. Install and configure all software on the server as an Administrator and make sure any TSR software such as Anti-virus or faxing is disabled or turned off. Configure the File Server for EbixONE Add a File Server Role to the server. For Windows 2003, you can use the Configure Your Server Wizard. 1. Open wizard. All Programs > Administrative Tools > Configure Your Server Wizard. 2. Select File server role and continue the wizard. 3. Leave Indexing Service turned on when prompted. 4. Create and share a folder called EBIXDATA in which CDPROD will reside. This can be done as part of the Share a Folder Wizard that is run during the File Server configuration. 5. Offline setting for the folder EBIXDATA needs to be changed so that files or programs from the share will not be available offline. 6. Change Permissions so that Administrators have full access; other users have read write access. 7. Once wizard finishes, place the entire CDPROD folder into the newly shared EBIXDATA folder. Add Terminal Server Role You can install the Terminal Server Role by using the Windows 2003 Server Configure Your Server Wizard or through the Add/Remove Programs under Control Panel. Option 1 Configure Your Server Wizard 1. Open wizard. All Programs > Administrative Tools > Configure Your Server Wizard. 2. Select Terminal server role and finish the wizard. Option 2 Add/Remove Programs through the Control Panel 1. Browse to Start > Control Panel > Add/Remove Programs > Add or Remove Windows Componets. 2. Select Terminal Server and click Next. 3. Select Full Security and finish the wizard. 9/26/2007 5 of 21

Share the Terminal Server Client Setup Folder The folder needs to be shared so that workstations can install the client software later. 1. Browse to the systemroot\system32\clients\tsclient\win32 folder, where systemroot is the folder containing your Windows installation (Example C:\windows). 2. Right-click the \win32 folder 3. Click Sharing and security and on the Sharing tab check Share this folder. 4. Click OK Install Applications on Server All applications that are to be used by terminal server clients must be installed through the Add or Remove Programs wizard. This insures that applications are installed while the machine is running Terminal Services in Application Server Mode. On Windows 2000, under the Add/Remove Programs Change User Option page, verify that All users begin with common application settings is selected. Microsoft Office 2000 or Office 2003. Word, Excel, and Outlook are used with merge features of EbixONE and it must be installed on the terminal server. Ebix recommends checking for any updates or downloads at the end of the installation. There are no special requirements by Ebix for installing Microsoft Office. Follow Microsoft s recommendations and instructions on installation. Install Pervasive.SQL V8 SP2 Also know as version 8.6, Pervasive.SQL V8 SP2 has been certified with Windows 2003 Terminal Server. Review Chapter 4 of the Getting Started with Pervasive.SQL V8 Server Edition guide for instructions on installing Pervasive.SQL V8. Pervasive SQL V8 must be installed at the server itself. It cannot be installed from a remote client machine. We recommend installing to the default system drive, usually C: If loading Terminal Services on a separate server, not the server with EbixONE on it, you will have to load the Pervasive Client instead of the Pervasive Server. Contact EbixSupport if you are planning to use separate servers. 1. Through the Add or Remove Programs, install Pervasive Server from the CD-ROM. 2. Place the Pervasive SQL V8 CD in the CD-ROM at the server. 3. Follow the prompts until prompted for your license key. The license is provided along with your software in the Pervasive.SQL V8 package. Enter the license key and keep this key in a safe location. 9/26/2007 6 of 21

4. Highlight Complete, then Next, then click the Install button to complete the installation. 5. Continue with the Transactional and Relational Tests when prompted. Review the Getting Started with Pervasive.SQL V8 Chapter 4 for more details on using tests. Report any failed tests to EbixSupport. If Pervasive (\PVSW) was installed to a hard drive other than the system drive(usually C:) the Pervasive tests will fail. Skip the Pervasive tests and test the connection to EbixONE using ODBS DSN Test later. Configure Pervasive.SQL V8 Server Settings 1. Open the Pervasive.SQL Control Center - Click Start > Programs > Pervasive > Pervasive Control Center. 2. Double click the Pervasive.SQL V8 Engines then select your Server. If your server is not listed, you will need to Register New Engine. Click Action, Register New Engine. Browse to your server and click OK. 3. Expand the Configuration folder. 4. Check Compatibility folder and double-click Create File Version. 5. Change File Version to 7.x and click OK. 6. From the Edit menu at the top of the Pervasive.SQL Control Center, select Apply to save your changes. Click Yes to the Apply confirmation. 7. Click the folder Access under Configuration > Server 8. Double-click Allow Cache Engine Connections to open selection box. 9. Change Allow Cache Engine to Off. Click OK. 9/26/2007 7 of 21

10. From the Edit menu at the top of the Pervasive.SQL Control Center, select Apply to save your changes. Click Yes to the Apply confirmation. 11. Exit the Pervasive Control Center and reboot the server. Adding Users Ebix recommends creating a Group for managing permissions for users that will use Terminal Services. 1. Create a Group - If you are using a Domain, use the Active Directory Users and Computers screen to setup the New Group. We recommend you give it a unique name that identifies it as the group that uses Terminal Services; example TSagencyname (where agencyname is your agency name). 2. Add Users to the Group - Once the Group is created, open the Group Properties and select Users to add to the group. All users that will be using Terminal Services should be added to this group. 3. Add Group to the Local Terminal Server s Remote Desktop Users - This can be done from the Computer Management screen. 3.1. Right-click on My Computer and left-click on Manage to open the Computer Management screen. 3.2. Expand System Tools > Local Users and Groups. 3.3. Right-click on the Remote Desktop Users in the right pane. 3.4. Select Add to Group 3.5. Click the Add button and enter your Terminal Services group and click OK. 3.6. Click OK again to exit to the Remote Desktop Users Properties window. 3.7. Close the Computer Management window. This completes assigning users that will use the Terminal Services. If any additional users need to use Terminal Services, they can be added to the Group and would have all the permissions as the rest of the group. 9/26/2007 8 of 21

Setting Up EbixONE on Terminal Server The server settings for the folder EBIXDATA needs to be modified to add sharing and security permissions for the new TSagencyname group, a mapped drive needs to be setup to point to the shared folder, and the EbixONE Client needs to be installed in Terminal Services mode. Create EBIX folder The folder EBIX is different from the EBIXDATA folder. It needs to be created to handle temporary files used with WordMerge, Excel Merge, and Memos. 1. On the server, open My Computer and browse to the local C: 2. Add new folder called EBIX through the File > New > Folder menu. Set Permissions for Group 1. Browse to the shared folder which contains CDPROD (Example: C:\EBIXDATA which is the default shared folder name recommended by Ebix, Inc.) 2. Right-click the folder and select Sharing and Security. 3. Select the Sharing Tab and make sure the Share this folder radio-button is selected. 4. Click the Permissions button to open the Permissions for Ebix. 5. Click the Add button and add the TSagencyname group to the share. Click OK. 6. Select the Security tab. 9/26/2007 9 of 21

7. Click the ADD button and enter the object name to select Group. The object name is the TSagencyname of your group. 8. Click OK. The group should now appear in the Security tab list. 9. Make sure the TSagencyname group has Full Control permissions checked. 10. Close the EBIXDATA Properties window. This completes the permissions setup on the EBIXDATA folder. 11. Repeat steps 2 to 10 on the folder C:\EBIX Create a Mapped Drive to Shared EBIXDATA Folder EbixONE uses drive mapping as a method of identification and communication. The drive mapping must be the same on all clients, whether they access from the Terminal Server or are directly connected on a client/server network. The default and recommended drive letter is F: If you are adding Terminal Services to an existing network, you can check a currently connected EbixONE client PC to see what drive letter is being used or, using Notepad, view the file global.ini under the CDPROD directory to see which drive letter is configured. 1. From the sever choose My Computer select Tools > Map Network Drive. 2. Choose drive letter (Example: F: ) 3. Browse to data folder (default EBIXDATA) 4. Make sure Reconnect at login check box is marked. 5. Click Finish. 9/26/2007 10 of 21

Install EbixONE Client on Terminal Server The EbixONE client must be installed through the Windows Add/Remove Programs found under the Windows Control Panel when installing on a terminal server. 1. Open Control Panel and click Add or Remove Programs. Visit www.microsoft.com or use your local PC Help for instructions on using the Add or Remove Program. If using Windows 2000 Terminal Sever, on the Add/Remove Programs Change User Option page, verify that All users begin with common application settings is selected. 2. Click Add Programs 3. Click load from CD or Floppy. No file will be found and a Browse button will appear. 4. Click on Browse and point to the location of your system server installation and run SETUP.EXE from the CDPROD\SYSFILES directory. Example: C:\EBIXDATA\CDPROD\SYSFILES\SETUP Note :If this fails, check if you have included SYSFILES 5. Click on OK. Then the following screen appears. Verify that no other programs are running then press Next. 6. Click the User Workstation button to install with minimum shortcut menu items for CSRs. Administrative menus can be installed on individual terminal clients later. 9/26/2007 11 of 21

7. Click Next. This routine will create the EbixONE Program Folder. 8. Click Next to be begin copying client files. 9. Click OK to the 8 dialog screens DLLRegisterServer referencing OCX components. Press OK on all of them. You may receive the following error message if you have a later comdlg32.ocx already installed. Document that you received the error and Press OK to continue. There is no need to report this error 10. If prompted to place an icon on your desktop, we recommend selecting Yes. 11. Press Yes to setup your DSN now. Continue to the next section ODBC DSN (Data Source Name) for EbixONE. 9/26/2007 12 of 21

Creating ODBC DSN (Data Source Name) You will need to configure a new ODBC Data Source Name for Pervasive.SQL. Once done on the Terminal Server it will be used for clients that connect to EbixONE. 1. Open your ODBC Data Source Administrator if not already started. (To open from Windows server, Click Start > Programs > Pervasive.SQL V8> Other Utilities > ODBC Administrator) 2. Click on the second tab, System DSN. Then click on Add 3. Scroll down to select Pervasive ODBC Client Interface. Click Finish 9/26/2007 13 of 21

4. Enter a Data Source Name under the client section. We recommend the name ebix client. Enter your Server IP address. Select Try TCPIP only for Transport Hint for Window Servers. 5. Click Create button to setup the Data Source Name in the server section. You only need to create the Data Source Name for the server once. You do not need to create it again when doing the remaining workstations. If you have previously created the ebix server Data Source Name or are using a separate File Server with EbixONE already installed, skip to Step 12. 6. Enter the User name and Password. You must use either administrator or a user ID that has administrator privilege to the server. Click OK 9/26/2007 14 of 21

7. Enter the Data Source Name (for the server). We recommend ebix server. 8. Click Create. The Create Database window displays. 9. Enter a Database Name. We recommend using ebixdata. 10. Browse the Dictionary Location to your ebix server data directory. (Example: F:\CDPROD\DATA). Click OK. 11. Click OK to close Create Database window. 9/26/2007 15 of 21

12. Click OK after reviewing Modify Engine DSN. 13. Click Get DSN List button and select Data Source Name for your server. You may have to click the down arrow button to view your DSN server list. 14.. Click Test button to test ODBC connection. If test fails, contact EbixONE Support. 15. Once test completes successfully, click OK to close the Pervasive ODBC Client DSN Setup window. 16. Click Finish at EbixONE Setup screen to complete the EbixONE Client installation. 9/26/2007 16 of 21

Install EbixONE Spell Checker 1. Click Add Programs from within Add and Remove Programs in the Control Panel. 2. Click load from CD or Floppy. No file will be found and a Browse button will appear. 3. Click on Browse and point to the location of your system server installation and run VSSPELL1.EXE from the CDPROD\SYSFILES directory. Example: C:\EBIXDATA\CDPROD\SYSFILES\VSSPELL1.EXE Note :If this fails, check if you have included SYSFILES 4. Click on OK.. Install spell check program following on screen commands. 5. Click Next and Finish then exit the Add or Remove Programs screen when done. Setting Up Terminal Client Workstations Pervasive and EbixONE must be installed and configured on the file server before connecting to the Terminal Services Client. Windows 2003 Server refers to Terminal Services as Remote Desktop. Loading Terminal Services replaces the Remote Desktop components on Windows XP. The following instructions must be done on each user workstation that plans to access the Terminal Server. Remote Desktop Connection Wizard Run the Terminal Client Setup which opens the Remote Desktop Connection Wizard. Review Microsoft Help or visit www.microsoft.com for more details. 1. Browse to the previously shared win32 folder on the Terminal Server 2. Click Setup.exe to begin Remote Desktop Connection Wizard 3. Complete all screens and click Finish to close the Wizard. Connect to Remote Desktop Session Use the Remote Desktop Connection screen to open a terminal client session. Later you can create a shortcut on your desktop for easier access. 9/26/2007 17 of 21

1. Open the Remote Desktop Connection. Programs > Accessories > Communication > Remote Desktop. 2. Enter Terminal Server computer name. 3. Press Connect to begin session. 9/26/2007 18 of 21

4. Login with your user name, password, and select your DOMAIN from the drop down list. Once logon completes, the initial Remote Desktop screen appears blank. The user can now configure shortcuts, background, or other desktop settings. 9/26/2007 19 of 21

Configure User Settings for EbixONE It is important that the following steps be done for each user that connects to the terminal server. Create a Mapped Drive for each User Terminal Client 1. From the Start menu, open My Computer and from the toolbar menu select Tools > Map Network Drive. 2. Choose drive letter (Example: F: ). The client network drive needs to be the same one created on the server. 3. Browse to shared folder (default EBIXDATA) 4. Make sure Reconnect at login check box is marked. 5. Click Finish. Copy EbixONE Shortcut to Desktop 1. Copy the EbixONE Shortcut from the Start > Programs > EbixONE folder to the desktop. Setup Version of Office to use with EbixONE WordMerge 1. Open the program Notepad and browse to the C:\Windows folder and open WINWORD6.INI 2. Change the VERSION and OS to match your version of Windows and Office. Windows XP and Office XP c:\windows\winword6.ini would have VERSION=10 and OS=XP Windows XP and Office 2000 c:\windows\winword6.ini would have VERSION=9 and OS=XP Windows 2000 and Office 2000 c:\winnt\winword6.ini would have VERSION=9 and OS=2000 Windows 2000 and Office XP c:\winnt\winword6.ini would have VERSION=10 and OS=2000 Example: [Microsoft Word] PROGRAMDIR=C:\PROGRA~1\MICROS~1\OFFICE11\ VERSION=10 OS=XP Copy the BTI.INI, DELPHI.INI, and WINWORD6.INI to local users folder 1. Open My Computer and browse to the C:\Windows folder 2. Copy the BTI.INI, DELPHI.INI, and WINWORD6.INI files. 3. Paste the 3 files into each Terminal Client s Users Windows folder. Example: C:\Documents and Settings\ TS User name here\windows The BTI.INI file is created during the Pervasive client installation. The DELPHI.INI and WINWORD6. INI files are created during the EbixONE client installation. 9/26/2007 20 of 21

Copy ARIAL.TTF Font for PDF Creation The font arial.ttf is required for the EbixONE PDF creator to work. It needs to be copied to the Terminal Users respective Windows folder. 1. From the Terminal Server, create a new folder called FONTS folder under each TS users C:\Documents and Settings\ USER \Windows\ folder. (Where USER is the WindowsTS users name). Example: C:\Documents and Settings\johnsmith\Windows\Fonts. 2. After creating the FONTS folder, copy the Server s C:\Windows\Fonts\Ariel.ttf font file into the newly created USERS FONTS folder. 3. Repeat for each TS user that will use EbixONE. Finalize Setup and Test Connection In order to setup required files for WordMerge in EbixONE, Microsoft Word must be opened prior to using WordMerge. Open Microsoft Word, and exit when blank screen is reached. This completes the setup and transfer of files. If you are planning to use Microsoft Outlook as your email application, you must open and configure Outlook before using the email function in EbixONE. Open Microsoft Outlook and configure email. Test connection to EbixONE by logging into EbixONE Double-click the EbixONE shortcut on the desktop and login. Access the Customer Lobby To Exit the Terminal Client session. From Start, select Shutdown and Log Off. This is the preferred method of disconnecting from a terminal client session. Optional Installations on Terminal Server LightPaper LightPaper has been certified with terminal services. Refer to the LightPaper Installation Instructions for details on setup. SwiftView SwiftView has been certified with terminal services. Refer to the SwiftView Installation Instructions for details on setup. 9/26/2007 21 of 21