Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Client Management Suite
Showing posts in English
cnpalmer75 | 21 Feb 2008 | 0 comments

This is another posting in regards to the articles I've done for Recovery Solution (RS) in the past based around the events which may occur that get written to the application event log.

Over the course of using this data, I have been able to identify several error sets that always occur in these pairs and in these sequences. Tracking these down was difficult since RS re-uses the same source, category & event ID for different events, only the description is changed. This, IMO, seems to be poor coding.

This is helpful in identifying a particular asset that may be creating these events for further investigation.

The cause of these is still unknown as I am working with Dev in Estonia to come up with a suitable answer, but for now being able to identify and track these error sets is the first step.

Hopefully, you do not see these in your environment.

BRING | 21 Feb 2008 | 0 comments

Task Server has added some great new capabilities to the Altiris environment. And some solutions are taking advantage of those capabilities. Software Delivery is one of them.

However, it is important to make sure that you have rolled out the Software delivery Agent for Task Server to all of the machines necessary. Otherwise you might just encounter an error like the one below:

Process: w3wp.exe (5152) 
Thread ID: 2376
Module: AltirisNativeHelper.dll
Source: Altiris.ClientTask.Web.RequestSubAgent.Page_Load
Description: Error getting subagent file ( Unhandled exception. Type=System.Exception Msg=Matching agent not found in the database:
AgentName='SWDAGENTFORTS.DELIVERSOFTWARETASKHANDLE', PlatformName='WINDOWS%20SERVER%202003', PlatformType=Production, OSType='WIN32' Src=Altiris.ClientTask
at Altiris.ClientTask.ClientTaskSubAgent.Load()
at Altiris.ClientTask.Web.RequestSubAgent.Page_Load(Object sender, EventArgs e) )

This occurs when a client...

BRING | 13 Feb 2008 | 0 comments

Naming objects in our Notification Server environment. Seems fairly simple, but the process can be a bit troublesome. Or naming applications, or custom dataclasses. Some times we like to use reserved characters in those names to be descriptive. Characters like($ ; & + , / : = ? @) are reserved characters, specifically to IIS.

These things can cause problems for custom inventories especially. You could see errors like:

Unable to process the file "...\Altiris\Notification Server\NSCap\EvtQFast\Process\INVblah.nse" Moving to "...\Altiris\Notification Server\NSCap\EvtQFast\Bad\AeXException\nseXXX.tmp". Reason: Failed to process NSE System.Xml.XmlException: An error occurred while parsing EntityName.

Certainly, if you can avoid the use of these characters in your naming conventions, that helps.

However, best practices...

kbuller | 06 Feb 2008 | 5 comments

I did a search for "Macintosh" on the Juice site the other day and came up with 4 results... Hopefully this article will be of interest to at least a few people.

The latest release of the Deployment Console supports Macintosh clients but in its current state it is no match for Apple Remote Desktop. I just wanted to share a couple scripts that I use from ARD to make the most out of the Altiris Client for Mac.

Click the "Unix" button on the toolbar of ARD and place these scripts in it.

Refresh Altiris Client Policies


Send Basic Inventory


Run Inventory

Replace -x on the last line with -r for Full, -h for Hardware, and -s for Software

#! /bin/sh...
MarioR | 19 Dec 2007 | 3 comments

While looking for information regarding package server redundancy, I was unsuccessful in locating any references. Hopefully, this posting will fill the missing information gap.


If a package server was defined for a site and that package server goes down, how will the Altiris Agent clients respond? Original thought was that if the clients were unable to pull from the package server, the clients would fail over to the NS to get their distribution.

Testing Results:

The client tries to download the package from the package server assigned to the site (which was shut down for testing). Since the server was down, initial download was unsuccessful but then client tried to connect again in 3 minutes, then 6 minutes. The check-in time kept doubling until the client checked every 2 hours. From that point on, the...

pragya_gupta | 14 Dec 2007 | 3 comments

Application packagers know there are some vendor MSIs that just can't be edited with Wise but can be edited with ORCA. If, in such a case, we want to add a file to the package, we can't with ORCA because ORCA has limitations and can not compress the file. In these cases, you can follow the steps given below to add the file to the package.


  1. Make the .CAB FILE of the File you want to add using makecab command.
    Makecab [Source] [Destination]

    Where source = path of the file along with file name and Destination = Path where you want .CAB file.

  2. Go to Component Table
    1. Make a component with the name of the file you want to add.
    2. Set the directory column with the path where you want to install the file.
  3. Go to featurecomponent Table
    1. Associate the component made in step 2 with the feature (Complete in case of captured Application).
  4. Go to File table...
BRING | 13 Dec 2007 | 0 comments

If you've been hearing this, "I have some limited access users that need to be able to use the passwords that Local Security Solution maintains. I keep getting errors like "Unable to discover your essential user data for logging purposes". What changes do we need to make to allow them access?" then this tip's for you, Bob.

In the attempt to extend access for Local Security Solution to a security role in Altiris, some errors were encountered.

The role was given the following privileges:

  • Item Tasks --> Show Managed Password, Show Current Password
  • Item Tasks - Local Security --> Show Managed User Passwords

And the following item permissions:

Report for LSS Access - Read, Run Reports
Resource Management/Resources/Defaults --> Read Resource Data, Read Resource Association, View Password, Write Resource Data

When logged in as a member of the limited access security role, a right-click is performed on a...

R-Vijay | 10 Dec 2007 | 11 comments

Using Wisecomcapture is always the best option to use when registering a DLL. See this article for some background.

But, if there is a case when the DLL doesn't exist in the package and there is a necessity to register a file manually, this tip should prove handy.

To manually register a .DLL using regsvr32.exe in a .MSI package:

Step 1: Go to MSI Script in the WSI project.
Add an Execute Program from Destination custom action after InstallFinalize in the Execute Immediate tab.
The Execute Program From Destination dialog appears.

Step 2: Fill in the following information:
Custom Action Name: <registerdll>
Working Directory: Enter SystemFolder
EXE and Command Line: Enter the full path to regsvr32.exe and the full path to .DLL.
Example: [SystemFolder]regsvr32.exe [WindowsFolder]123.DLL

Step 3: Accept all other defaults and click OK.


R-Vijay | 07 Dec 2007 | 0 comments

The internal version number for Windows Vista is 6.0. The GetVersion function returns this version number. The problem is, some applications will return a higher version number. This means trouble. Learn how to steer clear, here.

Symptoms of OS Version

  • Applications that check for OS version will get higher version number.
  • Application installers may prevent themselves from installing the app and apps may prevent themselves from starting.
  • Applications may warn users and continue to function properly.

Mitigation Techniques for OS Version

  • For apps and installers that check for OS version, a Compatibility mode is provided in Windows Vista
  • Users can right right-click the shortcut or the EXE and apply the Windows XP SP2 compatibility mode from the Compatibility tab. This applies multiple shims including "WinXPSP2VersionLie"
  • Better: Apply the shim "WinXPSP2VersionLie"
  • In many cases, applications...
kmieciooo | 06 Dec 2007 | 2 comments

Sometimes there is a need to slow down a software deployment. I had it once -- when deploying encryption software. In my case the problem was main encryption server -- which was not able to process more than 50 events from clients.

Here's how to sloooooow your deployment down a bit.

I was wondering how to deploy it slower to my more than 1000 machines. SQL helped me with simple solution -- which is -- using a SELECT TOP query in the target collection.

Simply create your target collection using the SELECT TOP ... query and it will be updated in next collection update cycle.

Enjoy your slow uptake ;-)