Without limiting the generality of the foregoing, you acknowledge and agree that (a) the sample code may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property (b) it may not be possible to make the sample code fully functional and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the sample code. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. You may use, modify and distribute it at your own risk. The above mentioned sample code is provided to you as is with no representations, warranties or conditions of any kind. Right-click the Scripts folder and select Properties.įrom the Virtual Directory tab, select Scripts and executables from the list of options for Execute permissions. Type scripts as the alias name and click Next.īrowse to locate the c:\inetpub\scripts folder and click Next.Ĭlear all the check boxes to remove the permissions. Right-click the STA Web site you created and choose new virtual directory. Provide a name to the Web site, for example, STA and click Next.Ĭhange the port for the Web site as 6556 and click Next.īrowse to locate the c:\inetpub\wwwroot folder and click Next. Right-click the server name and choose New Web Site. To avoid this issue, complete the following procedure to create a new Web site for the STA component: Note: For this section, it is assumed that the STA server is published on port 80. If the STA server is also used as a Web server for different Web sites, then you must indicate the new port number in each user HTTP addresses because Internet Explorer or the Web browser assumes that the HTTP port is 80. In the XML Service Port field, enter the new port number. In Xepp-Edit Settings, click Server Farms. Highlight the required site name that must be modified. To modify the Web Interface Server, complete the following procedure: In the Protocol settings, clear the Use default and specify your designated port in the TCP port check box. Highlight the STA server in the list and select Modify. Go to the Details of the server running the Secure Ticket Authority (STA) section. Open the Secure Gateway Configuration Wizard. To modify the Secure Gateway Server, complete the following procedure: Highlight and right-click on the xml service. Note: xxxx represents the new port number. Run the following command to register the xml service to the new port: Run the following command to unregister the xml service: To modify the XML server, complete the following procedure: The Director Login running in seconds after the XA 6.5 Controllers are shutting down.To update the STA port, you must complete the following procedure: I’m stumble in the path C:\inetpub\This file listed all Data Collectors from the XenApp 6.5 Environment, i delete this file from both Director Servers, running a iisreset again and…. After reboot the Director, the issue does not went away. I’m also enable the Log.FileName = C:\Logs\desktopdirector.log and the Log.LogToFile = 1 to get more informations behind.Īfter I’m logging in the Director again, I have a look to the Log C:\Logs\desktopdirector.log and can’t imagine what I see, the director discovered the old XenApp 6.5. I’m checking both Director Server and the Service.AutoDiscoveryAddressesXA is not shown. Now we are on the schedule to de-provisioning the old XenApp 6.5 Environment and starting to remove the Farm from the old Webinterface/StoreFront and remove it from the Citrix Director Servers in the IIS Application Settings, called Service.AutoDiscoveryAddressesXA as well and running a iisreset on both Director Servers.Īfter we are shutting down the old XA 6.5 Data Collectors we are have some phone calls from the ServiceDesk, they reported the Director login is very slow (up to 90 seconds), after we power on the old XA.6.5 Data Collectors the Director login is in a normale operation time. On my latest customer, we are finalized the Server 2016 Migration (XenApp 7.15 LTSR) just in time, end of June 2018.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |