Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Altiris Client Management Suite
Showing posts in English
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...

Terry Cutler | 12 Jun 2008 | 0 comments

With all the posting and information about configuring or provisioning Intel vPro technology, it might help to keep the end goal in mind. Configuring of the technology is a necessary step to realizing how it is used.

Joel put together a great series of usage models at In addition, the document linked below was co-authored between the Symantec\Altiris and Intel teams. It presents use cases for remote remediation and shows how Intel® Active Management Technology (Intel® AMT) and the Altiris Out of Band Management work together to improve help desk efficiency by reducing the number of desk side visits. Key usages of remote power control and redirection are shown.

The audience for...

Martin Charker | 12 Jun 2008 | 3 comments

Windows Installer 4.5 is now available as a redistributable system component for the following operating systems:

  • Windows Server 2008, 32-bit editions
  • Windows Server 2008, 64-bit editions
  • Windows Server 2008, Itanium-based editions
  • Windows Vista
  • Windows Vista Service Pack 1 (SP1)
  • Windows XP Service Pack 2 (SP2)
  • Windows XP Service Pack 3 (SP3)
  • Windows Server 2003 SP1
  • Windows Server SP2


Terry Cutler | 11 Jun 2008 | 0 comments

For environments wanting to use USB one-touch to enterprise provision Intel vPro systems - here are some tips and pointers on supported USB keys and ensuring the USB key partitions are setup correctly.

A common error is the USB key partitions are incorrect - some USB key vendors\models have a hidden partition at the beginning of the USB key which breaks the raw I/O lookup used during USB provisioning. Other models differed in responses across OEM platforms. Plus - some OEM platforms disable USB provisioning in the system BIOS.

Take a look at the USB guidelines and associated findings located at

In addition - take a look at the USB Key Provisioning...

SallyS | 07 Jun 2008 | 1 comment

I think out of band management vs in band is an unbelievable step forward in the support area. But unfortunately, I don't know where to begin. Is there a VPRO for dummies manual or VPRO 101 course? Where do I begin....thanks for any help you can provide.

CondorMan | 06 Jun 2008 | 4 comments

Sometimes a Windows Installer will fail with an error 16xx. What does that mean?

You can find out by viewing Microsoft's list of Windows Installer Error Codes and their meanings here. You might want to add that link to your favorites if you manage a lot of .msi installs.

CondorMan | 05 Jun 2008 | 1 comment

If your workstations are using the NTFS file system, you can use COMPACT.EXE that is included with Windows to compress files with a certain extension. For example, to compress all of the .CHM files (which are rarely used), use the command: COMPACT /C /S:C:\ *.CHM

Here is a list of all the available parameters:

COMPACT [/C | /U] [/S[:dir]] [/A] [/I] [/F] [/Q] [filename [...]]

/C Compresses the specified files. Directories will be marked so that files added afterward will be compressed.
/U Uncompresses the specified files. Directories will be marked so that files added afterward will not be compressed.
/S Performs the specified operation on files in the given directory and all subdirectories. Default "dir" is the current directory...
CondorMan | 05 Jun 2008 | 2 comments

I just learned that you can enable MSI logging so that if your installer fails with an error you can see where the MSI failed.

To enable MSI loggging:

  1. Open Regedit.
  2. Go to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer.
  3. Create a new Reg_SZ value named "Logging" with the value "voicewarmup".

While "voicewarmup" is easy to remember, it actually signifies all of the different options that you want to enable.

Here is the complete list of options:

v Verbose output
o Out-of-disk-space messages
i Status messages
c Initial UI parameters
e All error messages
w Non-fatal warnings
a Start up of actions
r Action-specific records...