Installation Guide for Click to Call Release 8.0

Deploying Click to Call in a Citrix Virtualized Environment

---

Revised: June 17, 2010

•Before You Deploy Click to Call in a Virtualized Environment

•Publishing Click to Call with Citrix XenApp

•Synchronization Considerations

Before You Deploy Click to Call in a Virtualized Environment

Before you deploy Click to Call to users in a virtualized environment like Citrix, consider the following:

•You must install Click to Call on the same servers as the applications that you want Click to Call to work with. For example, if you want your Microsoft Excel users to be able to use Click to Call, you must install Click to Call on the same server as the Excel application.

•You must install Click to Call in the same directory on every server in the virtualized domain. For example, if the Citrix environment comprises a mixture of 32-bit and 64-bit servers, you must modify the installation path during the Click to Call installation procedure to ensure that the installation path to Click to Call is the same on every server.

•You must publish the Click to Call application if you want your users to be able to change their preferences more than once, select a phone to use with Click to Call, call a number from your call history, and so on. To publish Click to Call, you must publish the file clicktocall.exe.

•If you publish an application that already has Click to Call installed, it is not essential to publish Click to Call separately to your users. However, if you do not publish Click to Call, users can only specify their Click to Call configuration once, cannot select a phone to use with Click to Call, cannot call a number from your call history, and so on.

If you do not want to publish Click to Call, but you want your users to be able to specify their configuration more than once, you can install Click to Call on the computers of your users. In this case, the user profiles must be synchronized with the terminal service user profiles.

•If you want your users to only use the Call with Edit dialog box part of the Click to Call functionality, you can publish the file CiscoCallApp.exe.

•The behavior of Click to Call depends on how the user profiles are configured. For more information about this topic, see Synchronization Considerations.`

Publishing Click to Call with Citrix XenApp

You can publish Click to Call to your users in several ways. Table 6-1 lists some of the available options.

Table 6-1 Click to Call Publication Options with Citrix XenApp

Publishing Method	Description
Server desktop	You publish a full desktop to your users. Processing occurs on the server. The applications for your users, and Click to Call, are installed on the server.
Seamless Click to Call phone, configuration, and other functionality	You publish individual applications to your users, and you want to make phone, configuration, and other functions available to your users. To do this, you publish an application that already has Click to Call installed, then you publish clicktocall.exe.
Seamless Click to Call phone functionality only	You publish individual applications to your users, and you want to make phone functions available to your users from within your applications. To do this, you publish an application that already has Click to Call installed. Users do not get the wider range of configuration functions, and other functions.
Seamless Call with Edit dialog box only	You publish individual applications to your users, and you want to make minimal phone functions available to your users. To do this, you can publish CiscoCallApp.exe.
Streamed application	This is not supported for Click to Call.

For more information about publication options, see Before You Deploy Click to Call in a Virtualized Environment. For more information about the functionality that is associated with clicktocall.exe, see Click to Call Executable Files, page 1-2.

Synchronization Considerations

The Click to Call configuration data, call history, and logs are stored in the roaming profile of the user. The roaming profile is contained in the %APPDATA% folder of the user. If Click to Call is installed locally, the Click to Call configuration files are synchronized across the Click to Call plug-ins. In a virtualized environment, depending on the configuration, you need to consider how the roaming profile of the user is synchronized.

If you publish a full desktop to your users, there are no synchronization issues. If your Citrix environment has several applications that use Click to Call, the applications are installed on separate servers, and the roaming profiles are not synchronized, then the configuration details, call history, and so on, of the user, might not be the same in all applications.

To resolve these synchronization issues, you must consider what kind of synchronization you want to implement in your Citrix environment. For more information about how to implement user profiles in a Citrix environment, go to the following URL:

http://support.citrix.com/article/CTX120285

In a virtualized deployment such as Citrix, Click to Call interacts with servers and applications as shown in

Figure 6-1 shows a Citrix environment where three servers host Microsoft Word, Excel, and Outlook. Users A, B, and C have their configuration files stored on a network share. In this configuration there are fewer synchronization issues.

Figure 6-1 Click to Call in a Citrix Environment Using Folder Redirection

Click to Call Icon

The default location of the Click to Call icon is:

32-bit Processor: C:\Program Files\Cisco Systems\Click to Call\icon\ClickToCall.ico

64-bit Processor: C:\Program Files (x86)\Cisco Systems\Click to Call\icon\ClickToCall.ico