EvtQueue, EvtQFast, EvtQLarge, and EvtQSlow. These folders within the Altiris folder structure are the lifeblood of data processing for your Notification Server.

One might wonder if EvtQueue is more important than EvtQFast, EvtQLarge, or EvtQSlow? Or could EvtQFast get preferential treatment? What happens when multiple NSE files are captured at the same time - does one queue get a priority over any other and if so, what is that priority?

Well, in the interest of fair play, the Notification Server does not play favorites. No queue has priority over another. Each one has been assigned one or more processor threads, (with the exception of EvtQLarge), and the remaining queues all process concurrently. The default threads for each queue are different however. EvtQFast has 10, EvtQueue has 3, and EvtQSlow has 1.

In Workflow, the term "Collection" is a term that does not refer to traditional Altiris Collections, unless it has the Altiris icon. If it is a blue file box, then it can be used for array items.

Collections are how array handling is done. If you have a list of computers in an array, and need to add a ticket for each one, then use the component: "For each element in Collection."

It has two output paths: Next Element and Finished. The Next Element is similar to a while or for loop. Just loop it through the rest of the components and back to itself. Inside of that process it can have things like matches or equals rules, Commands, Create or Edit Tickets and then the data path goes back to the For Each element in Collection until it runs out of elements!

There are other handy ways to handle items in arrays or...

Schedule this Query to run at least once a week to auto merge your duplicate computers (computers with the same GUID). This automatically takes the most recent data and merges the two records together. This is a great way to keep your environment clean.

DECLARE @MergeName nvarchar(400)
DECLARE @MergeDomain nvarchar(400)
DECLARE @FromGuid uniqueidentifier
DECLARE @ToGuid uniqueidentifier

DECLARE @PrimaryResource UNIQUEIDENTIFIER

PRINT 'The following script will automatically merge resources as per the ''Merge computers with duplicate names'' report.'
PRINT 'The merge automatically chooses the resource that has the most recent update.'

DECLARE merge_cursor CURSOR FOR
SELECT Ident.[Name], Ident.[Domain] FROM Inv_AeX_AC_Identification Ident
INNER JOIN
(
SELECT Ident1.[_ResourceGuid], Ident1.[Name], Ident1.[Domain]...

This query is very helpful in trying to determine what collections a machine belongs to without having to go through Resource Manager.

SELECT   vComputer.Name, vComputer.[User], vComputer.[OS Name], vComputer.[OS Version], vComputer.[IP Address], 
           CollectionIncludeResource.CollectionGuid, vCollection.Name AS 'Collection', vCollection.Description
FROM     CollectionIncludeResource INNER JOIN
           vComputer ON CollectionIncludeResource.ResourceGuid = vComputer.Guid INNER JOIN
           vCollection ON CollectionIncludeResource.CollectionGuid = vCollection.Guid