Citrix Server Configurations Technology Services Group

Transcription

1 Technology Services Group This document is meant to serve as a guide only for setting up the application in a Connect 2000/Metaframe environment and is provided without warranties of any kind. Although every effort is made to ensure the accuracy of this document, McKesson shall not be held responsible for any technical or editorial errors or omissions. Information is subject to change without notice.

2 Table of Contents 1. Introduction Configuring the Server in a Citrix Environment Clinical Applications: Admin-Rx, Horizon Ambulatory Care (HAC), Horizon Clinical Infrastructure (HCI), Horizon Care Record (HCR), Horizon Emergency Care (HEC), Horizon Order Management (HOM), Horizon Prenatal Care (HPC) Steps for configuring the client Operational Notes Horizon Blood Bank (HBB) Horizon Business Folder (HBF)/Horizon Patient Folder (HPF) Initial Install Steps for configuring the ODBC client Final Steps Steps for configuring the Encryption Utilities INI and Registry Changes Operational Notes: Page 2 of 26

3 1. Introduction Although every effort is made to ensure the accuracy of this document, McKesson shall not be held responsible for any technical or editorial errors or omissions. Information is subject to change without notice based on changes within McKesson or Citrix updates and new releases. This document is intended for internal use only. Any distribution outside of McKesson Provider Technologies is strictly prohibited. The configurations addressed within this document assume the following in regard to the Citrix presentation server environment: Server hardware and software is staged at McKesson facility including build-out of all server hardware including CPUs, disk drives, memory, controllers, CD-ROM drives, and other components and run system diagnostic tests. Access servers are deployed to customer s facility. Customer has provided any additional software that will need to be installed. Citrix version 4.5 must be installed to McKesson technology standards To minimize risk of complications, individuals executing the procedures contained within this document should have strong knowledge of both Citrix and McKesson applications. Additional information on optimizing Citrix server performance may be found in Chapter 7 of the Advanced Concepts Guide, Citrix Presentation Server for Windows Version 4.0, published by Citrix. As most of these are MS Windows or network level suggestions, it is left up to the Citrix coordinator to determine which of these are applicable to their specific environment. However, in testing, the smooth scrolling feature in Internet Explorer was disabled as suggested in the Applications Optimization section. 2. Configuring the Server in a Citrix Environment Configuring the Citrix server for the Remote Hosting environment differs little from the way it would be configured at a customer site. There are, however, a couple of settings unique to remote hosting. 1. For Terminal Services Configuration: Server Settings Restrict each user to one session No Connections ICA-tcp Properties Disable Com Port Mapping Disable Audio Mapping 2. Set permissions on application install directory to MODIFY for users. In a Citrix Environment the Citrix presentation server must be configured for each application it hosts, so specific installation instructions have been created for each application. For some applications, such as Horizon Business Folder (HBF), the workstation must also be configured to run the application. This document is broken out into sections with one section for each application, except for those instances in which the server configuration is identical for more than one application, for example, Horizon Business Folder (HBF) and Horizon Patient Folder (HPF). In those cases, the instructions for both applications will be maintained in the same section. Page 3 of 26

4 For any application to be installed, the presentation server must be put in install mode before clients are installed. Place the server in install mode manually by going to a command prompt and typing change user /install (see Figure2-1 below). This is necessary as the Add/Remove Programs applet in the Control Panel will not leave the server in install mode through the last steps of installation. Figure 2-1: Install mode 3. Clinical Applications: Admin-Rx, Horizon Ambulatory Care (HAC), Horizon Clinical Infrastructure (HCI), Horizon Care Record (HCR), Horizon Emergency Care (HEC), Horizon Order Management (HOM), Horizon Prenatal Care (HPC) For Horizon Clinical applications the only Citrix configuration issue is configuring the client for PCView. When configuring the Pcview client in a multi-user OS environment such as Terminal Services and Citrix, special consideration needs to be taken when dealing with the pcview32.cfg file. In a traditional PC or client server environment, the pcview32.cfg file is installed into the directory which houses the client application. By default when a connection is setup on that PC, all relevant connection information and unique settings such as the Workstation ID are written to this file. In this manner, each PC maintains it own unique pcview32.cfg file which in many cases has a unique Workstation ID (TTY ID). In a Terminal Services/Citrix environment the client is installed one time and shared by all users on that particular server. This presents a challenge with Pcview because the default setup would have each user sharing the same pcview32.cfg file. This document outlines the steps necessary to setup Pcview in a Citrix environment while maintaining a unique pcview32.cfg file for each device Steps for configuring the client 1. Install the client Page 4 of 26

5 In a Terminal Services environment, the server needs to be put into install mode either by going through Add/Remove Programs and running setup or by running the change user /install command Once the server has been put into Install Mode the standard installation steps for installing the client on a PC should be followed 2. Create a Clients share on a file server. In a typical Connect 2000 environment configured by Mckesson s Technology Services group, the profile server would house the clients share. Under this share, a directory needs to be created for each client device which will run the Pcview client on Citrix. The directory name should match the ICA client name defined for each device. The ICA client name for the device is typically the same as the computer name but it is important to note that it can be configured with another name. To obtain the list of ICA client names contact your Citrix administrator. Once the clients share is created and the ICA client names are created, a copy of the pcview32.cfg file should be copied to each directory. An example of the directory structure would be //profileservername/clients/pc1/pcview.cfg At this point there should be a directory created for each ICA client that will run the Pcview application with a pcview32.cfg file in it. 3. Create published app (or edit shortcut) The published app or shortcut to pcview needs to be edited to use the pcview32.cfg file under the clients share. The d switch allows the ability for pcview to utilize a pcview32.cfg in a definable location. An example of the path would be N:\hboc\pcview32.exe d //profileserver/clients/%clientname%/pcview32.cfg In the above example, the %clientname% variable allows the OS to determine which client device has launched pcview and go to the corresponding directory and use the pcview32.cfg file in that location. 4. Configure Pcview32.cfg files for each device In order to configure the unique pcview32.cfg files for Workstation ID s, etc. you will need to either login from each device and configure the pcview32.cfg while logged in from the ICA client that corresponds with the pcview32.cfg file in the matching directory OR repeatedly change the ICA client name from a single device while you configure the files. If the second method is chosen, make sure that after each time a file is configured that the user is logged out of Citrix and the ICA client is closed then reopened to insure the new client name has taken affect Operational Notes Make sure the server is put into install mode before the client is installed. All devices that are to run Pcview via Citrix must have unique ICA client names. If there is a typo in either the ICA client name or the corresponding directory that was created to house the pcview32.cfg file, Pcview will not open because it will not find the pcview32.cfg file associated with that device. Page 5 of 26

6 The Pcview client needs to remain in constant communication with the pcview32.cfg file. If there are network issues or communication problems between the file server housing the clients directory and the Citrix server the Pcview application will not run properly. A simple.cmd or.bat file can be created which copies down the pcview32.cfg file from the central store to the users locally cached profile then launches the Pcview application. The d switch will have to be pointed to use the local file. An example would be N:\hboc\pcview32.exe d M:\documents and settings\%clientname%\pcview32.cfg. 4. Horizon Blood Bank (HBB) 5. Horizon Business Folder (HBF)/Horizon Patient Folder (HPF) 5.1. Initial Install 1. All steps require the session to be in install mode. 2. On the Citrix server, run Setup.exe from the folder containing the most recent version of the application. Page 6 of 26

7 3. Click Next at the Welcome screen. Figure 5-1: Setup executable Page 7 of 26

8 4. Click Yes Figure 5-2: Welcome Screen Figure 5-3: License Agreement Page 8 of 26

9 5. Click Yes. 6. Click Next. Figure 5-4: Warning message Figure 5-5: Customer Information Page 9 of 26

10 7. Click on Browse to change the Destination Folder to X:\imnet [Replace X with the drive designator where you want to install the application]. 8. Select HPF Workstation. Figure 5-6: Destination Location 9. Click Next. Figure 5-7: Select Features Page 10 of 26

11 10. Click Next. Figure 5-8: Select Program Folder Figure 5-9: Copy files 11. Enter HPF1234 or do not enter anything and change in the registry later. Page 11 of 26

12 12. Select No, then Finish. Figure 5-10: Workstation serial number Figure 5-11: Install complete Page 12 of 26

13 5.2. Steps for configuring the ODBC client 1. Click Start Administrative Tools Data Sources (ODBC). 2. Click the System DSN tab and click Add. 3. Select SQL Server and click Finish. Figure 5-12: ODBC data source Figure 5-13: Create new data source Page 13 of 26

14 4. Enter CRSS for the Data Source Name and enter the correct SQL Server name. Click Next. Figure 5-14: New data source to SQL server 5. Select SQL Server authentication. Login ID: epr Password: oops. Click Next. Figure 5-15: Server authentication Page 14 of 26

15 6. Select the correct database and select it to change it to be the default. Click Next. 7. Click Finish. Figure 5-16: Select database Figure 5-17: Select database preferences Page 15 of 26

16 8. Test the Data Source and verify connectivity. 9. Click OK. Figure 5-18: Data source configuration Figure 5-19: Test results Page 16 of 26

17 10. Click OK to finish ODBC configuration Final Steps Figure 5-20: Complete configuration 1. Append.old to the EPRS.INI file, the IMNET.INI file & the IMNETWFE.INI file as shown in Figure Page 17 of 26

18 Figure 5-21: Change.ini file names 2. Copy the 3 files to the Windows folder if available. Figure 5-22: Copy files Page 18 of 26

19 3. Run the two registry keys if available. Figure 5-23: Run registry keys 5.4. Steps for configuring the Encryption Utilities 1. Click on Setup.exe in the Support\Encryption Utility folder. Page 19 of 26

20 2. Click Next Figure 5-24: Support/Encryption utility executable Figure 5-25: Cryptography installation wizard Page 20 of 26

21 3. Click Next. 4. Select Settings Encryption Utility Figure 5-26: Choose desination location Figure 5-27: Select Settings Encryption Utility Page 21 of 26

22 5. Click Next 6. Click Finish Figure 5-28: Select program folder Figure 5-29: Setup complete Page 22 of 26

23 7. Login User name: epr ; Password: oops Figure 5-30: Login 8. Data to encrypt: oops and check all boxes. Figure 5-31: Select data to encrypt Page 23 of 26

24 9. Select Yes. Figure 5-32: Confirmation 10. Select the Windows Registry tab and select the first 5 and last check boxes. Figure 5-33: Select data to encrypt Page 24 of 26

25 11. Select Yes INI and Registry Changes Edit <systemroot>\imnet.ini [DSS] Figure 5-34: Confirmation TmpDir=<user root drive>\imnet\obbroker\ierltmp LocalPathBld=1 [MSG] ListenForConnections=0 (This line may need to be added) DynamicSessions=1 Edit <systemroot>\imnetwfe.ini [WFAPI] ShutdownOBB=0 Check Registry for the following entries: [HKEY_LOCAL_MACHINE\SOFTWARE\IMNET\EPRS\AUDIT] DBName = AUDIT DBServer = <database server> [HKEY_LOCAL_MACHINE\SOFTWARE\IMNET\EPRS\CABINET] DBName = CABINET DBServer = <database server> [HKEY_LOCAL_MACHINE\SOFTWARE\IMNET\EPRS\HIS] DBName = HIS DBServer = <database server> <Leave blank> DBName = EIWDATA DBServer = <database server> Reboot 5.6. Operational Notes: Page 25 of 26

26 For multi-facility or unit-census-enabled operations, Unit IDs and Facility codes settings are found in HKEY_CURRENT_USER\SOFTWARE\IMNET\EPF\WORKSTATION, but need to be specific to the device. If users will roam from workstation to workstation, a batch script executed on application launch (or similar method) should be employed to populate the HKCU key above with a specific set of values based on the workstation ID. HKEY_LOCAL_MACHINE\SOFTWARE\IMNET must have security set to full control for the Users group in an Active Directory environment or the Domain Users group in an NT 4.0 domain. If reporting is required, local printers must be available in the session, and the drive containing the IMNET directory (typically remapped from C) must be substituted to C at the root. This is a known issue of hardcoding of the drive letter for EPRS.INI location in the Report Manager process of HPF Workstation. 1. Create a directory on the root of the same drive as the application called HPFINI 2. Copy the 3.INI files form the Citrix server s \WINNT (or WINDOWS) directory (EPRS.INI, IMNET.INI and IMNETWFE.INI) into this HPFINI directory. 3. Once they are copied, edit each file and put at the beginning of each file at the very top [Correct File XX/XX/XX] replace the X s with the current date 4. Each time you change this file you should change the date. By doing this it will allow you to know that the user is getting the correct file form the HPFINI directory. 5. In the \IMNET\EPWKS directory create a file called EPRS.CMD and include the following: a. Copy X:\HPFINI\*.INI X:\windows (replace the first X with the drive location of the HPFINI dir. And the second X with the users home drive designator. b. Start X:\IMNET\EPWKS\EPRS.EXE (replace the X with the drive that users see as installed with the application 6. Publish the EPRS.CMD file that you created above rather than the EPRS.EXE file. The ADI (Adjustment Document Index) function is controlled through the registry under IMNET\EPRS\IE\DUID key..make sure that DBNAME and DBServer are correct EPRStooltip issue "regsvr32 D:\Imnet\epwks\eprstooltip.ocx" Consolidated Search Issue Make sure to launch first as a local admin to set reg entries Also set rights to IMNET dir to full and propagate to all subdirs For HBF edit the registry: delete the HPF1234 from the license key. Eprs.cmd off Subst X: %temp% C: CD \imnet\epwks Start eprs.exe Page 26 of 26