Citrix Client Config
Posted on 2013-10-22
Migration project underway to upgrade users to a controlled, locked down W7 desktop environment.
Applications need to be approved, licensed and compliant prior to upgrade.
Enterprise citrix farm is in place, servicing enterprise applications.
The greater environment contains ~10 standalone domains, with firewall configs actively in place to facilitate Citrix Program Neighborhood access to independent Citrix farms running Presentation Server 4.5.
Standard configuration to enable access via Citrix (on XP platform), is Citrix Program neighborhood and MANUAL / LOCAL config of access using TCP/IP protocol
ACLs are managed per individual independent domain that is to say, that regardless of whether a user can see the shortcut to the independent domain, they will be required to add in independent domain login to progress. So in essence, we are facilitating access, not granting access.
Need to enable access to ~10 environments (running Citrix Pres. 4.5) in the new environment.
Current approved citrix client is via Citrix Receiver (http protocol).
1. Find compatible solution that may either involve a Citrix Receiver (HTTP) + Program Neighborhood (TCP/IP) mixed environment. Latter will require x10 shortcuts or configs embedded/packaged. User cannot edit local config files
2. Incorporate "shortcuts" to each ~10 independent domain within the Citrix receiver, taking into account the fact that each farm runs Citrix Pres 4.5.
1. Considering the protocol and Citrix server mismatch, can the "shortcut" be represented in the Citrix Receiver as an application by simply registering the current TCP IP address as a DNS alias thereby enabling the new config to transition to an HTTP configuration
2. Has Citrix Program Neighborhood been discontinued?