Joining Additional XenApp 6.5 Servers to a XenApp Farm Using Microsoft SQL Server Express Data Store
Recently, someone posted on Experts Exchange a problem they were having joining additional XenApp 6.0 servers to a farm that used a Microsoft SQL Server Express data store. I answered that question by writing an article. It didn’t take long for someone to ask how to do the same thing for XenApp 6.5. There were just enough differences between the screens in XenApp 6.0 and XenApp 6.5 that it was confusing. This article will show how to join additional XenApp 6.5 servers to a XenApp farm using Microsoft SQL Server Express. I will not cover XenApp 6.5 installation in this article.
I installed XenApp 6.5 onto fully patched, as of 25-Nov-2012, Windows Server 2008 R2 SP1 servers. These are the steps I took for the FIRST XenApp 6.5 server that will hold the Microsoft SQL Server Express data store database.
After the installation completed, I clicked Specify Licensing (Figure 1).
I always create a Citrix policy that contains the Citrix License Server information. Select Configure the license server later using a policy and click Next (Figure 2).
Click Continue (Figure 3).
I always create a Citrix policy that contains the Citrix Licensing Model information. Select Select the model at a later time and click Next (Figure 4).
Click Continue (Figure 5).
Click Configure (Figure 6).
Click on Create a new server farm (Figure 7).
Enter a New XenApp Server farm name and click Next. The farm name has a maximum length of 32 characters. By default, the account used to install XenApp 6.5 becomes a full farm administrator. Figure 8 shows a workgroup account and Figure 9 shows a domain account.
Click New database and click Next (Figure 10).
A prompt appears for the database credentials . Figure 11 shows a local account and Figure 12 shows an Active Directory (AD) domain account. Enter the necessary credentials and click OK.
Click Next (Figure 13).
The decision made on the Configure shadowing screen cannot be changed without reinstalling XenApp 6.5. For this article, click Next (Figure 14).
You will need to go through the four sections on the Specify advanced server settings screen and make the changes necessary for your environment. Click Next (Figure 15).
Review the configuration in Figure 16 and if needed, click Back to make any necessary changes. Click Apply.
As shown in Figure 17, Microsoft SQL Server Express is installed and the data store is created.
Click Finish (Figure 18).
Click Reboot (Figure 19).
Click Yes to restart the server (Figure 20).
After the first XenApp server restarts, login but don’t do anything at this time on this server.
Now go to the next XenApp server to add to the XenApp farm.
Click Specify Licensing (Figure 21).
Select Configure the license server later using a policy and click Next (Figure 22).
Click Continue (Figure 23).
Select Select the model at a later time and click Next (Figure 24).
Click Continue (Figure 25).
Click Configure (Figure 26).
Click Add this server to an existing server farm (Figure 27).
Click Existing Microsoft SQL Server Express database and click Next (Figure 28).
Enter the name or IP address of the first XenApp 6.5 server (Figure 29) and click Next. This is the server where Microsoft SQL Server Express was installed. If your servers are in a workgroup you will need to setup entries in each servers hosts file to allow name resolution of each server. In an AD domain environment, the servers should already be setup in DNS.
Note: In my opinion, if the only way this works is by using the IP address of the first XenApp server then you need to fix your name resolution issues.
Enter the same credentials used on the first XenApp server for the database and click OK. Figure 30 shows using local credentials and Figure 31 shows using AD Domain credentials.
Click Test Connection (Figure 32).
Click OK on the popup (Figure 33).
Click Next (Figure 34).
Click Next (Figure 35).
You will need to go through the four sections on the Specify advanced server settings screen and make the changes necessary for your environment (the same information entered for Figure 15). Click Next (Figure 36).
Click Apply (Figure 37).
The new XenApp server has now joined the existing XenApp server farm. Click Finish (Figure 38).
Click Reboot (Figure 39).
Click Yes (Figure 40).
After the server completely restarts and is sitting at the CTRL + ALT + DELETE logon screen, return to the first XenApp server. Click on Start -> Administrative Tools -> Citrix -> Management Consoles -> Citrix AppCenter (Figure 41).
Click Next (Figure 42).
Unselect Single Sign-On and click Next (Figure 43).
Note: If Single Sign-On is not used, the Citrix Single Sign-On Console can be uninstalled.
Click Add Local Computer (Figure 44).
Click Next (Figure 45).
Click Next (Figure 46).
Click Finish (Figure 47).
Note: If you get an error, double-click the error message to see what the error is. More than likely, if you are in a workgroup environment, the additional XenApp server could not be found. This is a name resolution issue. On the first XenApp server, add an entry to the hosts file for the additional XenApp server.
Since there are no published applications in the farm, click OK (Figure 48).
Expand the Farm (Figure 49).
Expand the Servers node and you will see both XenApp servers are in the farm (Figure 50).
That is it. Use the process starting at Figure 21 for each additional XenApp 6.5 server that needs added to the farm.
Note: Make sure you use CTX129229 and apply the recommended patches to all the XenApp servers in the farm.