The Client Request Handling node monitors the ability of Application Virtualization Server to handle and correctly respond to requests coming from Clients. These requests include desktop configuration requests, package loading requests, out of sequence requests, etc.
The Client Request Handling node monitors the ability of Application Virtualization Server to handle and correctly respond to requests coming from Clients. These requests include desktop configuration requests, package loading requests, out of sequence requests, etc.
Resolutions
The maximum number of simultaneous client connections that are allowed on an Application Virtualization server is determined by multiplying the maximum client connection per core process, by the number of configured core processes. The default maximum client connection per core is 1000 and is not configurable.
The number of core processes is set to 5 at install time by default. The number of core processes is configurable after install through the Application Virtualization Management Console.
For more information on the Application Virtualization Sever configuration that may need adjustment, please refer to the content on http://go.microsoft.com/fwlink/?LinkId=122170
Target | Microsoft.AppVirtualization.Server.45.VirtualApplicationServer | ||
Parent Monitor | Microsoft.AppVirtualization.Server.45.ClientRequestHandling.HealthState | ||
Category | EventCollection | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | MatchMonitorHealth | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.Windows.SingleEventLogManualReset2StateMonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |
<UnitMonitor ID="Microsoft.AppVirtualization.Server.45.VirtualApplicationServer.ClientRequestHandling_Adjustmaximumsimultaneousclientconnections_Application" Accessibility="Public" Target="Microsoft.AppVirtualization.Server.45.VirtualApplicationServer" TypeID="Windows!Microsoft.Windows.SingleEventLogManualReset2StateMonitorType" ParentMonitorID="Microsoft.AppVirtualization.Server.45.ClientRequestHandling.HealthState">
<Category>EventCollection</Category>
<AlertSettings AlertMessage="Microsoft.AppVirtualization.Server.45.VirtualApplicationServer.ClientRequestHandling_Adjustmaximumsimultaneousclientconnections_Application.Alert">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="EventRaised" MonitorTypeStateID="EventRaised" HealthState="Error"/>
<OperationalState ID="ManualResetEventRaised" MonitorTypeStateID="ManualResetEventRaised" HealthState="Success"/>
</OperationalStates>
<Configuration>
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Application Virtualization Server</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">41997</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</Configuration>
</UnitMonitor>