Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Client Management Suite
Showing posts in English
Terry Cutler | 24 Aug 2007 | 3 comments

The Intel® vPro™ Expert Center went live today. This community site provides collaboration among customers, OEMs, ISVs, Intel, and other contacts. The focus is on deployment of Intel® vPro™.

Anybody can register, view content, post content, and so forth.

The site is available at or

You can also check the primer Podcast as well on

Contribute, collaborate,...

riva11 | 23 Aug 2007 | 0 comments

The original article SVS 2.1 HotFix 2 Available , submitted by Scott Jones can be read by here .

La HotFix 2 per Software Virtualization Solution 2.1 è stata rilasciata nel sito Altiris Knowledgebase. Questa HotFix include numerose fix riguardanti la stabilità ed è raccomandata per tutti gli utilizzatori di SVS . Questo è un aggiornamento cumulativo, che include tutti gli aggiornamenti a partire da HotFix 1.


  • Workaround per difetti nei registri Microsoft che possono causare un blue screen quando sono chiamate certe funzioni di registro.
  • Fix per un problema di compatibilità di IIS -- Nota: IIS non è ancora supportato in un layer SVS ! Tuttavia, una prossima release di Wise Installation Studio richiede che SVS e IIS siano installate assieme nello stesso PC
  • Fix in caso di memory leaks che possono causare un anomalo supero del tempo nelle...
BRING | 22 Aug 2007 | 0 comments

Many people use Patch Management to meet all of the patching needs. Operating Systems, Office installations, and other applications all can get the benefit of Patch Management's capabilities.

When patching MS Office, frequently, access is required to the source files that were used during the install, in order for the patches to apply correctly. But what about other applications, such as MS Visio, and MS Project? Do they have the same requirements?

Well, KB article 37609 may not answer the questions for all other MS applications, but it does give the Visio and Project scoop. See the link here for the answer:

cnpalmer75 | 21 Aug 2007 | 0 comments

The previous post about the RS Tools provided a great run down on what's included in the tool set.

Here is a decent KB article that describes the RS Diag tools in fairly good detail and then how to get the collected data back into the hands of the gurus over in Estonia (that's where all your calls are directed if you need RS assistance) You don't even have to press 1 for English!

SK | 20 Aug 2007 | 0 comments

Patch Management Solution sometimes encounters problems when additional updates are created by Microsoft or when revised versions are released or even when the NS fails to download all of the updates the first time.

These scenarios will prevent you from creating a SW Update Task for the Bulletin until the missing updates have been downloaded.

I have quite frequently experienced that when using the "Recreate Packages" option, the NS still fails to download one or two of the updates.

When this happens, I simply disable the Bulletin, and then stage it again, as this always downloads all updates successfully.

WiseUser | 16 Aug 2007 | 3 comments

We use deferred custom actions to perform actions and manipulate system files. Here's an example where I learned something new about these actions and Installshield \ VB Script.

One of my applications needs to append a value to the Autoexec.bat file, and we use VBScript to do this work. I wrote a custom action to append a value in the .bat file. Since the file is present in "c:\" I used "WindowsVolume" but it was not recognized in the deferred custom action. This is because deferred custom actions doesn't recognize installer properties like SourceDir or WindowsVolume.

To solve this issue, here are the steps we took. This is not an issue if you use WiseScript. But not all projects use WiseScripts.

  1. Create a custom action which has embedded VB code in it that appends the value to the .bat file. Let the custom action name be "APPBAT" and set the custom action as deferred system context and leave the sequence blank -- to be modified later
  2. Create...
robertser | 06 Aug 2007 | 1 comment

When new computers are placed into Altiris it may take up to 24 hours for the system to get all of its patches and inventories completed. This is usally due to collection update times and long configuration update times (6+ hours).

There is an easy way to speed this whole process up and not effect the overall performance of your NS.

  1. Create a collection called "Computers Discovered 48 hours". Using the SQL code below it will contain PCs that are discovered in the last 48 hours.

    SQL Code:

    SELECT vr.guid    
    FROM vresource vr     
    join vComputer vc on vr.guid=vc.guid   
    join item i on vr.guid=i.guid    
    WHERE DATEDIFF(day, i.CreatedDate, getdate()) <= 2
  2. Create a duplicate of the collection "All Windows Desktop Computers Collection (excluding Package Servers)".
  3. Under the Altiris...
Terry Cutler | 03 Aug 2007 | 0 comments

The following is a summary list of key project team roles for successful Intel vPro projects. This is a summary from experiences based on real-world engagements with real-world customers.

Some items may seem obvious - yet sometimes oversight on the "obvious" is what leads to unfortunate realities.

Open to input from community.

  • Project Sponsor and Champion - The executive sponsor with the vision which may have produced or confirmed by the roles listed blow. This individual helps to obtain "buy-in" from other business units, has the insight and foresight to navigate through calm or troubled waters, and understands the potential risks and associated mitigations. Although not a day-to-day project player - this role is still critical.
  • Project Management - Coordination of resources, schedules, expectations, and so forth. A key role for any successful project, which often has representation both inside and outside a production...
BRING | 03 Aug 2007 | 0 comments

What a frustration. You click on your Inventory task and all of the sudden you see the following error: "Error when node clicked: An unexpected exception has occured during CreateInstance."

Read on for the remedy.

Well, the solution to this issue is not a simple as you might think. KB Article 36366, found at gives the best solution to making sure that you database is ready to handle to load that inventory solution can apply.

The bulk of the resolution to this issue comes...

riva11 | 30 Jul 2007 | 1 comment

During remote installation or will running a command script on a remote computer, I prefer to hide as much as possible from the remote computer's display. I've found that even if software installation can be done in a silent mode, there are some things, like OS scripts, that are not hidden. Here are a few tips to make sure you aren't exposing too much to prying eyes.

To hide some time jobs running on the user desktop, I found an easy way and is send a lock workstation command. Using the following method during an installation the only screen displayed is the logon screen. Nothing else is shown.

After this command the user does have to log in again. But it does enable you to run short scripts or use off-hours periods to run your scripts without them appearing on the screen.

Here is the script:

@Echo off