Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
R-Vijay | 26 Aug 2008 | 0 comments

Have you ever thought about creating installer packages in Visual Studio?

Do visit this below link to have more insights on that.

Topics which are covered in this link are,

  1. Building an MSI File: Visual Studio and Orca
  2. Building a Package
  3. A First Look at Shortcuts
  4. More About Properties
  5. GUIDs: Product, Upgrade, and Package Codes
  6. Into the Package with Programming
nac | 22 Aug 2008 | 1 comment

Well this is an intresting tip while moving from XP to Vista. When we launch the Help file in Vista, Help file (.hlp) may give you the following types of errors.

  1. An error like this means the particular Help file is not compatible to work on Vista. You need to apply a Help patch. So unless and until you apply a patch you will not be able to open the Help file.

    You can download this patch from following link.

  2. It doesn't stop there. After applying the patch you open Help again and this time you may...
BRING | 21 Aug 2008 | 2 comments

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.

So maybe EvtQFast is...

PeeGee | 12 Aug 2008 | 9 comments

Out of the box, Helpdesk Solution does not provide any possibility to highlight incidents which have a high priority or a specific status.

In the KB you can find the following article: Which deals with color coding the Incident Grid, which is already a big help. But on the day to day basis it also handy to find the same highlight colors, when looking at a single incident.

The code of this article shows, how the background color of the "Priority" field can be changed, depending on the priority. Of course this can be used for any other field as well.

Compared to the JavaScript approach of the above KB article, I simply...

neil_rogers | 07 Aug 2008 | 0 comments

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 add items to arrays...

ademeijer | 06 Aug 2008 | 0 comments

The attached document explains how the directory table is structured. The directory table is one of the least understood tables in Windows Installer, therefore I wanted to shed some light on this table.

Going through my archives I found this document which describes the directory table. It's also available at

Happy reading,

networkchic | 30 Jul 2008 | 3 comments

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


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.'

SELECT Ident.[Name], Ident.[Domain] FROM Inv_AeX_AC_Identification Ident
SELECT Ident1.[_ResourceGuid], Ident1.[Name], Ident1.[Domain] FROM...
networkchic | 29 Jul 2008 | 1 comment

Instead of viewing the 'Status' tab on a software delivery task (which is never reliable) use this query to see a list of computers which have the status of 'Not Run' - meaning they have not received the Task or have not delivered any status on the task. Use the Collection Guid in your where clause.

select Guid from vResource where Guid in (select Guid from (select TOP 400, b.guid    
 from CollectionMembership a, vcomputer b    
 where a.CollectionGuid in ( '{e04bebd1-92dd-40e2-b014-9fed9ddcdd32}','{b6914ce4-55d5-4b4b-a8f6-c029c13794d2}')  -- Laptops    
  and a.ResourceGuid = b.Guid    
  and a.ResourceGuid not in (select _ResourceGuid from Evt_Aex_SWD_Execution where AdvertisementName = 'Pointsec Mandatory Install - 2-21-08')    
 order by xxx)
networkchic | 29 Jul 2008 | 0 comments

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
networkchic | 29 Jul 2008 | 0 comments

This will give you information on the status of Sequential Software Delivery Tasks which you can build dynamic collections in Altiris.

In your search criteria use the AdvertisementName of one of the programs that will execute within the Sequential task NOT the actual name of the Sequential task.

Select, vc.guid,st.status, st.exitcode, 
From inv_synch_status st
  Join vcomputer vc on vc.guid = st._resourceguid Join item it on st.taskid = it.guid

Where st.synchronizationid in 
	(select guid from item where name Like '%%)
and st.status = 'completed'

Order by