VDA is highly available. You can access desktops and applications when delivery controller fails.

If all the delivery controllers in the xendesktop site fail, you can configure virtual delivery agent (VDA) to run in high availability mode so that users can continue to access and use their desktops. In high availability mode, the VDA accepts direct ICA connections from the user, rather than the connections represented by the Controller. In this way, you can continue to use the virtual desktop even if the DDC is down. This is the high availability mode of vda.

By default, the virtual desktop proxy VDA communicates with DDC every five minutes. Therefore, if DDC fails, communication between VDA and DDC may fail.

To implement this method, you need to perform the following settings:

1. Set the highavailability and haregistrartimeout registry items on vda.

2. provide you with an ICA Startup file. You can use this file to establish a direct ICA connection. You must create an ICA file for each user who needs this function.

Set registry key

To configure VDA so that it can run in high availability mode when necessary, you should add table items in the *** volume. This operation must be performed on

Run the command after installing vda.

1. Add Table items in the *** book to HKEY_LOCAL_MACHINE \ SOFTWARE \ Citrix \ virtualdesktopagent:

Name: highavailability

Type: REG_DWORD

Value:

1 = enable high availability mode

0 (zero) = Disable high availability mode

2. To change the time period for VDA to try to register with the controller before starting the high availability mode, add

Table items:

Name: haregistrartimeout

Type: REG_DWORD

Value: number of seconds. Default Value: 300 seconds.

3. Restart the virtual desktop.

Next let's talk about how to create an ICA file. It is necessary to describe the ICA file. ICA is a Remote Desktop Connection protocol developed by Citrix and also a file type, as long as you install something that parses the ICA file and know what it is, you can create an ICA file.

First, create a TXT file and write the following content in it:

[Encoding]InputEncoding=UTF8[ApplicationServers]Desktop=[Desktop]Username=USER_LOGON_NAME_HEREClearpassword=USER_PASSWORD_HEREDomain=DOMAIN_NAME_HEREAddress=DESKTOP_IP_ADDRESS_HERE:1494AutologonAllowed=ONBrowserProtocol=HTTPonTCPCGPAddress=*:2598ConnectionBar=1TransportDriver=TCP/IPClientAudio=OnDesiredColor=8DesiredHRES=1024DesiredVRES=768DoNotUseDefaultCSL=OnFontSmoothingType=0InitialProgram=#DesktopLPWD=31Launcher=WILocHttpBrowserAddress=!

You can modify the following fields.

• User_logon_name_here: your login Username

• User_password_here is your logon password.

• Domain_name_here your domain name

• Desktop_ip_address_here is the IP address of your virtual desktop.

Change the suffix to. ICA. Double-click the ICA file to connect to the virtual desktop.

However, this method has restrictions:

Only dedicated desktops are supported, that is, the relationship between virtual desktops and users. The pool random mode is not supported, and the pool static mode is supported.

In addition, this mode is enabled, and some functions are unavailable. Including:

User roaming. If a user device is connected to the desktop, the user cannot connect from other user devices.

Power Management. After the desktop power is turned on, registration will be attempted. If it fails, it will enter the high availability mode after timeout

.

The policy initiated by the delivery controller. Policies initiated on the controller (for example, policies that control client drive ing and clipboard access) do not work because they are not connected to the Controller. Policies initiated from domain controllers and local group policies are not affected. Note that the system will retain and use the previous registration policy, so the outdated policy may still be valid.

NetScaler gateway and remote access.

The high availability mode only lasts for 30 days, and the desktop is no longer available after 30 days. Once you enter the high availability mode (for 30 days), VDA will try to register with a controller for a maximum of 30 days, and the user will continue to use the desktop in this mode. When the Controller becomes available in the future, the desktop will register and the user's session will continue to run without interruption, but any subsequent connection will be proxy by the Controller as usual. If the desktop cannot be registered with the Controller after 30 days, the desktop will stop listening and the connection will no longer be available. This means that the Administrator has 30 days to repair the Controller infrastructure and should not rely on the high availability mode.

This article is from the blog "I get a year of chaos Floating Life", please be sure to keep this source http://tasnrh.blog.51cto.com/4141731/1435009