Error: 'Your User Profile was Not Loaded Correctly' in XenApp

Error: 'Your User Profile was Not Loaded Correctly' in XenApp

Read More ->>

XenApp Error: Google Chrome Becomes Unresponsive when Started as Published Application

XenApp Error: Google Chrome Becomes Unresponsive when Started as Published Application



You can also still get this issue when other published Citrix applications are opening Google Chrome through a href link (i.e. a link in an Outlook e-mail).

If so allow other applications to launch Chrome with the switch enabled updating the following registry key:

HKCR\ChromeHTML\shell\open\command\default

Read More ->>

XenApp error id 7011

XenApp 6.5 apply Rollup 04

XenApp 6.x apply

http://support.microsoft.com/kb/2465772
http://support.microsoft.com/kb/2265716

in this order.

Read More ->>

The Citrix Licensing Service Crashes on Startup

The Citrix Licensing Service Crashes on Startup

Read More ->>

Recommended Operating System Patches for Provisioned Windows Targets

Recommended Operating System Patches for Provisioned Windows Targets

Read More ->>

Choose between Cached Exchange Mode and Online Mode for Outlook 2013

Choose between Cached Exchange Mode and Online Mode for Outlook 2013

Read More ->>

Zero install ‘Receiver for HTML5 1.3’

Zero install ‘Receiver for HTML5 1.3’

Read More ->>

NetScaler - how to configure DNS with TCP

Some clients use the User Datagram Protocol (UDP) for DNS communications. However, UDP specifies a maximum packet size of 512 bytes. When payload lengths exceed 512 bytes, the client must use the Transmission Control Protocol (TCP). When a client sends the Citrix® NetScaler® appliance a DNS query, the appliance forwards the query to one of the name servers. If the response is too large for a UDP packet, the name server sets the truncation bit in its response to the NetScaler. The truncation bit indicates that the response is too large for UDP and that the client must send the query over a TCP connection. The NetScaler relays the response to the client with the truncation bit intact and waits for the client to initiate a TCP connection with the IP address of the DNS load balancing virtual server, on port 53. The client sends the request over a TCP connection. The NetScaler appliance then forwards the request to the name server and relays the response to the client.
To configure the NetScaler to use the TCP protocol for DNS, you must configure a load balancing virtual server and services, both of type DNS_TCP. You can configure monitors of type DNS_TCP to check the state of the services.
For updating the records proactively, the NetScaler uses a TCP connection to the server to retrieve the records.

Important: To configure the NetScaler to use UDP for DNS and use TCP only when the payload length of UDP exceeds 512 bytes, you need to configure DNS and DNS_TCP services. The IP address of the DNS_TCP service must be same as that of the DNS service.

Read More ->>