In the first part of the First Look: XenApp/XenDesktop series we discussed new things in this release, known issues and system requirements. We have installed as well core components on the server that hosts the Delivery Controller role. Let’s try now configure First Site. First of all we should launch Citrix Studio. To configure First Site choose option Site Setup – Deliver applications and desktops to your users. New wizard window called Setup Site will show up. First choice you have to make is if you what to create a fully configured Site or just empty one. I’ve chosen recommended choice and provided as well name of my new XenDesktop site. In the next step you will be presented with the window that allow to specify Database Server location and name of new Site Configuration database. After doing that you can test connection to that database server and check if the site’s database is created and available. In there is not database on the specified server with chosen name you will see the below message. This is my test environment so of course I chose to create the database automatically by Studio. The database was created and the connection test is passed. However in the production environment you might not have access rights on the database server/cluster and you will need to ask your DB admin to help you create that database. In that case it might useful to choose the option “Generate database script”.By default it is saved as shown on below screenshot. Now you can send that generated script to your DB admin and wait till he will run it and created needed database. In the next step you specify your license server name and TCP port on which it works. By default it is port number 27000. In my case I installed all core components on one server but for sure in production environment you should have dedicated license server. You have specify as well a location where your license file is located. I will use free 30-day trial. In next step you have configure connection to the hypervisor you use. You might want not to use Machine Creation Service and use instead Provisioning Services. In that case under “Create virtual machines using” choose “Other tools”. In my test environment I use right now XenServer 6.02 so I provided connection string and credentials to it. When trying to click Next I go the below error. It occurred after longer troubleshooting that I do not have network connection between my hypervisor and Delivery Controller. I needed to move my XenServer to other VLAN. Then you have to choose which network newly created Virtual Machines will use. I have only one network defined on my hypervisor so it was pretty easy to choose 🙂 In your production environment you will probably have few networks including production, backup and management networks. After time wizard will ask you where you would like to store your VMs. Additionally you can specify different location for users’ Personal vDisks. In production environment it will be recommended to store it somewhere else. I’ve chosen to store them on the same storage. And finally we can specify if we would like to use App-V streaming in our new XenApp/XenDesktop site. Citrix recommends using App-V for streaming applications to end users. I do not have App-V installed in my test lab so I skipped this step. The summary page shows the configuration we specified. Finally we can click Finish 🙂 After that installer creates the site’s database and configure the XenDesktop site. And finally our XenDesktop site is configured. As a last step we can check if everything is OK and click “Test site configuration”. As you can see there is 194 tests that check our site configuration. You can as well open generated report and see what might be wrong in your site configuration. Uff. That was long 🙂 Luckily we get to the end. In the next part of the series we will create a template image and first machine catalog.
Please check as well other parts of the XenApp 7.6/XenDesktop 7.6 First Look series:
In the first part – we installed first Delivery Controller and setup our new XenDesktop 7.6 site.
In the second part – we have configured first site.
In the third part – we prepared the template image of Windows Server 2012 R2 that will be used by MCS service for creation of new machines that will be hosting user desktops and applications.
In the fourth part – we upgraded XenApp 6.5 server to XenApp 7.6.
In the fifth part – we created machine catalogs and used previously prepared master image. We attached to the site as well upgraded XenApp 6.5 server.
In the sixth part – we delivered applications to the end users by creating delivery groups.
In the seventh part – we will configure StoreFront so that end users could launch their apps.
In the eighth part – we checked how Connection Leasing really works.