-
Install and configure the Citrix Gateway appliance
-
Deploy Citrix Gateway in a double-hop DMZ
-
Maintain and monitor Citrix Gateway systems
-
Configure DTLS VPN virtual server using SSL VPN virtual server
-
Integrate Citrix Gateway with Citrix products
-
Integrate Citrix Gateway with Citrix Virtual Apps and Desktops
-
Configure settings for your Citrix Endpoint Management Environment
-
Configure load balancing servers for Citrix Endpoint Management
-
Configure load balancing servers for Microsoft Exchange with Email Security Filtering
-
Configure Citrix Endpoint Management NetScaler Connector (XNC) ActiveSync Filtering
-
Allow Access from mobile devices with Citrix Mobile Productivity Apps
-
Configure domain and security token authentication for Citrix Endpoint Management
-
Configure client certificate or client certificate and domain authentication
-
-
Configuring Settings for Your Citrix Endpoint Management Environment
-
Configuring Load Balancing Servers for Citrix Endpoint Management
-
Configuring Load Balancing Servers for Microsoft Exchange with Email Security Filtering
-
Configuring Citrix Endpoint Management NetScaler Connector (XNC) ActiveSync Filtering
-
Allowing Access from Mobile Devices with Citrix Mobile Productivity Apps
-
Configuring Domain and Security Token Authentication for Citrix Endpoint Management
-
Configuring Client Certificate or Client Certificate and Domain Authentication
-
-
Citrix Gateway Enabled PCoIP Proxy Support for VMware Horizon View
-
Proxy Auto Configuration for Outbound Proxy support for Citrix Gateway
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
RDP connection redirection
A Citrix Gateway appliance now supports RDP connection redirection in the presence of a connection broker or session directory. An RDP proxy communication no longer requires an exclusive URL for every connection from the client to the server. Instead, the proxy uses a single URL to connect to an RDP server farm, reducing the maintenance and configuration overhead for an administrator.
Point to note:
- RDP connection redirection is supported only when SSO is enabled and is supported in both single Gateway and Stateless or Dual Gateway mode along with enforcement (SmartAccess).
- RDP Proxy feature is supported only with token-based redirection supporting IP cookies. IP-based routing tokens “msts=” are handed back by the Windows session broker or Connection broker when the Use IP Address Redirection functionality is disabled.
-
You can disable the Use IP Address Redirection setting to enable token-based redirection in the following location.
Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > RD Connection Broker
. -
Disable the Use IP Address Redirection setting on the RDSH machines and not the connection broker machine.
- Dedicated redirectors for RDP Proxy connection can be configured.
Prerequisites
-
Create an RDP server profile to enable the 3389 listener on the Citrix Gateway virtual server. If the machine that you want to RDP is not a member of any RDS connection broker infrastructure, then you do not need the 3389 listener.
-
Enable RDP connection redirection on the Citrix Gateway appliance to support RDP Proxy in the presence of a connection broker.
Deploy RDP Proxy in the presence of a connection broker
RDP Proxy in the presence of a connection broker can be deployed in the following two ways.
- With RD session host servers participating in RD connection broker load-balancing.
- In the presence of the RDP load balancing feature.
With RD session host servers participating in RD connection broker load balancing:
In this case, the RDP URL link can be configured to point to one of the RDP servers as the destination server, which acts as redirector. Also, it is possible to have one of the RDP servers in the farm as destination server (in this case the server does not accept any RDP session).
In the presence of the RDP load-balancing feature:
When connection broker load-balancing is not enabled, we can have the RDP load-balancing feature available on Citrix ADC to do the required load-balancing of the RDP sessions in the presence of a connection broker. In this case, the RDP URL link has to be configured to have the RDP load balancer as destination server. The RDP load-balancer can be on the same Citrix Gateway appliance as the RDP Proxy. For more information, refer Loading balancing RDP servers.
Configure RDP Proxy in the presence of a connection broker by using the CLI
At the command prompt, type;
add rdpserverprofile <Name> -psk <string> -rdpRedirection ( ENABLE | DISABLE )
add rdpserverprofile serverProfileName -psk “secretString” -rdpRedirection ENABLE
<!--NeedCopy-->
Configure RDP connection redirection by using the Citrix ADC GUI
- Navigate to Citrix Gateway > Policies > RDP.
- Right-click RDP to Enable or Disable the RDP redirection functionality.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.