http://msitproblog.com/2015/10/27/installing-an-app-v-5-1-server-infrastructure/
If you wish to configure your XenApp environment to be accessible via the same URL, both internal or external, then be aware that this isn't as simple as it used to be with Web interface. Web interface was in no way comparable to the enhanced security and architecture of the modern Citrix Storefront and Netscaler Access Gateway.
To configure the same URL for both internal and external users, you will likely need a SAN certificate with the CN name configured for your external domain, plus the internal Load Balanced store DNS address and Callback address.
It is possible to configure the Receiver client to use Beacons and identify whether they should authenticate via an internal or external URL. Think carefully with regards to single URL, as it may not be required. I'm not a fan of placing the internal storefront name on a Public Certificate. Do your users really care whether they have to type in "Storefront" into their web browser when working on site? It is also very easy to just place the external url on a corporate internet page as a link, or add the link as a shortcut to the Desktop or Browser favourites. Do you really need a single URL? Probably not.
To configure the same URL for both internal and external users, you will likely need a SAN certificate with the CN name configured for your external domain, plus the internal Load Balanced store DNS address and Callback address.
It is possible to configure the Receiver client to use Beacons and identify whether they should authenticate via an internal or external URL. Think carefully with regards to single URL, as it may not be required. I'm not a fan of placing the internal storefront name on a Public Certificate. Do your users really care whether they have to type in "Storefront" into their web browser when working on site? It is also very easy to just place the external url on a corporate internet page as a link, or add the link as a shortcut to the Desktop or Browser favourites. Do you really need a single URL? Probably not.
https://www.citrix.com/blogs/2014/05/28/a-video-is-the-next-best-thing-hdx-with-framehawk/
A useful presentation by "Scott & Scott" on Microsoft SPLA Licensing.
A good article on how to use VMware workstation to upgrade the VMware tools on your PVS vDisk. Possible alternative to using Winimage etc if Citrix environment is run over Vsphere.
https://www.virtuallyboring.com/citrix-pvs-use-vmware-workstation-to-upgrade-vmtools/
https://www.virtuallyboring.com/citrix-pvs-use-vmware-workstation-to-upgrade-vmtools/
http://www.jasonsamuel.com/2015/09/18/how-to-deploy-microsoft-azure-mfa-ad-connect-with-citrix-netscaler-gateway/
I've been working on a Xendesktop 7.6 project, which consists on two flexcast models. Static with PvD and Pooled random desktops. The client wanted a solution that could be used to convert their existing workstations into Thin Client devices--capable of connecting directly to a Hosted VDI desktop. We tested IGEL UDC2 and were impressed with how it worked. There were some initial tweaks, but in general this is a very good solution. The UMS console can be used to easily deploy thin client settings to the UDC2 devices, but also, any IGEL thin client devices.
