/images/android-chrome-192x192.png

Manage VM Protection Policies

To enable, disable, edit and delete VM Protection policies for a pool, you use the VM Protection Policies dialog box: on the Pool menu, click VM Protection Policies. Enabling a VM Protection policy When you enable a VM Protection policy, you turn it “on”: automated snapshots of the specified VMs will then be generated at the scheduled time and archived, if this is also configured. Scheduled snapshots will continue being taken until the policy is disabled.

Recovering VMs From Snapshots

To recover a VM from a scheduled snapshot To recover a VM from a scheduled snapshot, you simply revert the VM to the specified snapshot. Select the VM and click on the Snapshots tab. To show scheduled snapshots (by default, they are not shown on this tab): click View and then Scheduled Snapshots. Select the scheduled snapshot you want to revert the VM to and then click Revert To. To take a new snapshot of the current state of VM before reverting it back to the scheduled snapshot, select the check box.

Clone Citrix server

This task requires a system preparation utility, such as Microsoft Sysprep, third-party imaging software, and a text editor. This task assumes you want to clone a server for the purpose of hosting published applications and that a relational database (Oracle, SQL Server, or DB2) is hosting the data store. C is the drive on which XenApp is installed. If you are using Citrix Provisioning services, using the PVS PS Integration Utility can accelerate the integration process by automating some steps.

Function of the Local Host Cache

Each XenApp server stores a subset(a portion or part from the whole part, but not full part) of the data store in the Local Host Cache (LHC). The LHC performs two primary functions: • Permits a server to function in the absence of a connection to the data store. • Improves performance by caching information used by ICA Clients for enumeration and application resolution. The LHC is an Access database, Imalhc.

ICA Policy Settings

The ICA section contains policy settings related to ICA listener connections, mapping to the Clipboard and custom channels, connecting to server desktops, and controlling the launch behavior of non-published programs. ICA listener connection timeout Applicable products: XenApp; XenDesktop This setting specifies the maximum wait time for a connection using the ICA protocol to be completed. By default, the maximum wait time is 120000 milliseconds, or two minutes. ICA listener port number Applicable products: XenApp; XenDesktop

ICA Timeout vs Session Reliability

Session reliability works at the client end. It allows a client to reconnect and avoid inconvenience to a user during a short network interruption. Instead of removing all unresponsive apps and desktops from the client workbench, they will be kept open until the ICA client is able to reconnect to the terminal server. It uses port 2598 and is available with Advanced and Enterprise versions. Whereas ICA Keep-Alive works at the server end allowing a server to detect broken sessions and put them into a ‘disconnected’ state if it can’t ping the client device.

IMA Information

**How does IMA traffic get sent and processed amongst Citrix servers? **Citrix has what we call a transport “function” that is responsible for getting packets of information from one host to another. The transport component is relatively small and does not actually care about the data it is transporting. This is a small set of functions for setting up bindings to host and subsequently sending packets to those hosts. How does IMA know who the hosts in a farm are to ensure communication requests are from approved sources?

Make Virtual IP Addresses Available to Applications

Some applications, such as CRM and CTI, use an IP address for addressing, licensing, identification, or other purposes and thus require a unique IP address or a loopback address in sessions. Other applications may bind to a static port, which, because the port is already in use, causes the failure of multiple attempts to launch an application in a multiuser environment. For such applications to function correctly in a XenApp environment, a unique IP address is required for each device.

Printer and Encryption details in XenApp 5

In order to replicate or autoadd printer drivers to all our xenapp servers, use printer management in xenapp advanced configuration. Install the printer driver first into your xenapp server, using the printer management, replicate it to other xenapp servers. We can also set autoreplicate option in printer management so that any new xenapp server added to this farm will get that printer drivers added automatically. In order to use autoreplicate feature, right click on the driver and choose autoreplication option.