Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Server Management Suite
Showing posts in English
MFINN | 27 Aug 2008 | 2 comments

Here's some SQL that'll query computers with MS Office 2003 without the Office 2007 compatibility pack. Just go to reports, create a new one, and select 'Enter SQL Directly', then copy and paste the sql into there.

SELECT T0.[Domain] AS 'Domain', T0.[Name] AS 'Name',
T0.[OS Name] AS 'OS Name', T1.[Name] AS 'Name' FROM 
[Inv_AeX_AC_Identification] T0 INNER JOIN 
[Inv_AeX_OS_Add_Remove_Programs] T1 ON 
T0.[_ResourceGuid] = T1.[_ResourceGuid] WHERE T1.[Name] 
LIKE 'Microsoft Office%' AND T1.[Name] LIKE '%Edition 
2003%' AND T0.[Name] NOT IN (SELECT T0.[Name] AS 'Name'
FROM [Inv_AeX_AC_Identification] T0 INNER JOIN 
[Inv_AeX_OS_Add_Remove_Programs] T1 ON 
T0.[_ResourceGuid] = T1.[_ResourceGuid] WHERE T1.[Name] 
LIKE 'Compatibility Pack for the 2007 Office system')

piyushnasa | 27 Aug 2008 | 5 comments

Many times I come across articles, where people discuss on which to choose WISE Script or VBScript while creating Custom Action in the package. Here are some advantages and disadvantages of both.

While WISE Script is easy to make, I mean takes less effort, VBScript can be very complicated. People who do not know VBScript often find themselves searching for, and copying code from net. WISE Script can be easily written once you have basic understanding of statements. I give this point as an advantage to WISE Script, but people who know how to code in VBScript, will always choose that as an easy option.

Personally, I prefer VBScript over WISE Script because it has some really good advantages. As you might know, we compile WISE Script to an exe and include that in a package. But in doing this, we lose the code which we have written...

sm4rt | 26 Aug 2008 | 0 comments

Some files or attributes are excluded in the Special Group. File names at the end of the list are not being captured. This useful article will show you the solution.

CondorMan | 25 Aug 2008 | 1 comment

To silently install .Net Framework 2.0 with SP1, follow these two steps.

  1. Download NetFx20SP1_x86.exe from Microsoft
  2. Distribute NetFx20SP1_x86.exe via Deployment Server or Software Delivery Solution with the command-line parameters: /q /norestart

If the silent install finishes with return code 3010, that means that a reboot is required.

CondorMan | 25 Aug 2008 | 0 comments

If you need to silently install the .Net Framework 1.1 to multiple computers, you can follow these two simple steps.

  1. Download the Microsoft .NET Framework Version 1.1 Redistributable Package (dotnetfx.exe)
  2. Crete a Software Delivery Task or Deployment Server Distribute Software Task that runs dotnetfx.exe with the command line parameters: /q:a /c:"install /q"
Antonp | 05 Aug 2008 | 0 comments

I recently experienced an error in my Altiris Log Viewer that came up every 30 min when it was scheduled to run.

Error below:

Failed to find audit ini file at C:\Program Files\Altiris\Altiris Agent\auditpls.ini 
Process: AeXNSAgent.exe (116) 
Thread ID: 632 
Module: AeXAMAgent.dll 
Source: AgentUtils::GetAuditIniPath 
Description: Failed to find audit ini file at C:\Program Files\Altiris\Altiris Agent\auditpls.ini 

Error was resolved by applying the following settings in the Notification Server:

Configuration>Solution Settings>Software Management>Application Metering>Application Metering Solution Configuration. 

There is a section titled Inventory Solution Integration.

Select "Client Based Inventory Solution" and Apply.

This will fix the error and prevent the error messages from appearing in the Altiris Log Viewer again.

BRING | 04 Aug 2008 | 1 comment

Recently, it was discovered that a client machine had a Task History entry for Hardware Inventory, AEXMACHINV.exe of 'Task Stopped'? In fact, AEXMACHINV.exe stays active and in place, showing up in the computers task manager until a time-out occurs. Of course, there was no hardware inventory on the server either. What happened?

Well, occasionally the computers operating system services can become corrupted. In this case, the installation of the WMI service on this computer was in a corrupted state. A removal and re-installation of WMI resolved the problem.

dpeluso | 04 Aug 2008 | 1 comment

I may be crazy but I could not find a nice easy way of reporting on the success of a software delivery task other than the 'status' tab (Which I can't copy to Excel).

So when I came across KB Article: How do I make a report that will give me the same info as the Status tab?

I was very happy however there are 2 issues:

  1. I need to specify the GUID.
  2. I need cannot limit based on success or failed.

So attached is my report that solves these issue, please rename from .txt to .xml.

By the way there are no warranties etc. my environment is NS v6.0.6074

Patrick Tyler | 31 Jul 2008 | 6 comments

In the latest user group meeting, many have asked how a target collection can be created using AD groups for software delivery or other actions. I have found a KB article that tells you how to use SQL criteria to take AD Groups (With Users) and turn them into machine collections for NS policies.

Here is the article for reference: It is KB article number 39250.

I hope this helps!


Bcomp | 31 Jul 2008 | 0 comments

How do you set up the Inventory for UNIX to execute on a Non-English Locale system? This tech tip will help you along the way.

The Bash shell allows for modifying environment variables for child process without affecting the main operating system environment. The main inventory for UNIX/Linux binary is a shell script called 'aex-runinvnow'. By modify the 'aex-runinvnow' script as shown below, we can leave the operating system to use the non-English locale while allowing the script and its child processes to run with the C or Posix locale.

The aex-runinvnow shell script can be found in the following directory on the Notification Server. You will need to drill down to the appropriate platform and processor.

C:\Program Files\Altiris\Notification Server\NSCap\Bin\Unix\Inventory

Open the file in a text editor (see note below...