The Site database should always be in the primary zone. You can create one or more satellite zones once the site has been created. The primary zone has the default name “Primary,” which contains the SQL Server Site database, Studio, Director, StoreFront, License Server, NetScaler Gateway and rest of the components required for a XenDesktop 7.15 site. A site always has one primary zone, and its created automatically when you create the site. There are two types of Zones, primary and satellite. Citrix recommends a maximum of 50 zones per site, and if the network latency of the different zones is high, then a multi-site environment is still recommended. Zones can help users in remote regions connect to resources within a single site, without necessarily forcing their connections to traverse large segments of the WAN. Zones were introduced in XD 7.7, before version 7.7 you had to deploy multi-site environments if you had widely-dispersed locations connected by a WAN in your enterprise, where each site had to be managed independently. Zones can help administrators consolidate multi-site environments into a single site, and thus reduce the administrative overhead. Simply put, a site is the equivalent of a XenApp 6.5 farm. The site is created after you install the Delivery Controller, and then it can be populated with VDAs (through Machine Catalogs), Delivery Groups, and other components and configurations (such as policies and administrative roles). It comprises the components used in a XenApp/XenDesktop deployment, such as Delivery Controllers, Virtual Delivery Agents, Host Connections, and the Machine Catalogs and Delivery Groups you create and manage. FMA requires that you must be in a domain to deploy a site.Ī site is the name you give to a XenApp or XenDesktop deployment, it’s the highest level item in XenApp/XenDesktop 7.15 LTSR. FMA is the underlying architecture which defines and allows interoperability and management modularity across Citrix application and desktop virtualization technologies. While XenApp 6.5 relied on the Independent Management Architecture, XenApp (and XenDesktop) 7.1x relies on the Flexcast Management Architecture. Citrix Director can be placed on either client-side or the server-side of the network. In the illustration below you can see how the core components of a typical XenApp/XenDesktop 7.15 LTSR site interoperate. I’ll try to do a write up on pure cloud deployments in a future blog post. ![]() Keep in mind this write up holds true only for On-Premises and Hybrid Cloud deployments. While a XenDesktop license gives you access to both XenApp and XenDesktop features (VDI, Remote PC Access and Hosted physical desktops). A XenApp license gives you access to features that previously were exclusive to XenApp, namely server-based hosted applications and desktops. What matters is the license type you purchase and install. In the 7.1x versions, it doesn’t matter which of the products you install. ![]() As a matter of fact, in the earliest releases of XenDesktop 7.x, XenApp was completely merged into XenDesktop. This is done to provide a common architecture and a unified management experience for both products. Many of the old components that XenApp 6.5 and 6.0 comprised of, are done away with, and components that were part of XenDesktop 5.6 make up the backbone of XenApp (and XenDesktop) 7.1x. In this blog post we will review the architectural components that XenApp And XenDesktop 7.15 Long Term Service Release comprise.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |