To show Citrix Administrators how to recreate the XenApp ICA-TCP port in XenApp 6.x on Windows 2008 R2 servers.
 

---

Instructions

Recreating the ICA-TCP port is not as easy as it was when XenApp was on Windows 2003. Starting with Windows 2008 the ICA-TCP port cannot simply be recreated in Microsoft's Remote Desktop Session Host Configuration Utility. If you delete the ICA-TCP port from there you will NOT be able to recreate it.

Sometimes it is necessary to recreate the ICA-TCP port on certain XenApp servers if it becomes corrupted or it is not functioning properly so here are your options:

Follow these steps if you have a working XenApp server in your Farm:

WARNING! Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

1. Export and backup the ICA-TCP port registry key from a working XenApp server.

1. Delete the ICA-TCP port registry key (shown above) from the non working XenApp server.
2. Reboot the non working XenApp server.
3. Import the ICA-TCP port registry key from the working XenApp server to the non working XenApp server.
4. Reboot the non working XenApp server again.
5. Verify the ICA-TCP port is now visible in Microsoft Remotes Desktop Session Host Configuration Utility.

1. Test launching a published application it should work without issue.

Follow these steps if you do not have a working XenApp server in your farm:

1. On the non working XenApp server, Delete the ICA-TCP port from Microsoft's Remote Desktop Session Host Configuration Utility.
2. Delete the ICA-TCP registry key from the non working XenApp server.
3. Run a repair of the XenApp installation on the non working XenApp server which will recreate the ICA-TCP port and registry keys.
4. Reboot the XenApp server.
5. Verify the ICA-TCP port is now visible in Microsoft Remotes Desktop Session Host Configuration Utility.
6. Test launching a published application it should work without any issue.

1. Delete the ICA-TCP port registry key from the non working XenApp server.
2. Reboot the non working XenApp server.
3. Import the XA65icatcp.reg file to the non working XenApp servers registry.(should be able to just double click on it to have it update the XenApp servers registry)
4. Reboot the non working XenApp server again.
5. Verify the ICA-TCP port is now visible in Microsoft Remotes Desktop Session Host Configuration Utility.
6. Test launching a published application it should work without any issue.

Note: A good practice moving forward  is to backup a working ICA-TCP port registry key from your own farm so should you need to recreate the ICA-TCP port, you have it.

This registry file is provided to you “AS IS” with no representations, warranties or conditions of any kind. You may use, modify and distribute it at your own risk. 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. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the registry file 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 registry file 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 registry file. In no event should the registry file be used to support of ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE REGISTRY FILE, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Although the copyright in the registry file belongs to Citrix, any distribution of the registry file should include only your own standard copyright attribution.

The above mentioned sample code is provided to you as is with no representations, warranties or conditions of any kind. You may use, modify and distribute it at your own risk. 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. 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. In no event should the code be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SAMPLE CODE, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Although the copyright in the code belongs to Citrix, any distribution of the sample code should include only your own standard copyright attribution, and not that of Citrix. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the sample code.

This article goes over the options a Citrix Administrator needs to know if they want to recreate the ICA-TCP port in XenApp 6.x. To show Citrix Administrators how to recreate the XenApp ICA-TCP port in XenApp 6.x on Windows 2008 R2 servers.