IPv4/IPv6 support

This release supports pure IPv4, pure IPv6, and dual-stack deployments that use overlapping IPv4 and IPv6 networks.

The following components support only IPv4. All others support IPv4 and IPv6.

  • Citrix Provisioning
  • Citrix Hypervisor
  • Virtual Delivery Agents (VDAs) not controlled by the Only use IPv6 Controller registration policy setting

IPv6 communications are controlled with two VDA connection-related Citrix policy settings.

  • Primary setting that enforces the use of IPv6: Only use IPv6 Controller registration.

    This policy setting controls which form of address the VDA uses to register with the Delivery Controller.

    When enabled, the VDA registers and communicates with the Controller using a single IPv6 address chosen in the following precedence: global IP address, Unique Local Address (ULA), link-local address (only if no other IPv6 addresses are available).

    When disabled, the VDA registers and communicates with the Controller using the machine’s IPv4 address. This is the default value.

    If a team frequently uses an IPv6 network, publish the desktops and applications for those users based on an image or Organizational Unit (OU) that has the Only use IPv6 Controller registration policy setting enabled.

    If a team frequently uses an IPv4 network, publish the desktops and applications for those users based on an image or OU that has the Only use IPv6 Controller registration policy setting disabled.

  • Dependent setting that defines an IPv6 netmask: Controller registration IPv6 netmask.

    A machine can have multiple IPv6 addresses. This policy setting allows administrators to restrict the VDA to only a preferred subnet, rather than a global IP, if one is registered. This setting specifies the network where the VDA registers. The VDA registers only on the first address that matches the specified netmask.

    This setting is valid only when the *Only use IPv6 Controller registration policy setting is enabled. Default = Empty string

Deployment considerations

If your environment contains both IPv4 and IPv6 networks, create separate delivery group configurations for IPv4-only clients and for the clients who can access the IPv6 network. Consider using naming, manual Active Directory group assignment, or SmartAccess filters to differentiate users.

Session reconnection might fail if the connection starts on an IPv6 network, and then you try to connect again from a client that has only IPv4 access.

IPv4/IPv6 support