Transcription
Citrix SCOM Management Pack 3.14 for XenApp andXenDesktopNov 27, 20 17Use Citrix SCOM Management Pack for XenApp and XenDesktop to monitor and manage XenApp and XenDesktopinfrastructure with the Microsoft System Center Operations Manager (SCOM).With the Citrix SCOM Management Pack for XenApp and XenDesktop, you can:Improve the XenApp and XenDesktop infrastructure availability and healthT he virtual application and desktop infrastructure availability is checked with rigorous connectivity probing and activeservice checks. It is important that users are able to connect to their virtual desktops and applications. T his is a processthat involves many Delivery Controller components (such as Broker Service or Machine Creation Services).Gain insight into the XenApp and XenDesktop performance and usage informationIt is critical to know how users are using the virtual infrastructure delivering desktops and applications in order to be ableto tune it accordingly. With the Citrix SCOM Management Pack for XenApp and XenDesktop you will get more insightinto which users are logging in to the virtual desktops and applications (identify slow logons and logon bursts), how manyusers are connecting to the Sites, if the infrastructure is able to handle all user requests accordingly, for example bymaintaining the size of the idle pool defined by the desktop group power management policy, by ensuring enoughresources for delivery of applications and desktops defined by the load management policy, and so on. Another aspect isthe end-user resource usage (what is the resource usage for each user connection/session) and virtual infrastructureresource usage (what is the resource usage of my server OS machines). Detailed machine and session performanceinformation helps in managing your infrastructure and enables better planning and decision making.Citrix SCOM Management Pack for XenApp and XenDesktop fully integrates the topology, health, and performance datainto SCOM.It provides centralized monitoring in SCOM and covers the following key scenarios:Are Delivery Controller instances up and running?Is the infrastructure (for example, brokers, machine creation services, and so on) on the Site level operational?Do users have issues connecting to the virtual desktops and applications (for example, delivery group limit/capacity isreached, desktop OS or server OS machines cannot register, other infrastructure issues are present)?What is the availability of published applications?Are there any events that indicate a problem with the infrastructure?Have any performance thresholds been violated?What is my server OS machine performance?What is the user session resource usage on server OS or desktop OS machines?Are there any user logons with lengthy duration? Which logon phases are causing the delay?Important: T o collect machine and session performance data, the product's Machine Agent must be installed andconfigured in addition to its main agent (referred to simply as Agent). For a general overview of the machine and sessionmonitoring concepts, see Machine and session performance monitoring.Architecturehttps://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.2
T he following diagram shows how the Citrix SCOM Management Pack for XenApp and XenDesktop connects with theSCOM management platform and the XenApp and XenDesktop infrastructure.https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.3
What's newNov 27, 20 17Citrix SCOM Management Pack 3.14 for XenApp and XenDesktop introduces the following enhancements:Support f or Citrix XenApp and XenDesktop 7.16. Citrix SCOM Management Pack for XenApp and XenDesktop nowsupports XenApp and XenDesktop Version 7.16.Support f or Citrix zones. T he product now supports the zones configuration. T he Site topology displays all primaryand secondary zones within the Site. Delivery Controllers and hypervisors are contained in zones. T his feature works withXenApp and XenDesktop Version 7.7 and later.New reports on application usage. T his release introduces two new reports.Application usage report shows the application usage list for the selected Site. T he report displays metrics depictingspecific application usage such as the cumulative usage time, the number of launches, and the number of distinctusers. Use this report to see most and least used, and unused applications in your Site. You can drill down from thisreport to the Application usage by user report.Application usage by user report shows application usage metrics per user for the selected application.Site Database Availability. T he topology now includes the Site Database object. Additionally, two monitors areintroduced to monitor and report the Site database availability in regular and high availability database configurations.Site Database Availability Monitor triggers an alert when the database is unavailable and specifies the reason forthe lack of availability.Site Database High Availability Monitor can be used if you have a high availability the database setup withmirroring. T he monitor triggers a warning alert when one of the databases is unavailable.Known issuesT he following is a list of known issues in this product version:Issue ID: SCOM-502Symptom: In the SCOM Operations console, when you attempt to run the Start Citrix Director task on a XenApp andXenDesktop alert that is not a session performance or logon alert, the invocation fails and SCOM reports the followingerror:Citrix Director URL not configured. Please configure the Citrix Director URL by using XenDesktop MP Configuration tool.Action: None. T he error message is incorrect, so you can safely ignore it. You can run the Start Citrix Director task onlyon session performance alerts and logon alerts.Issue ID: SCOM-143Symptom: In the SCOM Operations console, the ApplicationExcludeRegExtPattern andApplicationIncludeRegExtPattern parameters of application discoveries (Application Discovery (n of 5)) are ignored. You,therefore, cannot exclude applications from the discovery process or include them into it.Action: None. T here is no workaround available.Issue ID: SCOM-86 (6297)Symptom: After Citrix SCOM Management Pack for XenApp and XenDesktop (both its server-side and agent-side parts)is installed and configured on the computer for the first time (without being upgraded from an earlier product version),https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.4
and a valid XenApp and XenDesktop Platinum license cannot be retrieved, no license-related alerts are sent. Such alerts,therefore, cannot be monitored in the Monitoring view of the SCOM operations console.Action: None. T here is no workaround available.Issue ID: SCOM-77 (6194)Symptom: In the output of the Check Requirements and Configuration for Citrix MPXAXD Agent task in the SCOMOperations console, site names that contain non-ASCII characters are not displayed correctly. For example, Spanishcharacters çñ appear as in the name of a XenApp and XenDesktop Site. No other symptoms exist.Action: None. Apart from the visual glitch, the functionality of the product is not affected in any way. You cantherefore safely ignore the issue.Issue ID: SCOM-210 (5380)Symptom: While a workflow is running, error messages (31551 and 31552) are logged into the Operations Manager eventlog on the management server. T hey contain the following description:Failed to store data in the Data Warehouse.T his error occurs when the Default action account in SCOM does not have write permission on the data warehousedatabase and none of the XenDesktop controllers is discovered as Site Data Collector. T his may happen when:T he Site Data Collector object switches from one XenDesktop Delivery Controller to another.Collector object switches from one XenDesktop Delivery Controller to another.None of XenDesktop Delivery Controllers is operational.T his issue occurs only with some of the workflows, for example, ConnectionsLogonsDW.Rule or ApplicationInstanceDW.Rule.Action: Ensure that at least one Delivery Controller is active at all times.Issue ID: SCOM-211 (5163)Symptom: T he Delivery Group - Logon Details (Troubleshooting) report does not function if the Use business hoursoption is selected.Action: Clear the Use business hours option.Issue ID: SCOM-212 (5162)Symptom: When launching Citrix Director by using the Start Citrix Director task in the Operations Manager Console foruser logon or session alerts, Citrix Director is not opened for the users' context if the user is anonymous. Anonymoususers were introduced in XenApp and XenDesktop 7.6.Action: None. T here is no workaround available.Issue ID: SCOM-1426Symptom: T he Object and Counter names in all Performance views on the SCOM Management Server are not localized,but appear in English.Action: None. T his issue does not impact product functionality.Applies to French, German, Japanese, Simplified Chinese and Spanish languages.Issue ID: SCOM-78Symptom: If the password of the Citrix SCOM Management Pack for XenApp and XenDesktop Monitoring useraccount contains non-English characters the Check Requirements and Conf iguration f or Citrix MPXAXD Agent taskreports an error in the Citrix XenApp/XenDesktop Powershell Interface section as follows:“Could not get data from Citrix PowerShell interface.”Action: Change the password of Citrix SCOM Management Pack for XenApp and XenDesktop Monitoring user accounthttps://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.5
to contain only English characters.Applies to French, German, Japanese, Simplified Chinese and Spanish languages.Issue ID: SCOM-1391, SCOM-1384Symptom: In the SCOM Console, the output messages of all tasks are not localized, but appear in English.Action: None. T his issue does not impact product functionality.Applies to French, German, Japanese, Simplified Chinese and Spanish languages.Issue ID: SCOM-1156Symptom: Surrogate pair characters in the Citrix SCOM Management Pack for XenApp and XenDesktop reports appearincorrectly.Action: None. T his issue does not impact product functionality.Applies to Japanese and Simplified Chinese languages.Issue ID: SCOM-1222Symptom: If the XenApp and XenDesktop Site name contains Japanese or Simple Chinese characters, an error mightoccur when running the Check Requirements and Conf iguration f or Citrix MPXAXD Agent or Check Requirementsand Conf iguration f or Citrix MPXAXD Machine Agent task.T he Director URL for the Site is configured successfully, but the task might display the following error message:“Director URL is not configured for Site sitename . Please configure Director URL for this Site in 'XenApp andXenDesktop MP Configuration' tool and deploy new configuration using 'Update Configuration on Citrix MPXAXDAgent/Machine Agent' task in SCOM.”Action: Avoid Japanese and Simplified Chinese characters in the XenApp and XenDesktop Site name.Applies to Japanese and Simplified Chinese languages.Issue ID: SCOM-2100Symptom: T he reports - Delivery Group Server OS - Machine Performance, Server OS Machine - Performance (Plan andManage), and Server OS Machine - Performance (T roubleshooting) can show incorrect load index values for certainServer OS Machines.Action: NoneIssue ID: SCOM-2137Symptom: Site level performance monitoring: Data collection for Sessions on Site, Connected Users on Site, and UserLogon Performance might stop after running for a while.Action: Restart the Microsof t Monitoring Agent service on the Delivery Controller that acts as the Site DataCollector.Issue ID: SCOM-2288Symptom: When a machine running active sessions registers with a different Delivery Controller, the Machine Agentmight not monitor some running sessions.Action: NoneIssue ID: SCOM-2359Symptom: T he Check Requirements task of the Machine Agent might report incorrect discovery times for Server andDesktop OS machine discovery.Action: None. Ignore the machine discovery time values.Issue ID: SCOM-2510Symptom: When you generate the Application usage report for multiple Sites with the scope set to top N or bottomhttps://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.6
N, the application entries in the are listed only in the order of usage but not grouped by Site. T he report might beinaccurate and difficult to comprehend.Action: Select one Site at a time to get accurate ordering of the applications with the scope set to top N or bottom Nentries.Issue ID: SCOM-2514Symptom: T he Show only applications used by user filter of the Application - Usage report lists unused applicationsalso.Action: Ignore applications with usage duration as zero.Fixed issuesIssue ID: SCOM-2421Symptom: Failure of Site performance monitoring results in the following:a Citrix MPXAXD Agent Not Operational alert with workflow id site-perf ormance is triggered.running the Check Requirements task shows the following error:'site-performance'Not OperationalWorkflow errorOne or more errors occurred.the log file ComTrade.MP.XenDesktop.Service.log contains an entry, System.IO.FileNotFoundException: T henetwork path was not found.T his might happen when VDA Service monitoring is on and one or more VDAs have been deleted.Issue ID: SCOM-2407Symptom: Discovery for Sites running Citrix XenApp and XenDesktop Version 7.6 with more than 2000 VDAs might fail.Issue ID: SCOM-2362Symptom: T he Citrix SCOM Management Pack Agent for XenApp and XenDesktop tries to monitor machines that areinactive (lifecycleState 1). When this happens, the Site-performance workflow fails.LicensingLicensing of Citrix SCOM Management Pack for XenApp and XenDesktop depends on licensing of the monitored product,XenApp and XenDesktop. For Citrix SCOM Management Pack for XenApp and XenDesktop to operate properly and remainfully functional, its licensing must be covered. During installation or upgrade, no further actions are necessary on either theSCOM management server or the computers that host the product's Agent and Machine Agent instances.Covered licensing means that the following conditions are fulfilled:T he XenApp and XenDesktop Site that you plan to monitor uses a Platinum license within either maintenance program:Subscription Advantage, Software Maintenance.Subscription Advantage Date (of the Platinum license) falls after the Subscription Advantage Eligibility date that isembedded into binary files of the current version of Citrix SCOM Management Pack for XenApp and XenDesktop. Forinstructions on how to check this, see Install and Configure. In Citrix product documentation, Subscription AdvantageEligibility date may also be referred to as product burn-in date.Important: T he Subscription Advantage Eligibility date of this product release is 2017.1101.https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.7
Example: If the Subscription Advantage Date of your Platinum license for XenApp and XenDesktop is 2016.0531 (meaning31 May 2016), and the Subscription Advantage Eligibility date of Citrix SCOM Management Pack for XenApp andXenDesktop is 2016.0518 (meaning 18 May 2016), the product remains fully functional after 31 May 2016, provided yourXenApp and XenDesktop license remains valid (unexpired). If you upgrade to a later version of Citrix SCOM ManagementPack for XenApp and XenDesktop whose Subscription Advantage Eligibility date is, for example, 2016.0710 (meaning 10 July2016), Citrix SCOM Management Pack for XenApp and XenDesktop stops gathering and reporting new data (topologyupdates, incoming alerts, newly discovered objects).Renewal af ter expired XenApp and XenDesktop LicenseIt may take up to 24 hours for the Citrix SCOM Management Pack Agent for XenApp and XenDesktop instances to detectrenewal of an expired Platinum license in the XenApp and XenDesktop Site. After such license renewal, to restore licensingcoverage of XenApp and XenDesktop on Delivery Controllers (agent-managed computers) immediately, do the following:1. On a Delivery Controller, stop the Citrix MPXAXD Agent service by using an operating system tool.2. From the db subfolder of the Agent's data files folder (%ProgramData%\Citrix\XenDesktop MP Agent by default),remove the agent-license-info.json file.3. Start the Citrix MPXAXD Agent service again.4. Repeat steps 1 to 3 on each additional Delivery Controller.UpgradingNote: Product versions earlier than 3.6 were released under the name Comtrade Management Pack f or Citrix XenAppand XenDesktop.Upgrade is available for versions 3.5 and later. During the upgrade process, the included management packs of an earlierproduct version are automatically upgraded; their prior removal is not required. Your management pack customization ispreserved.Caution:Before upgrading from an earlier product version, ensure that licensing of this version of Citrix SCOM Management Packfor XenApp and XenDesktop is covered. For instructions on how to verify licensing coverage, see Preparing forInstallation in Install and Configure.Upgrading to an unlicensed version of Citrix SCOM Management Pack for XenApp and XenDesktop results in ceasedprocess of gathering and reporting new data. T he data already collected is preserved and remains available to SCOM. Ifthis occurs, downgrading to the earlier (licensed) product version requires a complete uninstallation of the new productversion (including removal of the included management packs from SCOM), followed by reinstallation of the earlierproduct version. T he management pack removal from SCOM deletes all the operational data (alerts, events, performancedata) while the reinstallation ensures continued availability of data in the SCOM data warehouse (reports).For upgrade instructions, see Upgrade in Install and Configure.https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.8
System requirementsNov 27, 20 17Before installing Citrix SCOM Management Pack for XenApp and XenDesktop, make sure that your environment meets therequirements listed in this topic.Hardware requirementsComputers that will host Citrix SCOM Management Pack Machine Agent for XenApp and XenDesktop must meet thefollowing minimum hardware requirements:One physical CPU with two cores (for physical systems), two virtual CPUs (for virtual systems); CPU clock speed of 2.3 GHz4 GB of RAM (excluding the paging file size)1 GB of free local storage spaceFor more information on the Machine Agent, see Install and Configure.Sof tware requirementsCitrix SCOM Management Pack for XenApp and XenDesktop requires a supported version of the following products that itintegrates with:Citrix XenApp and XenDesktopMicrosoft System Center Operations ManagerAdditionally, Citrix SCOM Management Pack for XenApp and XenDesktop requires a supported version of Citrix Licensing inthe XenApp and XenDesktop Site where it is deployed.Make sure that the following software is available on the DeliveryControllers:In addition, make sure that the following software is available on the Delivery Controllers:Microsoft .NET Framework 4.5.2 or laterMicrosoft's Visual C Redistributable Packages for Visual Studio 2013Supported versions of Citrix XenApp and XenDesktopCitrix SCOM Management Pack for XenApp and XenDesktop is compatible with the following Citrix XenApp andXenDesktop versions:Product version (Delivery Controller)SupportedCitrix XenApp and XenDesktop 7.16 Citrix XenApp and XenDesktop 7.15 LT SR Citrix XenApp and XenDesktop 7.14 Citrix XenApp and XenDesktop 7.13 https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.9
1Citrix XenApp and XenDesktop 7.12 Citrix XenApp and XenDesktop 7.11 Citrix XenApp and XenDesktop 7.9 Citrix XenApp and XenDesktop 7.8 Citrix XenApp and XenDesktop 7.7 Citrix XenApp and XenDesktop 7.6 LT SR Citrix XenApp and XenDesktop 7.61 Citrix XenApp and XenDesktop 7.5 Citrix XenApp and XenDesktop 7.1 Citrix XenApp and XenDesktop 7.0 T his entry covers the following configurations: 7.6, 7.6 FP1 (Feature Pack 1), 7.6 FP2, 7.6 FP3.Product version (Citrix Director)Supportedversions included with the supported Delivery Controller versions Supported Citrix Licensing versionsCitrix SCOM Management Pack for XenApp and XenDesktop can be deployed in environments where any of the followingversions of Citrix Licensing is used:Product versionCitrix Licensing 11.14 or laterSupported Supported versions of SCOMCitrix SCOM Management Pack for XenApp and XenDesktop is compatible with the following SCOM versions:https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.10
Microsof t System Center Operations Manager version1SupportedMicrosoft System Center Operations Manager 2016 Microsoft System Center Operations Manager 2012 R2 Microsoft System Center Operations Manager 20121 T his entry covers the following configurations: base release, base release SP1 (Service Pack 1).Supported operating systemsAgent operating systemsCitrix SCOM Management Pack Agent for XenApp and XenDesktop is compatible with all operating systems that aresupported by Delivery Controller of Citrix XenApp and XenDesktop.Machine Agent operating systemsCitrix SCOM Management Pack Machine Agent for XenApp and XenDesktop is compatible with the following operatingsystems:Operating systemSupportedMicrosoft Windows Server 2016 Microsoft Windows Server 2012 R2 Microsoft Windows Server 2012 Regional settings supportT he product can be deployed and operates correctly in environments with regional setting configured to use any of thefollowing languages:LanguageLanguage codeSupportedEnglishen Spanishes https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.11
Performance overviewNov 27, 20 17Generally speaking, Citrix SCOM Management Pack for XenApp and XenDesktop consists of three parts:T he part installed on the SCOM management server (mandatory)Citrix SCOM Management Pack Agent for XenApp and XenDesktop (mandatory)Citrix SCOM Management Pack Machine Agent for XenApp and XenDesktop (optional)The SCOM management server-side partT his part, a collection of management packs includes discoveries, monitors, rules, tasks, and reports. T his part does notsignificantly add to the basic resource requirements (CPU and memory) of the SCOM management server. It is not resourceintensive in terms of storage requirements on the SCOM reporting data warehouse database. Hence, the SCOMmanagement-server part does not require a specific configuration to monitor larger Citrix XenApp and XenDesktopenvironments.Citrix SCOM Management Pack Agent f or XenApp and XenDesktopPerformance and resource consumption of Citrix SCOM Management Pack Agent for XenApp and XenDesktop primarilydepend on the size of your XenApp and XenDesktop environment, specifically on the number of resources within each Site.Furthermore, they are influenced by the load on the Delivery Controller instances. In contrast, the number of Sites in yourXenApp and XenDesktop environment has no influence on the performance and resource consumption.For scaling up Citrix SCOM Management Pack Agent for XenApp and XenDesktop, the hardware of the hosting DeliveryController must be reconfigured. T he Agent cannot be scaled out.Citrix SCOM Management Pack Machine Agent f or XenApp and XenDesktopT he product's Machine Agent can be scaled up without the need of altering XenApp and XenDesktop deployment, as noXenApp and XenDesktop component is installed on its proxy node. Machine Agent can also be scaled out; you can achievethis by installing multiple instances on multiple proxy nodes and configuring it such that each Machine Agent instancehandles only a subset of all Delivery Controller instances.Configuration specificationsAll figures in this document are valid for environments that:Are monitored with the specified product version of Citrix SCOM Management Pack for XenApp and XenDesktopMatch the documented configuration specifications for XenApp and XenDesktop and SCOMUse the default configuration of management packs in terms of which rules and monitors are enabled (this applies tomanagement packs included in Citrix SCOM Management Pack for XenApp and XenDesktop and management packsbundled with SCOM). In addition:Disable VDA service monitoringEnable connectors when the environment contains more than 600 Server OS machines. For more information onconfiguring connectors, see Configuring SCOM Administrator.Increase the monitoring interval of Citrix MPXAXD Machine Agent. For more information, see Increasing discoveryhttps://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.12
interval of Citrix MPXAXD Machine Agent in Configuration for large XenApp and XenDesktop environments.Use the default configuration of SCOM management server and SCOM agents, without fine-tuning or any specialadjustment.For the product to work with the scale of the environment documented here, it is recommended that you configure theSCOM agent on all controllers. For environments with approximately 15,000 VDAs and/or around 25,000 sessions (DesktopOS and Server OS) or more, follow the recommended configuration steps in Configuration for monitoring large XenAppand XenDesktop environments.Validated Citrix SCOM Management Pack f or XenApp and XenDesktop versionValidation of Citrix SCOM Management Pack for XenApp and XenDesktop was performed with the product version listed inthe following table.ProductVersionCitrix SCOM Management Pack for XenApp and XenDesktop3.14Citrix XenApp and XenDesktop configuration specificationWith this configuration, the Site database server is deployed outside the Delivery Controller computer.Computer: Delivery ControllerSpecif ication itemValueComputefour virtual CPUs; CPU clock speed of 2.67 GHzMemory16 GB of RAMSoftware versionCitrix XenApp and XenDesktop 7.14.1Computer: Site database serverSpecif ication itemValueComputefour virtual CPUs; CPU clock speed of 2.67 GHzMemory24 GB of RAMSoftware versionMicrosoft SQL Server 2014 R2https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.13
Microsof t System Center Operations Manager configuration specificationWith this configuration, the SCOM database and data warehouse server is deployed outside the SCOM management servercomputer.Computer: SCOM management serverSpecif ication itemValueComputeeight virtual CPUs; CPU clock speed of 2.67 GHzMemory16 GB of RAMSoftware versionMicrosoft System Center Operations Manager 2012 R2Computer: SCOM database and operations management serverSpecif ication itemValueComputeeight virtual CPUs; CPU clock speed of 2.67 GHzMemory24 GB of RAMSoftware versionMicrosoft SQL Server 2014Computer: SCOM database and data warehouse serverSpecif ication itemValueComputeeight virtual CPUs; CPU clock speed of 2.67 GHzMemory24 GB of RAMSoftware versionMicrosoft SQL Server 2014https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.14
Computer: SCOM reporting databaseSpecif ication itemValueComputefour virtual CPUs; CPU clock speed of 2.67 GHzMemory8 GB of RAMSoftware versionMicrosoft SQL Server 2014 R2Monitoring ability of Citrix MPXAXD AgentT he following table lists the maximum values at which the Citrix MPXAXD Agent part of Citrix SCOM Management Pack forXenApp and XenDesktop was successfully validated. T he product might be able to monitor environments larger than statedbelow. However, this hasn't been tested.Maximum number of monitored items (per Site)ItemValueDelivery groups300Server OS machines2000Server OS machines in a delivery group200Desktop OS machines36,000Applications2,500Concurrent sessions68,000 (36,000 Desktop OS sessions 32,000 Server OS sessions)Average resource consumptionResource consumption was measured in a XenApp and XenDesktop Site with six Delivery Controller instances. T hemeasurement was made on the Delivery Controller where Citrix SCOM Management Pack Agent for XenApp andXenDesktop did most data processing. Measuring spanned a period of 2.5 days. Windows Performance Monitor was usedas the measuring tool.Important: In XenApp and XenDesktop deployments with multiple Delivery Controller instances, the majority of datahttps://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.15
processing is performed by a single instance of Citrix SCOM Management Pack Agent for XenApp and XenDesktop (on oneDelivery Controller). Resource consumption is documented only for the primary controller, as the other controllers in the Sitehave minimal resource usage.Average consumption on a Delivery Controller (f or 38,000 VDIs)Item1ValueMPXAXDAgent CPU usage110.62%HealthService CPU usage1.90%MonitoringHost CPU usage3.88%MPXAXDAgent memory usage1480 MBHealthService memory usage174 MBMonitoringHost memory usage240 MBCPU usage is calculated based on the % Processor Time counter and the number of processor cores or virtual CPUs.T he number of published applications has a negligible effect on the CPU usage of the MPXAXDAgent service.T he following figure shows changes in CPU usage of MPXAXDAgent , HealthService and MonitoringHost after theseservices had been started for the first time. Values are taken from the first part of the entire measurement time period (firstfour hours), when initial high data inflow loaded compute resource substantially. After first three hours, initial high loaddecreased significantly.https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.16
T he following figure shows typical patterns of changes in CPU usage of MPXAXDAgent , HealthServiceand MonitoringHost through a major part of the measurement time period, after the initial high load had already subsided.https://docs.citrix.com 1999-2017 Citrix Systems, Inc. All rights reserved.p.17
As the figure above shows, bursts of high CPU usage of MPXAXDAgent occured every five minutes, while spikes of high CPUusage of HealthService and MonitoringHost were not periodical.T he following
With the Citrix SCOM Management Pack for XenApp and XenDesktop you will get more insight into which users are logging in to the virtual desktops and applications (identify slow logons and logon bursts), how many users are connecting to the Sites, if the infrastructure is able to handle all user requests accordingly, for example byFile Size: 3MB
