Quantcast
Channel: Secure Gateway – Carl Webster
Viewing all articles
Browse latest Browse all 14

Using One Citrix Web Interface Site with Multiple XenApp Farms

0
0

I frequent Experts Exchange (http://www.experts-exchange.com/) and because of my status there, I often receive questions. Some of the questions have a common theme. Such as:

  • “How do I show published applications to my users when I have multiple XenApp farms?”
  • “How can I use Web Interface to migrate users to a new XenApp farm while using both farms?”
  • “If I have the same application published in multiple farms, how can I control which farm the application is run from?”

In this article, you will learn how to configure Web Interface 5.4 and Citrix Secure Gateway 3.3 for multiple XenApp farms.

There are several potential reasons for using multiple XenApp farms:

  • XenApp 6.0 and XenApp 6.5 require new farms
  • Distinct farms for 32-bit applications and 64-bit applications
  • Organizational security requirements
  • Business mergers and acquisitions
  • Multiple internal environments

XenApp 6.x cannot be integrated into the farm of an earlier version of XenApp or Presentation Server. Similarly, XenApp 6.5 cannot be mixed with a XenApp 6.0 farm. Attempting to join a XenApp 6.x server into an earlier farm will damage the data store.

Deploying a 32-bit application on a 64-bit server will install the application, by default, in the C:\Program Files (x86)\ folder tree. Deploying a 32-bit application on a 32-bit server will install the application, by default, in the C:\Program Files\ directory. This means that the default application location used when publishing the application is different for 32-bit and 64-bit versions of Windows Server when installing a 32-bit application.

An enterprise may have applications that are required to be separated from other applications for security or business requirements. Installing the applications to XenApp servers that are in different farms can allow for segregated farm administration and more granular user access.

When one business merges with or acquires another business, it is possible that both businesses may have pre-existing XenApp farms. Business requirements, during the transition phase, may necessitate the need to keep the XenApp farms separate temporarily or permanently.

A highly structured environment with strict change management controls may require different farms for different environments. For example, an organization may have Development, Test, QA, Training and Production environments. An application may be installed into the Development farm until network and systems administration procedures are documented. Once documented, the settings for the application can be moved into the Test farm. The Test farm can then be used for user acceptance testing. Once user testing has been completed, the settings for the application can be moved into the next farm. And so on, until the application is put into the production farm.

For this article, the following Virtual Machines (VMs) will be used:

  • Domain Controller: TrainingDC
    • The VM will be assigned two virtual CPUs (vCPUs), 2GB of RAM and 24GB of Hard Drive space
    • Windows Server 2008 R2 SP1
    • Domain Controller for the WebstersLab.com Active Directory domain
    • Remote Desktop Services License server and Citrix Licensing server
    • Static IP Address 192.168.1.100
  • SQL Server: TrainingSQL
    • The VM will be assigned two vCPUs, 2GB of RAM and 24GB of Hard Drive space
    • Hosts the SQL Server data stores for all four XenApp farms
    • Microsoft SQL Server 2008 R2 SP1 on Windows Server 2008 R2 SP1
    • Static IP Address 192.168.1.101
  • XenApp 5 #1: XA520031
    • The VM will be assigned two vCPUs, 4GB of RAM and 32GB of Hard Drive space
    • XenApp 5 for Server 2003 Hotfix Rollup Pack 7 on Windows Server 2003 SP2 32-bit
    • Static IP Address 192.168.1.102
    • Default XML port of 80
    • Farm name XA52003
  • XenApp 5 #3: XA520081
    • The VM will be assigned two vCPUs, 4GB of RAM and 32GB of Hard Drive space
    • XenApp 5 for Server 2008 Hotfix Rollup Pack 1 on Windows Server 2008 SP2 32-bit
    • Static IP Address 192.168.1.104
    • Default XML port of 80
    • Farm name XA52008
  • Web Interface and Citrix Secure Gateway: CitrixWI
    • The VM will be assigned two vCPUs, 2GB of RAM and 24GB of Hard Drive space
    • Windows Server 2003 SP2 32-bit
    • Web Interface 5.4 with Hotfix WI540MSI002 and Citrix Secure Gateway 3.3
    • Not a member of the WebstersLab.com domain
    • Static IP Address 192.168.1.105
  • XenApp 6.0: XENAPP60
    • The VM will be assigned two vCPUs, 4GB of RAM and 40GB of Hard Drive space
    • XenApp 6.0 Hotfix Rollup Pack 1 on Windows Server 2008 R2 SP1
    • Static IP Address 192.168.1.106
    • XML port 8060
    • Farm name XA60Farm
  • XenApp 6.5: XENAPP65
    • The VM will be assigned two vCPUs, 4GB of RAM and 40GB of Hard Drive space
    • XenApp 6.5 on Windows Server 2008 R2 SP1
    • Static IP Address 192.168.1.107
    • XML port 8065
    • Farm name XA65Farm

In addition to the Administrator account, five accounts were created in the WebstersLab.com domain:

  • User03, who has access to only the XA52003 farm
  • User08, who has access to only the XA52008 farm
  • User60, who has access to only the XA60Farm farm
  • User65, who has access to only the XA65Farm farm
  • UserAll, who has access to all four farms

Each farm has two resources published.

  • XA52003
    • Notepad
    • Word 2010
  • XA52008
    • Paint
    • Word 2010
  • XA60Farm
    • Calculator
    • Word 2010
  • XA65Farm
    • WordPad
    • Word 2010

Viewing all articles
Browse latest Browse all 14

Latest Images

Trending Articles





Latest Images