Article ID: 50726

Notification Server 6.0 SP3 R13 Release Notes

This document contains the following topics:

Introduction

This update provides support for Microsoft 7 and Microsoft Windows Server 2008 support for the following products and components:

  • Altiris Notification Server 6.0 SP3 (client side)
  • Altiris Application Metering 6.1
  • Altiris Inventory Solution 6.1
  • Altiris Inventory Pack for Servers 6.1
  • Altiris Monitor Solution 6.0
  • Altiris Monitor Agent for Windows 6.0
  • Altiris Monitor Pack for Servers 6.0
  • Altiris Task Server 6.0

Notes:

  • Deployment Solution was previously updated to include Windows 7 support (Deployment Solution 6.9 SP3). See 47793.
  • No update was required for Software Delivery Solution or Patch Solution.

    Known issues with Patch Solution are listed below in the Known Issues section.
Supported Client Computer Platforms:

This update provides support for the Altiris Agent, Task Agent, and solution agents to run on the following platforms:

  • Microsoft Windows Vista SP2 (32 and 64 bit)
  • Microsoft Windows 7.0 (32 and 64 bit)
  • Microsoft Windows Server 2008 (32 and 64 bit)
  • Microsoft Windows Server 2008 SP2 (32 and 64 bit)
  • Microsoft Windows Server 2008 R2 (64 bit)
  • Microsoft Windows 2008 Core SP2
  • Microsoft Windows Core R2

For information about support for Microsoft Active Directory 2008, see article 49882.

Components Included:

This update provides the following components which need to be installed individually:

  • Notification Server 6.0.1323  (SP3 R13 )
  • Application Metering 6.1.55
  • Directory Connector (Active Directory Import) 6.1.74 
  • Inventory Solution 6.1.2004
  • Inventory Pack for Servers 6.1.1058
  • Monitor Solution 6.0.1341
  • Task Server 6.0 build 1524

Back to top

Installation and upgrade

Installing Rollup 13 (R13) for Notification Server 6.0 SP3

To install this service pack:

 

  1. Download Altiris_NS_6_0_SP3_KB50726.exe from the following location:
    http://www.solutionsam.com/solutions/6_0/Altiris_NS_6_0_SP3_KB50726.exe
  2. Run Altiris_NS_6_0_SP3_50726.exe on the Notification Server.
  3. After Notification Server is installed, launch the Altiris Console.
  4. Click the Configuration tab.
  5. Click Upgrade/Install additional solutions.
  6. Install the solution components in the following order through the NS Console:
  • Altiris_TaskManagement_6_0_1524.exe
  • Altiris_DC_6_1_KB49882.exe
  • Altiris_InventorySolution_6_1.exe
  • Altiris_InventoryPackForServers_6_1.exe
  • Altiris_ApplicationMetering_6_1.exe
  • Altiris_MonitorCore_6_0.exe
  • Altiris_MonitorAgentWindows_6_0.exe
  • Altiris_MonitorPackServers_6_0.exe

R13 includes a new NSAgent which has a version of 6.0.2416

Back to top

Fixed Issues in this Release

The following are previous issues that were fixed in this release. This includes the beta release of this HotFix. If additional information about an issue is available, click the Article ID link.

 

 

Issue
Notification Server
Windows 7 display name is Windows Vista

When you install Altiris Agent using the PUSH method, the console displays the Windows 7 Operating System as Windows Vista, but after the installation is complete, the computer name is displayed as Windows 7 Operating System.

Resource discovery also identifies Windows 7 as Windows Vista.

The Help control for the Altiris Agent interface is not available on the Windows 2008 Core Operating System

Windows Server 2008 Core does not support HTML help; thus, the help icon is not displayed.

NS SP3 R11 Altiris Agent does not get installed on Windows 2008 x86/x64 Core Operating System

Install NS SP3 R13 Altiris Agent on Windows 2008 x86/x64 Core Operating System.

NS SP3 R12 Altiris Agent prevents tasks that have the "Only run at scheduled time" from running.

This has now been addressed in the R13 Altiris Agent. See 50822.

Windows 2008 Core machine is listed under package server candidate list

Windows 2008 core platform is not supported as a package server; still it is present on candidate computers for package server dialog.

Inventory policy with "Logged In Context" fails on Windows server 2008 R2 Core machine

Inventory policy with "Logged In Context" fails on Windows server 2008 R2 Core machine

Task Server
Task Server- Power Control task with option “log off” does not work, logs off Windows Vista and above operating systems

Task Server- Power Control task with option “log off” does not work, logs off Windows Vista and above operating systems

Monitor Solution (Monitor Pack for Windows 2003 Server)
MSDTC Category does not get activated on 64 bit clients

“Windows Server 2003 – Basic”/ “Windows Server 2003 – Extended” Monitor Pack > MSDTC Category: Though the detection method is passed, MSDTC Category does not get activated on Windows 2008 (SP2/R2) 64 bit machines (Check Config.xml on client machine).

IIS 6.0 Category does not get activated on Windows 2008 R2 client

“Windows Server 2003 – Basic” / “Windows Server 2003 – Extended” Monitor Pack > IIS 6.0 Category: Though the detection method is passed, IIS 6.0 Category does not get activated on Windows 2008 R2 64 bit client (Check Config.xml on client machine).

IIS 6.0 Category does not get activated on Windows 2008 R2 client

“Windows Server 2003 – Basic” / “Windows Server 2003 – Extended” Monitor Pack > MSMQ Category: Though the detection method is passed, MSMQ Category does not get activated on Windows 2008 R2 64 bit client (Check Config.xml on client machine).

Application Metering
Windows 7 and Windows Vista SP2 64-bit client computers not displayed

When you install the Application Metering Agent on Windows 7 and Windows Vista SP2 64-bit operating systems by using the PUSH method, the Windows 7 and Windows Vista SP2 64-bit client computers are not displayed on the "Client Requiring Application Metering Agent Install/Upgrade" collection page.

Applications are not getting blocked on Windows Vista SP2 64 bit Operating system

Applications are not getting blocked on Windows Vista SP2 64 bit Operating system when user runs the application through “Run” option of Windows Start menu.

Inventory Solution
Inventory Policy and standalone package fails to run on Windows 2008 Core and Windows 2008 R2 Core operating systems

When you run Inventory Policy and standalone package on Windows 2008 Core and Windows R2 Core operating systems, the Inventory Policy fails to run and the standalone package crashes. This occurs because the Windows 2008 Core and Windows R2 Core operating systems do not have certain dependent DLL’s.

The standalone package does not collect any basic inventory if User Access Control (UAC) is enabled on Windows 7, Windows Vista SP2, or Windows 2008 operating systems

If UAC is enabled on Windows 7, Windows Vista SP2 or Windows 2008 operating systems, the standalone package does not collect any inventory.

Server Inventory Policy fails to run on Windows 2008 Core and Windows 2008 R2 Core operating system if run in “Logged In” and “Specified User” context

If you run the Server Inventory Policy under “Logged In” or “Specified” user context, the policy status shows as failed.

AeXBasicInventory.dll version for Inventory and AeXBasicInventory.dll version for Notification Server mismatch

The version of AeXBasicInventory.dll in the \Program Files\Altiris\Altiris Agent folder and \Program Files\Altiris\Notification Server\NS Cap\Bin\Win32\x86 must be the same, but many times a version mismatch occurs.

On Windows Server 2008 Core 32 bit and Windows 2008 R2 Core operating systems, "Logon Name" and “Logon Domain" fields for AeX operating system data class are not populated

 

Inventory Solution does not work when it is installed on a NS that is configured to use a non-default website

 

For Windows 7 (64 & 32 bit) /indir switch of AeXCustInv.exe works when creating “Vista” folder and for Windows 2008 R2, it works when creating folder named “Longhorn” and the NSI gets created.

 

BIOS Vendor,Version & Release Date fields of AeX HW BIOS data class are not populated on Win2008 Core and Windows 2008 R2 Core Operating system when Hardware inventory is run

 

Inventory Pack for Servers
Inventory pack for Server policy and standalone package fails to run on Windows 2008 Core and Windows R2 Core operating systems

When you run Server Inventory policies and standalone package on Windows 2008 Core operating systems, the Inventory policy fails to run and the standalone package crashes, as the Windows 2008 Core and Windows R2 Core operating systems do not have certain dependent DLLs.

The Inventory Policy does not run and the standalone package crashes also on Windows 2008 SP2 and Windows 2008 R2.

 

The standalone package does not collect any basic inventory if User Access Control (UAC) is enabled on Windows 7, Windows Vista SP2, or Windows 2008 operating systems

If UAC is enabled on Windows 7, Windows Vista SP2 or Windows 2008 operating systems, the standalone package does not collect any inventory.

Server Inventory policy fails to run on Windows 2008 Core and Windows R2 Core operating systems if run in “Logged In” and “Specified User” context

If you try to run the Server Inventory Policy through “Logged In” or “Specified” user context, the policy does not run.

Inventory for AEX Srv IIS Status data class is not collected for any version of Windows 2008 operating Systems

 

Inventory for IIS FTP data class is not collected on Windows server 2008 R2 and Windows server 2008 SP2 operating systems

 

Active Altiris Agent Log Viewer window disappears from the Windows 2008 client computer while the Server Inventory policy is running

If you are viewing the Active Altiris Agent Log Viewer window while the Server Inventory Policy is running on the Windows 2008 client computer, the Active Altiris Agent Log Viewer Log window disappears. However, the task continues to run and completes successfully. If you try to reopen the Altiris Agent Log Viewer window, it opens without any error.

If you run Software Inventory policy on a computer having SQL Server installed, the SW SQL Server data class does not gather any inventory.

 

Inventory for DNS/DHCP data class not collected

 

The inventory of "AeX Srv System DSN" data class does not get collected on Windows Server 2008 SP2 and Windows 2008 R2 operating system

 

“Updated Version” field of AeX Srv SQL Server data class does not get populated when user runs Server Inventory policy.

 

Back to top

Known Issues in this Release

The following are known issues for this release. If additional information about an issue is available, click the Article ID link.

Issue
Registry settings are not updated correctly for the user option set in Altiris agent UI for Windows Vista and Windows 7 operating systems

On Altiris Agent UI > Software Delivery page, the options set do not reflect the correct registry location when the User Access Control (UAC) is on.

Workaround: Turn off the UAC of the machine for the user option set in Altiris agent UI to get reflected in the registry.

Altiris Agent service does not start if Data Execution Prevention (DEP) is enabled - KB 51781

Agent will not work when DEP is ON and set to “AlwaysOn”

Workaround: Turn off the UAC of the machine for the user option set in Altiris agent UI to get reflected in the registry.

Task server tasks are not executing on windows 2008 domain controller machine

Task server tasks for example: Script task/ Delivery Software task do not execute on windows 2008 server domain controller machine. But they execute on windows 2008 server machine(without domain controller).

Defragment Computer task is not working in 64 bit OS

Task server- patch management task ‘Defragment Computer’ does not execute on vista (x64), windows 2008 server (x64) and windows 7(x64) machines. On windows 2003(x64) machine this task type executes and returns the success but task instance shows script error when you check the task instance for more details.
This task type works well on all x86 platforms; problem is present only on x64 platforms.

Workaround: Turn off the UAC of the machine for the user option set in Altiris agent UI to get reflected in the registry.

NS SP3 R13 to NS 7.0 SP4 Upgrade
Sequential Software Delivery tasks of Software Delivery Solution migrated from NS6 to NS7 do not get executed most of the time

When Sequential software delivery tasks are migrated from 6x to 7x those get converted to Managed Software Delivery tasks in 7x. These converted tasks do not execute on client machines though state of the tasks is On. These tasks reach to client machine but do not get executed and eventually fails when times out occurs.

Application Metering
The values are not getting retain on Application Metering Solution Page, when upgrading the Application Metering Solution 6.1.32 to 6.1.53

The values on the page Configuration >> Software Management >> Application Metering Solution Configuration page do not remain the same after an upgrade from 6.1.32 to 6.1.53.

Inventory Solution and Inventory Pack for Servers
Altiris Agent Crashes when Server Inventory is run on a machine in upgrade scenario

After NS 6.x Agent is upgraded to NS 7. x Agent, then server inventory is applied on Windows 2008 full machine, the task starts, however the Altiris Agent crashes during the task is being executed.

Policies and tasks once executed are not getting executed for the second time

After NS 6.x Agent is upgraded to NS 7. x Agent, then server inventory is applied on windows 2008 core machine, the task gets executed. Once completed the task does get applied for the second time.

Workaround: Take a clone of Server Inventory. Name it and apply that task. The task gets applied now.

 "Serial Number" of AeX HW SerialNumber data class shows no data

Serial number field does not show any data, i.e. it remains blank on non-branded machines. This data can be seen on branded machines having serial numbers

Monitor Solution (Monitor Pack for Windows 2003 server)

After enabling the Windows Server 2003 Monitor Pack and applying the Windows Server 2008 R2,SP2 and core collection to this pack, the Pack should be activated on these systems after the Configuration Update occurs locally on each Monitor Agent icon the Windows 2008 R2 collection.

A review of the C:\Program Files\Altiris\Altiris Agent\Monitor Agent\Config.xml file should show that the "Windows Server 2003 Monitor Pack" should be enabled and the following Categories should be activated. There are specific issues with each of the Categories and the Rules within the Categories (listed below) on those monitor agent systems running Windows 2008 R2, SP2 and Core:

  1. FTP Publishing Service Category does not get activated on Windows 2008 R2

    "FTP Publishing Service is running on Windows 2008 R2 machines. Here "FTP Publishing Service" Category has detection method "MSFTPSVC(Service, Running)" But in Win 2k8 R2 this service is renamed to 'FTPSVC' due to which that category is not getting activated.

    Workaround: Create Custom rule by replacing NT Event Source name MSFTPSVC by FTPSVC.

  2. World wide web Publishing Service

    Events are generated but still rules are not getting triggered (For Clients: Windows 2008 SP2/R2)

    Workaround: Create Custom rule by replacing NT Event Source name W3SVC by IIS-W3SVC.

  3. Active Directory

    Events are generated but still rules are not getting triggered(For Clients: Windows 2008 SP2/R2)

    Workaround: Create Custom rule by replacing NT Event Source name "NTDS ” by "ActiveDirectory-DomainService”.

  4. Security

    Events are generated but still rules are not getting triggered (For Clients: Windows 2008 SP2/R2

    Workaround: Cerate Custom rule by replacing NT Event Source name SAM by "Directory-Services-SAM”.

  5. Dynamic Host Configuration Protocol Service (DHCP)

    Events are generated but still rules are not getting triggered (For Clients: Windows 2008 SP2/R2)

     

  6. Windows Terminal services

    Events are generated but still rules are not getting triggered (For Clients: Windows 2008 SP2/R2).

    Workaround: Create Custom rule by replacing NT Event Source name "Terminal Service" by "RemoteConnectionManager".

  7. RRAS Category

    The config.xml of a local Monitor Agent will show a valid Application Detection method defined for the ’RRAS Category'. However, this detection criteria is not visible in the NS Console.

Monitor solution upgrade shows Monitor Agent Install policy duplication

Though there are duplicate policies for install/uninstall/upgrade Install/Uninstall/Upgrade happens without any issue.

Workaround:
In case of upgrade policy if you are using agent upgrade policy for first time you can use any of 2 the policies but if you have already used the Windows Monitor Agent Upgrade policy then you need to select the new upgrade policy by checking policy GUID. New Windows Monitor Agent Upgrade policy GUID is “a6296a6e-bf70-42bd-9301-d51418b8090f”.

Or you can just reschedule the used policy.

Patch Solution
Status shown as default after installing updates

 

Installation failed for the Update MS09-062 Office2007-972581-fullfile-x86-glb.exe on Windows Vista SP2 client machine

 

When Package does not exist physically on server patch agent should not retry continuously it should stop retying

 

Not able to import Patch Management Core Solution policy XML file

 

Enable checkbox missing on Default MS Inventory Policy page

 

Warning is displayed on various pages of Software Inventory configuration even after selecting a collection node

 

Global Update Schedule on agent seems inappropriate for multiple schedules

 

Back to top

Where to get more information

For more information, you can use the following resources:

ResourceDescriptionLocation

Knowledge Base

Articles, incidents, and issues about this product.

http://kb.altiris.com/

Symantec Connect (formerly the Altiris Juice)

An online magazine that contains best practices, tips, tricks, and articles for users of this product.

http://www.symantec.com/connect/endpoint-management-virtualization

Online Forums

Forums for users of this product.

http://forums.altiris.com/

Back to top

Version 1: April 30, 2010