Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Configuring
Showing posts in English
R-Vijay | 13 Feb 2009 | 1 comment

Windows Installer version 5.0 is included in Windows 7 Beta. The MSDN documentation section has been updated accordingly and available for online viewing. The most significant properties being.


This property can be used to reduce the time required to install a large Windows Installer package. The property can be set on the command line or in the Property table to configure operations that the user or developer determines are non-essential for the installation. The value of the MSIFASTINSTALL property can be a combination of the following values.

Value Meaning
0 Default value
1 No system restore point is saved for this installation.
2 Perform only File Costing and skip checking other costs...
Lokeshji | 13 Feb 2009 | 1 comment

"7 Reasons Why your Installations May Fail on Windows Vista (And How You Can Fix Them)" is an article outlining the top reasons why the author sees failures of Windows Installer (MSI) packages on Vista

Windows Installer is not just a technology but also a set of rules and best practices. While these rules have been specified in the SDK for several years, many of them haven't been enforced. While ignoring these rules didn't break your setups in the past, installations that don't follow best practices may eventually fail on Windows Vista. This article alerts you to the most common pitfalls in setup authoring and helps you troubleshoot your installations to be compatible with Windows Vista.

Read it here:...

BRING | 11 Feb 2009 | 0 comments

Rumor has it that there is an auditing feature built into Notification Server 6.x. How do I access, use and and manipulate Notification Server's internal auditing capabilities?

The Auditing capabilities are extremely lightweight and the procedures are simple. The details for them are:

  1. The Notification Server stores changes (add, modify, delete events) to the Database using the NS Item Management's resource data class.
  2. This data class uses the Evt_NS_Item_Management table to store the information. It stores the following:

    ItemGuid, ItemName, ItemAttributes, User, Action, ItemClassGuid, ResourceTypeGuid, Description

  3. Auditing is activated automatically - No user intervention is required.
  4. Auditing is NOT able to be turned off.
  5. Purging is the only method to clean the data.
  6. It...
Deepanshu | 10 Feb 2009 | 2 comments

Runtime Error 339: Component or its dependencies not properly registered.

Check if the package is working fine when logged in into the same system using admin ID and password. If it works that means it's a permission issue which you need to resolve using filemon and regmon.

You can try to register that dll also using regsvr32... sometimes this also resolve the issue.


riva11 | 09 Feb 2009 | 3 comments

Sometimes it happens. Scenario: During a Windows Office 2007 installation someone thought to shutdown the computer. In this case when you start again the Office 2007 installation, you will see a generic error and the setup will not continue.

I found an article that mentioned a Microsoft Knowledge Base with explained the error and the simple resolution. You have only to delete the rgstrtn.lck file!

In the Knowledge Base article, The 2007 Office suite Setup program will not restart after an initial installation is interrupted there is a detaileddescription with the cause and the workaround about this issue.

In case of some kind of issue and before send a new installation package on the computer, better read this KB srticle, delete the file and go ahead with the ususal installation.


dcudney | 09 Feb 2009 | 0 comments

I had a single user that was receiving an error message when attempting to view assets from within HelpDesk. This was the error message:

"Item has already been added. Key in dictionary: "asset_name_633688238248225379" Key being added: "asset_name_633688238248225379"
Exception - System.ArgumentException: Item has already been added. Key in dictionary: "asset_name_633688238248225379" Key being added: "asset_name_633688238248225379"
  at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
  at System.Collections.Hashtable.Add(Object key, Object value)
  at Altiris.AppWeaver.WrappedFlexGrid.PrepareGrid()
  at Altiris.AppWeaver.WebGrid.SetColumnDefinition(String def)
  at _ASP.subAssetTable_ascx.LoadDataSources()
  at Altiris.AppWeaver.TemplateModule.ProcessChildren(Control ctrl, TemplateControl host)"
pcalver | 06 Feb 2009 | 0 comments

Would you like to patch those notebooks out in your company vehicles without leaving your desk? Check out this article from Josh H. at Intel. He is using a Panasonic CF-19 with the vPro technology.

Thanks Josh.

Raman | 30 Jan 2009 | 1 comment

I have just found another useful blog for Altiris have a look at it.

vortex0007 | 29 Jan 2009 | 1 comment

A bit of SQL that I have found very useful for building Collections in Altiris Notification Server 6 (NS6) is posted below.

This SQL is very handy for helping to configure NS6 policies. For example a configuration policy might need different settings based on what subnet a machine falls into.

To use this, open the NS console > choose Resources > under Collections choose My Collections > Right-click on My Collections > Choose New Collection. Use the option to enter SQL directly and cut and paste the SQL below.

You will need to edit 3 places for this to work in your environment.

  1. Edit Line 8 where ip.[Subnet] Like '192.%' to your appropriate subnet.
  2. Edit Line 9, the very last 0 should be changed to be the beginning of your range.
  3. Edit Line 10, the very last number 110 should be changed to be...
MaggieH | 27 Jan 2009 | 0 comments

These keys hold all the information of all Windows Installer products and components that are installed on your workstation.

  • [HKEY_CLASSES_ROOT\Installer]
  • [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Installer]
  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer]
ALLUSER Value Install Type Registry Location
0 Per User HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-21-xxxxxxxxxx-xxxxxxxxx-xxxxxxxxx-xxx
1 Per Machine HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18
2 Per user or machine (this depends what users rights the installing user has) ...