With the  release of XenApp 6 and higher the installation process has been greatly improved.  With XenApp 5 you needed to first install all the supporting software and configure it, and then you can go about installing XenApp.  I know from experience it would take much longer than it does now to setup a server.  The installation process is straight forward now, so here is how to go about it.


After inserting the XenApp DVD in the Windows 2008 R2 Server you would choose Install XenApp Server.

If this is a fresh server install and .Net 3.5 sP1 has not already been installed, the installer will detect this and prompt to install it for you before continuing.

Once .Net 3.5 has been installed the XenApp Server Role Manager will launch.  We will want to choose Add server roles.

You then need to choose the version of XenApp that you have purchased.  For my demonstration I am going to choose Platinum Edition as this will show all the options that are available during installation.

The Citrix license Agreement screen is up next, assuming you accept the terms and conditions click on I accept the terms of the license agreement and then click on next to continue.

You are then presented with the options of which server roles you wish to install on this server.  It is best to install these roles on separate servers.  For myself I generally choose to install the License server on the domain controller, the XenApp server is installed on each server that will be on the Farm, and while in small environments you can installed the Web Interface on the same server as the XenApp server it is best to have this on a separate server as well.  The same goes for roles such as the secure gateway.  If you are doing this in a lab environment this can be done easily with different VMs, or if needed can all be installed on the same server.  I am just going to choose XenApp and click on Next to continue.

Next we come to the sub-components of the roles we are installing.  By default XenApp Server, XenApp Management, and Windows Desktop Experience Integration are checked.  I generally leave these on, however you can remove them all except for XenApp Server which is required.  Other components included XML Service IIS Integration, which you would use if you wish to have the XML service share port 80 with the IIS server.  I generally do not use this option and choose to have XML monitored over port 8080 instead.  Once you have chosen all your options you would click on next to continue.

You can then review all the changes that are about to be made to the server once the installation begins.  It shows that a restart will be required during the installation process and all software and roles that will be installed onto the Windows 2008 R2 server.  Once you are ready, just click on next to continue.

You are now ready to install, click on Install to begin the process.  This process takes a while to complete and will require the server to reboot a number of times depending on the options you chose.

Once the first set of software has been installed you will be required to reboot the server before continuing, just click on Finish to continue.

You can either close the screen and reboot manually, or click on the blue reboot link and the server will automatically reboot.  Once the reboot has finished XenApp will launch and continue with the installation process.

You will be presented with the option to resume the installation after the reboot, just click on the blue Resume Install link to continue.

You are presented again with a list of tasks that are about to be performed.  Click on Install to begin.

Once the installation has finished you can click on Finish and move on to configuring the XenApp server.

Next you will need to configure where the license server is.

Enter the server name of your citrix license, you can use the fully qualified name, short name, or IP address for this.  I entered dc01.encom.local for mine, and stuck with the default port of 27000 for the server.  You can test the connection and then once finished click on next to continue.

You then select your licensing model, which will vary depending on the licenses you purchased from Citrix.  An * is placed next to the recommended option based on the information provided by your licensing server.

Next we will configure XenApp, which will involve joining or creating a new farm.

If this is the first XenApp server you will want to create a new Farm, otherwise you would join an existing farm.  This is my first server for this example, so I am going to choose create a new Farm.

Enter the name of the farm information, for my example I used Encom for the farm name and used the domain administrator account for the Citrix administrator account.

Next we need to choose which database to use.  For small environments and labs SQL Express will work just fine and will be installed on your first Citrix server.  If you have a larger environment or just wish to explore other options you chose use an existing Microsoft SQL 2005 or 2008 Server database.  You would want to have this on a different server of course, and if your servers plan on communicating over the WAN it is recommended that you use a SQL server to improve the performance of the Farm.  You would have a SQL server on both sides of the Wan so only SQL replication needs to be sent across the wan and the farm on each side can communicate directly with the database server.

My environment for this demonstration is small, so I am going to choose New database and use SQL Express.

You will then need to authenticate with the domain, once done, click OK.

Click on Next to continue.

Next you need to choose if shadowing is going to be allowed.  It is best to choose allow shadowing and then if you wish to disable it, you can via policies, as this setting is permanent and can not be changed after setting it.  Based on your polices of your company you can choose whether users will be notified they are being shadowed or not.  Click next when ready to continue.

Next you can enter a custom zone name, this can be based on subnet (such as I used here with or geographic location, or any other method that makes since to your company.

You can change the port information for XML service at this point as well as in citrix policies.  If you did not choose XML integration you will need to pick a port other than 80 such as 8080.

If you know the URL address of the web interface you may enter it now, otherwise just leave it blank and you can configure this at another time once the service has been installed.

Finally you can choose which remote desktop users should be used.  The default is to add anonymous users, and add the list of users from the users group.  Click next once you have chosen what works best for your environment.

You can now review the changes that are going to be made and click on Apply when ready.

Once the process is complete you can click on Finish.

You will need to reboot the server one more time and then you are ready to start managing your new XenApp 6.5 Farm.

As you can see, the installation while it does take a little time to get through is much easier than in the past.  I hope you have enjoyed this walk through and if you have any questions, please feel free to drop a note.


Leave a Reply

Your email address will not be published. Required fields are marked *

19 − eleven =