AppSense Performance Manager 10.1 Product Guide

Product Guide
Version 10.1 FR1
Ivanti Performance Manager 10.1 FR1 Product Guide
Copyright Notice
This document contains the confidential information and/or proprietary property of Ivanti, Inc. and its
affiliates (referred to collectively as “Ivanti”), and may not be disclosed or copied without prior written
consent of Ivanti.
Ivanti retains the right to make changes to this document or related product specifications and
descriptions, at any time, without notice. Ivanti makes no warranty for the use of this document and
assumes no responsibility for any errors that can appear in the document nor does it make a
commitment to update the information contained herein. For the most current product information,
please visit www.ivanti.com.
Copyright © 2003-2017, Ivanti. All rights reserved.
Ivanti and its logos are registered trademarks or trademarks of Ivanti, Inc. and its affiliates in the
United States and/or other countries. Other brands and names may be claimed as the property of
others.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 2 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Table of Contents
Product Guide
Copyright Notice
Table of Contents
What's new in Performance Manager?
Performance Manager Features
Application and Process Discovery
Application Groups
User Groups
Conditions
CPU Resource Management
Memory Management
Licensing
Auditing
Configuration Profiler
Working in Passive Mode
Licensing
Managing Licenses
Export License Files
Import License Files
Troubleshooting
Service Packs
Installing Service Packs
Rolling Back Service Packs
Managing Configurations
Open, Save and Export Configurations
Preset Configurations
Using System Center Configuration Manager for Configurations
Configuration Profiler
Resolve Configuration Violations
Feature Options
Feature Usage
Application Memory
Excluded Applications
Multi-process Applications
General
Application Groups
Create Application Groups Manually
Create Application Groups Using Application Discovery
Resource Planning
Evaluation Order
Resource Planning Nodes
Resource Planning Sub-nodes
Windows Fair Share
1
2
3
5
6
6
6
6
6
7
8
8
8
8
9
10
10
12
12
12
13
13
14
15
15
17
18
19
21
22
22
23
24
25
26
28
29
31
33
33
33
35
41
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 3 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Thread Throttling
Configure Thread Throttling
Include System Processes in Thread Throttling
Auditing
Local Events
Environment Variables
Streamed Applications
42
43
45
46
46
50
51
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 4 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
What's new in Performance Manager?
Console rebrand to Ivanti
The Performance Manager console has been updated to reflect the new company name of Ivanti.
You may still see references to the AppSense name used in certain areas, such as the Registry or
Windows Services.
Console refresh
The Performance Manager console has an icon set update in response to customer feedback on the
10.0 console.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 5 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Performance Manager Features
Application and Process Discovery
Application Discovery allows you to automatically populate Application Groups with Desktop
Applications, Services or 16-bit Applications. You can select items to include in an Application Group
from the results of a discovery, which are displayed in categories based on application type:
l
Desktop Applications discovers Installed Applications, Running Processes and File Types.
l
Services discovers Installed Applications and Services.
l
16-bit Applications discovers 16-bit Applications by searching running NTVDM services for the
specified 16-bit applications to run as if they were executed on a DOS machine) services for the
specified 16-bit applications.
NT Virtual DOS Machine. Allows 16-bit applications to run as if they were being
executed on a DOS machine.
64-bit Windows operating systems do not support 16-bit applications.
Application Groups
Application Groups are groups of Desktop Applications, Services or 16-bit Applications. You can
define Application Groups to create custom lists of applications which you assign to rules for
managing the demand on CPU, memory or resources. The groups indicate specific files or folder
names, and path and command line attributes with pattern matching, using wildcards and regular
expressions.
Desktop Applications, services or 16-bit applications can be collated to create Application Groups
which can be automatically populated using the Application Discovery function.
User Groups
User Groups are a generic way to refer to a single Windows user account or Windows Group within
the Performance Manager console. As an Administrator you can use one or more User Groups to
customize the way Performance Manager is deployed across your network.
Conditions
Use Conditions to define criteria for when resources are allocated to applications or users. Conditions
depend on a match with the state of the window, session or desktop, or combinations of each.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 6 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
CPU Resource Management
CPU Management controls the distribution of CPU resources to applications and users on the system,
and includes the following:
l
l
l
l
l
Share Factors – Allocate relative proportions of the CPU resources to applications and users.
Share factors ensure optimum performance at peak load and continuously regulate the fair
distribution of available processor resources.
Reservations – Ensure that certain applications and users are guaranteed specific levels of CPU
resources, as the need arises. At times of peak demand on the system, the minimum reserved
resources are obtained and the remaining resources are reallocated according to share factors
allocated to other applications.
Limits – Prevent certain applications and users exceeding specific levels of CPU capacity when
others demand their share. CPU intensive use can be managed by Hard Limits or Soft Limits.
Hard limits are fixed proportions of the processor load beyond which applications and
users cannot exceed even when spare capacity is available. Soft limits are more flexible and only
confine applications and users within certain levels during peak load to free up resources.
When general demand falls back again and resources are released, controlled applications and
users can exceed limits and resume more CPU intensive activity.
CPU Affinity – Assigns Application Groups and User Groups to specific CPUs when operating
on multiprocessor servers.
Thread Throttling – Patented technology which dynamically clamps processor intensive tasks
when CPU load is too heavy whilst including flexible settings for modifying thresholds and
ranges.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 7 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Memory Management
Memory Management controls the distribution of memory resources on the system and includes the
following:
l
l
l
Hard Limits - Are always imposed and used to define proportions of the processor load
beyond which applications cannot exceed even when spare capacity is available.
Soft Limits - Are less rigid then Hard Limits and only confine applications within certain levels
during peak load to free up resources.
Application (Virtual) Memory Limits – Sets limits on memory use on a per application basis
and allows you to close or terminate applications when allocated memory limits are exceeded.
The Close option generates a prompt to the user to close an application after the specified
period. The Terminate option forces the application to stop after the specified period.
The Terminate option will result in the loss of data for the application being
terminated.
l
Physical Memory Limits – Sets limits on the use of physical memory by applications. Minimum
limits guarantee adequate resources are available ensuring applications function correctly.
Maximum limits prevent resource intensive applications from causing congestion on the
system.
You can also select application memory trimming to reduce unnecessary consumption at
process startup and when the state of the application window, user session or desktop
changes.
Licensing
Use the DesktopNow Licensing console to manage the licenses for your Performance Manager
installation.
Auditing
The Auditing node is used to configure event logging. Settings allow you to specify where to log
events and which events to include in the audit. Auditing can also be managed in the Management
Center.
See the Management Center Help for more information.
Configuration Profiler
The Home tab includes the Configuration Profiler option for displaying a summary report of the
Performance Manager configuration rules. The reports can be used to analyze configurations before
implementing them on a live system.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 8 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
The Configuration Profiler report includes the details of Feature Options, Application Groups,
Resource Planning, and Thread Throttling.
Working in Passive Mode
Each of the Performance Manager configuration settings can be optionally set to monitor
performance control actions affecting processor and memory utilization before you commit to the
policies for taking corrective action.
In Passive mode, auditing data continues being recorded, when enabled in the configuration, except
for CPU Share Factors, Reservations and Soft limits.
You can apply Passive Mode to each feature using the Feature Options dialog which you access by
selecting Options on the Resources Setup ribbon. You can also include or exclude system processes
for certain features in this dialog.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 9 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Licensing
DesktopNow Licensing console allows you to manage DesktopNow product licenses.
The Licensing console allows you to:
l
l
l
Manage licenses for single products, the DesktopNow Suite and Evaluation mlicenses.
Export license packages to MSI or LIC file format for saving to the Management Center or other
computers which can be remotely accessed.
Import and manage licenses from LIC file format.
For information about license deployment to endpoints, see Management Center Help.
Managing Licenses
License details are included in the License Agreement which is issued when an order for the software
has been completed.
The License Agreement includes the following information:
l
Product, Feature, and Version Details
l
Issue Date
l
Expiry Date
l
Customer Name
l
Serial ID
Together with the license agreement you will receive either a TXT file or a LIC file. Use these in the
Licensing Console to add or import the license.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 10 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Add a License
1. Open the Licensing console.
2. Click Add.
The Add License Key dialog displays.
3. Enter the License Key and click Add.
If you received a TXT license file, open the file and copy the license key, paste it in to the Add
License Key dialog.
If you received a LIC license file, refer to "Import License Files" on the next page.
Details of the license are displayed in the console and the license key is added to the following
location:
%ALLUSERSPROFILE%\AppSense\Licenses
Activate a License
Once added, some licenses require activating.
1. Select a license or add one to the licensing console.
2. Click Activate.
3. Type or copy and paste the activation code.
4. Press Enter to accept the code.
The license console saves the license key to the MS Windows registry on the local machine. The License
Status field updates to show the status of the license and the license details display in the lower part
of the console.
To check that the license is active on your endpoint, search the registry for the license code. If
the search finds the code, then the license is active.
Remove a License
1. Highlight the required license and click Remove.
A confirmation dialog displays.
2. Click Yes to confirm.
The selected license is deleted and removed from the console and the MS Windows registry or
%ALLUSERSPROFILE%AppSense\Licenses location, whichever is applicable to the license type.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 11 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Export License Files
Export licenses to an MSI or LIC file to create a backup and enable distribution to other endpoints
using the Licensing console or the Management Center.
1. Highlight the license you want to export.
2. Click Export to display Windows Save As dialog.
3. Browse to the required location to save the license file.
4. Enter a name for the file.
5. Select the file type: MSI or LIC.
6. Click Save.
A file is created and saved in the selected location. This file can be copied to any network location and
loaded via the DesktopNow Suite Licensing console or in the Management Center console.
Import License Files
Import a previously exported license to an endpoint using the Licensing console.
1. Open the Licensing console.
2. Click Import to display the Windows Open dialog.
3. Navigate to the required LIC file.
4. Click Open.
Details of the license are displayed in the console and the license key is added to the following
location:
%ALLUSERSPROFILE%\AppSense\Licenses
Troubleshooting
I received an license, what do I do?
If you have received a product license you can load the license by launching the DesktopNow Suite
Licensing Console on your client computer and entering the license code.
I have entered an license, but it says it is not activated, why?
Pre version 10.0 product licenses require activation before they can be used. Activation codes are
provided by Ivanti. Activate a license by entering the License and Activation codes into the console.
Post version 10.1 product licenses do not require an activation code.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 12 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Service Packs
Service Packs are self contained packages or patches that are used to update specific files within a
DesktopNow application without reinstalling the full application. Service packs can be applied more
often and reduce the need for system restarts on your endpoints. Service packs are delivered as a
Windows Installer patch (MSP) file and are often referred to as patch files.
Installing Service Packs
Service Packs can be installed or deployed using the same technology and techniques used when
installing MSIs. Both Microsoft System Center and the Management Center 8 FR4 or later can deploy
MSPs. If neither of these products are available, service packs can be installed using the command line
interface.
For example, the command:
msiexec.exe /p PerformanceManagerAgent64.msp
installs any files that have been amended as part of the patch for just Performance Manager 64 bit
agent.
The following command installs the base version of the Performance Manager Agent (MSI) and the
Performance Manager patch file (MSP) simultaneously:
msiexec.exe /i PerformanceManagerAgent64.msi PATCH=c:\fullpath\PerformanceManagerAgent64.msp
A base version must be installed before the patch file can be applied.
If the patch file contains driver or hook files that are currently in use on the machine the patch is being
applied to, you are informed that a reboot is required. If you chose to continue, the system is restarted
when the patch has been applied.
For information on installing and upgrading service packs using Management Center, see the
Management Center Help.
Installation Order and Dependencies
It is recommended that all components of a service pack are installed.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 13 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Rolling Back Service Packs
There are two ways to roll back, or uninstall Service Packs:
l
Using the Windows Control Panel Programs and Features.
l
Using Management Center 8 FR4 or later
Rolling Back Service Packs Using Management Center 8 FR4 or Later
1. In the Management Center console, select Overview > Deployment Groups tab >
Deployment Groups.
2. Highlight the Deployment Group and select Settings > Assigned Packages.
The Assigned Packages work area displays a list of all the products and their associated
packages.
3. Highlight the required Performance Manager service pack and click Unassign from the Actions
menu.
4. Click Review and Submit.
The Submit Changes dialog displays.
5. Check the details are correct and click Submit.
The patch is unassigned based on the deployment group Installation Schedule.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 14 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Managing Configurations
Performance Manger configuration files (APMP files) contain the policies for managing performance
and resources on an endpoint. The Performance Manager Agent checks the rules contained within
the configuration to determine the actions to take for managing performance.
Configurations are stored locally in %PROGRAMDATA%\AppSense\Performance Manager.
If using just the Performance Manager product, configuration changes are written directly to the local
APMP file from the Performance Manager console. If you are using Performance Manager as part of
the DesktopNow suite of products with Management Center, configurations are created and stored
centrally in the Management Center database and distributed to endpoints in MSI format.
Configurations can also be exported and imported to and from MSI format, which is useful for
creating templates or distributing configurations using third party deployment systems.
Open, Save and Export Configurations
The File menu, in the top left-hand corner of the console, allows configurations to be opened, saved,
imported and exported. Performance Manager saves configurations in APMP (AppSense Performance
Manager Package) file format.
The following options are available:
Option
Description
New
Creates a new default configuration which is locked for editing.
Open
Opens an existing APMP configuration file for editing from one of the
following locations:
Save
l
Live configuration on this computer.
l
Configuration from the Management Center.
l
Configuration from System Center Configuration Manager.
l
Configuration file from disk.
The Save options are specific to the use of the configuration with the
Management Center:
l
l
Save and continue editing - Saves the configuration and keeps it
locked whilst open for editing. Configurations cannot be deployed
whilst locked.
Save and unlock - Saves the configuration and unlocks it to allow
deployment. The current configuration closes and a new default
configuration opens.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 15 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Option
Description
l
Save As
Saves the configuration with a new name to one of the following locations:
l
l
l
l
Import and Export
Unlock without saving - Unlocks the configuration without saving any
changes made. The current configuration closes and a new default
configuration opens.
l
l
Live configuration on this computer - Save the current configuration
on the current computer and apply it as the working configuration.
Configuration in the Management Center - Creates the current
configuration in the package store on the selected Management
Center.
Configuration in System Center Configuration Manager - Saves your
configuration to the specified System Center Configuration Manager
server.
Configuration file on disk - Saves the current configuration as a file on
a local or network drive in APMP format.
Import configurations from MSI - Imports a configuration from an
existing MSI package, for example, legacy configurations which have
been exported and saved from legacy Consoles.
Export configuration as MSI - Exports the current configuration as an
MSI package.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 16 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Preset Configurations
When the Performance Manager Console is opened or a new configuration is created, preset
configurations are available to cater for most types of environments. If the presets do not meet the
requirements of your environment, configurations can be created manually.
The following preset configurations are available:
l
l
l
l
General Purpose - This configuration is optimized for general purpose use. Thread Throttling is
configured for all non-system processes and CPU priority is given to system processes.
Physical Desktop - This configuration is optimized for physical desktops. Thread Throttling is
configured for all processes and CPU priority is given to system processes. CPU Reservations
and Application Memory Limits features are enabled.
Terminal Services / Remote Desktop Services (RDS) - This configuration is optimized for
Terminal Services/Citrix XenDesktop environments. Thread Throttling is configured for all
processes. CPU Reservations, Application Memory Limits and Physical Memory Control are all
enabled.
Virtual Desktop Infrastructure (VDI) - This configuration is optimized for VDI environments.
Thread Throttling is configured for all processes. CPU Reservations, Application Memory Limits
and Physical Memory Control are all enabled.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 17 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Using System Center Configuration Manager for
Configurations
System Center Configuration Manager (SCCM) is a systems management software product by
Microsoft for managing large groups of Windows-based computer systems. Configuration Manager
provides the following:
l
Remote control
l
Patch management
l
Software distribution
l
Operating system deployment
l
Network access protection
l
Hardware and software inventory
For more information on System Center Configuration Manager, see Configuration Manager.
Performance Manager allows configurations to be opened and saved using System Center
Configuration Manager version 2012 onwards.
Connect to System Center Configuration Manager Server
When opening or saving a configuration to SCCM, a dialog displays and allows you to connect to a
System Center Configuration Manager Server and maintain a list of servers.
The following settings are available:
l
l
l
New Server – Click to add a new server to the list by providing details in the Add System Center
Configuration Manager Server dialog, including friendly name, server name (computer name or
IP address). Use the Location field to specify the network location to be used to store your
configuration files. The configuration location should be readable for the users who are to view
the configuration or writable for those users who will be saving configurations.
Edit Server – Click to edit a listed server by providing details in the Edit Server dialog, including,
friendly name, server name and edit the location that your configuration are to be stored on
your network.
Delete Server – Remove the highlighted server from the list.
Highlight the server you want to connect to, click Connect and provide credentials for connecting to
the selected server, either using the currently connected user account or a custom user. You can
browse for a user on the active directory or local network, provide a password and, where
appropriate, the domain.
To use SCCM remotely, some additional configuration is required. For further information, see
Configure DCOM Permissions for Remote Configuration Manager Console Connections.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 18 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Configuration Profiler
The Configuration Profiler, available from the Home ribbon, allows administrators to produce detailed
reports on configurations. This can be done whether they are stored locally or centrally. The reports
can be a general study of the overall configuration or can be aimed at how it interacts with a specific
user, group of users or specific file.
This section provides details about the reports generated by the Configuration Profiler, and includes
the following:
Report Type
The configuration profiler allows you to report on the configuration currently open in the
console. General reports are produced to assist auditing and compliance such as Sarbanes Oxley or
HIPAA. You can produce custom reports to assist in troubleshooting large configurations.
The configuration profiler is a reporting tool that can be used to generate quick reports based on the
details of a product configuration which is currently open. The report can be generated in the
following ways:
l
l
Complete Report – produces a report which Includes all aspects of the configuration.
Report based on specific criteria – produces a report based on the specified criteria as selected
in the Report Criteria section.
Enter an asterisk (*) to see all actions controlled by a particular type of condition.
Report Criteria
Use the criteria to specify what is to be included in the report.
Enter the value or select an option to match for any of the following:
l
User/Group – enter the name of a user or user group you wish to include in the report.
l
Application – enter the name of an application you wish to include in the report.
l
Application Group – select an application group to include in the report or select the asterisk
(*) to produce output for all groups.
l
CPU – select Include or Exclude to show or hide CPU settings in the report.
l
Memory – select Include or Exclude to show or hide Memory settings in the report.
The User/Group and Application fields support wildcard character matching using the
asterisk (*) and question mark (?) characters. The asterisk represents zero or more
characters, while the question mark (?) wildcard represents zero or one characters.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 19 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Report Output
Generate a report by selecting Configuration Profiler from the Home ribbon of the console.
The report output is produced in sections and sub-sections covering the following details of the
configuration:
l
l
l
l
Feature Options — Provides details about features which are enabled, in passive mode, or
include system processes.
Application Groups — Provides details of the application groups which you have configured
including the description and path of each application in the group and any command lines
which are applicable.
Resource Planning — Provides details of the resource planning settings for user groups and
Application Groups including CPU, Memory and Disk settings.
Thread Throttling — Provides details of the Thread Throttling settings including CPU monitor,
clamping action and exceptions.
l
The report displays in the Preview window where you can manage the following:
l
File settings: Page Setup, Print, Export (PDF or image file), Send via email (PDF or image file)
l
Background: Color and Watermarks.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 20 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Resolve Configuration Violations
Violations can occur when conflicting values are present in a Performance Manager configuration. If
you attempt to save a configuration with conflicts, the Configuration Violations dialog displays. This
identifies the area of the configuration where the conflict arises and provides a description of the
issue. All issues must be resolved before the configuration can be saved.
The following table provides details of configuration violations that can occur.
Violation Type
Description
Application Group allocated more
than once in the resource plan
In Resource Configuration > Resource Planning, only
one occurrence of an Application group can be allocated
in the resource plan.
User Group allocated more than once
in the resource plan
In Resource Configuration> Resource Planning, only
one occurrence of a user group can be allocated in the
resource plan.
CPU Reservation value exceeds CPU
Limit
In CPU, the Reservation must be less than or equal to the
Limit.
The Physical Memory Minimum limit
exceeds the Maximum
In Memory > Physical Memory the Minimum limit must
be less than or equal to the Maximum limit.
[Clamp CPU by] exceeds [Apply
clamping when CPU reaches].
In Thread Throttling, Clamp CPUby must be less than or
equal to Apply clamping when CPU reaches.
[Do not clamp threads below] exceeds
[Do not clamp processes below].
In Thread Throttling, Do not clamp threads below must
be less than or equal to Do not clamp processes below.
Application Soft Memory Limits has
been enabled but no action has been
selected.
When applying Application Memory Limits to an
Application Group and choosing a soft limit, an action of
either close or terminate must be selected.
CPU Reservations & Limits have been
enabled but a value of zero has been
entered.
When applying CPU Reservations and Limits a value
greater than zero must be entered.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 21 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Feature Options
Performance Manager Feature Options provides system-wide settings that affect all users with the
deployed configuration.
To access the Feature Options, click Options in the Resources Setup ribbon.
l
Feature Usage
l
Application Memory
l
Excluded Applications
l
Multi-process Applications
l
General
Feature Usage
For each Performance Manager feature, specify the following:
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 22 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
l
l
l
Enabled - If selected, the feature is enabled.
Passive Mode - If selected, the feature runs passively in the environment. Performance
Manager makes no changes to the system, however it monitors and raises audit events where
configured.
Include System Processes - If selected, system processes are included for the feature.
Application Memory
Configure the content of the Close and Terminate warning messages. The following settings are
available:
l
l
Close Message Details - Configure the title and message displayed when applications are due
to be closed for exceeding the specified application memory limit.
Terminate Message Details - Configure the title and message displayed when applications are
terminated for exceeding the specified application memory limit.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 23 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Excluded Applications
Add applications to exclude from Share Factor allocations and Thread Throttling policies.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 24 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Multi-process Applications
Add multi-process applications, such as web browsers, to efficiently manage CPU and memory
resources for processes that spawn additional helper processes of the same name.
This feature allows multiple instances of the same process to be consolidated when considering the
window’s state - foreground/background and maximized/minimized. For Microsoft Internet Explorer,
this means each tab can be managed independently. For Google Chrome and other applications,
Performance Manager calculates a summary window state so that the same foreground/background
and minimized/maximized limits are applied to all matching processes based on their compounded
windows state. This applies even if some matching processes have no windows or always have a fixed
windows state, for example, if a helper process is always 'not visible' or in the background.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 25 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
General
Apply general settings such as Share Factor Aggressiveness and Session Idle Timeout.
Specify the following options on the General tab:
l
Share Factor Aggressiveness - Use the slider to set a value for Share Factor Aggressiveness.
This values determines how quickly Performance Manager reacts to changes in the CPU load.
When the slider is set to Max, Performance Manager reacts quickly to the changes in load. This
can cause Performance Manager to take unnecessary action against processes that have brief
spikes in CPU load and cause control over high demand processes to be lifted too soon if they
briefly lower their demand for CPU resources.
When the slider is set to Min, Performance Manager monitors the effects of the changes over
time, rather than taking immediate action. This can cause Performance Manager to take too
long to control high loading CPU processes to free processes from control once they have
definitively transitioned to a state of low CPU demand.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 26 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
l
l
l
System Memory Settings - Set whether overall system memory usage must reach a specified
threshold before memory control is applied. Use the slider to set the threshold level.
Session Idle Timeout - The Session Idle Timeout refers to the period when no keyboard and
mouse activity takes place. This condition can be used in a rule to specify changes in resource
allocations when the idle time reaches a set duration. The default setting is 10 minutes of no
keyboard activity and mouse activity.
Number of CPUs - Set the number of CPUs which can be used in CPU affinity settings in the
CPU tab of a Resource Planning > Resource Allocations node.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 27 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Application Groups
Application Groups are a collection of applications whose CPU, memory and disk resources can be
controlled together. Applications can be added either manually or using Application Discovery.
In the configuration, Application Groups can be combined with specific users to allocate resources at
a granular level. A typical Application Group could contain graphic-intensive applications which utilize
a high proportion of system resources. A rule could be added to allow members of the Graphics
Design team to run these applications with adequate resources.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 28 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Create Application Groups Manually
1. Select Application Groups in the navigation tree.
2. Click Add New from the Resources Setup ribbon.
The Add New Application Group dialog displays.
3. In the Name field, enter a name for the Application Group.
4. From the Type drop-down, select the type of applications to be added to the Application
Group:
o
Desktop Applications.
o
Services.
o
16-bit Applications.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 29 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
5. Click Add New.
6. Enter an executable name, executable path or folder path in the Path field.
Both the asterisk (*) and question mark (?) wildcard characters can be used in the file or folder
path. The asterisk wildcard represents zero or more characters and the question mark wildcard
represents zero or one character.
For example, C:\Folder* matches all executables within C:\Folder.
To convert text to available Environment Variables, click the percentage sign and Convert To
Use Environment Variables after entering the name or path.
7. If the Path field contains regular expressions, select Use regular expressions.
8. To match the command line, select Enable command line matching and enter the relevant
command line.
9. In the Description field, enter a description for the application.
10. Click Next.
The Select Where to Go dialog displays.
11. Select one of the following options:
o
Allocate Resources - Adds the new Application Group to the Resource Planning node so
that rules can be added.
o
Finish - Does not add the Application Group to the Resource Planning node. The
Application Group can be added manually by selecting Add Applications from the
Resources Setup ribbon.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 30 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Create Application Groups Using Application Discovery
Application Discovery can be used to populate Application Groups with installed applications, running
processes or file types.
Application Discovery can be run on the local or a remote computer with the Performance Manager
Agent installed.
1. Select Application Groups in the navigation tree.
2. Click Add New from the Resources Setup ribbon.
The Add New Application Group dialog displays.
3. In the Name field, enter a name for the Application Group.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 31 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
4. From the Type drop-down, select the type of applications to be added to the Application
Group:
o
Desktop Applications.
o
Services.
o
16-bit Applications.
5. Click Discover Applications.
A dialog to select the endpoint displays.
6. Select the endpoint on which to perform the analysis:
o
Select the local machine name to perform an analysis on the local endpoint.
o
Select A remote computer to perform an analysis on a remote computer. The Connect
to a Remote Computer dialog displays. Specify or navigate to the remote computer.
Options are available to navigate to a computer on the network, one in the
Management Center or to a favorite computer.
The Application Discovery dialog displays.
The dialog contains tabs to select installed applications, running processes and file types. It
may take a few minutes to populate the data from the endpoint.
Once the data is populated, select the installed applications, running processes and file types
to add to the Application Group. Filters can be applied by entering text into the Filter field.
7. Click Next.
The Add New Application Group dialog displays.
The selected items from Application Discovery are added to the dialog. Review the contents
and, if necessary, amend the Path, Command Line and Description fields for each application.
8. Click Next.
The Select Where to Go dialog displays.
9. Select one of the following options:
o
Allocate Resources - Adds the new Application Group to the Resource Planning node so that
rules can be added.
o
Finish - Does not add the Application Group to the Resource Planning node. The Application
Group can be added manually by selecting Add Applications from the Resources Setup ribbon.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 32 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Resource Planning
CPU, memory and disk resources are allocated according to the Resource Plan within the
configuration.
Resource Planning nodes are top-level Application Groups or User Groups that define how the overall
system resources are allocated. Each Resource Planning node contains one or more sub-nodes to
match specific Application Groups or User Groups. Each sub-node then contains one or more rules
match application attributes.
Evaluation Order
Performance Manager evaluates items in the following order to apply the Resource Plan:
1. Resource Planning nodes in descending order.
2. Resource Planning sub-nodes in descending order.
3. Resource Planning sub-node rules in descending order.
The arrows in the navigation pane and work area show the order of precedence.
In the above example, the Development node is evaluated first. If the user matches the User Group,
then the sub-nodes under Development are evaluated.
Resource Planning Nodes
Resource Planning nodes are top-level User Groups or Application Groups. Resources are first
allocated to the Resource Planning nodes. Finer control can be applied by adding sub-nodes for
specific Application Groups or User Groups.
Add Resource Planning Nodes Based on User Groups
1. Select the Resource Configuration navigation button.
2. Select Resource Planning from the navigation tree.
3. On the Resources Setup ribbon, click Add Users/Groups and select Select User/Group.
The Select User/Group dialog displays.
4. Choose a user or group using one of the following methods:
o
Enter the name of a user or group in the Name field.
o
Click the percent sign (%) and add an environment variable.
o
Click the ellipses (...) and browse to the user or group.
The User Group is added as a Resource Planning node to enable its resources to be managed.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 33 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Add Resource Planning Nodes Based on Application Groups
1. Select Resource Planning from the navigation tree.
2. On the Resources Setup ribbon, click Add Applications and select an Application Group for
which to create a Resource Plan or create a new Application Group.
The Application Group is added as a Resource Planning node to enable its resources to be managed.
Re-order Resource Planning Nodes
1. Select a Resource Planning node from the navigation tree.
2. Select either Move Up or Move Down from the Resources Setup ribbon.
The Resource Planning node is moved up or down in the list.
CPU Share Factor
CPU Share Factor allows the CPU resource to be split between Resource Planning nodes.
It allocates User Groups or Application Groups a greater or lesser proportion of CPU time.
The pie chart in the work area provides a visual representation of the CPU allocation between the
nodes. In the above example, the pie chart represents the relative CPU share between the Resource
Planning nodes entitled Development, HR, Sales and <Other Users>.
To set CPU Share Factor:
1. Select a Resource Planning node in the navigation tree.
2. In the work area, select the CPU tab.
3. In the CPU Share Factor section, adjust the share factor by either using the slider or entering a
value into the box.
As the CPU Share Factor is adjusted, the pie chart updates to provide a visual representation of
the resource allocation between the Resource Planning nodes.
The CPU Share Factor of the Resource Planning node, relative to the other Resource Planning nodes, is
set and the processor time is split accordingly on endpoints.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 34 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Resource Planning Sub-nodes
Sub-nodes allow a finer level of control to be applied for specific Application Groups or User Groups.
Rules within a Resource Planning sub-node allow resources to be allocated based upon attributes of
the application window, such as whether it is maximized or minimized.
Add Resource Planning Sub-nodes Based on Application Groups
1. Select a Resource Planning node from the navigation tree.
2. On the Resources Setup ribbon, click Add Applications and select an Application Group for
which to create a Resource Plan.
The Application Group is added as a Resource Planning node to enable its resources to be managed.
Add Resource Planning Sub-nodes Based on User Groups
1. Select a Resource Planning node from the navigation tree.
2. On the Resources Setup ribbon, click Add Users/Groups and select Select User/Group.
The Select User/Group dialog displays.
3. Choose a user or group using one of the following methods:
o
Enter the name of a user or group in the Name field.
o
Click the percent sign (%) and add an environment variable.
o
Click the ellipses (...) and browse to the user or group.
The User Group is added as a sub-node of the Resource Planning node to enable its resources to be
managed.
Re-order Resource Planning Sub-nodes
1. Select a Resource Planning sub-node from the navigation tree.
2. Select either Move Up or Move Down from the Resources Setup ribbon.
The Resource Planning sub-node is moved up or down in the list.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 35 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Rules
Rules within a Resource Planning sub-node allow resources to be allocated based upon attributes of
the application window, such as whether it is maximized or minimized.
In a typical setup, maximized windows in sessions that are connected, not idle and unlocked are given
a greater proportion of the available resources.
Add Rules for Resource Planning Sub-nodes
1. Select a Resource Planning sub-node from the navigation tree.
2. From the Resources Setup ribbon, select Add Rule.
A new rule is created within the work area.
Add Conditions to Rules for Resource Planning Sub-nodes
1. Select a Resource Planning sub-node from the navigation tree.
2. In the work area, select a rule.
3. Select the Conditions tab.
4. Set one or more of the following conditions:
Condition
Description
Window
Position
Set whether the assigned application window is Minimized, Not Minimized, in the
Foreground or in the Background.
Session
Connected
Set whether the assigned application is running in a session that is Connected or
Disconnected.
Session Idle
Set whether the assigned application is running in a session that is Idle or Not
Idle.
Desktop
Set whether the assigned application is running in a session that is Locked or
Unlocked.
The condition is added to the rule. The name of the rule is updated in the work area based upon the
selected conditions.
Re-order Rules for Resource Planning Sub-nodes
1. Select a Resource Planning sub-node from the navigation tree.
2. From the Resources Setup ribbon, select either Move Up or Move Down.
The rule is moved up or down in the list.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 36 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
CPU Share Factor for Resource Planning Sub-nodes
CPU Share Factor allows the CPU resource to be split between Resource Planning sub-nodes. It
provides Application Groups or User Groups a greater or smaller proportion of CPU time.
The pie chart in the work area provides a visual representation of the CPU allocation
between all sub-nodes in the configuration.
To set CPU Share Factor:
1. Select an Resource Planning sub-node from the navigation tree.
2. In the work area, select a rule.
3. Select the CPU tab.
4. In the CPU Share Factor section, adjust the share factor by either using the slider or entering a
value into the box.
As the CPU Share Factor is adjusted, the pie chart updates to provide a visual representation of
the resource allocation between the Resource Planning sub-nodes.
The CPU Share Factor of the Resource Planning sub-node, relative to the other Resource Planning
sub-nodes, is set and the processor time is split accordingly on endpoints.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 37 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
CPU Reservations and Limits for Resource Planning Sub-nodes
CPU Reservations ensure that the Application Group or User Group has a guaranteed level of available
CPU resource. CPU Limits restrict the amount of CPU resource available to the Application Group or
User Group.
To set CPU Reservations and Limits:
1. Select a Resource Planning sub-node from the navigation tree.
2. In the work area, select a rule.
3. Select the CPU tab.
4. In the CPU Reservation & Limits section, set one or more of the following settings:
Setting
Description
Reservation
Ensure that a guaranteed level of CPU resource is available to the Application Group
or User Group. At times of peak demand on the system, minimum reserved
resources
are obtained and the remaining resources are reallocated according to CPU Share
Factors.
Limit
Prevent the Application Group or User Group exceeding specific CPU levels. Select
the type of limit:
l
Soft Limit - The restriction applies during high CPU demand only.
l
Hard Limit - The restriction applies even when spare capacity is available.
As the Reservation and Limit fields are adjusted, the bar chart updates to provide a visual
representation of the resource allocation relative to other sub-nodes.
The CPU Reservation or Limit is set. Where the Reservation is specified, the sub-node has a guaranteed
level of CPU resource. Where the Limit is specified, the sub-node has a limited amount of CPU resource.
CPU Affinity for Resource Planning Sub-nodes
CPU Affinity restricts the Application Group or User Group to one or more specific CPUs.
To set CPU Affinity:
1. Select a Resource Planning sub-node from the navigation tree.
2. In the work area, select a rule.
3. Select the CPU tab.
4. In the CPU Affinity section, select Enabled and specify the CPU numbers.
Use commas to specify individual CPUs or dashes to specify ranges of CPUs. For example, 0,2
uses CPUs 0 and 2 and 0-2 uses CPUs 0, 1 and 2.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 38 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
The CPU Affinity is set. The sub-node has the specified CPUs available only.
Physical Memory Limits for Resource Planning Sub-nodes
Physical Memory Limits allow a minimum or maximum amount of memory to be configured for the
Application Group. Options are available to trim the process memory on application startup or when
the application enters the rule.
To set Physical Memory Limits:
1. Select a Resource Planning sub-node from the navigation tree.
2. In the work area, select a rule.
3. Select the Memory tab.
4. In the Physical Memory Limits section, select Enabled.
5. Specify the following settings:
Setting
Description
Minimum
Ensure that a guaranteed level of physical memory is available to the
Application Group. At times of peak demand on the system, minimum
reserved resources are obtained and the remaining resources are
reallocated according to CPU Share Factors. Select the type of limit:
l
l
Maximum
Hard Limit - The reservation applies even when spare capacity is
available.
Prevent the Application Group exceeding specific physical memory levels.
Select the type of limit:
l
l
Trim process
memory on
application
startup
Soft Limit - The reservation applies during high memory demand
only.
Soft Limit - The restriction applies during high memory demand
only.
Hard Limit - The restriction applies even when spare capacity is
available.
Trim process memory when the process has been created. The memory is
trimmed only once.
Trim process
Trims a process memory whenever the state matches the associated state
memory when rule.
application
enters this
rule
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 39 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
As the Minimum and Maximum fields are adjusted, the bar chart updates to provide a visual
representation of the resource allocation.
The Physical Memory Limits are set. Where the Minimum is specified, the sub-node has a guaranteed
level of physical memory. Where the Maximum is specified, the sub-node has a limited amount of
physical memory. The process is trimmed according to the settings.
Application Memory Limits for Resource Planning Sub-nodes
Application Memory Limits allow the amount of virtual memory available to an application to be
restricted. Applications can be either closed or terminated for exceeding their limit.
To set Application Memory Limits:
1. Select a Resource Planning sub-node from the navigation tree.
2. In the work area, select a rule.
3. Select the Memory tab.
4. In the Application Memory Limits section, select Enabled.
5. Specify the following settings:
Setting
Description
Application
Limit
Set the memory level, in megabytes, at which the action is taken. Select
the type of limit:
l
Soft Limit - The limit applies during high memory demand only.
l
Hard Limit - The limit applies even when spare capacity is available.
Close
application
after
Users are prompted to close the application once the application has
exceeded the limit for the specified number of minutes.
Terminate
application
after
The application is terminated once the application has exceeded the limit
for the specified number of minutes.
Terminating an application can result in data loss within the application.
As the Limit field is adjusted, the bar chart updates to provide a visual representation of the
resource allocation.
The Application Memory Limits are set. The application is closed or terminated after exceeding the
limit for the specified time.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 40 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Windows Fair Share
A reduction in performance management efficiency may occur where Windows Fair Share is enabled
on machines with the Performance Manager agent installed. It is therefore recommended that
Windows Fair Share is disabled.
To disable Windows Fair Share, set the following registry values:
Key
Value Name
Valu
e
HKEY_LOCAL_
MACHINE\SOFTWARE\Policies\Microsoft\Windows\SessionManager\DF
SS
Enable DFSS
0
HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Services\TSFairShare\Disk
EnableFairShar
e
0
HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Services\TSFairShare\NetFS
EnableFairShar
e
0
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 41 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Thread Throttling
Thread Throttling sets a system-wide CPU thread throttling policy that triggers when the system is
heavily loaded. The throttling provides unutilized processor time to allow new users to log on or new
applications to execute.
Performance Manager samples system performance data at one second intervals. Once the system is
detected to be in a heavily loaded state for the specified interval, threads are clamped to achieve the
specified percentage reduction in server load. The clamp is unapplied after the specified duration.
Where necessary, clamping is reapplied repeatedly until the processor remains stable.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 42 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Configure Thread Throttling
To configure Thread Throttling:
1. Select Thread Throttling in the navigation tree.
2. Select Enabled.
Specify the following settings:
Section
Settings
Monitor
Set the CPU utilization percentage and the internal (in seconds)
for which the CPU must remain at the utilization level before
clamping is applied. Additionally, set whether the clamping
occurs when any one processor reaches the threshold on multiprocessor systems.
It is recommended that the interval does not exceed 60 seconds.
Action
Set the percentage by which to clamp the CPU and for how long
the clamp is applied (in seconds).
It is recommended that the interval does not exceed 60 seconds.
Exceptions
Set the minimum CPU utilization for processes and threads to be
clamped. Processes and threads below the specified level are not
clamped.
As the options are set, the chart in the work area updates to provide a visual representation of the
Thread Throttling behavior.
Thread Throttling is enabled for all users on the system. When the system reaches the specified CPU
utilization threshold for the specified interval, threads are clamped by Performance Manager.
Example
The example below explains typical Thread Throttling behavior. As the options are set in the console,
the chart updates to provide a visual representation of the behavior.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 43 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Label Description
A
The CPU utilization reaches the threshold of 95%, as specified in the Monitor section.
B
The CPU remains at or above the threshold of 95% for 20 seconds, as specified in the
Monitor section.
C
The initial clamping of 45% (from 95% to 50%) is applied, as specified in the Action section.
D
The CPU remains clamped by 45% (from 95% to 50%) for 18 seconds, as specified in the
Action section.
E
The clamping is unapplied after the clamp duration expires. The clamp is reapplied if the
CPU utilization reaches the threshold of 95%, as specified in the Monitor section.
F
The minimum percentage for process clamping. Processes utilizing below 35% are not
clamped, as specified in the Exceptions section.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 44 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Label Description
G
The minimum percentage for thread clamping. Threads utilizing below 15% are not
clamped, as specified in the Exceptions section.
Include System Processes in Thread Throttling
By default, system processes are not included in Thread Throttling. This ensures system processes
continue running for critical system tasks.
1. Click Options on the Resources Setup ribbon.
The Feature Options dialog displays.
2. Select the Feature Usage tab.
3. On the Thread Throttling row, select Include System Processes.
4. Click OK.
System processes are included in the Thread Throttling behavior.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 45 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Auditing
Use Auditing to define rules for the capture of auditing information, you can setup rules about where
event data is stored for logging to a local file and the application event log, and you can setup filters
to specify the events you want to capture in the log.
Local Auditing allows you to specify whether to log events in the Windows Application Event Log or to
a custom Event Log. Events can be written to a local file in CSV or XML format.
By default, the log file is located at
%SYSTEMDRIVE%\AppSenseLogs\Auditing\PerformanceManagerEvents_%COMPUTERNAME%.csv (or
.xml)
An alternative location can be configured for the log file. In this mode, auditing also includes an event
filter to log only specific events.
When managed by the Management Center, events are forwarded via the Deployment Agent. Under
these conditions, event data storage and filtering is configured through the Management Console.
Make events anonymous
Specify whether events are to be anonymous. If, Yes, the computer name and user name is omitted
from all events. Anonymous logging also searches the file path for any instances where a directory
matches the username and replaces the directory name with the string USERNAME or
COMPUTERNAME.
Send events to local file log
Select whether to send events to the local file log. If Yes, the events are sent to the local log file as
specified in the Text box. The default is:
%SYSTEMDRIVE%\AppSenseLogs\Auditing\PerformanceManagerEvents_%COMPUTERNAME%.csv
Local file log format
Specify whether the event log is to be saved in XML format or CSV format.
Local Events
The Event filter table is a comprehensive list of all events and is used to select the events you want to
audit. You can sort the table numerically by ID number, or alphabetically by Event Name or Event
Description. Selected events are highlighted in bold. Click Toggle selected to change the states
between selected and cleared.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 46 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Events are reported to the local Windows Event Log or the local Event Log, according to the
Deployment Group Events settings, and also to the Management Server by the Deployment
Agent (CCA), unless otherwise indicated.
Event
ID
Event Name
Event Description
9104
Thread Throttling
Clamping On
Total CPU Usage has exceeded a threshold and
will be clamped.
Information
9105
Thread Throttling
Clamping Off
Total CPU Usage has fallen under a threshold
and clamping will stop.
Information
9106
Application CPU
Usage clamping On
An Application has exceeded its CPU Usage limit.
Information
9107
Per Application
Memory Usage
Exceeded
Memory usage for a particular application has
exceeded a threshold.
Information
9108
Per Application
Memory Usage
Reduced
Memory usage for a particular application has
dropped below a threshold.
Information
9109
Per Application
Memory Usage
Terminated
An application has been terminated because it
used too much memory.
Warning
9110
Application CPU
Usage Clamping Off
An application has now fallen below its CPU
Usage limit and will no longer be clamped.
Information
9115
Working set
trimmed
Working set for an application has been
trimmed.
Information
9116
CPU Affinity
changed
CPU Affinity of an application has changed.
Information
9119
Per Application
Hard Memory Limit
Reached
Memory usage for a particular application has
reached its maximum limit
Warning
9120
Thread Throttling Clamped Processes
Total CPU Usage has exceeded a threshold and
applications will be clamped.
Information
9121
Application CPU
Soft Limit - Started
Because of the overall CPU Usage a CPU soft limit
will be applied to an application.
Information
9122
Application CPU
Soft Limit - Stopped
An application will be no longer controlled by an
CPU soft limit.
Information
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 47 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Event
ID
Event Name
Event Description
9123
Application CPU
Reservation
Applied
A CPU Usage reservation was applied to an
application.
Information
9170
Settings not found
in package
Some configuration settings were not found in
the configuration package.
Error
9171
Settings not valid in
package
Some configuration settings in the
configuration package were not valid.
Error
9172
Settings loaded
from package
The configuration settings were successfully
loaded from the configuration package.
Information
9173
Settings applied live
to the Agent
The configuration settings were applied live to a
running Performance Manager Agent.
Information
9174
Package has been
loaded and all
settings applied
All settings in the package have been applied to
the Agent.
Information
9175
The package is
invalid
The configuration package is invalid.
Error
9176
Package not found
The configuration package does not exist.
Warning
9197
Valid License Found
Performance Manager is licensed.
Information
9198
Invalid License
Found
Performance Manager has detected a product
license which is not compatible with the current
used Performance Manager version. Upgrade
your Performance Manager license.
Error
9199
Valid License Not
Found
Performance Manager is not licensed.
Error
9235
NP-VDI Config path
Update
Detected the Deployment Agent has updated
the endpoint native configuration path.
Error
9236
System Memory
Exceeded
Threshold Warning
The system memory has exceeded the minimum
threshold. New processes will be eligible for
memory limitations.
Warning
9237
System Memory
Exceeded
Threshold Lapse
The system memory has fallen back below the
minimum threshold. New processes will not be
monitored for memory limitations.
Warning
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 48 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
System Events
The following are non-configurable system events:
Event ID
Event Name
Event Description
8095
No Configuration found
[Product Name] cannot find a valid configuration
8096
Configuration Upgraded
A configuration for a previous version of [Product
Name] has been detected and upgraded.
8099
Invalid License
[Product Name] software is not licensed.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 49 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Environment Variables
You can convert to environment variables certain types of data which are manually entered in different
areas of the Performance Manager console. For example, directory paths to applications. Environment
variables are available by selecting the percent sign (%) where it appears in particular dialogs. For
example, the Add New Application Group dialog.
The following table shows the types of environment variables and where they can be used in the
Performance Manger console.
Environment Variables
Add Users/Groups
Add Application
%ProgramFiles%
Yes
%SystemRoot%
Yes
%SystemDrive%
Yes
%CommonProgramFiles%
Yes
%AllUsersProfile%
Yes
%ComputerName%
%WinDir%
Yes
Yes
Yes
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 50 of 51
Ivanti Performance Manager 10.1 FR1 Product Guide
Streamed Applications
To set up Citrix XenApp streaming applications to work with Performance Manager you need to
specify certain exclusions, as follows:
1. Navigate to Citrix Streaming Profiler for Windows.
2. Open the Application Profile.
3. Highlight the relevant Target and select the Edit menu.
4. Select Target Properties. The Target Properties screen displays.
5. Select Rules. The Rules work area displays on the right hand side.
6. Click Add in the Rules work area. The New Rule Select Action and Objects dialog displays.
7. In the Action section leave the default setting as Ignore.
8. In the Object section select Named Objects and click Next. The New Rule Select Objects dialog
displays.
9. Select Some Named Objects and click Add. The Choose Named Object dialog displays.
10. Add \??\pipe\AppSense* and click OK. This displays in Named Objects on the New Rule Select
Objects dialog.
11. Click Next to display the New Rule Name Rule dialog.
12. Enter a name for the rule or accept the default and click Finish.
13. Click OK. The Target Properties screen re-displays and the Ignore all named objects rule is now
listed in the work area on the right hand side.
14. Save the profile.
15. Repeat for each application profile as required.
Copyright © 2017 , Ivanti. All Rights Reserved.
Page 51 of 51