I have created the following report when I was asked to write an altiris report, to find a list of software installed on the given user’s PCs.

I was given a list of users as input to the report. Now I have to find out the list of software in each user’s PC. There are actually two reports in this.

1. Finding primary user of the computer
2. Display list of software on the computer

1. Finding primary user of the computer:

SELECT DISTINCT (PU.[User]), vComputer.[Name] AS 'Machine Name',
ACI.[Domain] AS 'Domain'      
FROM vComputer        
INNER JOIN [inv_aex_ac_primary_user] PU  
ON PU._ResourceGuid = vComputer.Guid        
JOIN [Inv_AeX_AC_Identification] ACI  
ON ACI.[_ResourceGuid] = vComputer.Guid   
WHERE PU.[Month] = datename(month, getdate())   
AND UPPER...

XX_Rider and I worked out this query on the #altiris freenode channel and we thought it might be useful for the community at large:

A use case from XX_Rider:

"The SQL shows all the jobs in the database that were run by the user. Our need was to find out if our staff was using the deployment console. They claimed they were using it but we couldn't find any jobs pushed by them. Other uses would be if an employee leaves, maybe done something they shouldn't have before they left, or to find out what users are making use of the console efficiently, i.e., using jobs instead of doing things manually."

SELECT su.user_id,
       su.displayname,
       c.Computer_name,
       es.start_time,
       e.name
FROM   Computer c,
       event_schedule es,
       securityuser su,
       event e
WHERE  c.computer_id = es...

TCPView will display which active and listening sockets an application has created. This can be helpful for troubleshooting network applications.

More information can be found at http://technet.microsoft.com/en-us/sysinternals/bb...

When using Deployment Solution to roll out new IBM x3850 servers, the Linux PE environment received an interesting error when attempting to boot:

'badness in do_exit at kernel/exit.c'

This particular server had 16 processors. Apparently the Linux kernel configured for this boot process was unable to correctly address multiple processors.

Fortunately, this was a fairly simple fix. Deploying the image was not really a multi-processor critical operation. By adding the 'maxcpus=1' statement, as defined below, the kernel was then configured to only operate using one CPU. This resolved the problem.

In the MISC folder

--freeldr.ini

CommandLine="root=/dev/ram0 rw ramdisk_size=32768 maxcpus=1"

--isolinux.cfg

default linux
label linux
 kernel linux
 append initrd=rootfs.gz root=/dev/ram0 rw...