This page refers to an older version of the product.View the current version of the User Help.
The deployment statistics report on the number of agents and configurations deployed for each of the User Workspace Manager products. This allows a user to see if they are compliant on license count with the number of licenses they have purchased versus how many agents are deployed.
For each product, data is gathered and reported on in the following three areas:
- Number of agents installed
- Number of configurations installed
- Number of computers with an installed agent that have polled in within the last 30 days
Agents and configurations are included in each count if they have a status of Installed, Pending Uninstall, or Unmanaged.
Statistics display on the Home page showing a general overview of all computers polling to the management server. They also display on the Deployment Group Summary page, showing an overview of all computers in that deployment group.
An unmanaged package state occurs when an agent is installed on a computer that has a polling Deployment Agent, but no agent package is present in the database for that product, and the install schedule for that deployment group is set to Do not Install Agents.
Unmanaged packages are ignored for all purposes other than deployment statistic counting and are effectively treated as installed.
When dealing with unmanaged packages, you must account for the following:
Packages installed on a computer are not in the database
If the Management Server that a managed computer polls into has no agent packages for that product present in the database, and the install schedule set to Do not Install Agents, then agent packages that the Deployment Agent reports as present on the endpoint appear as unmanaged. These packages are included in deployment statistical counts, both globally for the server, and at the deployment group level.
If an agent package matching the product of the unmanaged agent package is then afterwards added to the Management Server database, then the state of the package changes to Pending Uninstall. The agent package will otherwise remain unaffected, and still be included in the deployment statistic counts, while the deployment group install settings remain set to Do Not Install Agents. No uninstall instructions are sent to the Deployment Agent. The state changes to Installed, if the version of the package matching the previously unmanaged package is then assigned to the deployment group packages.
In any other case, the agent package is removed as per the agent install schedule.
Packages are in the database but not assigned to the deployment group
If the deployment group the managed computer polls into has the install schedule set to Do Not Install Agents, then agent packages appear as Pending Uninstall. They are still included in deployment statistical counts, but no instruction is sent to the Deployment Agent.
If all agent packages for the product are then afterwards deleted from the Management Center database, and the deployment group install schedule remains set to Do Not Install Agents, then the package state changes to Unmanaged.
In any other case the agent package is removed as per the agent install schedule.