{"id":163,"date":"2018-05-05T21:26:02","date_gmt":"2018-05-05T21:26:02","guid":{"rendered":"https:\/\/projects-42.nl\/?p=163"},"modified":"2018-05-09T18:00:47","modified_gmt":"2018-05-09T18:00:47","slug":"citrix-xendesktop-7-17-part-2-configuring-storefront","status":"publish","type":"post","link":"https:\/\/projects-42.nl\/index.php\/2018\/citrix-xendesktop-7-17-part-2-configuring-storefront\/","title":{"rendered":"Citrix Xendesktop 7.17 part 2: Configuring storefront for the HTML5 Reciever"},"content":{"rendered":"

In the first part<\/a> of this series of articles about Xendesktop, we have installed a delivery controller and configured a empty site. In part 2 we will be configuring Citrix Storefront for use with the Receiver for web application and we will setup the necessary policy’s. This will greatly improve the enviroment for testing purposes because we wont have to install or reconfigure the Citrix Receiver application every time we want to test something.<\/p>\n

\"\"
When we start Citrix studio, there are two snap-ins loaded: Citrix Studio and Citrix storefront. When we click on The storefront snap-in we get the option to view or change stores or create a new store. Citrix adds a store by default so Click on “View or Change Stores<\/strong>“.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
The next screen gives a list of available stores and some basic information about the selected store. We want to enable the HTML5 Receiver. to do this, Click the “Manage Receiver for Web Sites<\/strong>” link on the lower right site of the screen.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
After clicking the link the above window appears. Click the Configure…<\/strong> button to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Select the “Deploy Citrix Receiver<\/strong>” tab and choose “Always use Receiver for HTML5<\/strong>” at the Deployment options drop down.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Click on the “Client Interface Settings<\/strong>” tab and deselect “Auto launch desktop<\/strong>” under Web sessions, otherwise every time you open the receiver page it will attempt to launch the first available desktop. Click OK<\/strong> to close the dialog. Click Close<\/strong> on the next dialog.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Now we want to setup the default domain, this step is not necessary but it will save the trouble of retyping the domain name every time we want to login to the receiver. Click “Manage Authentication Methods<\/strong>” at the bottom right of the screen.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Click the gear icon next to the “User name and password” method and click on “Configure Trusted Domains”.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Select “Trusted domains only<\/strong>” if you only want to allow logon attempts for trusted domains. Click on Add…<\/strong> and type the name of your domain. Click OK<\/strong> to close the dialog. If you have multiple domains you can check the show domains list in logon page checkbox. Click OK<\/strong> to close the dialog and click OK<\/strong> again to close the second dialog.<\/figcaption><\/figure>\n

Now we have Storefront ready to go, we still have to set a policy to allow WebSocket connections to all Xendesktop and Xenapp systems. Without WebSockets enabled we wont be able to use the HTML5 Receiver.<\/p>\n

\"\"
In Citrix Studio, navigate to the Policies<\/strong> section and click Close<\/strong> to close the welcome message.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
This section of Citrix Studio gives an overview over the applied policies. We want to create a new policy to do this, click the Create Policy<\/strong> link at the right side of the screen.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
After clicking the Create Policy button, the Create Policy wizard pops up. We want to enable WebSockets, so we search for “webs<\/strong>” or something like it. There are 3 settings shown: Allow connections, port numbers and trusted origins. for the testing purposes we only need to enable WebSockets. Press the Select<\/strong> link after the WebSockets connection<\/strong> setting.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
At the Edit Setting dialog Click the Allowed<\/strong> radio button and click OK<\/strong>. Click Next<\/strong> on the Create Policy wizard to continue with the wizard.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Click the “All objects in the Site<\/strong>” radio button on the “Users and Machines” tab. If you only want to use the HTML5 receiver on specific systems or desktop groups you can also do this with the “Selected users and machine objects” option. But in this case we want all systems to be able to use WebSockets. Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Add a name for the Policy and check the Enable policy<\/strong> checkbox. Click Finish<\/strong> to activate the policy.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Now we can logon to StoreFront. browse to the web-store URL and login with an AD account. You will be presented with the above screen. Since we don’t have applications or desktops the screen is empty.<\/figcaption><\/figure>\n

In the next part we will be adding a Desktop to the mix.<\/p>\n","protected":false},"excerpt":{"rendered":"

In the first part of this series of articles about Xendesktop, we have installed a delivery controller and configured a empty site. In part 2 we will be configuring Citrix Storefront for use with the Receiver for web application and we will setup the necessary policy’s. This will greatly improve the enviroment for testing purposes […]<\/p>\n","protected":false},"author":1,"featured_media":164,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[44,17],"tags":[45,49,48,46,47],"class_list":["post-163","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-citrix","category-projects","tag-citrix","tag-html5-reciver","tag-storefront","tag-xenapp","tag-xendesktop"],"_links":{"self":[{"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/posts\/163","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/comments?post=163"}],"version-history":[{"count":7,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/posts\/163\/revisions"}],"predecessor-version":[{"id":187,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/posts\/163\/revisions\/187"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/media\/164"}],"wp:attachment":[{"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/media?parent=163"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/categories?post=163"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/tags?post=163"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}