{"id":188,"date":"2018-05-10T20:18:44","date_gmt":"2018-05-10T20:18:44","guid":{"rendered":"https:\/\/projects-42.nl\/?p=188"},"modified":"2018-06-21T18:15:14","modified_gmt":"2018-06-21T18:15:14","slug":"citrix-xendesktop-7-17-part-3-publishing-a-desktop","status":"publish","type":"post","link":"https:\/\/projects-42.nl\/index.php\/2018\/citrix-xendesktop-7-17-part-3-publishing-a-desktop\/","title":{"rendered":"Citrix Xendesktop 7.17 part 3: publishing a Desktop"},"content":{"rendered":"

After setting up the delivery controller and configuring storefront to allow the HTML5 Receiver it is finally time to add a desktop to the mix.<\/p>\n

In this step by step article we will be adding a single desktop in “remote PC access mode”. this means that XenDesktop wont power manage the desktop and we wont be able to mass deploy it (its not a golden image).<\/p>\n

This might sound a little disappointing but its good for the basics, if your setting up a lab environment you probably want it this way because its way more flexible and when you have your image the way you want it, you can always re add it with a differed configuration.<\/p>\n

Lets get started.<\/p>\n

We start by installing the XenDesktop VDI agent on the VM. In my setup this is a Widows 10 VM but you can use all supported versions (7 to 10 at this time) and even some Linux distro’s!<\/p>\n

\"\"
After installing windows on a new VM we can start the XenDestkop\/Xenapp installer. This is the same installation media used for setting up the delivery controller. Click the Start<\/strong> button after the XenDesktop row to start the installation.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Click the “Virtual Delivery Agent for Windows Desktop OS<\/strong>” button to start the installation process.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Just like I wrote earlier I’m installing in Remote PC mode. In this case i want only one VDI and i’m not interested in rolling out a new set of VDI’s after every change (lab enviroment, remember). So select “Enable Remote PC Access<\/strong>” and click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
We might as well install the Receiver in the VDI, if we want to use Xenapp applications we can do it from inside the VDI (saves a lot of mouse work). Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
I wont be using any of the additional components in this particular VDI. If you think you need any (supportability tools and profile manager are very useful if your planning to deploy the VDI to multiple users), select them and click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Now we need to add specify the deliver controller. you can do this manually or using AD. I only have one delivery controller and i don’t mind typing the name. Type the FQDN for the delivery controller, use the “Test connection..<\/strong>” button to verify there is a delivery controller on the other side of the line. Click Add<\/strong>.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
After clicking Add. the screen looks like the above image (but probably with an other FQDN). if you don’t want to add another delivery controller click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

Now were able to select features, everyone wants to optimize performance so that will be an easy pick \ud83d\ude09 . Remote assistance is needed if we want to use the shadow functionality from Citrix Director. Real-Time audio kind of explains itself. Framehawk is new transport protocol optimized for low bandwidth WAN connections. In my case I want everything but Framehawk.<\/p>\n

\"\"
Select the features you want and click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
The can create firewall rules for windows firewall. If you are running Windows firewall you can let the setup do its thing. Otherwise you have to make the rules yourself. Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
The setup has all information to start installing. It politely shows what its going to install on your system. Click Install<\/strong> to start installing.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
The installation will take up a good 10 minutes (depending on your system). we have to wait till its finished.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
After installing the setup wants you to enable call home, the Citrix telemetry service. I don’t need nor want telemetry services so thanks but no thanks. Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Now the setup is truly done. After restarting the system will be good to go. Click Finish<\/strong> to restart the machine.<\/figcaption><\/figure>\n

 <\/p>\n

Now were done on the VDI side of things. We will continue the operation on the delivery controller with Citrix Studio.<\/p>\n

\"\"
In Citrix Studio, navigate to the Machine Catalogs<\/strong> tab and click the “Create Machine Catalog<\/strong>” link on the right side of the screen. This will open the Machine Catalog Setup wizard.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Were adding a Desktop OS system so select the “Desktop OS<\/strong>” radio button and click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Since we only want one VDI and were not letting Xendesktop power manage it we select the appropriate radio buttons (no power management<\/strong> and another service or technology<\/strong>). Click Next<\/strong> co continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Since we only have one VDI and we might have multiple users we will be using a random pool. Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
We have to define the VDI’s we want to add to the pool. This is not necessary if your using an other provisioning technology like PVS or MCS. Click “Add computers…<\/strong>” type the name of your computer and Click OK<\/strong>.\u00a0Since were using the latest version of Xendesktop we can live the functional level the way it is. Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Type a name for the Machine Catalog and click Finish<\/strong>.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
We have now created a Machine catalog with a machine in it \ud83d\ude42 . Lets add it to a delivery group so we can start it from the Receiver.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Navigate to the “Delivery Groups<\/strong>” tab in Citrix Studio and click the “Create Delivery Group<\/strong>” link on the right side of the screen to.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
At the “Create Delivery Group” wizard introduction page, click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
At the Machines tab, select the machine catalog we created earlier, set the number of machines to 1<\/strong> (we only have one machine in the catalog) and click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
At the Users tab, we can chose to limit the availability of the desktop group to specific users and or groups. In this lab setup all users may access the delivery group so we just click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
If we want to publish applications, this is the place to do it. Since we want to publish the entire desktop we wont publish applications. Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Because a delivery group can house multiple types of desktops (for example desktops with and without GPU acceleration), we have to at least one desktop assignment. Click the “Add…<\/strong>” button to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Type in a display name for the delivery group, this is the name the end user will see in the Receiver. We can restrict this desktop assignment rule to desktops with a specific tag. Tags can be added for individual desktops from the search tab in Citrix Studio. We can restrict which users will be able to use the desktops, in this case all users are allowed to use the published desktop. Click OK<\/strong> to continue.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
One desktop assignment added. Click Next<\/strong> to continue.<\/figcaption><\/figure>\n

For some strange reason I forgot to take a screenshot of the Summary page. Luckily the summery page displays no new information.<\/p>\n

 <\/p>\n

 <\/p>\n

\"\"
Assuming we have clicked the Finnish button on the summary page, we are now back at Citrix studio. It shows the newly added delivery group, so we can go and see if the desktop is added to the Receiver.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
Yep, its showing up on the Receiver side of things. Lets fire it up.<\/figcaption><\/figure>\n

 <\/p>\n

\"\"
One windows 10 Desktop sitting happily in a webbrowser, i love progress \ud83d\ude42 .<\/figcaption><\/figure>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

After setting up the delivery controller and configuring storefront to allow the HTML5 Receiver it is finally time to add a desktop to the mix. In this step by step article we will be adding a single desktop in “remote PC access mode”. this means that XenDesktop wont power manage the desktop and we wont […]<\/p>\n","protected":false},"author":1,"featured_media":223,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[44,17],"tags":[45,50,47],"class_list":["post-188","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-citrix","category-projects","tag-citrix","tag-windows10","tag-xendesktop"],"_links":{"self":[{"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/posts\/188","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=188"}],"version-history":[{"count":8,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/posts\/188\/revisions"}],"predecessor-version":[{"id":231,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/posts\/188\/revisions\/231"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/media\/223"}],"wp:attachment":[{"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/media?parent=188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/categories?post=188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/projects-42.nl\/index.php\/wp-json\/wp\/v2\/tags?post=188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}