Symantec Management Platform 7.0 SP4 HF1 Release Notes

Article:DOC2070  |  Created: 2010-02-11  |  Updated: 2010-02-11  |  Article URL http://www.symantec.com/docs/DOC2070
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Documentation


Description



Introduction

Known Issues in this Release

Resolved Issues in this Release

Introduction

This document contains information about the issues that were resolved in the SMP 7.0 SP4 Hot Fix 1.

The fixes in this article apply to the following build numbers:

Product Build Number
Notification Server 7.0.7436
Task Server 7.0.7416.3
Software Management Framework 7.0.7417
Pluggable Protocols Architecture 7.0.7417
Altiris Agent for UNIX, Linux, and Mac 7.0.7461
Network Discovery 7.0.7417
Monitor Solution 7.0.7722
Event Console 7.0.7421

Known Issues in this Release

The following are unresolved issues in this release. For additional information regarding an issue, click the Article ID link.

Known issues in the SMP 7.0 SP4 release are fully described in the Symantec Management Platform 7.0 SP4 Release Notes.

Task Server

   
Known Issue Article ID Defect ID
Task Server SP4 HF1 version number not incremented from SP4

The msi for the 7.0 SP4 HF1 version of Task Management has the same version number as the SP4 build (7.0.7416). Hence the hotfix is registered with that same version number.

This results in "Altiris Task Management" and "Altiris Task Management (x86) 7.0 Sp4 Hotfix 1" being displayed in the Installed Products webpart as both being Version 7.0.7416.

None 2015969

Resolved Issues in this Release

Notification Server

 
Resolved Issue Defect ID
Right-click action needed for Dell RunCmd /(Dell) Check server certificate in RunCmd

Previously, the Command Line Right-Click Action was prohibited from running to prevent malicious vulnerability attacks. This would also stop users/solutions from using it. The Command Line Right-Click Action has been restored; however it requires an extra security layer. Users are required to install a registry entry of the SMP server’s HTTPS certificate thumbprint, and run the Command Line Right-Click Action by HTTPS only.

1923385, 1953098
Uninstalling Patch Management solution no longer causes the Purging Maintenance pages to fail

Previously, when Patch Management solution was uninstalled, a dataclass table was not cleared correctly. This caused an unhandled exception error when you attempted to access the Purging Maintenance pages.

A stored procedure has been updated to prevent this from occurring when the solution is uninstalled.

1931365
Using the Security Role Manager to apply security permissions to items in a folder structure now works reliably

Previously, when you selected a top level folder in the item picker, all sub-level items were marked as selected. This made it appear as though the permissions that you applied to the top level were being applied to all sub-level items. However, if a sub-level folder had permission inheritance turned off, the items in that folder did not receive the new permissions. The item picker now correctly applies the new permissions to all selected folders and items, without affecting the permission inheritance setting on any sub-level folders.

An example scenario was when you applied the Read permission to the 'Agents/Plugins' folder, but found that the 'Altiris Agent Install' folder (a child folder) did not receive it, so was being hidden from the user.

1949054
The Resource Manager script method that handles the Task menu item click events has been modified to include the appropriate resource Guid

Previously, when you selected an item action through the Task menu in the Resource Manager, the page was called without the required resource Guid being supplied. This caused the page to fail with a Server Error message.

1954582
Task Management now collects the correct name for a local Task Server

In scenarios where a customer has only one Task Server running on the Notification Server computer, they have a PreferredNSHost configured in conjunction with a SSL certificate that uses the same name. Task Management now collects the correct name for this Task Server, PreferredNSHost. Previously Task Management was providing the real name of the Notification Server (the FQDN) for use as a task server. However, the client task agent could not connect to it over HTTPS as the server name did not match the name on the certificate.

1970301
The Resource Summary view in the Resource Manager now shows the correct information for total memory

The Resource Summary view in the Resource Manager (menu path: Resource Manager -> Summaries -> Resource Summary) now shows the correct information for total memory. Previously it displayed the value of one memory module instead of the sum of all modules.

1991199

Task Server

 
Resolved Issue Defect ID
/Altiris/TaskManagement/CTAgent/GetClientTaskServers.aspx returns FQDN or Netbios

When a Client Task Agent was requesting a list of the available Task Servers in an environment, either the Fully Qualified Domain Name or NetBios name of the Task Server would be returned. This was inconsistent and would particularly cause issues for agents registering when an SSL certificate would specify the Fully Qualified Domain Name. This has been changed so that only the Fully Qualified Domain Name of the Task Servers is now returned by GetClientTaskServers.aspx.

1926396
Sometimes Client Task Agent does not work after initializing

When a Managed Software Delivery policy was scheduled to run ‘At Computer Startup’, the Client Task Agent would sometimes hang before the policy could be installed. This was caused by the agent not always being fully initialised before the install of the policy was started. This has been rectified to ensure that the agent has completed its start up before any policy is run.

1951932
Altiris/TaskManagement/CTAgent/GetClientTaskServers.aspx does not use PreferredNSHost, if configured

If a ‘PreferredNSHost’ had been configured, GetClientTaskServers.aspx would not use this setting when returning available Task Servers to a Client Task Agent. Instead, the actual Notification Server name would be used and result in the agents not being able to register with the Task Server on the Notification Server. This has been fixed so that if configured, GetClientTaskServers.aspx will now return the PreferredNSHost name for the Task Server on the Notification Server.

1970301
Mismatched tmInsertTaskInstanceEvent stored procedure

The stored procedure tmInsertTaskInstanceEvent was being supplied with more parameters than the procedure required. This has been fixed to ensure that the correct number of parameters are now being supplied.

2002961
tmLockTaskInstanceTables Stored Procedure missing

The stored procedure tmLockTaskInstanceTables was missing from the previous release. It has been restored in this hotfix.

2003474

Software Management Framework

 
Resolved Issue Defect ID
Software Managed delivery into the SVS layer fails is the EXE file is used to install the software

This is fixed.

1941118
A Managed Software Delivery policy cannot correctly install software into a Symantec Workspace Virtualization 6.1 layer

Symantec Workspace Virtualization 6.1 did not allow captures to be done by processes running as SYSTEM. This is now allowed.

The Software Virtualization Solution/Symantec Workspace Virtualization APIs were not being called correctly and therefore the install process was not being tracked during capture. Symantec Workspace Virtualization is now updated to properly use the Software Virtualization Solution APIs.

1922879
Unable to select "Allow the user interaction..." when selecting the option "Whether or not a user is logged in"

On the Quick delivery page, user was unable to select "Allow the user interaction..." when selecting the option "Whether or not a user is logged in". This is fixed.

1947177
Incorrect resource keys are being created when a software resource is created by a software data provider plug-in

The problem was that, if a data provider plug-in supplies a company name such as "Adobe Systems", this name was not used when the resource key was used to generate the software component resource. Instead, the known-as entry of "Adobe" was used. This caused duplicate entries to be created within the software catalog when the keys did not match.

Now, when the resources are created from a data provider, the name that is supplied is used instead of the known-as entries.

1970093
Replicating package delivery task through "Replicate Now" option replicates all the software resources down the hierarchy

Only the software resource that is associated with the particular task now replicates down the hierarchy.

1981656
Replicating QD task through "Replicate Now" option replicates all the software resources down the hierarchy

Only the software resource that is associated with the particular task now replicates down the hierarchy.

1944581

Web Controls

 
Resolved Issue Defect ID
N/A

Pluggable Protocols Architecture

 
Resolved Issue Defect ID
Need to support the common Connection Profile in the SNMPTrapSenderPlugin

This is fixed.

1954956
Altiris.PluggableProtocols.Alert object does not support serialization

This is fixed.

1946706
AMTRedirectionService not registered after upgrade of PPA

This is now registering.

1896166
Cannot connect to the client using the network protocol with custom credentials if another protocol is turned on with runtime credentials

This is fixed.

1940084
OOB Rollout job fails when run on multiple servers

When an OOB rollout job was created on multiple servers from a single S&D Wizard, the 'Staging' completed successfully, but the rollout job ran only on one server and failed on the rest, with the message : A WSMAN Connection could not be established. Check the selected connection profile to see if the WSMAN protocol is enabled and configured correctly. Return code : -4

This is fixed.

1979841
OOB tables missing for Server and iDRAC discovery / inventory

The default Session Timeout was increased from 5 to 10 seconds. If this is not sufficient for your environment, you can override the timeout by creating a new DWORD value in the registry = HKLM\Sofware\Altiris\PluggableProtocols\CimWsman\ConnectionTimout

1975901

Event Console

 
Resolved Issue Defect ID
N/A

Altiris Agent for UNIX, Linux, and Mac

 
Resolved Issue Defect ID
ULM Targeted Settings policies are now migrated correctly from NS 6.2 to SMP 7.0 SP4 HF1

The 6.2 Unix and Mac configuration policies are successfully overwritten with the 'All Linux/Mac Workstations' and 'All UNIX/Linux/Mac Servers' configuration policies. Previously, the 'All Linux/Mac Workstations' policy was replaced with the non-functional 'All Macintosh Computers (excluding Legacy 6.0 Agents). As a result, all Linux/Mac workstations could not update their client.conf files and therefore could not work with the new functionality of SMP 7.x.

See also Known Issue KB 52165.

1950016

Unix, Linux and Macintosh computers now correctly upgrade the agent when redirected from a Notification Server 6.x computer to a Notification Server 7.x computer

Previously, after being redirected by the Advanced Settings policy, the 6.x agents attempted to communicate with the specified Notification Server 7.x. The agents appeared to send basic inventory but they could not refresh their policies from the new Notification Server so were not upgraded.

1953328

Network Discovery

 
Resolved Issue Defect ID
Duplicate entries made in the Inv_VM_Host table when discovering ESX hosts directly, then through their managing vCenter

This is fixed.

1946852
Server IP gets swap with drac IP after doing wmi+wsman discovery when selecting for running task

When a server(R210) and Idrac IP was discovered together using WMI+WSMAN, the server DNS name came with a drac IP when a server was selected from "QUICK RUN" in any task. This is fixed.

1967350
Network Discovery does not clean up host-VM relationships when discovering virtual hosts (ESX and HyperV) that have had VMs deleted or moved

This is fixed.

1896527

Monitor Solution

 
Resolved Issue Defect ID
Altiris Monitor Solution shows as not configured after updating from 7.0 SP4

This is fixed.

1981382
After a restart of RMS, a false alert appears in Event Console if there is more than 1 raised alert in Event Console

Rule state was not stored correctly. Rule state signaling about the load from the file has been moved to the appropriate data structure. Previously, it was working only for the first resource that is monitored by a given rule. All others had broken repeat counts and generated false alerts.

1954925
During monitoring by the PING - Number of Hops metric, it always returns value "-1", even if the resource is available

This was an integration problem. Monitor was incorrectly determining the offline state of the resource when HOPS was requested. The check for off line status is now corrected.

1954148
Ping metric/rule - Getting false alerts from offline servers after monitor agent restart

This is fixed.

1878643
Race condition in the CSwimmingThread leads to a monitor hang on reconfiguration

This is fixed.

1957301
ICMP plug-in performs both Ping and Trace-route requests at the same time and this causes Ping metrics to timeout for distant targets

This is fixed.

1942378
Monitor Agent hangs on UNIX when an upgrade from a pre 7.0 SP3 release is performed

Problem was caused by a not graceful stop of the monitor agent during upgrade. This is fixed.

1966494
Monitor Solution 7.0.7416: NT rule does not trigger with a denial condition

Fixed the NT Event Rule conditions to solve this problem.

1968553
Monitor Solution 7.0.7416: Upgrade - Unnecessary monitor agent rollout-upgrade policy appeared after Monitor Solution 7.0.7416 SP4 RC upgrade

This is fixed.

1950897
MonitorMetricData Table gets only partial data update

This is fixed.

1958831
Need to change the GUID of an upgrade policy for every release

To avoid a possible issue with client upgrades, when clients do not receive upgrade policies because a previous version of policies is already active on the client, we now change the GUID of the upgrade policy every release.

1940104


Legacy ID



51432


Article URL http://www.symantec.com/docs/DOC2070


Terms of use for this information are found in Legal Notices