Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
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 | 12 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...

Invid | 03 Apr 2009 | 1 comment

This is my personal blog on what trials and tribulations an Altiris Management Client Suite n00b must go through to become competitive and proficient in the IT world.

We'll start off with a simple hello and that I'm currently setting up my environment to manage my network of ~4600 nodes.

carubin | 26 Mar 2009 | 2 comments

I cut my teeth in the Altiris world with Deployment Server and it still is my preferred way of managing the workstations in our environment.  I like the speed and the instant feedback.  Today, though, I encountered a situation that made me glad I had NS in my toolkit.

We needed to add an internal web site to the list of trusted sites.  You can do this through a registry entry but the entry is to HKEY_Current_User.  In DS there was no way that I could think of to touch this key but in NS I just set the job to run for all users of the machine and voila problem solved.

WiseUser | 20 Mar 2009 | 1 comment

If an application contains the odbc driver settings, use Retain Registry information as is in setup capture settings. If we capture the driver details as odbc drivers in Wise it will throw an installation error, to overcome this issue capture everything in registry as is and delete the odbc driver entry from odbc section in Wise.

rbrucelee1978 | 19 Mar 2009 | 0 comments

I have noticed that most of the links to sites "designed to help beginners" generally talk about how to create msi's, how to modify these packages or even how to fix some ICE errors. However, these sites do not give beginners any information on very important basic concepts such as Self Healing, Installation Sequences, how to read the logs generated on installation of the msi. These "basic" concepts can help beginners understand things like how these ICE errors occur or say in the even of a failed msi installation where to look in the package based on the information given by the verbose log file.

This site (written by John McFadyen) will provide detailed information on these concepts Windows Installer Blog.

Happy reading!! :-)

Raman | 11 Mar 2009 | 1 comment

In this post I will provide links to KB articles that cover some issues that were encountered and solutions that have resolved them. The intention here is to decrease the pain if you are facing such issues in your environment. I hope it will be informative for you.

What Hardware Information is reported by Hardware Inventory?

See: Article 25924

Inventory Solution report 'Count of Computers with/without Antivirus Software' does not recognize Mcafee VirusScan Enterprise or Kaspersky Antivirus

See: Article 34199

Esther Aladieff | 10 Mar 2009 | 0 comments

At long last the release of Altiris 7.0 was announced in this morning’s keynote. I’ve worked at Altiris/Symantec for almost four years and it seems like for most of my time Altiris 7.0 was “almost” done or that the release was right around the corner. Now it is a reality. Because of my role in the company – I work with customer references – I was most interested in seeing what the early adopter customers had to say.

The three early adopter customers were, Meijer Stores, SMSC, and MaximumASP. All three seemed to have fairly uneventful upgrades in terms of problems with the product, and are excited about the possibilities Altiris 7.0 will have to offer them. Look for customer success stories on all most of them to be posted to the customer success site in the...

Cobra7 | 05 Mar 2009 | 0 comments

Symantec User Migration (SUM) is a great tool to pull a users files, icons, registry settings and Windows settings and put them in a nice and neat little file. They can either then be saved as a backup or installed onto another PC.

The Following back files are what I use to capture and restore a users settings. I keep them out on the network for easy access. Also please note I have SUM installed on the network server and a custom SCMMigrationOptions.xml is being used.

To Capture I use:

@echo off
echo "This will use SUM Wizard to capture a users data for Desktops"
echo "Enter name "
set /p UserName=

echo "Saving to \\Server\share\User_Migration\%UserName%.ump
\\Server\share\SUM\User Migration Wizard\SUMWizard.exe" /action:create...

Cobra7 | 03 Mar 2009 | 9 comments

This is for the Windows (and WinPE) drivers for any PC that uses Intel network drivers 825XX (Such as 82567LM for example) and how to put them into WinPE.

First you will need to download the drivers from Intel, NOT Dell or HP or whatever brand you have.

You can find the site

On the search, type in the network card type (example, 82567LM). Follow the instructions, make sure you get the Vista drivers and not the ones for Windows 64.

The file you should be downloaded should be called "PROVISTA32_v13_5.exe"

Next, you can either use WinZip or WinRAR to extract the files by following this Blog: