Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Reporting
Showing posts in English
Eshwar | 13 May 2008 | 5 comments

You can find whether a software package is installed on computers on you network by querying the [Inv_AeX_OS_Add_Remove_Programs] table.

Here's how to find the machine name by joining the [Inv_AeX_AC_Identification] table.


SELECT DISTINCT(ACI.[Name]) AS 'Machine Name', ACI.[Domain] AS 'Domain', ARP.[Name] AS 'Application Name'
FROM  [Inv_AeX_AC_Identification] ACI 
INNER JOIN [Inv_AeX_OS_Add_Remove_Programs] ARP 
ON ACI.[_ResourceGuid] = ARP.[_ResourceGuid] 
WHERE ARP.[Name] LIKE '%Application Name%' 

Eshwar | 12 May 2008 | 1 comment

Did you know you could retrieve hardware serial numbers and memory module information from your Inventory Solution data? It's possible by joining [Inv_AeX_HW_Serial_Number] and [Inv_AeX_HW_Memory_Modules] tables with [Inv_AeX_AC_Identification].

Here's the syntax:


SELECT DISTINCT(ACI.[Name]) AS 'Machine Name', AHS.[Serial Number] AS 'Serial Number', MM.[Size], MM.[Type]
FROM [Inv_AeX_AC_Identification] ACI
INNER JOIN [Inv_AeX_HW_Serial_Number] AHS ON ACI.[_ResourceGuid] = AHS.[_ResourceGuid]
JOIN [Inv_AeX_HW_Memory_Modules] MM ON MM.[_ResourceGuid] = ACI.[_ResourceGuid]  

vortex0007 | 07 May 2008 | 0 comments

Active Directory and Altiris Notification Server seem to have a love hate relationship. The Active Directory connector loves to import user names and computer names, but it hates to do anything related to group membership. A common request has been the ability to incorporate user group information from Active Directory into collections in order to allow user based software delivery. In other words, install Quickbooks to all of the users who are in the Accounting OU. This tip steps through how to accomplish this.

The first step is to create a connection between the Microsoft SQL Server hosting the Altiris databases and the Active Directory. This is accomplished through a SQL concept known as "Linked Servers." There is a bit of black magic to making linked servers work and a full technical drill down into how they work is beyond the...

KSchroeder | 29 Apr 2008 | 0 comments

Do you ever look at your Recovery Solution job queue and wonder "I wonder how far along that Integrity Check/SSM job is?" Well I did, and was very frustrated since there wasn't a good way I had found to monitor the progress. Well, by using the following Stored Procedure, you too can find out about the progress of the job.

To install this, just load the attached .SQL file into Query Analyzer (or whatever tool is used in SQL 2005), select your Recovery Solution database, and execute it. It will add the spGetRSJobStatus Stored Procedure (SP) to the database. To run the query, just execute the SP from Query Analyzer:

EXEC spGetRSJobStatus

Note: I just attached a NS report you can use to run this without having to fire up Query Analyzer.

Note that this works best for checking the Integrity Check job's status as...

vortex0007 | 22 Apr 2008 | 6 comments

I'm always surprised to find how few customers take advantage of Altiris Inventory Solution's ability to inventory an application's installed serial number. This information can be invaluable when trying to tie copies of applications installed in your environment back to software license agreements.

Each time Altiris Inventory Solution scans are run, the serial numbers for installed applications are captured and stored in the Inv_AeX_OS_Add_Remove_Programs table.

It is impossible for us to list every single application that will report back a serial number properly, but testing in large environments has revealed at least 500 business applications that return this information properly, including most of the business applications from Microsoft, Adobe.

The following SQL query can be run against the Altiris database to find out...

cnpalmer75 | 26 Feb 2008 | 0 comments

The release of the newest rollup pack for NS brings about a whole list of added updates.

Have you ever wondered though what was fixed with the current rollup you have installed now?

Well this download will allow you to see what each rollup pack has incorporated for fixes.

This info from taken from KB21248 and can be found in the Altiris KB, but the formatting was way off to read it. This Word doc should help straighten all of that out.

cnpalmer75 | 22 Feb 2008 | 0 comments

In case anyone else may have missed the release earlier this month, here are the details surrounding the security vulnerability for any Altiris Agent pre- 6.0.2389 build. Linky here...


February 6, 2008
Symantec Altiris Notification Server Agent Privilege Escalation Vulnerability

Severity: Medium
Remote Access: No
Local Access: Yes
Authentication Required: Yes
Exploit publicly available: No


A privilege escalation vulnerability in the Symantec Altiris Notification Server Agent has been identified.

Affected Product(s)

Product Version Build Solution(s)
Altiris Notification Server 6.X All 6.0 SP3 R7


The Symantec...

BRING | 21 Feb 2008 | 0 comments

Measure twice and cut once. Sometimes not remembering to do that causes trouble, and has sometimes ruined some beautiful wood stock.

Frequently we do something similar in the Task Server environment when we forget to check the collection references that our tasks are assigned to. Like sending a Shutdown, or Restart task to "All Computers".

While this won't be painless to all end users, we can mitigate it and stop it from hitting everyone, using the following procedure:

  1. 1. Delete the Task from the Console. This may also involve deleting any referenced items as well.
  2. 2. Restarting the Altiris Object Host Service. This will clear the Task Server cache, and allow any deleted jobs to be cleaned and not promulgated to other machines.

It's just that simple. And while it won't be painless for you as the...

cnpalmer75 | 21 Feb 2008 | 0 comments

This is another posting in regards to the articles I've done for Recovery Solution (RS) in the past based around the events which may occur that get written to the application event log.

Over the course of using this data, I have been able to identify several error sets that always occur in these pairs and in these sequences. Tracking these down was difficult since RS re-uses the same source, category & event ID for different events, only the description is changed. This, IMO, seems to be poor coding.

This is helpful in identifying a particular asset that may be creating these events for further investigation.

The cause of these is still unknown as I am working with Dev in Estonia to come up with a suitable answer, but for now being able to identify and track these error sets is the first step.

Hopefully, you do not see these in your environment.

neil_rogers | 31 Jan 2008 | 4 comments

I recently received request for a report that would show which of our computers are covered by a warranty. I looked around and didn't see a report off hand (that was not tied to the expiration of the warranty) but I did see a lot of similar reports for expiring leases.

Hopefully my solution to this reporting problem will come in handy for someone else.

My Solution

Change the attached txt file to xml to import into NS.

This report first shows all warranties. Choose a warranty and right click for a drill down to show the active computers that are covered by the warranty.

While I just list the warranty and the computer, to see all the associated fields available, add a * to see all the rows of data that are available.

Here are the two sql queries:

level 0:
Select * from vWarranty

level 1...