Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Symantec Management Platform (Notification Server)
Showing posts in English
apascucci | 18 Jun 2008 | 1 comment

Using Terminal Services client to connect to the NS Server, we need to add the "/console" command line switch to prevent installation failures. No surprise there!

But I had some issues while with a customer (corrupt installation or strange behavior...), so I took a few minutes to make sure it wasn't 'my fault'.

I checked the server Terminal Services Manager Session ID, which should be 0 (zero) when connected in Console, and it wasn't!

Then I did


As I'm running Vista, the /console is /admin

Thanks MSFT,
Nice try to confuse me ;o)

CondorMan | 18 Jun 2008 | 0 comments

If you've ever had a domain join fail, you can understand how frustrating it can be to troubleshoot. There is a log file that will make it much easier to figure out what is wrong.

  • Open the file C:\WINDOWS\Debug\NetSetup.log.
  • Go to the very bottom of the file and find the last "NetpDoDomainJoin: status:"
  • If it is not 0x0, then the domain join failed and the code listed instead of 0x0 is the reason it failed.
  • Now, look at each previous line in the file until you come across the last line in the file that returned the same failure code as your Domain Join.
  • You have found the step of the domain join that failed and the reason it failed.
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 /?"

marcoads | 17 Jun 2008 | 1 comment

In any environment, it is an advantage to have the ability to control how many resources will be targeted during the automated push install of the Altiris Agent. In addition, old computer registrations, laptops that are off the network and other unavailable resources, might add unnecessary load. How would one deal with these problems?


In order to provide for these functions, a custom collection must be created for the Push install to utilize. This collection should be built up using the following SQL statements (not all will be applicable to everyone).

  #SELECT TOP x limits the total size of the collection
  SELECT TOP x Guid FROM vResource  
  #Unmanaged computers
  WHERE IsManaged=0
  AND ResourceTypeGuid LIKE '493435F7-3B17-4C4C-B07F-C23E7AB7781F'
  #Agent push has not been attempted and failed in last 1 day (...
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...
vortex0007 | 22 May 2008 | 0 comments

For my Altiris implementation I have SQL 2005 64-bit running on a 64-bit Windows Server 2003 server. One of the most frustrating parts of getting this server properly configured was getting the 64-bit version of ASP.NET 2.0 properly configured prior to installing SQL.

Here's the steps necessary to make this happen:

To run the 64-bit version of ASP.NET 2.0, follow these steps:

  1. Click Start, click Run, type cmd, and then click OK.
  2. Type the following command to disable the 32-bit mode:
  3. cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
  4. Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:
  5. %SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
  6. Open IIS...
johnquinn | 16 May 2008 | 9 comments

Do you hate, when launching the Altiris console for the first time, that you have to install those CAB files?

Well, Altiris has provided a neat little utility to install those CAB files for you.

I found this information on the Altiris Forums and I thought it would be something really good to post here as well.

The file is called AltirisNSCABInstaller.exe. It is located in the NSCap share under Bin\Win32\X86\NS CAB Installer Package.

All you have to do it run this file and it installs those cab files for you.

I ran a test on two freshly imaged machines. I installed this on only one. On that machine I didn't get prompted to install the CABs, whereas on the other one I did.

This has now become part of my deployment process. I simply created a DS job and pointed it at that file.

This is not a completely...

vortex0007 | 14 May 2008 | 0 comments

During the architecture and design of an Altiris solution, network traffic is a key factor to determining server placement. The following chart shows the typical network traffic generated between the Altiris Notification Server and the Altiris Notification Server Agent. Use this as a guideline to help plan the placement of Altiris architecture components.

Component Traffic Frequency
Configuration Update 232 bytes Once every 12 hours
Basic Inventory 6 Kb Once a day
Package Installation Depends on Package size For example a 100 MB package will generate 100 MB of traffic. Depends on number of packages
Creating Package from Source Files Varies by Package...