This article contains information about Load Manager rules.
Load Manager Rules
The Advanced Load Manager feature included with MetaFrame Advanced Edition (XPa) and MetaFrame Enterprise Edition (XPe) allows administrators to combine individual rules into load evaluators for highly customized load management.
The following individual rules can be configured as part of a load evaluator:
Application User Load
This rule allows the load evaluator to calculate a load based on the number of users accessing a specific published application on the attached server.
When the number of users accessing the published application is less than or equal to the threshold value indicated here, Load Manager reports a load percentage based on the threshold value.
The valid range for this rule is 1 to 10000.
Context Switches
This rule allows the load evaluator to calculate a load based on the CPU context switches. A context switch occurs every time the operating system switches from one executing process to another.
The valid range for the high and low thresholds is 0 to 2147483647.
CPU Utilization
This rule allows the load evaluator to calculate a load based on CPU utilization.
The valid range for the high and low thresholds is 0 to 100.
Disk Data I/O
This rule allows the load evaluator to calculate (in kilobytes) a load based on the disk I/O throughput.
The valid range for the high and low thresholds is 0 to 2147483647.
Disk Operations
This rule allows the load evaluator to calculate a load based on the number of disk operations per second.
The valid range for the high and low thresholds is 0 to 2147483647.
IP Range
This rule allows the load evaluator to enable or disable access to a published application based on whether the IP addresses of the ICA Clients are within the specified IP address ranges
Formula for matching clients with the specified ranges:
If the IP address of the ICA Client is greater than or equal to the specified [Starting IP Address] AND the IP address of the ICA Client is less than or equal to the specified [Ending IP Address], the client is considered to be a part of the specified range and action is taken depending on the inclusion or exclusion mode.
Use this rule in conjunction with another rule. This rule will not load balance connections by itself.
License Threshold
This rule allows the load evaluator to calculate a load based on the number of assigned or pooled connection licenses used on each server.
To indicate that a license type is to be ignored, enter zero for the license type. You can enter zero for only one of the license types.
The valid range for the high threshold is 0 to 9999.
Memory Usage
This rule allows the load evaluator to calculate a load based on memory utilization.
The valid range for the high and low thresholds is 0 to 100.
Page Fault
This rule allows the load evaluator to calculate a load based on the number of page faults per second. A page fault occurs every time the operating system accesses physical memory that has been flushed to disk.
When the number of page faults per second is within the low and high thresholds, Load Manager reports a load percentage based on the threshold values.
When the number of page faults per second exceeds the high threshold, Load Manager reports full load. When the number of page faults per second is less than the low threshold, Load Manager reports no load.
The valid range for the high and low thresholds is 0 to 2147483647.
Page Swap
This rule allows the load evaluator to calculate a load based on the number of page swaps per second. A page swap occurs every time the operating system swaps physical memory to virtual memory on disk.
The valid range for the high and low thresholds is 0 to 214748364.
Scheduling
This rule allows the load evaluator to enable and disable availability of a server or published application during certain days of the week and certain hours of the day.
The squares are indicated in half hour time blocks. Filled squares are enabled and white squares are disabled.
Use this rule in conjunction with another rule. This rule will not load balance connections by itself.
For example:
The following output displays the first connection with the default load evaluator:
C:\>qfarm /load
Server Name Server Load
-------------------- ------------
FTLRDRINEHAR11 100
The following output displays the second connection with the default load evaluator:
C:\>qfarm /load
Server Name Server Load
-------------------- ------------
FTLRDRINEHAR11 200
The following output was displayed with just the Scheduling load evaluator rule. The two (2) original connections were still active:
C:\>qfarm /load
Server Name Server Load
-------------------- ------------
FTLRDRINEHAR11 0
The following output was displayed after applying the Server User Load and Scheduling load evaluator rules. The two (2) original connections were still active (this is the expected result until 6 P.M when the server is still available).
C:\>qfarm /load
Server Name Server Load
-------------------- ------------
FTLRDRINEHAR11 200
The following output was displayed after applying the Server User Load and Scheduling load evaluator rules. The two (2) original connections were still active (this is the expected result after 6 P.M when the server is unavailable).
C:\Documents and Settings\Administrator.UOFM>qfarm /load
Server Name Server Load
-------------------- ------------
FTLRDRINEHAR11 10000

Server User Load
This rule allows the load evaluator to calculate a load based on the number of users on an attached server.
The valid range for the high threshold is 1 to 10000.
Additional Resources
CTX112082 –
Troubleshooting Load Balancing Issues