Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Tip/How to
Showing posts in English
Mohammad Bamya | 20 Apr 2009 | 1 comment

Once the client machine boots up into the PreOS it will need an IP address to communicate with the Ghost Cast Server, and by default that IP address will come from the DHCP. When there is no DHCP server, the client machine will not get any IP address, hence, the machine will not be able to communicate with the Ghost Cast Server.

To force the PreOS WinPE or WinPE-512 to use a static IP address:

  1. Go to "\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\winpe\ghost" for WinPE and "\Documents and Settings\All Users\Application Data\Symantec\Ghost\Template\common\winpe-512\ghost" for WinPE-512
  2. Remove the read only from start.bat
  3. Edit start.bat using the notepad and add the following line between x: and cd \ghost

    netsh int ip set address local static

    (IP address of with a Subnet Mask of and a Default Gateway of would be set on...

Mohammad Bamya | 19 Apr 2009 | 0 comments

To avoid settting a password to run a Schedule task or Backup Regime, use NT AUTHORITY\SYSTEM in the run as box.

jloubser | 18 Apr 2009 | 3 comments

One of the most frustrating things I have encountered using Altiris for software deployment purposes is that in order for me to push a number of packages to any given target device such that the packages require to be installed in a specified order, I would have to create a sequential software delivery task.
Creating this as a once off or even two or three times is not an issue, but when I become twenty or thirty times with no end in sight then it gets real old real quick.

What I suggest is that a mechanisim be put in place to rank the created packages and that the installation order would then depend upon the ranking the package was given.

For example, say I build a new device and that that device due the the area it is to be employed in requires 20 different applications to be installed before delivery. The build team could then either via the software portal or whatever other mechanisim select the 20 applications required for the installation and press the...

jloubser | 18 Apr 2009 | 2 comments

Of the things I miss the most when working with the Altiris suite the following two things are pretty close to the top of the list:
Customisable user message screens which may be associated per deployment task type. In other words, I don't want to have to create such type things to be part of my deployment package. A simple interface which allows me to communicate with my target audience with reference to what is about to happen on their device would be most useful. Connected to this is the lack of ability to have a countdown timer which may be associated with the task in question. For example, I deploy a certain job which requires the user to click on ok. The problem with this is that most users will just ignore this message, putting it into the background. What would be most useful is if I can set a timer on the job such that if the user has not clicked on ok within the set timeframe the job then automatically executes. This accompanied with a visible countdown box which...

Ram Champion | 16 Apr 2009 | 0 comments

Hi Connect Members,

Here tool for remote diagnostic tool which has improved features. It allows you to connect remotely Altiris to view configurations and troubleshoot.

Link for tool


John Atkins | 16 Apr 2009 | 0 comments

After running into the problem of trying to find out what computers are using what network printers I created a report that will list all of the computers that have a specific printer installed.  This report can also be used to setup a dynamic collection of these systems.  This comes in handy when you look at what the prnmngr.vbs can do (which is a vbscript built into Windows for managing printers).  For more information about this go to

I was able to create a job in NS that would install a printer and delete another printer all based on the collections built with this report.

Since you can not attach .xml files just remove _.txt from the following attachment.

Scot Curry | 14 Apr 2009 | 4 comments

Hi Connect Packagers.  I have agreed to speak at the San Diego Endpoint Management & Security User group.  They have asked me to talk about Advanced Packaging topics.

There are a couple of things that come to mind:  Driver Installation, Self Registration (DON'T DO IT), Upgrades and Patches.

If you were coming to an Advanced Packaging presentation, what would you like / expect to see.

Thank you for your input.

R-Vijay | 14 Apr 2009 | 2 comments

The product code is a Globally Unique Identifier (GUID) that is the principal identification for an application or product. GUIDs are 128-bit values that are generated using an algorithm defined by the Open Systems Foundation to guarantee uniqueness across time and space.

When to Change the Product Code
• The original and updated product installations will be installed on the same machine.
• The name of the .MSI file has changed.
• The component code for an existing component has changed.
• A component has been added or removed from an existing feature.
• An existing feature has become the child of an existing feature.
• An existing child feature has been removed from its parent feature.

When not to change
•For minor changes to a product, the product code does not need to be changed.
•When you add a new child feature to an existing feature that...

R-Vijay | 13 Apr 2009 | 0 comments

While both deferred and immediate custom actions can run in the context of the user initiating the installation, only deferred custom actions can run elevated using the system context.

Deferred custom actions can only be sequenced between the InstallInitialize and InstallFinalize actions in execute sequence tables. Immediate custom actions, on the other hand, can be sequenced anywhere within any of the sequence tables. Deferred custom actions are not executed immediately. Instead they are scheduled to run later during the execution script. The execution script isn't processed until the InstallExecute, InstallExecuteAgain, or InstallFinalize action is run.

Deferred custom actions cannot access the installation database. In fact, deferred custom actions have very limited access to the installation session because an installation script can be executed outside of the installation session that created it. Immediate custom actions have access to the installation...

jjesse | 06 Apr 2009 | 2 comments

When you are ready to migrate to NS7 there are two options or ways to make sure all of your NS6 agents upgrade correctly to NS7. I'll discuss breifly two options and which one I believe is the cleaner and easier method.
When discussing the update of the client agents I ask one question:  Do you have the DS Agent installed on the client?  In the second way to upgrade the agent I'll discuss why I ask that question.
The recommend way to upgrade your agents from Symantec is to first enable the unistall agent policies for each subagent (not the main Altiris Agent) on the NS6 box and wait for the clients to check in, get the new policies and then remove those subagents. While those agents uninstall, make sure the Upgrade Agent policiy is enabled on the NS7 system.  Once the subagents are uninstalled, Inventory, Software Delivery, Patch, etc, then on the NS6 box change the Altiris Agent policy to point to an alternate NS, being the NS7 system. ...