Troubleshooting

You may face problems when using the slipstream process to install Software Virtualization Solution in an XP Service Pack 3 environment. Have you tried? It ends up rolling back.

This only occurs in a slipstreamed XP Service Pack 3 installation.

In the previous 4 sections we covered troubleshooting for the Provisioning process for Intel vPro capable systems. The next few articles will cover troubleshooting the management side once systems have been provisioned. The management of AMT systems can be accomplished through Task Server (via the APIs included with Real-Time Console Infrastructure, or RTCI) or through the Real-Time tab available with Real-Time System Manager (RTSM). Part 5 covers the configuration of Real-Time Console Infrastructure, which both RTSM and Task Server uses when invoking AMT functions.

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.

A common issue for Inventory Solution is for the Inventory Task to crash or hang in one way or another. This article discusses the common sources for the problem, including how to configure Inventory Solution to avoid them, or how to troubleshoot the issue if the standard fixes do not resolve the issue. Also included is the methodology of how to pinpoint where the issue is coming from, including how to generally fix the issues we have seen.

This article shows the troubleshooting methodology we use in Altiris Support to diagnose and remedy problems reported with Software Delivery Task Executions. As there are several components involved with a Task, this document covers all the mechanisms and potential problem points with the execution. This document does not cover download issues, though the symptoms associated with it are provided for reference.

So, finally you've decided to install SVS and you want to build your first packages! On the Juice you've found all the articles about packaging. You found out that you can choose between Single Program Capture and Global Capture. You also found out that a Global Capture takes a lot of work to clean up. You read a post about cmd.exe that enhanced your packaging skills. You even found, downloaded and tested the multiple packaging tool on the Juice.

How can I correct problems with Windows Installer itself? How many times have you asked yourself that question? When registration of the engine is corrupted, all attempts to run .msi packages fail.