-
Recent Posts
Categories
- Application Virtualization (2)
- XenApp (1)
- AWS (1)
- Azure (1)
- Benchmarking (3)
- LoginVSI (3)
- Cloud Computing (8)
- Excalibur (1)
- Horizon (5)
- NetScaler Gateway (1)
- Desktop Virtualization (20)
- VMware View (11)
- XenApp (2)
- XenDesktop (9)
- Enterprise Virtualization (47)
- Microsoft Hyper-V (5)
- vSphere (16)
- XenServer (1)
- GRID (1)
- Mobility (3)
- MDM (3)
- VDI (2)
- Application Virtualization (2)
Meta
Blogs I Follow
- Virtualization Team
- Gabes Virtual World
- Virtual Architect - Gerben's Blog on Virtualization
- HYPERVIZOR
- PeetersOnline
- PlanetVM
- Professional VMware
- rogerlunditblog.blogspot.com
- seanclark.us
- TechHead
- Technodrone
- Tim's Technical Thoughts
- UP2V
- VCritical
- vmetc.com
- VMdamentals Blog
- VMpros
- kb.vmware.com/selfservice
- VROOM! Performance Blog
- WordPress.com News
yellowbricks – duncan epping
- Using vSAN Datastore Sharing aka HCI Mesh to connect OSA with ESA is that supported?
- How to stop vCLS VMs from running on a vSphere HA Failover Host?
- Unexplored Territory Podcast Episode 067 – Introducing Rubrik!
- vSAN ESA and the minimum number of hosts with RAID-1/5/6
- Unexplored Territory Episode 065 – Jatin Purohit discussing Oracle Cloud VMware Solution
- Happy Holidays: vSAN 8.0 U1 Book Discounted to less than 5 USD for the ebook!
- Doing network/ISL maintenance in a vSAN stretched cluster configuration!
- Call to action: Help cancer patients enjoy life when still possible!
- What does Datastore Sharing/HCI Mesh/vSAN Max support when stretched?
- Unexplored Territory episode 59: Introducing vSAN Max!
David Davis videos
- vChat – Mike Foley – Fortifying VMware vSphere Security – Episode 53 – @MikeFoley @DavidMDavis @Kiwi_Si
- vChat – Scott S Lowe – Kubernetes for vSphere Admins – Episode 52 – @Scott_Lowe @DavidMDavis @Kiwi_Si
- Video: How to Deploy the New Cloud Daddy for AWS Data Protection and Disaster Recovery
- vChat – Stu Miniman – What’s New at @TheCube – Episode 51 – @Stu @DavidMDavis @Kiwi_Si
- vChat – Bill Kleyman – Building IoT like Tony Stark – Episode 50 – @QuadStack @DavidMDavis @Kiwi_Si
- vChat – Aaron Delp on Podcasting and Cohesity – Episode 49 – @aarondelp @thecloudcastnet @cohesity
- vChat – VMware vSAN 6.6 New Features with vExpert Jase McCarty – Episode 48 – @jasemccarty @davidmdavis
- vChat – AWS Certified Cloud Practitioner – Episode 47 with @kiwi_si and @davidmdavis
- vChat – 2018 Enterprise Tech Conferences Past and Future – Episode 46 with @kiwi_si and @davidmdavis
- vChat – Blockchain Cryptocurrency Bitcoin Ethereum Mining Oh My! – Episode 45 with @kiwi_si and @davidmdavis
-
Join 146 other subscribers
LinkedIN
sitemeter
Live Statistics
Blog with Integrity
Disclaimer
The views expressed here do not reflect the views of the organization I work for(or have worked with). The opinions expressed by visitors on this blog are theirs. You are free to use this information but I am not responsible if you ever happen to suffer a loss/inconvenience/damage using it.Upcoming Events
- AirWatch
- AWS
- Azure
- Benchmarking
- ESXi
- GPU
- GRID
- hardware
- horizon view
- hyperV
- LoginVSI
- MAM
- MCM
- MDM
- MEM
- microsoft RDP
- microsoft windows server 2012
- NetScaler
- netscaler gateway
- NVIDIA
- storefront
- troubleshooting
- vdga
- VDI
- vgpu
- vmware
- VMware Horizon Application Manager
- vmware mirage
- VMware View
- vsga
- vsphere
- vSphere 5
- Windows 8
- xenapp
- XenDesktop
- XenServer
Follow me on Twitter
My TweetsFollow me on Strava
How to: Enable HTML5 in XenDesktop 7 to access Virtual Desktops from a HTML5-enabled web browser
Step1: Enable Receiver for HTML5 in Citrix StoreFront
Please follow the steps to enable Receiver for HTML5 in XenDesktop 7 environment. This is achieved by logging (RDP) to your Delivery Controller and using the Citrix StoreFront management console. Either accessing it from Citrix Studio console or from Citrix StoreFront console. Open the Citrix Studio management console. Click on Receiver for Web.
In the middle pane, make sure the appropriate Store is selected.
In the right pane, Under Actions > Store Web Receiver: Click Deploy Citrix Receiver
To enable Receiver for HTML5, there are 3 options:
o Install locally
o Use Receiver for HTML5 if local install fails
o Always use Receiver for HTML5 Select Use Receiver for HTML5 if local install fails Step2: Enable ICA WebSockets connections policy in Citrix Studio (i.e. on your XenDesktop and XenApp servers) Once the configuration on the Citrix Studio end is complete, follow the below steps to enable WebSockets policies using the Citrix Studio management console. Reference edocs Modify an existing (default) policy Under Citrix Studio, go to Policy In the middle pane, under Policies, either modify an existing policy or create a new policy. In the right pane, under Actions > Edit Policy.. Edit Unfiltered window opens, type websoc and hit enter. It will filter you all the three WebSockets related policy settings. Click Select for all of them. Select Allowed and click OK Leave default click OK Leave default click OK Click Next Enter a Policy name or leave default. Make sure Enable Policy is tick marked. Click Finish NOTE: If you modify an existing default (unfiltered) policy, the option Assign policy to user and machine objects is not available. Therefore, it is recommended to either modify an existing (not default) policy or create a new policy. Create a new policy to enable WebSockets policy settings In Citrix Studio > Policy, under Actions > Policy, Click Create Policy In the search field, type websoc and hit enter. It will filter all the 3 WebSockets related policy settings. Click Select for all of the three policy settings. Click Next Assign permission based on delivery group, , Tags. Select Delivery group. Click Assign. Once you click on Assign, a window – Assign Policy opens. Select the appropriate Delivery Group from the drop-down. Click OK If you Select Delivery Group Type, click Assign. You can select from the following delivery group types: > Private Desktop > Shared Desktop > Private Application > Shared Application If you select Organizational Unit (OU), then you have the option to select specific OU from your AD environment. On the Summary window, review your policy settings, click Finish Step3: Verify HTML5 by access Desktop and Application(s) using web browser Login via StoreFront URL http://<XDControllerIPaddressorFQDN>/Citrix/StoreWeb using domain credentials based on permission (users/groups) in delivery group. When you see this page, click on Log On. You get this page when you select Use Receiver for HTML5 if local install fails. That means you have two options:
1) Citrix Receiver Plugin
2) Receiver for HTML5 Enter the appropriate Username and Password The page will enumerate all the Apps and Desktops you have access to. Please note only desktops can be launched using HTML5 browser. For Applications, you need to use Citrix Receiver plugin. Windows 7 desktop from a HTML5 compatible browser. In this example, Google Chrome. References
WebSockets policy settings – edocs (XenDesktop 7)
Configure Receiver for Web sites – edocs (StoreFront)
o Install locally
o Use Receiver for HTML5 if local install fails
o Always use Receiver for HTML5 Select Use Receiver for HTML5 if local install fails Step2: Enable ICA WebSockets connections policy in Citrix Studio (i.e. on your XenDesktop and XenApp servers) Once the configuration on the Citrix Studio end is complete, follow the below steps to enable WebSockets policies using the Citrix Studio management console. Reference edocs Modify an existing (default) policy Under Citrix Studio, go to Policy In the middle pane, under Policies, either modify an existing policy or create a new policy. In the right pane, under Actions > Edit Policy.. Edit Unfiltered window opens, type websoc and hit enter. It will filter you all the three WebSockets related policy settings. Click Select for all of them. Select Allowed and click OK Leave default click OK Leave default click OK Click Next Enter a Policy name or leave default. Make sure Enable Policy is tick marked. Click Finish NOTE: If you modify an existing default (unfiltered) policy, the option Assign policy to user and machine objects is not available. Therefore, it is recommended to either modify an existing (not default) policy or create a new policy. Create a new policy to enable WebSockets policy settings In Citrix Studio > Policy, under Actions > Policy, Click Create Policy In the search field, type websoc and hit enter. It will filter all the 3 WebSockets related policy settings. Click Select for all of the three policy settings. Click Next Assign permission based on delivery group, , Tags. Select Delivery group. Click Assign. Once you click on Assign, a window – Assign Policy opens. Select the appropriate Delivery Group from the drop-down. Click OK If you Select Delivery Group Type, click Assign. You can select from the following delivery group types: > Private Desktop > Shared Desktop > Private Application > Shared Application If you select Organizational Unit (OU), then you have the option to select specific OU from your AD environment. On the Summary window, review your policy settings, click Finish Step3: Verify HTML5 by access Desktop and Application(s) using web browser Login via StoreFront URL http://<XDControllerIPaddressorFQDN>/Citrix/StoreWeb using domain credentials based on permission (users/groups) in delivery group. When you see this page, click on Log On. You get this page when you select Use Receiver for HTML5 if local install fails. That means you have two options:
1) Citrix Receiver Plugin
2) Receiver for HTML5 Enter the appropriate Username and Password The page will enumerate all the Apps and Desktops you have access to. Please note only desktops can be launched using HTML5 browser. For Applications, you need to use Citrix Receiver plugin. Windows 7 desktop from a HTML5 compatible browser. In this example, Google Chrome. References
WebSockets policy settings – edocs (XenDesktop 7)
Configure Receiver for Web sites – edocs (StoreFront)
This entry was posted in Desktop Virtualization, XenDesktop and tagged XenDesktop. Bookmark the permalink.
That is a comprehensive explanation @cloudray, but doesn’t the published application use the HTML 5 receiver too?
Yes, it has changed since the time I posted this blog. Meanwhile, I suggest please refer the most recent edocs as mentioned at the end of this blog for the latest updates for HTML5 features and supportability.
somehow it didnt work for me dude.. i have enabled the policy as you mentioned, searching by websocs. Enabled those 3 values in a new policy, changed the storefront deployment method. Firstly login to storefront took lot of time for me and then it gave msg, there are currently no resources published for you etc..
Please check your delivery group assignment for both the HTML5(websocket) policy as well as on the delivery controller where you have the delivery group (ensure appropriate user/group access is in-place)
Cloudray, This is did not work for me either. I’m able to access the storefront but then I get the error 404- file or directory not found