ADCs also assist in application acceleration and provide security for applications. To force an outage, edit the registry of each Cloud Connector server. This setting instructs the Local Host Cache broker to enter outage mode, regardless of the state of the connection to Citrix Cloud. Your email address will not be published. Save my name, email, and website in this browser for the next time I comment. Skip to content How many Citrix Delivery Controllers are there?
How many Citrix Delivery Controllers are there? What happens if Citrix license server goes down? What is Citrix architecture? What are the components of Citrix? What is Citrix for dummies? Feature compatibility matrix. Data granularity and retention. Troubleshoot Director failure reasons. Document History. Aviso legal.
Multi-forest deployments, by default, do not have inter-domain trust relationships between the forests. An AD administrator can establish trust relationships between the multiple forests, allowing the users and computers from one forest to authenticate and access resources in another forest. For forests that have inter-domain trusts, it is recommended that the appropriate settings be configured to allow the Delivery Controllers to communicate with both domains.
When the appropriate trusts are not configured, multiple XenDesktop sites for each forest must be configured. This section outlines the storage requirements on a per product basis and provides sizing calculations. Infrastructure components for a XenApp and XenDesktop deployment should reside within their own dedicated organizational units OUs ; separating workers and controllers for management purposes.
By having their own OUs, the objects inside will have greater flexibility with their management while allowing Citrix administrators to be granted delegated control. Whenever possible, permissions and authorization should be assigned to user groups rather than individual users, thereby eliminating the need to edit a large number of resource permissions and user rights when creating, modifying, or deleting user accounts. Permission application example:. The majority of Citrix products discussed within this document require a database.
The following table outlines the usage on a per product basis:. Based on the capabilities of the various SQL Server editions available, the Standard edition is often used for hosting the XenApp and XenDesktop databases in production environments. The Standard edition provides an adequate number of features to meet the needs of most environments.
For more information on the databases supported with Citrix products please refer to the Citrix Database Support Matrix. Different versions of Citrix products support different versions of the SQL server; therefore, it is important to check the support matrix to ensure the version of SQL server used is compatible with the Citrix product being deployed. The SQL Server must be sized correctly to ensure the performance and stability of an environment.
Since every Citrix product uses SQL server in a different way, no generic all-encompassing sizing recommendations can be provided. Instead, per-product SQL server sizing recommendations are provided below. XenApp and XenDesktop Brokers use the database as a message bus for broker communications, storing configuration data and storing monitoring and configuration log data.
The databases are constantly in use and the performance impact on the SQL server can be considered as high. Based on results from Citrix internal scalability testing the following SQL server specification for a server hosting all XenDesktop databases are recommended:. The database files and transaction logs should be hosted on separate hard disk subsystems in order to cope with a high number of transactions.
In addition to static configuration data provisioning servers store runtime and auditing information in the database. Depending on the boot and management pattern, the performance impact of the database can be considered as low to medium.
The SQL server should be carefully monitored during the testing and pilot phase in order to determine the optimal configuration of the SQL server. In order to estimate storage requirements, it is important to understand the disk space consumption for common database entries. Since the database of a XenApp or XenDesktop site contains static configuration data and dynamic runtime data, the size of the database file depends not only on the physical size of the environment but also user patterns.
The following factors all impact the size of the database file:. The following table shows the typical maximum database size Citrix observed when scale testing XenApp and XenDesktop with a sample number of users, applications, and desktop delivery methods. This sizing information is a guide only. Actual database sizes may differ slightly by deployment due to how databases are maintained.
Determining the size of the transaction log for the Site database is difficult due to factors that can influence the log including:. During XenDesktop scalability testing, Citrix observed the transaction log growth rate at 3.
In a large environment, transaction log usage requires careful management and a regular backup, to prevent excessive growth. This can be achieved by means of scheduled jobs or maintenance plans. Of the three databases, the Monitoring database is expected to be the largest since it contains historical information for the site. Its size is dependent on many factors including:. The following table shows the estimated size of the Monitoring database over a period of time under different scenarios.
This data is an estimate based on data seen within scale testing XenApp and XenDesktop assuming a 5 day working week. For more information please see the Citrix Support article — XenDesktop 7. The size of the transaction log for the Monitoring Database is very hard to estimate, but XenApp and XenDesktop scalability testing showed a growth rate of about The Configuration Logging Database is typically the smallest of the three databases.
Its size and the size of the related transaction log depends on the daily administrative activities initiated from Studio, Director or PowerShell scripts, therefore its size is difficult to estimate.
The more configuration changes are performed, the larger the database will grow. Some factors that can affect the size of the database include:. This temporary database is used to store Read-Committed Snapshot Isolation data. XenApp 7. Citrix recommends that all XenApp 7. The size of the tempdb database will depend on the number of active transactions, but in general it is not expected to grow more than a few MBs.
The performance of the tempdb database does not impact the performance of XenApp and XenDesktop brokering, as any transactions that generate new data require tempdb space. XenApp and XenDesktop tend to have short-lived transactions, which help keep the size of the tempdb small.
The tempdb is also used when queries generate large intermediate result sets. Guidance and sizing the tempdb can be found on the Microsoft TechNet article Optimizing tempdb Performance. The Provisioning Services farm database contains static configuration and configuration logging audit trail data.
The record size requirements outlined below can be used to help size the database:. Due to the nature of the data in the PVS farm database the transaction log is not expected to grow very quickly, unless a large amount of configuration is performed. In contrast to XenApp, which also offers the ability to track administrative changes, the related information is not written to a dedicated database but directly to the Provisioning Services farm database.
In order to limit the size of the Provisioning Services database it is recommended to archive the audit trail data on a regular schedule. XenApp and XenDesktop utilizes three different databases: site configuration, monitoring and configuration logging.
All three databases can be hosted on the same server or on different servers. An ideal configuration would be to host the Monitoring database on a different server from the Site Configuration and Configuration Logging databases. The location of the Configuration Logging database cannot be changed when mandatory logging is enabled.
The following table highlights the impact to XenApp, XenDesktop and Provisioning Services when there is a database outage:. In addition to the built-in database redundancy options, Microsoft SQL Server, as well as the underlying hypervisor in virtual environments , offer a number of high availability features.
These enable administrators to ensure single server outages will have a minimal impact if any on the XenApp and XenDesktop infrastructure. Microsoft is planning to remove mirroring as a high availability option in a future release of SQL Server and is discouraging its use in new network development. Citrix offers organizations the flexibility of multiple licensing models that align with common usage scenarios.
Several Citrix products use the license server, while other products require a license to be installed on the product itself. For more information on XenDesktop 7. For more information, see Scalability. For a typical environment, a single license server is sufficient. If additional redundancy is required, Citrix supports the following high availability solutions for the license server.
Each method allows an administrator to exchange a single license server for another without an interruption in service; assuming that the change occurs during the grace period and that the following limitations are considered. If the thread count is set too low, requests will be queued until a thread becomes available.
Conversely, if the thread count is set too high, the license server will become overloaded. The optimal values are dependent on the server hardware, site configuration, and license request volume. Citrix recommends testing and evaluating different values to determine the proper configuration.
Setting the maximum number of processing threads to 30 and the maximum number of receiving threads to 15 is a good starting point for large scale deployments. Delivery Controller scalability is based on CPU utilization. The more processor cores available, the more virtual desktops a controller can support.
As the storm increases in intensity, the CPU utilization of the controller will increase. Adding additional CPU cores to a Delivery Controller will lower the overall CPU utilization, thus allowing for greater numbers of desktops supported by a single controller.
This is really only feasible when dealing with virtualized controllers as adding virtual CPUs is fairly easy and straightforward. The other alternative is to add another controller into the site configuration. The controller would have the same configuration as other controllers, and the load would be evenly distributed across all controllers, thus helping to reduce the overall load on each single controller. Testing has shown that a single Delivery Controller, using the following configuration, can support more than 5, desktops.
The following formula can be used to calculate the number of Delivery Controllers required for a Citrix site. If the server hosting the Delivery Controller is unavailable, users will not be able to access their virtual desktops or published applications. If one controller fails, the others can manage connections and administer the site. The locations of all Delivery Controllers are specified on the VDA, allowing it to automatically failover if communication with one Delivery Controller is unavailable.
The VDA checks the following locations, in order, stopping at the first place it finds the Delivery Controller:. Citrix Consulting recommends utilizing the auto-update feature enabled by default. Even if the SQL database is highly available, there is the risk of not having access to the database if the network connection between the delivery controller and SQL database fails, which is an important concern for sites that span geographical locations.
To overcome this risk, the delivery controllers can utilize the local host cache feature that creates a local copy of the SQL database, used only if the delivery controller loses contact with the database. The Citrix XML protocol uses clear text to exchange all data, with the exception of passwords, which are transmitted using obfuscation.
If the traffic between the Storefront servers and the XenDesktop Controllers can be intercepted it will be vulnerable to the following attacks:. For most organizations, the Citrix XML traffic will be isolated on a dedicated physical or virtual datacenter network making interception unlikely. The default settings specify the maximum number of sessions a server can host at and do not consider CPU and Memory usage. Capping session count does not provide a true indication of load, which can lead to an overburdening of Server OS delivery groups resulting in a degradation of performance or an underutilization of Server OS delivery groups resulting in an inefficient usage of resources.
Different rules and thresholds can be applied to each Delivery Group depending on the different resource bottlenecks identified during testing.
For more information on the available Load Management policy configurations refer to Citrix Docs — Load Management policy settings. It is highly recommended that this value and others be customized based on the results from scalability testing. Cloud Connector scalability is based on CPU utilization. To view the contents of the Logging Database, in Studio, click the Logging node.
On the right is Create Custom Report. The XenDesktop Database can become heavily utilized under load in a large environment. This can improve the interactivity of Studio and Director. It should be noted that this option may increase the load on the tempdb files. This can be adjusted up to days by running a PowerShell applet. From Citrix docs. XenDesktop uses an Active Directory service account to log into vCenter.
This account needs specific permissions in vCenter. To facilitate assigning these permissions, create a new vCenter role and assign it to the XenDesktop service account.
The permissions should be applied at the datacenter or higher level. If vCenter is using a self-signed certificate, in order for Delivery Controller to trust the vCenter certificate, you must import the vCenter certificate on both Delivery Controllers. When you create a machine catalog, you select a previously defined Hosting Resource and the Cluster, Storage, and Network defined in the Hosting Resource object are automatically selected.
If you are installing Director 7. Also install Citrix Group Policy Management 2. In line or line you will have the following. Note: onblur and onfocus attributes were added in newer versions of Director. Save the file. This will prepopulate the domain field text box with your domain name and still allow the user to change it, if that should be required.
By default the idle time session limit of the Director is min. If you wish to change the timeout, here is how to do it. From docs. This information can be viewed by all administrators that have access to the Activity Manager feature in Director. To protect the privacy of users and the applications they are running, you can disable the Applications tab from listing running applications.
In a large Active Directory environment, this query can take some time or even time out. If there are a large number of machines, the Director administrator can now configure site groups to perform machine search so that they can narrow down searching for the machine inside a site group.
The site groups can be created on the Director server by running the configuration tool via command line by running the command:. Then provide a site group name and IP address of the delivery controller of the site to create the site group.
The Monitoring database contains more data than is exposed in Director. You can use Excel to pull data from the OData Data feed. This particular blog post shows how to use an Excel PivotChart to display the connected Receiver versions. Once installed you can create custom reports from within Director. Here is a summary of the configuration steps. See the blog post for detailed configuration instructions.
This script generates a graph similar to the following:. Andrew Morgan — New Free Tool: Citrix Director Notification Service : The Citrix Director Notification service sits on an edge server as a service or local to the delivery controller and periodically checks the health of:. And if any of these items fall out of bounds, an SMTP alert is sent to the mailbox of your choice for action. Again, thanks for your help awhile back with my Citrix upgrade! We started out with Citrix Xenapp 7.
However, here we are 7 years later, now running Xenapp 7. I was told that since we had started with 7. IF we had started with 3, would have been fine. In Citrix Studio, click the Configuration node. The Citrix techs steered me wrong. This is the problem that makes me crazy with Citrix Tech support. Then the other issue is two techs telling you two different things.
Director will pull down the list of all Controllers in the farm and automatically fail over if localhost is down. Most companies purchase the per-core or per-socket licenses. Hi carl, we have an issue in xd76 studio where machine search is not working and throwing an error as database couldnt contacted , after long time.. Can you still install Xendesktop 7. If you install specific versions of software, Citrix will support those versions for 5 years.
You can directly install 7. No need to install any older version first. Carl can you explain something for me please? How do we have to split this, there have to be 2 sites so each site can use a separate type of license. Can a storefront server serve 2 separate sites, and what is the procedure for the Netscaler? Or ask your Citrix Partner to quote you a price to trade-up the licenses to the same type. Note: if you installed the Controller software in a non-default path, and if UAC is enabled, you will need to run command prompt as administrator and run the MSP files from there.
Otherwise the Citrix services will revert to the default path. I have one customer using non-standard paths. When they upgraded it moved the files. Citrix Broker Service 7. I currently have a 7. Is it possible to upgrate thise licenses server to 7. Citrix Xenapp 7. Hi Carl, I am planning for secure xml communication Currently its configured as below: 1. You might be able to put a cert on the load balancer and configure StoreFront to point to the load balanced FQDN using https.
The other two are not there. If I logon to either of the other two server the ones not showing in Studio and launch Studio, it launches and presents the Same info as the third DDC. I am in the process of upgrading to 7.
Any thought on this? Please help, I am not in a position to rebuild the site, as this is a live production environment. Did you use Studio to remove the Controllers? After doing that, on the removed Controllers, did you set the database connection strings to null? I was not able to remove the other two DCs through studio, as they did not show up in the list of controllers.
I set DB connections to null and ran evict scripts to try to get them out entirely but when i launch studio from either DC1 or DC 2 it still opens like they are functional. I guess my roundabout question is why does studio open on DC 1 and 2 if they do not show up in the list of controllers? Hoping you can shed some light on that. Since the session hosts will be configured to pull Per User licenses, there is no need to install licenses on the RD Licensing Server.
If we have a XenApp 7. But you must still be compliant with licensing requirements. Using 7. Are you blocking Internet access from the Studio machine? If you run Studio on a machine that has Internet access, is it faster? Hey Carl, I recently upgraded from 7. When I look at the details of the Citrix.
I have a call logged with support, but wanted to know if you or anyone else has seen this before? Do you think they deprecated the service? The service is still actively running on both my storefront servers. Have you tried uninstalling StoreFront and reinstalling? If you have a Server Group, you should be able to then replicate the config from the other node. I think I will wait for support before I take that on. Everything, to my knowledge, is currently working so I am a little gun shy with making too many changes without support on the call.
HI Carl i want to upgrade from 7. Is there a bug with 7. I published a simple notepad and calc and screen is black. A published desktop is working as expected. The published apps are running on a windows R2 server.
I have many 7. We are on XenDesktop 7. We use two delivery controllers, the first one contains also the license server. Do you see any problems when I upgrade the first delivery controller, database, delivery groups etce during working hours? Are there logins still possible on the secont delivery controller?
In theory, it should continue to allow logins during the upgrade process. Once the database is upgraded, the upgraded Controller will handle logons.
Did you expect a force schedule restart of all delivery groups after upgrading database in studio? Was the database offline during a scheduled restart of RDSH? If so, once the database is back online, it might kick off the scheduled restart.
Hi Carl: Thanks, as usual, for the very helpful documentation here on your Site. Thanks very much! Other installers might need it. Is this just getting the initial cert from when it first connected to the license server, nad not the current SSL cert?
Is there a way to get it to fetch the current one? Or is it indeed getting the current one and I need to do something on the Licensing server, renew a cert or…? Is this anything to worry about, or update on a regular basis, anytime the cert shows as expired? Or ignore? I am going to implement Citrix XenApp users session and want to know how much bandwidth would be required at datacenter for the same.
Navigation Change Log Upgrade to 7. You can upgrade directly from any Delivery Controller version 5. Cumulative Updates include bug fixes only.
Cumulative Updates do not include any new features. OS Upgrade — If you are currently have 7. Build a couple new Windows Server VMs with 7. Adjust monitoring tools to point to the new Win16 Controllers.
If other components are installed on the old Controllers, move those components to the new Win16 Controllers. Decommission the Windows Server R2 Controllers. License Server — Before upgrading to 7. Sysadmin permissions — The person upgrading Delivery Controller needs temporary SQL sysadmin permission so the databases can be automatically upgraded.
Close PowerShell and Consoles. Make sure all Citrix Consoles and PowerShell consoles are closed. If StoreFront fails, then the StoreFront configuration is wiped out. If StoreFront is installed on the Controller, take a snapshot before attempting the upgrade. Another option is to export the StoreFront configuration so you can restore it later if something goes wrong. Run AutoSelect.
On the top left, under Upgrade , click Studio and Server Components. In the Licensing Agreement page, select I have read, understand, and accept the terms , and click Next. If any tests fail, then click View Test Report. Click Next. In the Firewall page, click Next. In the Summary page, click Upgrade. If you see a Running Processes window, close the listed programs, and click Continue.
Click OK when asked to start the upgrade. Click Close if you are prompted to restart. After the reboot, login. Go back to the Locate window. On the bottom left, under This PC, click the mounted drive. Then click the Select Folder button.
Installation will resume. In the Call Home page, make a selection. If participating, click Connect , login with mycitrix. In the Finish page, check the box next to Launch Studio and click Finish. If you choose to Manually upgrade this site , then note that there might not be an upgrade for the Logging Database schema, depending on what version you are upgrading from.
Note: 7. If your Catalogs are already set to VDA version 7. Then do the same for the Delivery Groups. VDAs 7. The name of the monitoring database must not have any spaces in it. No lesser SQL role will work. In that case, the person running the scripts only needs the dbcreator and securityadmin roles.
It is possible to create the three databases in advance. Each Basic Availability Group has its own Listener. Assign a service account to the role at the Datacenter or higher level. Add two cores for LHC. Add at least three more Gigs of RAM and watch the memory consumption. Configure the Delivery Controller VM with four cores per socket. The only difference is the product name displayed in the installation wizard. On the top left, click Delivery Controller. In the Core Components page, you can install all components on one server, or on separate servers.
Splitting them out is usually recommended for the following reasons: large environments; or if you have multiple farms, and want to share the Licensing, and Director components across those farms. In CU6 and later, StoreFront is no longer an option in this metainstaller, but it can be installed separately.
In the Summary page, click Install. This will take several minutes. In the Finish page, click Finish. Studio will automatically launch. Ensure the two Controller VMs do not run on the same hypervisor host. Create an anti-affinity rule. After it loads, click Deliver applications and desktops to your users.
In the Introduction page, select An empty, unconfigured site. This reduces the number of pages in this Setup wizard. The other pages will be configured later. Enter a Site Name aka farm name , and click Next. Only administrators see the farm name. In the Databases page, if you are building two Controllers, click Select near the bottom of the same page.
Click Add. Note: the Delivery Controller software must already be installed on that second machine. Then click Save. If you installed Licensing with your Delivery Controller, then simply enter localhost. If the Certificate Authentication appears, select Connect me , and click Confirm. Then select your license, and click Next. In the Summary page, if your databases are mirrored or in an Availability Group, each database will show high availability servers , and the name of the Mirror server.
0コメント