KNOWN ISSUE: Optimizing the Software Delivery and Task Sync Agent rollout collections

Article:TECH25393  |  Created: 2006-11-27  |  Updated: 2007-01-25  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


In large environments (10,000 or more nodes), the rollout collections for the Software Delivery Agent and the Task Synchronization Agent are taking too long to rebuild.

Under certain circumstances, the console will time out when trying to view the members of the collections. For reference, the names of the collections are:

  • Windows Computers with no Software Delivery Solution Agent Installed
  • Windows Computers with no Task Synchronization Agent Installed


Notification Server 6
Software Delivery Solution 6.1, 6.1 SP1, 6.1 SP2


Both collections depend upon the legacy view "Wrksta" to determine which computers are running a 32-bit Windows operating system. The Wrksta view has been retained for backward compatibility purposes, but is a known cause of poor SQL performance in current environments.

In regards to the collection membership page timeout, this can occur in situations such as an agent migration to a new NS. These collections will not be targeted by an enabled policy to avoid unnecessary network traffic.When the administrator views the collection, the auto-rebuild of the stale collection is triggered (the last rebuild time > delta update interval), and the page times out prior to the completion of the collection rebuild.


Import the attached custom collections (far right side of this article) under their respective folders:
  • Software Delivery Agent Rollout folder
  • Task Synchronization Agent Rollout folder
Modify the existing rollout policies to use the new optimized collections. Don't forget to uncheck the original collections.
  • Software Delivery Agent Install  > Optimized - Windows Computers with no Software Delivery Agent Installed
  • Task Synchronization Agent Install > Optimized - Windows Computers with no Task Synchronization Agent Installed
Because the original collections will no longer be targeted by an enabled policy, the server will not incur a SQL performance penalty during collection update processing.

Revised collections are expected to be included in SP3 for Software Delivery 6.1

Supplemental Materials

ValueLB 54942
DescriptionLogged in Littlebuggy (Altiris - Lindon, Plymouth) database

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices