Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Client Management Suite
Showing posts in English
marcoads | 16 Jul 2008 | 0 comments

Want to recover the Recovery Solution cluster settings in the Notification Server database? This tip will tell you the method to do so.

• Operational knowledge of the SQL Enterprise Manager required.
• Make sure no jobs are currently running on the Recovery Server and stop the Altiris Recovery Solution Server services.
• Make sure the Altiris Console is closed.
  1. On a fresh Notification Server install Recovery Solution of a correct version, Recovery Solution version can be found in Recovery Solution client registry [HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\Recovery Solution Agent]Product Version =
  2. Create new Recovery Solution Cluster with same attributes as original one:
    • Cluster name, Recovery Solution database name, and database file locations must be the same...
marcoads | 15 Jul 2008 | 0 comments

Configuring Patch Management 6.2 can be a big hassle. This tip will give you a quick summary on how to configure this program. Note that you do need to set up the computer collections and add the needed computers for each.

First, you need to go to Configuration tab > Solution Settings > Software Management > Patch Management > Windows > Default Software Update Agent Configuration and enable the default software update agent configuration policy, and point it to the collection that is to be updated automatically. This will set the schedule for the updates to download and install, and to provide the schedule for rebooting, so the computers do not reboot after each update or at sporadic times throughout the day. This policy can be cloned by right-clicking in the left pane and cloning, but...

Eshwar | 07 Jul 2008 | 14 comments

You can manually delete temporary files and folders from the following locations:
[C:\Documents and Settings\<username>\Local Settings\Temp]
[C:\Documents and Settings\<username>\Local Settings\Temporary Internet Files]

You can ignore the above method since there is a smart way to do it. Just execute the following script and you are done.

'Comment: This script will delete all temporary files and folders

On Error Resume Next

'Declare variables
Dim fso 
Dim oFolder1
Dim oFolder2
Dim oFolder3
Dim oSubFolder1
Dim oSubFolder2
Dim oSubFolder3
Dim colSubfolders1
Dim colSubfolders2
Dim colSubfolders3
Dim oFile
Dim userProfile
Dim Windir

'Set up environment
Set WSHShell = CreateObject("WScript.Shell")
Set fso = createobject("Scripting.FileSystemObject")
userProfile = WSHShell.ExpandEnvironmentStrings("%userprofile%")...
Terry Cutler | 27 Jun 2008 | 0 comments

Frequently I get asked for my favorite online sites, articles and materials in regards to Intel vPro and the Altiris client management environment. Here's a summary - and I'm open to additions by others.

Understanding the Basics and Having a Community of Experts

  • For those new to Intel vPro and wanting to understand more on the core - see the demo and resources here.
  • vPro Expert Center provides a great medium to collaborate (share, discuss, request, etc) - vPro Expert and vPro Activate

Focusing on the value of Intel vPro usage models and associated ROI

Each customer will have a specific interest or expectation in using Intel vPro within an Altiris environment. The top reasons include Out-of-Band Asset Inventory, Remote Power\On, Redirection...

CondorMan | 26 Jun 2008 | 4 comments

There are a few ways to have a batch script wait for a number of seconds. The simplest and most widely available without any additional programs is to use the ping command.

The following is is an example... PING!

ECHO Waiting 5 seconds
PING -n 1 -w 5000 > NUL

CondorMan | 25 Jun 2008 | 0 comments

OSQL is a flexible command-line utility that allows you to run SQL Queries, Commands, and Stored Procedures from the command-line or through a Batch script.

In order to run OSQL, you can either run it on your SQL Server or copy OSQL.EXE and osql.rll to a location that a client machine can run them from.

The syntax for OSQL is:

usage: osql       [-U login id]     [-P password]
 [-S server]      [-H hostname]     [-E trusted connection]
 [-d use database name] [-l login timeout]   [-t query timeout]
 [-h headers]      [-s colseparator]   [-w columnwidth]
 [-a packetsize]    [-e echo input]    [-I Enable Quoted Identifiers]
 [-L list servers]   [-c cmdend]      [-D ODBC DSN name]
 [-q "cmdline query"]  [-Q "cmdline query" and exit]
 [-n remove numbering] [-m errorlevel]
 [-r msgs to stderr]  [-V severitylevel]
 [-i inputfile...
CondorMan | 18 Jun 2008 | 1 comment

Sometimes a Windows Executable, Script, or Command will fail with an error. What does that mean?

While there is no enforced set of error code meanings, most executables and all system commands follow a standard definition of error codes.

You can find out the meanings by viewing Microsoft's list of Windows Error Codes and their descriptions here.

You might want to add that link to your favorites.

CondorMan | 18 Jun 2008 | 0 comments

Have you ever wanted to start, stop, delete, create, or configure a service in your batch script? The "SC" command will allow you to do this and more.

Here are a few examples of how you can use this command:

Start a service sc start ServiceName
Stop a service sc stop ServiceName
Delete a service sc delete ServiceName
Create a service sc create ServiceName binPath="C:\Program Files\InstallDir\Service.exe" start=auto
Configure a service sc config ServiceName <options>

For more information about the settings you can make when creating and configuring services, go to a command prompt and type "sc create /?" and "sc config /?"

Terry Cutler | 17 Jun 2008 | 0 comments

In addition to the many tools, resources, and articles referenced on this site (Altiris Juice), there are additional tools at Intel vPro Expert Center.

The following podcast provides a brief introduction with an encouragement to "self activate".

If you are unable to view the embedded video - the direct link is ...

nravenscroft | 16 Jun 2008 | 1 comment

While running some reports on server hardware I realized that some of the servers were missing the serial, manufacturer, and model information. I needed this information for inventory forwarding and system model counts. After identifying the systems I realized that all of these systems were Windows 2008 64Bit.

I called Altiris and they acknowledged that this is a know issue and is not likely to be resolved until NS 7.0. Well I need this data in the reports today not months down the road.

The Problem

The issue appears to be in the aexsnplus.exe uses 16bit code and the 16bit subsystem is removed from Windows 2008 64bit, so the aexsnplus.exe ends failing to run.

The Solution

Since the information we're looking for is available in a couple of WMI classes (Win32_ComputerSystem & Win32_BIOS), I figured I could...