Back to Blog
![]() I only have one XenApp server configured, so I’ll click Next.Ĭlick Next unless you want to change connection timeout and limits. It is desirable to specify a second and third server running the STA. In the TCP port field make sure this is the same as the Citrix XML Service port you’ve configured on your XenApp servers. For now we won’t secure traffic between the STA and Secure Gateway so make sure that is not checked. Use “/Scripts/CtxSTA.dll” for the path, this will point to the library file on the STA even though it is located in the directory “C:\Program Files (x86)\Citrix\system32”. The STA is automatically installed on servers that run the XenApp server role.Įnter the fully qualified domain name the first XenApp server. Select “Secure Sockets Layer and TLSv1” and that All is selected for the cipher suite, then click Next.Īccept the default on what to monitor for inbound client connects and click Next.Ĭlick Add to give details on servers running the Secure Ticket Authority (STA). Also make sure that it says that there is a private key corresponding to this certificate. This must be the same as the server name that the clients will enter in their web browser when accessing the Secure Gateway. Select the certificate that you imported earlier and click View.Ĭonfirm that in the Issued to field the fully qualified domain name for the host appears. We’ll go through the Advanced configuration type, so select it and click Advanced. It will automatically start the Configuration Wizard so click OK.
0 Comments
Read More
Leave a Reply. |