
More information can be found here
Blog site to provide a quick way to find solutions on problems encountered during a day to day work. Some articles are just copies of KB or Forums, but they might come in handy.
Office updates fail to install on client computers. After further investigation, it is discovered that the update returned one (or more) of the following error codes:
1603
1612
-1073741510
-2147467259
1605
Cause
There could be several reasons why these error codes are returned.
The install program for the Office* update program has the Starting Window set to Normal. This causes a command prompt window to appear on the screen and, if a user is not logged on, the update will fail.
The Office update requires access to the source installation files, but cannot find a valid path to where they are stored. Typically, Office installations come from a network share. If these files are moved, or if the path to them changes, the clients become out of date and hold an invalid location in their registry. When the update cannot find these files, it will try to prompt the user for a valid location. Since the update is set to run hidden, the window is supressed and the update fails.
It is possible for the clients to have a valid network location for source files, but when the updates attempts to retrieve those files, the update again fails. This would be caused by running the Office update with the System Account and storing the files on a share with limited access.
If you are using Notification Server 6.0 SP2, then you could be running into a known issue. The Altiris Agent was known to spawn instances of update.exe to install patches, but then did not kill them once the patch was installed. When the next patch goes to install, it will fail because update.exe is already running.
Resolution
Ensure that the update is set to run hidden, see article 23997, "How do I ensure that an Office update will run silently?"
Verify that all clients have a valid path to source installation files. See article 24002, "How do I verify that clients have a valid Office source installation files location?"
Set this update to run using different credentials. See article 22705, "Can I specify an alternate account with which to install updates?"
Apply Hotfix 20 for NS 6.0 SP2 (or just apply SP3). See article 21167, "Patches fail to install with a 1603 error code."
Hint: If the location of the Office Source Install files in article 24002 is on a Network Share, the Update needs to be run with User Credentials that has Network rights. To make this change see article 22705 for how to set up the Bulletins to be installed with a Domain User account. (Verify that this Domain User has rights to the Network share.)Note: It is recommended that the latest version of Windows Installer be installed on client computers. Older versions are known to be a catalyst for the above issues
Windows VISTA Support
From HPCM 6.2 and later, in addition to other supported operating systems, the following types of Windows VISTA operating systems are supported in HPCM for client computers:
Vista Business
Vista Business x64 Edition
Vista Enterprise x32 and x64
HP Backup and Recovery -- Configure HP Backup
This feature lets the administrator create a backup policy to initiate a backup task of the HP Backup and Recovery Manager on the client computer. An entire system backup is taken as per the schedule mentioned in the policy. Ths feature is available only if the licensed Altiris® Software Delivery Solution™ software (Altiris - SWD Solution) is installed.
Out of Band Management
HP Client Manager now supports computers using Intel* vPro Technology (Intel* AMT). HP Client Manager 6.2 includes Altiris Out of Band Management Solution that you can use to perform discovery, hardware inventory, power management, alerting, and other configuration tasks on HP computers vPro systems, all independently of system power and OS state. HPCM 6.2 includes full reporting of AMT capabilities for HP systems.
This feature lets the administrator access Altiris® Out of Band Management Solution™ software in the Altiris 6.5 Console. A link is provided in the Additional Link section of HP Client Manager Quick Start. This link is available only if the licensed version of Out of Band Management Solution (OOB) is installed.
AexMachINV.exe process does not stop on servers; rows and rows of calls to gethostbyaddr() using what appears to be a garbage address
A fix is available in KB : http://kb.altiris.com/article.asp?article=22442&p=3
The official fix will be shipped with the SP2 version of IS 6.1. |
Please read the following document when upgrading to PM6.2
http://kb.altiris.com/article.asp?article=30816&p=3
I'm even under the impression they released it a bit early...
This KB is a summary of all important known issues http://kb.altiris.com/article.asp?article=29104&p=3
It combines fixes for the issues addressed here
KB24764 KB24537 KB25767 KB27776 KB26457 KB26458
KB26459 KB26460 KB26463 KB26464 KB27777 KB26466
KB27778 KB27779 KB28017
Release Notes: http://kb.altiris.com/article.asp?article=25133&p=3
SELECT vC.[Name], vC.[Domain], vC.[OS Name], vC.[OS Type], a.LastConfig, vC.[Guid]
FROM vComputerEx vC
INNER JOIN Inv_AeX_AC_Client_Agent acca
ON vC.[Guid] = acca.[_ResourceGuid]
INNER JOIN (
SELECT ResourceGuid, LastConfig = datediff(dd,MAX([StartTime]),GETDATE()),
LastConfigDate = MAX([StartTime])
FROM Evt_NS_Client_Config_Request
GROUP BY ResourceGuid
HAVING DATEDIFF(dd,MAX([StartTime]),GETDATE()) <= 30 --change to a lower number if desired
) AS a
ON a.ResourceGuid = vc.Guid
WHERE 1 = 1
AND vC.[Guid] NOT IN (
SELECT DISTINCT _ResourceGuid
FROM Evt_Inventory_Rule_Summary
)
AND acca.[Agent Name] = 'Altiris Software Update Agent'
________________________________
The results of this report will be all machines which have requested configuration from the NS within the last 30 days but have not sent an Inventory Rule summary (or the Inventory was rejected by the NS for some reason due to some problem).
How to determine which Dell systems may have a battery for recall.
Question | |
How do you determine which systems in your environment may have a battery that needs to be replaced with the Dell laptop battery recall? | |
Answer | |
You can run the following SQL query. NOTE: This query requires that your Notification Server have the Dell Client Manager installed. Select vc.[name] AS 'Computer Name', | |
| Problem | |
| Sometimes after uninstalling a solution from either the Add/Remove Programs or from the Solution Center you find that this has not removed the solution completely from the Database. Some symptoms that you will see is referrences to the Solution in the Tree Structure on the Notification Server Admin Console. You may also see a refference to the Solution when attempting to view the GetLicenseDetails.aspx page which would returns a ASP Dump. | |
| Environment | |
| Cause | |
| At this time the root cause is undetermined. It may be a combination of things including SQL Deadlocks or Security. | |
| Resolution | |
Use the following Solution Removal Tool. In the sample below this will remove Web Administrator for Windows from the Altiris Database. Please remeber when running this tool to select the correct database to run the query against. Please note that you use this Removal Tool at your own risk, Database backup is higly recommended before running. REM Replace GUID with Product GUID of the Solution you wish to Remove from the Altiris Database SET @GUID = '{B2CF75A5-C442-4945-A979-1EAFDD182A76}' Delete from Item where Guid = @Guid | |