Video Screencast Help

Endpoint Management Community Blog

Showing posts in English
Screenbert | 06 Feb 2007 | 2 comments

Ever seen "Pimp my ride"? This takes it to a whole new level. This is the second of a three-part installment for Pimp my Console.

Have you ever wanted to customize your background on your console from blue to something cool?

Well now you can.

Just go to the "C:\Program Files\Altiris\Altiris Web\Images" folder on your NS server and modify the bgLine.gif with your favorite editor.

Be sure to backup your image before modifying it and as always, I would doubt this customization is supported by Altiris.

Now go pimp your console!

Screenbert | 06 Feb 2007 | 1 comment

Ever seen "Pimp my ride"? This takes it to a whole new level. This is the first of a three-part installment for Pimp my Console.

Have you ever wondered what Rollup you were running on your console but didn't remember what version it was? Now you can modify your page to display this.

Open the folder called "C:\Program Files\Altiris\Notification Server" and modify the header.aspx file.

About line number 113 change the text that says:

<asp:label id="lblVersion" runat="server" Font-Name="Verdana" Font-Size="x-small" ForeColor="white" /></b> (SP 3)</td>".

Add (R1) after the part that says (SP 3).

Be sure to back-up your header.aspx before modifying it and, as always...

BRING | 02 Feb 2007 | 0 comments

Have you ever been working so hard in your CMS environment that you inadvertently highlight and (heaven forbid) delete a dataclass that you need? Then this tip's for you, bud.

Whether you've lost a custom dataclass, or even worse, an NS Core dataclass, life becomes pretty frustrating. How do you recover from that mistake, and is data lost?

The answers are fairly simple.

The first thing to remember is the data is more than likely okay. Some item references may be need to be recreated.

In the case of Custom Data Classes, an NSE file can regenerate that info. See the Altiris Knowledge base Article 28243 found at for the details.

In the case of NS Core data classes, the solution is a...

Screenbert | 30 Jan 2007 | 1 comment

After repackaging an application, do you find it a pain to go change 10 different settings inside of the Windows Installer Editor? Here's a tip that's sure to help.

You can take your company standard for these settings and change their defaults. For instance, if you wanted Windows Installer Editor to always create an EXE instead of a MSI, you would follow these steps:

  1. Open your Wise Share Point\Templates folder
  2. Open the "Windows Application.wsi" file
  3. Click Installation Expert and then Build options under the Release definition section.
  4. Change your setting.
  5. Save and close your wsi file

From now on, all of your repackaged applications will use your new...

Screenbert | 29 Jan 2007 | 9 comments

Many times packagers use merge modules for applications to prevent conflicts when uninstalling that application later on. Here's a "best practice" to keep in mind when using merge modules.

There are drawbacks to merge modules, such as if a patch comes out for something in that module. You would then have to create a patch for each application you have.

You may find that it is better to ban merge modules altogether. Instead create a MSI for each of your merge modules and then make them a pre-requisite for the application that requires it.

The benefit of this is that when a patch comes out for whatever is in the merge module you only have to deploy one patch instead of a patch for each module.

stebro | 26 Jan 2007 | 1 comment

Here's another very cool feature of Endpoint Security Solutions -- the reporting of files being copied to removable media.

As cool as this feature is, there is some confusion surrounding it. Read on to get a clear picture.

Removable Media Reporting

ESS focuses on data leakage which explains the approach the product takes. As of the 6.0 release, ESS reports file copies or moves to a removable storage device: USB flash drive, IPod, Fireware drive, etc.

On a related note, files burned to CD or DVD are not currently reported. Do not confuse removable storage with optical devices. The control settings are separate in a policy with only reporting options available for removable storage devices.

stebro | 26 Jan 2007 | 1 comment

Keep your Endpoint Security Solution up to date by applying the latest patches and hot fixes. Here's the info on two of the most recently released code updates.

As of December 2006, there are two hot fixes for Endpoint Security Solution.

Hot Fix 1 addresses problems when copying large files to removable storage devices. See for details.

Hot Fix 2 accommodates Endpoint Security Solution and one of its sub-solutions (Removable Storage Security Solution or Wireless Security Solution) to be installed on the same NS. See for details.

Both fixes will be rolled into service pack 1.

BRING | 24 Jan 2007 | 0 comments

It can really be tough when you want to get your Patch Management system upgraded to the latest version, Patch 6.2. Especially if, throughout the history of your Altiris database, you have moved it, restored it, etc. without using the Altiris AppID account in those procedures.

Make sure that you remember log in as the Altiris APP ID to do any type of database maintenance, when installing or upgrading Patch or other solutions. This will make the upgrades to those solutions much easier.

For specific details on one particular issue, see

Happy Patching!

BRING | 23 Jan 2007 | 0 comments

If you've ever looked at the Resource Manager for a computer resource, you will notice a listing for the Network Interface Cards (NICs). One example might be:

NIC 1: IP Address -
NIC 2: IP Address - - The address that NS Uses

What is not very clear is why the IP address for the NIC that the NS talks to, and that I can PING, is NOT listed as the TOP or PRIMARY one?

Shedding Some Light

There is a stored procedure which, when the Resource Manager screen is selected, returns SORTED (this is very important) results.

When it comes to IP Addresses, comes way before This is why, even though it is not the IP address that the NS is communicating on, it appears to be the primary NIC.

For more technical details, see

BRING | 17 Jan 2007 | 1 comment

The $64 Question:
What Notification Server Rollup must be installed for the Patch Validator to run and fix errors correctly?

The Correct Answer:
Notification Server R2 (KB 25133) must be installed for the Patch Management Upgrade Validator to run and fix issues correctly. The Validator tool is used to prepare Patch Management Servers for upgrade from Version 6.1 to 6.2