Notification Server 7.0 SP5 Release Notes

Article:DOC2172  |  Created: 2010-06-14  |  Updated: 2010-11-16  |  Article URL http://www.symantec.com/docs/DOC2172
Article Type
Documentation

Product(s)

Languages

Description



Build number 7.0.8641

This document contains the following topics:

 

Introduction

This component is part of the Symantec Management Platform 7.0 SP5. For release notes, see knowledgebase article DOC1956.

Back to top

 

New Features

There are no new features in this release.

Back to top

 

Installation and Upgrade

Prerequisites

Windows Server 2000 was end-of-life with Symantec Management Platform 7.0 SP4. It is no longer supported. Windows Server 2003 or later is required for the platform, and Windows XP or later is required for desktops.

New installation

You can install this product by using the Symantec Installation Manager. You can download the installation files directly to your server or you can create offline installation packages.
For more information, see the Symantec Management Platform Installation Guide (see knowledgebase article

Upgrade

You can upgrade this product from 6.x versions if you run the Symantec Installation Manager on a Notification Server 6.x computer. To upgrade from the 6.x version, you must first upgrade your 6.x Notification Server to Symantec Management Platform 7.0 or later. During the Notification Server upgrade process, you can select to upgrade to the latest version of this product.
For more information, see the Symantec Management Platform Installation Guide (see knowledgebase article HOWTO9795).

Installation and upgrade issues

The following are known issues related to installing and upgrading this product. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID
Upgrading Notification Servers in a hierarchy
When you have a group of Notification Servers joined in a hierarchy and you wish to upgrade them to a higher service pack of Notification Server 7.0, you should follow the suggested best practices.		 HOWTO21657  N/A

Back to top

 

Fixed Issues in This Release

The following are previous issues that were fixed in this release. If additional information about an issue is available, you can read it by clicking the Article ID link.

Issue Article ID Internal ID
Altiris Agent Installation Page - Discover Computers link not working in all circumstances
If you nagivate to the agent installation page from the top menu by clicking on All settings, the discover computers link works correctly. However if, from the top menu, you selected Settings > Agents / Plus-ins > All Agents / Plug-ins, then the discover computers link on the agent installation page did not work.This issue has been fixed.		 N/A 1584249
Linux computers now return the correct name reliably
Previously, in some scenarios, multiple Linux computers returned the same computer name, such as “localhost.localdomain”. This was because Linux basic inventory sometimes merged all clients that had the same 'name.domain' value on statically configured networks. On statically configured systems, resources keys and basic inventory now return the correct values for hostname, domain, FQDN, regardless of the entries in /etc/hosts file.However, as systems can be configured manually in many ways, there is still a possibility that unexpected values may be reported as network information. Refer to the Knowledgebase article for more information.		 TECH133273 1974547
Unable to add more than one IP address in the Altiris Agent Install page
When you wanted to push the Altiris Agent to multiple computers, you could specify the appropriate IP addresses in the Altiris Agent Install page (menu path: Actions > Agents/Plug-ins > Push Altiris Agent). However, in some circumstances you were unable to add more than one IP address. Clicking the Add button to add a second IP address had no effect.This issue has been fixed.		 N/A 1843039
Push or pull installation of Altiris Agent to RedHat 3 computers sometimes failed in SMP 7.0 versions prior to SP5
The following error message was logged:.data/AltirisAgentInstaller.bin: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directoryThe reason for the failure was glibc-2.3.2-95.30. That package did not install libraries into /lib directory. This issue affected any installation to RH3 computers that had an outdated version of glibc.As RH3 is no longer supported, this issue is considered fixed.		 TECH47692 1906065
Explicitly excluded resources cannot be removed from a filter
This issue did not affect explicitly excluded filters but excluded resources. Prior to version 7.0 SP5, when you tried to remove explicitly excluded resources from a filter, your changes were not applied. Instead, this is what happened: You attempted to remove an excluded resource from a filter (menu path: Manage > Filters and selected the filter in the left pane. Then, in the Filter page you clicked Edit, and under Explicit Inclusions and Exclusions you clicked the Resources excluded in this filter link), but the changes were not applied to the filter. The original list of excluded resources remained in place. Updating the filter membership had no effect.This issue has been fixed.		 N/A 1852504, 1870092
ForwardServer table contained many duplicates of the same Notification Server name
When you ran a query on the table ‘ForwardServer’, it contained two entries for the local Notification Server computer. When adding a hierarchy, removing a hierarchy, then re-adding, new entries were put into the ForwardServer table for the same Notification Server name. This was showing up on stand-alone replication rules.This issue has been fixed.		 N/A 1582301
Resource replication rules cannot contain more than 60 resource types
Previously, when creating resource replication rules, you had to specify the resource types and the data classes to replicate. However, if you selected a large number of resource types, an error sometimes occurred when you attempted to select the appropriate data classes. When you clicked the Data Classes link, the following error message was displayed:Failed to construct the dynamic Virtual Window.This issues has been fixed. You can now select more than 60 resource types in a resource replication rule and do not need to create multiple replication rules.		 N/A 1585854
You cannot create a new hierarchy relationship via remote console from a Notification Server with a non-default port
If you were on a Notification Server that was using a non-default port, and you accessed another Notification Server using remote console and attempted to create a new hierarchy relationship (menu path: Settings > Notification Server > Hierarchy to open the Add Hierarchy Node Wizard), the attempt failed.When you completed the Add Hierarchy Node Wizard and clicked Finish, the Hierarchy Node Progress dialog box appeared with the error “Hierarchy Node Process failed. Please review the log for details.” The log viewer logged the error “Failed to retrieve remote server guid.”This issue has been fixed. Note that this issue affected only the specific scenario described in this entry and that it also works correctly in the following scenarios:
  • Creating the hierarchy relationship via the actual Notification Server machine (not using remote console).
  • Creating the hierarchy relationship from a Notification Server using a default port to a Notification Server that uses a non-default port.
 N/A 1847386
The Subnet column name in the New Site window reverts to English after you add a new subnet to the site
If you created a new site and then added a new subnet to it, the Subnet column name in the New Site window reverted to English. (This is the menu path to the previously occurring error: Settings > Notification Server > Site Server Settings. In the left pane, click Sites, in the right pane click New to open the New Site window, and then click New to create a new subnet.)When you clicked OK in the New Subnet dialog box, the new subnet was added to the New Site window, but the Subnet column name was then displayed in English.This issue, which affected all languages, has been fixed.		 N/A 1868836
Packages may go missing when you upgrade SMP service packs
Previously, when you upgraded Symantec Management Platform version 7.0 service packs, tasks that involved downloading a package via HTTP may have failed. This issue did not affect packages that were available via a UNC path.This issue has been fixed.		 N/A 1678272
In the Report Query Builder, the registry path that you specify for a report parameter may not be saved
When you created or edited a report, if you used a Registry Parameter Value Edit Control as the value provider for a report parameter, the path that you specified was not saved. (In the Report Parameters tab within the Query Builder, open the Parameter Editing/Creation Dialog, and under Value Provider, select Registry Parameter Value Edit Control. In the Registry Path box, enter the appropriate valid registry value and then click OK.)When you reopened the Parameter Editing/Creation Dialog after performing those actions, the Registry Path box was empty. If you added the parameter to the report query, the report failed to run.		 N/A 1870221
The Objects Replicated drill-down report now returns the correct results for all installations.
Previously this report sometimes returned no results. This issue was fixed in version 7.0 SP4 for fresh installations only and still existed on upgraded systems.This issue has been fixed in version 7.0 SP5 for all installations.		 N/A 1892402
Changes that you make to a report query using the Query Builder in Basic mode are now saved correctly
When you modify a report query using the Query Builder in Basic mode, the changes are now saved correctly. Previously when you modified an existing report using Basic mode (the default mode) the changes that you made appeared to be processed (you saw a “please wait...” message) but they were not saved. The filter expression and resolved query still reflected the original state. You needed to switch the Query Builder to Advanced mode to make the necessary changes.		 N/A 1912860
Previewing a URL-based web part on the Web Part Configuration page fails if you are using both IE8 and SSL
If you created or edited a web part by using the Web Part Configuration page (menu path: Settings > Console > Web Parts), you were able to view the web part in the Preview panel (click Show Preview) before saving the changes. However, if the web part content was a URL (you specified the URL in the Show URL box), and you were using both Internet Explorer 8 and SSL, the preview failed. A message saying “Navigation to the webpage was canceled” was displayed.This issue has been fixed. It did not affect any other Internet Explorer / SSL scenario:
  • Using IE8 without SSL works correctly.
  • Using IE7 with or without SSL works correctly.
 N/A 1871519
Security Roles do not display correctly after you reconfigure the CMDB
As part of previous service pack upgrades (for example, the SP1 to SP2 upgrade process), you may have wanted to reconfigure or upgrade the CMDB. You were able to reconfigure the CMDB manually by way of the Database Settings page of the Symantec Management Console (you select the appropriate database and then click Reconfigure Database). However, after you did this, the security roles were not displayed correctly: when you viewed the list of available security roles (menu path: Settings > Security > Roles), none of the security roles were shown.To resolve this issue, you had to navigate to another menu option and then return to the Security Roles page. The list of security roles was then displayed correctly.This issue has been fixed, and the workaround is no longer necessary.		 N/A 1710256
Passwords with the “;” character are not supported
The “Use privileged account multiple passwords” option did not support passwords with the “;” (semicolon) character. This character was always treated as a separator between passwords.This issue has been fixed.		 N/A 1775542
Creation of Organizational views and groups now controlled by the Create Children permission
There was no Create Children permission on individual organizational groups or views. There is a Create Children permission on the top level folder 'Organizational Views'. This create children permission inherits down to all the organizational views and groups. If you broke the inheritance for a role, you could no longer create organizational views and groups unless you gave the role full permissions. There are now separate Create Children permissions on each organizational view and group which gives you the ability to create child organizational groups.		 N/A 1582683
Restore defaults not restoring the default control state for a particular multicast setting
This issue has been fixed.		 N/A 1582962
Added the IP address to the computer information on the Resource Manager Home page
Added the IP address to the computer information on the Resource Manager Home page. Also, seperated the GUID from the Name, Domain, OS, IP information.		 N/A 1584794
Database Settings: Now can connect to the database when saving changes or reconfiguring on SQL 2008 computer
When Notification Server was installed on a SQL 2008 computer, in the Database Settings page, when you connected to another database server, then pointed back to the localhost DB, then clicked Save Changes or Reconfigure, the following error message appeared:Failed to connect to the database using the database credentialsIf you refreshed the page, then reconfiguration appeared to work fine.This issue has been fixed.		 N/A 1585262
When loading column mappings on an AD connector rule, an error occured if there were duplicate dataclass names
Added the IP address to the computer information on the Resource Manager Home page. Also, seperated the GUID from the Name, Domain, OS, IP information.When loading column mappings, all dataclasses were selected and then their names were put into a sorted list (arrSorted). These sorted lists could not handle duplicate strings.This issue was occuring with HPCMS which has duplicate named inventory and event tables in DataClass.This issue has been fixed.		 N/A 1585687
Report outputs saved in spreadsheet format now showing in correct characters for all non-English characters
When a report was saved in spreadsheet formt, all non-English characters displayed in garbage characters in the file.This issue has been fixed.		 N/A 1599835
A clone of a resource association now clones all the fields
A clone of a resource association did not clone all the fields. Some fields were returned to a default value.This issue has been fixed.		 N/A 1661461
For Query Builder, ‘NOT’ logical operator now not being removed from query when report is saved
This occurred when using the Query Builder to create a report query containing the ‘NOT’ logical operator. The query was initially resolved as valid and running the raw SQL that was generated. When the changes were saved, the NOT condition was being removed.This issue has been fixed.		 N/A 1674265
Notification Server registry was being deleted during upgrade from Notification Server 6 to Notification Server 7 on box
When upgrading from Notification Server 6 to Notification Server 7 on box, the Notification Server 6 agent is automatically upgraded. The agent upgrade logic was migrating the Event Logging registry from the Notification Server to the agent and deleting the Notification Server registry.This issue has been fixed.		 N/A 1716013
Managed delivery policy did not execute if the scheduled time was 00:00
The policy now gets executed immediately when it is scheduled at 00:00 as expected.		 N/A 1750442
Symantec Management Server Error was displayed if the user did not have permission to access Automation policies
Now no server error is displayed when accessing the Manage > Automation Policies, either when permissions are given or not given.		 N/A 1792461
Hierarchy Management, Replication Page resets State of Resource Replication Rules
This issue affected resource, event, and advanced grids. A change was applied to address the issue in each of these grids.		 N/A 1829620
Symantec CMDB transaction log growth limit increased
The Symantec CMDB transaction log growth limit was increased as follows:Data file - Initial size: 1GB, growth by: 500MB, maximum size: unlimitedTransaction Log - Initial size: 500MB, growth by: 500MB, maximum size: 2GB		 N/A 1834510
Agent Push does not read proxy configuration
An environment that had a firewall between clients and Notification Server required computers to use a proxy server to communicate with Notification Server. A proxy configuration was implemented to fix this.		 N/A 1841058
Hierarchy/Replication default settings were too small for new target environment sizes
The default timeout for hierarchy and replication jobs during retry, and for the wait time for destination processing, was set to 24 hours. The timeout is now set to 48 hours. Also, the default maximum number of data class rows per replication was increased by a factor of 50.		 N/A 1843558
User created Shared Schedules can now be renamed
The Shared Schedules page has been modified so that shared schedules can now be renamed.		 N/A 1843674
Recovery Home Page now displays Web parts and Pie charts that were hidden
There was no user interface on the Recovery Home page. This happened because the Web part was hidden from the Portal View because its required product was not installed.		 N/A 1848671
Full error with stack trace was shown when Invalid SQL entered in Query Builder
Instead of the invalid query being handled gracefully, the full error was displayed plus the stack trace. An appropriate error is now displayed.		 N/A 1853708
Unable to drilldown using "Selected Data" parameter
The included parameter types are now passed the selection information and the failing drilldowns are now fixed.		 N/A 1854970
Constrained Package Server grid lost state of tick boxes on any refresh of the grid which includes any scrolling
"GridControl" webcontrol did not save the state for checkboxes by default and the pre-existing javascript to handle checked/unchecked item was not working correctly.This issue has been fixed.		 N/A 1858773
Changing the description of an Item now deletes the string from cultures, as is done with Item Name
When an Item Name is changed, the Item Name is removed from other culters and replaced with the Invariant. However this was not the case with the description. If the description of an Item was changed, the string was not removed from the other cultures. This means that the description could appear differently in other cultures (in the case of cloned item) or did not appear at all for those users in a culture other than the one being updated.This issue has been fixed.		 N/A 1859971
OwnerNSGuid now not set to a stale GUID if the database is reconfigured
When a database is now changed and the Save button is pressed on the Database Settings page, the OwnerNSGuid value from the ServerSettingGuids table is loaded from the new database and is written to the CoreSettings.config file.		 N/A 1861472
User from built-in domain group now being added
User from built-in domain group being added as software portal manager did not authenticate as software portal manager. The built-in users and groups are no longer displayed in the 'Select Users or Groups' popup.		 N/A 1863130
On Edit filter page, an error occurred when right-clicking the rows in the membership grid
This issue has been fixed.		 N/A 1872600
Query Builder: Basic Filter Expression with Nested Groups was not being saved
This issue has been fixed.		 N/A 1878012
AexAgentUtil /Clean did not remove 2 Surrogate processes
AexAgentUtil /Clean did not remove 2 Surrogate processes. Because of this, the Agent failed to re-install even after a reboot.This issue has been fixed.		 N/A 1881516
Package Server did not enable Active Server Pages in IIS 7 the same as it does for IIS 6
This issue has been fixed.		 N/A 1886734
User could modify role name to the same name that has been used by other role
User is now unable to modify the role name to the same role name that exists.		 N/A 1890876
Automation policies with a system message as a trigger was running even when not enabled
The trigger execution for automation policies that were not enabled has now been disabled.		 N/A 1893975
Unix agent was sending up install status messages that contained HTML
The Unix agent was sending up install status messages that contained HTML. The grid on the push install page did not support this and was displaying the raw HTML markup. The Select Computer in Windows and ULM tab now shows all the computers (both windows and non-windows).		 N/A 1897777
Unix agent was sending up install status messages that contained HTML
The Unix agent was sending up install status messages that contained HTML. The grid on the push install page did not support this and was displaying the raw HTML markup. The Select Computer in Windows and ULM tab now shows all the computers (both windows and non-windows).		 N/A 1897777
GetPackageSnapshot.aspx could not handle packages with a snapshot over 4 MB
Both asp and aspx pages do not use buffering now and send the response in portions correctly.		 N/A 1915912
Site Servers which had been unassigned from an auto assigned package were never reassigned even if required
This issue has been fixed.		 N/A 1921273
Symantec Management Server Error page appears when opening Resource Manager of a computer with duplicate records in database
The Resource Manager page now handles any duplicates by showing the correct resource.		 N/A 1925026
Roles now getting listed in the list of roles on the Security Replication Rule page
All created roles are now listed in the role's list on the Security Replication Rule page.		 N/A 1927082
Items replicated via ‘Replicate Now…’ are not appearing inside the Hierarchy-related reports
The 'Replicate Now...' operation was not working in upgrade scenarios. This is related to incident 1936188.This issue has been fixed.		 N/A 1933334
CustomColsoleUpgrade.msi is not laid down where the NS is installed
This issue prevented the migration from loading. This is related to incident 1933391.This issue has been fixed.		 N/A 1934402
Database Settings/Reporting Tab - Visual Studio Debugger error dialog pops up
This issue has been fixed.		 N/A 1940162
Security Role Manager with a large number of checked items will fail to save its state
Previously, if a customer used the Security Role Manager to create a role with a large number of checked items (individually checked, rather than checked by inheritance from higher nodes), then the next time the picker was opened, these selections were not shown. Instead, the picker had a clean slate (no checked items). Clicking on 'Save Now' caused the role to have no access.This issue has been fixed.		 N/A 1940554
Delta Resource update fails to update the "File" Scope Collection with a System.OutOfMemoryException with more than 800k file created
This occurred because all the resource GUIDs were being copied from the database to the service process and results were written back to the database. This caused a serious SQL slowdown. The diff now runs on the database rather than involving the SQL server.This issue has been fixed.		 N/A 1946055
An unexpected exception occures in SoftwareManagement core class during Inventory Solution configuration.
This issue has been fixed. This incident is a parent to incident 2053209, which has also been fixed.		 N/A 1948492
Core lays down "Network Resource" Resource type without a description
This issue has been fixed. The description has been added and appears in both clean and upgrade installations.		 N/A 1950377
Resource counts are incorrect. Organizational Groups and Filters are affected.
This is a descendant of incident 1999010. The problem occurred because hierarchy auto-merge was running against two computer resources where the "winning" resource did not have a name.This issue was fixed by the fix to the parent incident.		 N/A 1952282
SMP 7.0.7416 (SP4): software resource links are not re-created in IIS -> Packages after an upgrade
This is a parent of incident 1950701, which was fixed.This issue has been fixed. Software resource links are now retained after an upgrade.		 N/A 1952960
Console throws “Index was out of range” error when user tries to sort more than 90 nodes by the Server Name column in Hierarchy Management > Topology > Grid view
This issue has been fixed. All the columns are now sorted without throwing an error.		 N/A 1968346
Cannot add more than 20 subnets to a site at creation
Previously, when users tried to add more than 20 subnets to a new site, the resultant site had only 20 subnets. This occurred because the javascript function getRowCount in the dlgManagesite.js was not returning the correct number of rows for the grid, which was becoming corrupted after more than 20 rows were selected (two vertical scroll bars started showing up in the grid).This issue has been fixed.		 N/A 1974755
A stored procedure is missing. SP "CtsKillChildInstancesNotComplete" calls sp "tmLockTaskInstanceTables", which does not exist.
This issue has been fixed. The missing stored procedure has been added and verified.		 N/A 1975996
When the user creates a new schedule for an Agent page, the "Computer is available at the exact scheduled time" option is always selected and cannot be unchecked
This issue has been fixed. The option can now be checked or unchecked as desired when adding a schedule in all agent upgrade policies.		 N/A 1980072
Resource Membership update schedules (delta and full) fail on SQL timeout of the "File" scope collection
This error occurred in large environments (more than 6,000 computers), where the Scope Membership for the "File" scope collection timed out. The timeout caused the SQL connection to close, which then caused all other scope updates to fail.This issue has been fixed.		 N/A 1981576
Cannot create a new menu item for a portal page.
Customers were unable to create new menu items for portal pages using the available options.This issue has been fixed.		 N/A 1995153
When a user tries to edit a target with special characters in the name, such as the slash (\), the application throws a javascript error
This is related to incident 1920454. The expected behavior was that the application should have opened the Edit Selected Group window so that the user could edit the target.This issue has been fixed, and no javascript error is produced.		 N/A 1998108
spResourceMerge does not handle string table; ResolveDuplicates handling of string table is incorrect
This is the parent of incident 1952282. This error occurred in a hierarchy scenario. If a resource flip-flopped due to two replication jobs from two children being run too close together, the resource sometimes ended up with no string entries. This happened when ResolveDuplicates did a blanket deletion of the duplicate's strings.This issue has been fixed.		 N/A 1999010
Resource merge during hierarchy replication may promote a duplicate, but merge notification processing at children doesn't fix GUIDs
Duplication of computer resources caused errors in hierarchy replication when resources were merged.This issue has been fixed.		 N/A 1999026
Scope collection performance update improvements: resolve outstanding issues and commit
This issue has been fixed.		 N/A 2003624
PortalView.CreateWebPartControl() didn't handle security properly
This bug caused server errors in the CMDB. It is a descendant of incident 1718581.This issue has been fixed.		 N/A 2007772
Replication of file resources (required for product usage numbers) fail with OutofMemory errors.
This issue has been fixed.		 N/A 2020854
Hierarchy not replicating role membership when Domain Local Group is a member
This error occurred in a hierarchy with two Notification Servers in a parent-child configuration. Both were members of the same domain, with a user in a Domain Local Group and a user in a Domain Global Group.This issue has been fixed. Role, permissions, and privileges replicate without errors, as do Domain Global Group and Domain Local Group.		 N/A 2031665
Notification Server 7 agent upgrade does not remove Notification Server 6 plugins
When customers load legacy client objects (such as Carbon Copy and HPCMS) that are incompatible with the NS 7 agent, the application identity is sometimes locked out.This occurs because legacy agents (those without an NS 7 version) have not been disabled or removed.This behavior is by design. See related KB article.		 54040 2044988
When editing security on an NS with a large number of items, an IE script warning is displayed in the Security Role Manager
Previously, the javascript to set the item check boxes as checked made a large number of script calls, which caused the IE warning message.This issue has been fixed.		 N/A 2045360
spSaveItemAppliesTo DAL implementation prevents policies having more than 20 targets
Previously, if users tried to save a grid with more than 20 targets in it, the original targets were overwritten.This issue has been fixed.		 N/A 2051215
Exporting data to CSV causes issues when data includes commas.
Previously, when users exported reports into a comma-separated value format (listed as "Save As - Spreadsheet") and the data in that report included commas, then the resultant report was missing a column for every comma included.This issue has been fixed.		 N/A 2056187
Reports are not able to have permissions set on them individually
The report resource-associated item 'report datasource' inherited security from the parent folder of the report rather than from the report item. This meant that if a user set security on a report individually, that report did not work.This issue has been fixed.		 N/A 2060058
Alternate URL Agent policy settings were replicating down the hierarchy
Agents from the child SMP were inadvertently re-directed to the parent if the agent settings were hierarchy enabled.This issue has been fixed.		 N/A 2060071
The time value to 'Defer' installation Agent/Plug-In could cause the item of the policy to not work
This issue has been fixed.		 N/A 2060099
Bad pointer arithmetic in AeXUtility Path::SplitURL
This could stop the Agent from being able to request the client configuration.This issue has been fixed.		 N/A 2065995
Automation Policy page dlgEditActionParamsMapping.aspx did not call InitializeParameterEdit on the task server Parameter
This issue has been fixed.		 N/A 2065998
Partitioned Resources could be deleted by any user - did not check security for deletion
Users without the correct permissions were able to delete all types of partitioned resources even if not given specific access to do so.This issue has been fixed.		 N/A 2075257
When computers in "applies to" computer list are deleted from database, all remaining computers in database are targeted by the policy or task
If all of the resources in the filter list were deleted, the filter was being completely ignored, which was resulting in the target evaluating to all resources if no other filters were present.This issue has been fixed.		 N/A 2077071
Automation Policy page dlgEditActionParamsMapping.aspx did not save parameters configured
User was not able to configure parameters for their automation policy to run as customisable.This issue has been fixed.		 N/A 2088933
Manual Notification Server 6 to Notification Server 7 Agent upgrade doesn't redirect the client to the new Notification Server 7
When manually upgrading the Agent from Notification Server 6.x to Notification Server 7.0 using AeXNSC.exe and specifying a Notification Server paramater, the Agent upgraded but was not pointed to the new Notification Server.This issue has been fixed.		 N/A 2088984
The ServerScheduleControl.js shared schedule did not allow scheduling on Sundays
When creating a new schedule for a directory connector rule and setting it to run weekly on a Sunday, when the rule was saved, an error occured.This issue has been fixed.		 N/A 2098846
Added logging to Replication for use in troubleshooting
There was no easy way to tell what step Replication was at if errors occured. More logging has been added to Replication.		 N/A 2112264
Importing a Console menu from an XML file did not work
If you attempted to import new Console menu items from an XML file, you may have received a warning message saying that the items you were importing already existed in the system under a different folder. If you clicked OK to continue with the import, the process appeared to proceed normally, but no new menu items were imported.This issue has been fixed.		 N/A 1585391
The Domain Picker does not load when accessed in a Windows XP FDCC locked environment.
This issued occurred in the Windows XP FDCC locked environment. When you used the Domain Membership/WINS Import page (menu path: Actions > Discover > Import Domain Membership/WINS) and clicked Browse (the open folder icon) to select from the available domains, the Domain Picker dialog box opened. However, if you were running a Windows XP FDCC locked environment, the Domain Picker failed to load the relevant information. The dialog box would hang and display a “Loading...” message.This issue has been fixed.		 N/A 1630095
The OK and Cancel buttons in the Edit Attribute dialog box are not functioning
This issue applied only to the French version. When you edited a substitution parameter in a right-click action (menu path: Settings > Console > Right-click Actions, then in the Right-click Action page you selected the substitution parameter and clicked Edit to open the Edit Attribute dialog box), the OK and Cancel buttons in the Edit Attribute dialog box did not function. You could not confirm the changes or close the dialog box.This issue has been fixed.		 N/A 1866298
Tasks that are scheduled to run at logon do not run on some 64-bit computers
This issue has been fixed.		 N/A 1630923
Integrity package check on Solaris fails for aex-configure
When performing a package integrity check on Solaris, using the command “pkgchk ATRSnsclt” displays an error.This is by design. The file is marked as volatile in the package, meaning that its contents are expected to change after installation.You need to use the command “pkgchk -n ATRSnsclt” for skipping content checks for volatile files.		 TECH46192 1777842
Slow ULM Agent response on AIX systems due to DNS settings
This issue has been fixed.		 N/A 1883570
UNIX Agent 7.0.1607 - Unable to import list of computers using provided .csv template
On the Altiris Agent for Unix, Linux, and Mac installation page, you were unable to import a list of computers using the provided csv template. Instead, an error was logged to the NS log.This issue has been fixed.		 N/A 1777054
UNIX agent 7.0.3102 - Integrity package check on Solaris fails for aex-configure
This error occurs with these solutions installed:
  1. Symantec Platform x86 version 7.0.3798
  2. Altiris Software Management Solution for UNIX, Linux and Mac x86 version 7.0.3034
  3. Altiris Server Inventory for Linux x86 version 7.0.3020
  4. Altiris Patch Management Solution Core version 7.0.1300
  5. Altiris Patch Management for Linux x86 version 7.0.1343
  6. Altiris Inventory Solution 7.0, version 7.0.1060
  7. Altiris Inventory Pack for Servers 7.0 version 7.0.1013
  8. Altiris Inventory for UNIX, Linux and Mac x86 version 7.0.3027
  9. Altiris Agent for UNIX, Linux and Mac x86, version 7.0.3102
The reason for the error is that the aex-configure file is probably zero size during package installation and is being populated / appended later during installation.This is by design. The file is marked as volatile in the package meaning that its contents is expected to change after installation. Please use "pkgchk -n ATRSnsclt" for skipping contents check for volatile files.		 N/A 1777842
SMF Agent - Not using SMF messages handler
The SMF agent was not being changed to not report names for resources and to report names to the new SMF dataclass ("Agent Discovery Details" {FA938E85-1A23-478b-A4FA-6C1110EF5AD2})". The name of resources that were reported by the SMF agent were being ovewritten.This issue has been fixed.		 N/A 1777908
Unix CTA: Synchronize server communication protocol and behavior with Windows CTA.
Several caching and other task-server-related errors were generated before the server communication protocol was synchronized with Windows CTA changes.These issues have been fixed.		 N/A 1778227
Unix Agent 7.0.4016 - Impossible to push NS Agent for Windows onto a Windows computer after unsuccessful attempt to push NS Agent for UNIX on this client
This error was caused by "Unknown" values being inserted, after an unsuccessful push installation, to the DB table columns "OS Name" and "OS Version."This issue has been fixed.		 N/A 1778248
Unix Agent 7.0.4062 - Uninstall is not complete on Solaris, when BASH is made the root's primary shell.
This error was specific to the Solaris platform and only when the uninstallation script "aex-uninstall" was started manually from the client.This issue has been fixed.		 N/A 1778439
Unix agent 7.0.4244 - "aex-cta list" shows tasks in the incorrect order if the execution Date/Time is the same
This issue has been fixed.		 N/A 1778729
ULM 7.0.4370: no command line generated for bz2 package import
Users could not auto-generate the install/uninstall command for any imported bz2, bz, or bzip2 package and had to type them in manually.This issue has been fixed. Parent incident 1821424 was also fixed.		 N/A 1818863
ULM Agent 7.0.4371: BZ2 files set as installation files are not listed in BZ2 Command Line Builder
The Installation File list did not contain available installation files, so no install or custom command line could be generated. This is the parent issue to incident 1818863.This issue has been fixed.		 N/A 1821424
Agent crashes after receiving an Inventory rollout policy on ESX.
After receiving the rollout policy, the agent crashed and stopped working.This issue has been fixed. It is related to incident 1999286.		 N/A 1836891
Notification Server 6.x legacy Software Delivery tasks cause an error and stop the Altiris Agent for UNIX, Linux, and Mac in version 7.0 SP4.
When migrating from version 6.x, certain tasks caused the aex-pluginmanager process to stop, which caused the agent to stop. Restarting the agent did not bring up the second aex-pluginmanager process.This issue has been fixed. It is related to incident 1836891.		 N/A 1999286
ULM agent 7.0.4371: a unified command should be generated for tar.z file extraction
A unified command for tar.z file extraction was needed.This issue has been fixed.		 N/A 1841218
Hierarchy - UNIX/Linux/Mac tab in all targeted policies is editable on child
This error occurred when two Notification Servers were included in a hierarchy, with clients on each NS.This issue has been fixed.		 N/A 1842738
# AIX # .bff files: Command line builder generates incorrect command for .bff files
This issue caused installation to fail. This issue has been fixed.		 N/A 1848095
Confusing warning appears in NS log every time CL builder is activated.
This issue has been fixed.		 N/A 1868415
Very slow response for refreshpolicy and sendbasic inventory on AIX and HP-UX
This issue has been fixed.		 N/A 1883570
ULM Agent: Upgrade from SMP 7.0 SPx should not be followed by drop of the tables
This issue has been fixed. Tables that had been dropped during upgrades are no longer being dropped.This is related to incident 1826202.		 N/A 1890559
Package builder does not support productId that contains spaces.
This issue has been fixed. The package builder now supports productIds that contain spaces.		 N/A 1891201
ULM Agent 7.0.4312 - proxy settings - password reset in case of changes to any other setting
This issue has been fixed. Changing proxy settings no longer generates an error.		 N/A 1902898
IRAgent (used by Patch Module) for Linux 7.0.2039: When the NSAgent is installed to a custom location, the IRAgent installation registers the plugin to a default location
Installing NSAgent to a custom location did not change the installation location of the plug-in agent, as it should have done.This issue has been fixed. The plugin agent in this situation is now also installed to the custom location.		 N/A 1903217
"Altiris Agent for UNIX/Linux/Mac - Upgrade" upgrade policy is not being applied on 6.x clients during upgrade to 7.0 SPx
This issue has been fixed. These errors are no longer produced.		 N/A 1904853
Agent did not upgrade to 7.x automatically
The Mac Agent 6.2.1316 and ULM Agent 7.1.510 were not upgrading automatically.		 N/A 1905760
RedHat3 AS 64bit: push/pull installation fails
The RH3 glibc package was not installing libraries into the /lib directory. This issue has been documented for those who are using RH3.As RH3 is no longer supported, this issue is considered fixed for this release.		 DOC1816
TECH47692		 1906065
ULM Agent cannot be push-installed on SLES 11 machines with KSH or SH as a default shell
This is related to incident 1873385, which was fixed for SP4.This is has now been fixed for version 7.0 SP5 as well.		 N/A 1907008
ULM Agent fails to push-install onto HP-UX (ia64) with bash set as as root shell.
System paths were missing for the environment.This issue has been fixed. It was closely related to incident 1911128.		 N/A 1912642
Can't collect hardware inventory on AIX because of ODM accessing errors (corrupted agent environment)
Details about this incident can be found in incident 1883566. This incident is also related to incident 1884778 and is based on incident 1884863.This issue has been fixed, as the ODMDIR variable is now reset correctly.		 N/A 1916373
ULM Agent SP4 cannot be pushed onto any RHEL 5.2 system with KSH set as boot/root shell.
The ULM agent could not be pushed to Red Hat Enterprise Linux Server release 5.2 Tikanga (either 32- or 64-bit) if KSH was set as a boot/root shell.This issue has been fixed.		 N/A 1916448
After importing .csv file with approximately 60 machine names, "Failed to get machine date" error appears in the Altiris Log Viewer
This issue affected Push installations with more than 60 computers.This issue has been fixed.		 N/A 1918850
After successfully upgrading through HTTPs, the agent does not detect Notification Server
This issue has been fixed. The CTAgent successfully connects to NS/TS. Both sendbasicinv and refreshpolicies now work as expected.		 N/A 1924002
Change the way in which the serial number is reported in basic inventory and the way in which the unique ID is generated for resource keys.
This issue affected Linux x86 and Solaris x86 platforms. The uniqueid resource key and "Serial Number" field of the basic inventory "AC Identification" table did not contain the expected values, which caused errors.This issue has been fixed. The way in which the ULM agent reports the hardware serial number no longer generates errors.		 N/A 1926332
On SuSE Linux systems, ULM Agent 7.0.7308 reported the wrong value as 'DHCP Server'
The DHCP Server value (address) was being read from the wrong field, which resulted in the '0.0.0.0' value being reported.This issue has been fixed. The DHCP Server field is now populated with the correct information.		 N/A 1933968
Need to change GUID of upgrade policy for every release
Old upgrade policies caused conflicts when upgrading to newer service pack releases.This issue has been fixed.		 N/A 1940105
ULM Agent 7.0.7416 (SP4): four unhandled exceptions appear when enabling 'ULM Agent - Upgrade' policy
This issue has been fixed.		 N/A 1950539
Multiple Linux computers return computer name of 'localhost.localdomain'
Linux basic inventory returned multiple 'name.domain' values - one with the real computer name and a second with 'localhost.localdomain'. The 'name.domain' value was a resourcekey. The result was that all such Linux clients were being merged.This issue has been fixed.		 TECH133273 1974547
If Migration Update Component is installed into non-default location, a part of vital exporters is not initialized and processed.
This issue occurred during migration from 6.x to 7.0.x, resulting in 6.x data loss.This issue has been fixed.		 N/A 1998396
During 7.0 SP5 installation with 7.0 SP4 HF1 database reconfiguration, an unexpected drop of several tables appears
Data in certain tables was dropped by design. However, one table that should not have dropped data was dropping it.This issue has been fixed.		 N/A 2121950

Back to top

 

Things to Know

The following are things to know about this release. If additional information about an issue is available, you can read it by clicking the Article ID link.

Things to know Article ID Internal ID
You must configure web controls to support ActiveX
Typical error: Pop-up dialog box is blank when selecting Edit/New icon on "Update summary data" dialog. This is just one example of errors that can occur if Internet Explorer settings prevent the ActiveX control from running. For Notification Server to run properly, you must be able to install (or be prompted to install) ActiveX objects. Otherwise, you may see errors with jobs and task, among other functions. (This is by design.)		 DOC2164 1850633
Take care when using the Query Builder in Basic mode
When you modify a report query using the Query Builder in Basic mode, be careful when you change the first condition of a Filter expression. When you change the first condition, the operator drop-down list reloads its contents. You might need to re-select the correct operator in order to successfully resolve the report query.Note that such unresolvable filter expressions are shown as “Blue” in the Query Builder.		 N/A 1912860

Symantec Management Platform 7.0 SP5 does not support Windows 2000 clients

Because Symantec Management Platform 7.0 SP5 does not support Windows 2000 clients, these clients are not upgraded when you upgrade to Symantec Management Platform 7.0 SP5.

    

Back to top

 

Known Issues in This Release

The following are known issues for this release. If additional information about an issue is available, you can read it by clicking the Article ID link.

Issue Article ID Internal ID
All issues except UNIX/Linux/Mac (listed at the end)    
Installation failed during PerformLicenseCheck for certificate store
When installing SMS and then Dell Client Management Suite, this error is generated.This issue is targeted for resolution in a later release. It is related to resolved incident 1932128.		 N/A 1932127
Windows 2000 clients are not upgraded after offbox upgrade from SMS/CMS level III to ITMS 7.1
Windows 2000 is end-of-life after SMP 7.0 SP4. Neither SMP 7.0 SP5 nor SMP 7.1 supports Windows 2000.		 N/A 2091376
Client task schedules are not getting replicated by custom as well as complete replication for an upgraded NS
Client tasks are not being replicated as expected when upgrading from NS 7.0 SP4 to SP5. (Client task schedules are getting replicated as expected in clean installations, however.) This is a known issue for upgrades to SP5.		 N/A 2100946
Creating new AP creates error and a warning-level message is logged
When you create a new automation policy on an SP5 computer, an error is generated and warning message are logged.However, after you create the policy you can load it, change settings, and save it without the error recurring.This is a known issue for this release.		 N/A 2131251
Cannot perform upgrade if NS is configured to require SSL
The installation fails to complete because HTTP access to the web site is not allowed.This is a known issue for this release.To work around this issue, temporarily allow HTTP access to the web site for the installation/upgrade. 		 54042 2053245
Using SSL to access Symantec Management Platform does not create a correct shortcut in start menu
If you manually set SSL to be enabled, the shortcut does not open the console properly.This is a known issue for this release.		 N/A 2054229
"Create new database" task failed on CoreSolution.config configuration
Some users are unable to create a new database when agents and plugins are installed.This is a known issue for this release.		 N/A 2110558
Memory leak in CTA
Perfmon counters show a steady increase rather than increasing and then decreasing. This indicates a memory leak.This is a known issue for this release.		 N/A 2112881
"Unspecified Dataloader Exception encountered for event data class AeX SWD Package" error message is logged to NS log during plug-ins rollout
If this error occurs, incorrect or incomplete information about agents or packages may be stored.This is a known issue for this release.		 N/A 2127247
Symantec Management Agent 7.0.8581.1581 crashes on startup
This error occurs inconsistently and is a known issue for this release.		 N/A 2131871
Legacy 6.x SWD tasks sometimes ignore scheduling and execute as soon as they arrive on ULM 7.0 client systems
In some cases the Run once ASAP option is checked in the legacy SWD task. This option supersedes any scheduled time or maintenance window. This is by design.If this option is not deselected, the software delivery task will be executed as soon as a policy arrives on the client systems, overriding any schedule. When you are adding schedules to a legacy software delivery task, you should uncheck the Run Once ASAP option unless you intend the task to execute at the first opportunity.		 TECH133274 2045828
The Create Resource Targets privilege is not currently utilized
Any user that has the permission Apply to Resource Targets can create resource targets. Enabling or disabling the Create Resource Targets privilege (menu path: Settings > Security > Roles, then select the Privileges tab) has no effect.If you want to prevent a user from creating resource targets you need to remove the Apply to Resource Targets permission from that user. Removing this permission means that the user cannot open the resource selector dialog box.		 N/A 2055221
Attempts to access the Symantec Management console using the FQDN in the console URL may fail with an error message
If the Symantec Management console is set up to use a non-default port, when you access a page of the console by FQDN (non-localhost), an exception error occurs. The following error message is displayed:Data for the page you are currently viewing has expired		 TECH121988 1845092
Empty data classes are sometimes displayed in the Resource Manager
When you view data class information in the Resource Manager, all data is displayed correctly. (menu path: To open the Resource Manager, click Manage > Resource, then select the appropriate resource. To view data class information, in the Resource Manager, click View > Inventory.)However you may see empty data classes included with the displayed data. These empty data classes should be hidden.		 TECH122043 1942311
Notification Server events are not logged after upgrade from NS 6.x
After migrating from NS 6.x to NS 7.0 SP4, the Altiris Log Viewer shows only the Altiris Agent entries. Notification Server events are no longer logged.		 TECH122132 1941412
Altiris Agent icon may not be removed when the Altiris Agent is uninstalled
When you uninstall the Altiris Agent from a Windows 7 computer, the Altiris Agent icon is not removed. The Altiris Agent icon remains listed in the Customize Icons list.To view the Customize Icons list on a Windows 7 computer, do one of the following:
  • Right-click the Task Bar and then select Properties > Customize.
  • Click the Show hidden icons button on the toolbar.
 TECH44030 1735930
Altiris Agent icon may not appear in the system tray
When you install the Altiris Agent, you can choose to display the Altiris Agent icon in the system tray on the client computer. However, on Windows 7 computers, the Altiris Agent icon does not appear in the system tray.		 TECH44034 1739975
Incorrect message may be displayed when you save report results as a static filter
When you save the results of a report as a static filter (Save As > Static Filter), you can select the items (rows in the results grid) that you want to include. In the Save As dialog box you specify the new filter name, and choose whether to include all of the report results or just the selected rows. If you did not select any rows in the results grid, and then select the Save 0 selected rows option in the Save As dialog, there are no items to include in the new filter, and hence no filter is created. However, in this scenario, a message is displayed stating that the new filter has been created successfully and giving the location at which the new filter is stored. This message is incorrect and should be ignored.		 N/A 1664903
Replicated Altiris Agent Settings - Targeted policy can be edited or deleted on child Notification Servers
If you replicate the Targeted Agent Settings policy (in the Settings tree: Settings > Agents/Plug-ins > Altiris Agent > Settings > Altiris Agent Settings - Targeted) to child Notification Servers, the replicated policy is editable on the children. This is not correct behavior. Replicated system policies should be read-only on child Notification Servers, and you should not be able to modify or delete them.Note that any changes that you make to this policy on a child Notification Server will be overwritten on the next replication schedule, when the same policy is replicated again from the parent.		 N/A 1670099
The test for Notification Server proxy configuration settings does not detect invalid user names or passwords
When you specify Notification Server proxy configuration settings (Notification Server Settings page, in the Proxy tab) for a protected proxy server, the Test Settings button lets you verify that the specified credential is correct. This test is not functioning correctly, and may not detect invalid credentials. If the correct credentials have been successfully tested, any subsequent changes that you make to the user name and password are also flagged as correct.However, if you attempt to use these invalid credentials to download files, such as patch files, the proxy authentication will fail.		 N/A 1787302
Incorrect agent installation status is shown when the client time is behind the Notification Server time
If you perform a push install of the Altiris Agent to a computer that has its time behind the Notification Server time (that is, the computer time is in the past relative to the Notification Server time), the install status displayed in the Altiris Agent Install page is incorrect. The install status for a Windows agent is shown as “Starting Altiris Agent install service” and for a ULM agent is shown as “Starting bootstrap.”This is an issue with the Altiris Agent Install page, and can be ignored. The Altiris Agent is correctly installed.		 TECH46209 1828777
The Altiris icon goes missing when you install Symantec Management Platform
When you install Symantec Management Platform, the Altiris icon (on the Start menu alongside the Altiris Console 7.0 option) does not display correctly. This is because the Windows icon cache is not refreshed automatically when Symantec Management Platform is installed.This is a known issue with Microsoft Windows. You need to force Windows to update the icon cache. You can do this from the Display Properties dialog box.		 TECH46215 1841146
Attempting to add Data Classes to a new Resource Type sometimes fails with a script error
If you create a new resource type (left pane: Settings > Notification Server > Resource and Data Class Settings > Resource Types > Asset Types, then right-click and select New > Resource Type) and then in the Resource Type Edit page, click the Add Data Classes button, a script error message is displayed.Note that you must have CMDB Solution installed in order to access the New Resource Type page.This issue is related to your Internet Explorer browser configuration which is preventing the necessary ActiveX control from loading. To enable the data class picker (the AexTreeCtrl ActiveX control) to load successfully, you need to enable Automatic prompting for ActiveX controls under the Internet Explorer security settings.		 TECH46224 1850593
When you upgrade Notification Server to SP3, the option to hide the client tray icon in the Targeted Agent Settings policy always reverts to the default setting (enabled)
You can specify whether to show or hide the Altiris Agent icon in the client tray via the Targeted Agent Settings policy (menu path: Settings > Agents/Plug-ins > Targeted Agent Settings, then in the User Control tab select or deselect the Show client tray icon checkbox). However, when you upgrade to SP3, this setting is always enabled.		 N/A 1747069
A warning message sometimes appears during differential replication
The warning message “Unable to calculate the specified item's hash during replication...The current User does not have required permission 'read' to load item...” sometimes appears during a differential replication. The items affected include:
  • Altiris Reporting
  • Task Server Tasks
  • Inventory Rule Management
  • Directory Connector Installation
  • Altiris Console
  • Notification Server Reports
  • Software Management
  • Task Management
  • Altiris NS Automation
The result is that the item gets replicated even if its hash matches (that is, the item was unchanged, and should not be replicated in a differential replication).		 N/A 1824193
Task Server needs to be restarted after a new database has been created
When you create a new database, you need to restart Task Server (Altiris Object Host Service) from the Windows service console. This is required to make the previously scheduled PM import task run.		 TECH45090 1585535
The Symantec Management Console does not provide a way to purge old Audit Inventory information from the database
The Inv_Audit table will continue to grow as resources are added. To remove old and unwanted data from this table, you need to follow the manual process described in the linked knowledgebase article.		 TECH41981 1630894
Non-Latin characters are not displayed correctly when used in custom data class attribute names
When you create a custom data class (via Inventory Solution, in the Manage Custom Dataclass page in the Inventory Solution Setting folder) and specify attribute names that contain non-Latin characters, the characters are initially displayed correctly in the console page. However, when you click Save Changes to save the new data class, the names are replaced with “??”. This issue affects only the languages that use non-Latin characters. Inventory Solution must be installed in order to access the custom data class functionality.		 N/A 1851757
Drill-down reports fail when the drill-down targets a remote Notification Server that uses a non-default port
If you have a hierarchy of Notification Servers, some reports display summary data for each Notification Server and allow you to drill down into the results (by clicking on the appropriate row in the results grid) for detailed data on a particular Notification Server. However, if a Notification Server is installed to a non-default website and port, its summary data is displayed correctly in the summary report but any attempt to drill down to display the detailed data fails. A new browser window opens to display the report results, but it contains a Server Error message telling you that the resource cannot be found.		 TECH46377 1871461
Adobe Flash must be installed in order for the Topology Viewer control to function correctly
If you are running Notification Server in secure mode (https), you must ensure that you have Adobe Flash installed.		 TECH46641 1820896
The Resource picker for OOB Patch may not allow you to select any computers
When you use the Stage and Distribute Wizard for OOB Patch, you need to specify the target computers under the Out Of Band Targets. However, if you click on Apply to > Computer, the Resource picker opens but does not let you select any computers.You need to choose Apply to > Resources instead of Apply to > Computer. This option functions correctly and lets you select the appropriate computers.		 TECH46959 1892038
The minimum requirement for installing the Migration Framework is .NET 2.0
The Notification Server 7.0 Migration Framework that is used to migrate data to the Symantec Management Platform 7.0 has a minimum requirement of .NET 2.0. When exporting data from a Notification Server 6 installation (which is using the .NET Framework 1.1), you need to first install the .NET 2.0 Framework. This is required so that the Migration Framework can run and export data from the Notification Server 6 installation. The Migration Framework installer checks that the appropriate version is installed on the system and, if .NET 2.0 is not found, will terminate the installation. The following error message is displayed: “The .NET Framework 2.0 is not installed.”Note that some customers have been incorrectly advised that .NET 1.1 is the minimum requirement.		 HOWTO9712 N/A
Tasks that are contained within jobs must be migrated separately
When you migrate a job from 6.0 to 7.0, you also need to migrate the associated tasks. The tasks that are included in the job are not migrated automatically with the job.		 N/A 1584703
“Hidden” organizational groups are not displayed in the Security Role Manager
If you use the Filter Visible Groups feature to hide any of the organizational groups in the Default organizational view, the hidden groups are not displayed in the Security Role Manager. If you want to change the permissions on any of the hidden organizational groups, you need to first make them visible in the Default organizational view.		 N/A 1582271
The Query Builder does not let you add conditions to joins
When you are using the Query Builder to create a report, you cannot add conditions to joins.		 TECH41312 N/A
Report names are limited to a maximum of 250 characters
The maximum number of characters that you can have in a report name is 250. The maximum number that you can have in a report description is 512. Any extra characters that you enter in the Name or Description field are not displayed.		 TECH41315 N/A
The Sort Direction of a Field in a report query is not saved unless a Sort Order is also specified
Setting the sort direction of a field in a report query has no effect unless the sort order is also specified. There is currently no check on this so, if you set a sort direction with no sort order, the sort direction setting is reset to the default.		 TECH41316 N/A
Importing organizational groups from XML files sometimes gives an “Undefined” error message
An error is logged if you export an organizational group to XML, then delete the parent organizational view and all of its organizational groups, and then re-import the organizational group from XML. The following pop-up message appears: “Error importing item: undefined.” This is because the new (imported) organizational group must be a child of an existing organizational view.		 TECH41234 N/A
If a new security role has the same name as a deleted role, the membership of the deleted role is automatically applied to the new role
To work around this issue, when you create a new security role, ensure that the new role name is different from any previously deleted security roles.		 TECH41287 N/A
Legacy data does not have hierarchy replication disabled
Currently, legacy data (items such as reports and collections imported from Notification Server 6.x) do not have replication disabled. You need to disable replication for each imported item manually. You can do this in the item tree by selecting the appropriate item and choosing to disable replication. Legacy data that you import from Notification Server 6.x to Notification Server 7.0 should not be replicated. This is because some of these legacy items may not function properly after being imported to Notification Server 7.0.		 TECH41290 N/A
The Migration Wizard does not detect which solutions are installed
The Migration Wizard automatically enables the exporters and importers of all solutions, whether or not the solutions are installed in Notification Server 6.x or Notification Server 7.0. You need to manually disable the solutions that you don’t want to migrate. Failure to do this gives errors in the log for the product readiness check.		 45350 N/A
The data in the Store browser shows only the item GUIDs
In the Diagnostics tool, the store browser table name contains only the GUID of each item. The item name is not shown, which can make it difficult for you to check which items are being exported.		 TECH41293 N/A
The Database name cannot include special characters
Notification Server 7.0 fails to create a database if the database name includes any special characters (special characters are any of the following: @#$%^&*()_! ). Ensure that you specify a database name that does not include any special characters.		 TECH41295 N/A
There is currently no way to generate the FQDN (Fully Qualified Domain Name) for the UNC codebases
The only way to work around this issue is to either implement WINS in the company infrastructure or disable the UNC codebase generation.		 TECH24075 N/A
Package Replication Solution will not work on Notification Server 7.0
Package Replication Solution will not work on Notification Server 7.0 because the package replication rules created using this solution on Notification Server 6.0 SP3 cannot be upgraded to the Replication Rules equivalent that exists in Notification Server 7.0. Errors appear when you attempt to use the package replication importer found in the Migration Wizard.		 TECH41330 N/A
Newly created filters sometimes disappear from the tree view
A newly created filter will disappear from the tree view on the Filters page if you return to Edit mode before refreshing the page.		 TECH41274 N/A
The “Select a resource” link sometimes goes missing when you edit a filter
The “Select a resource” link, which is normally located between the number of computers and the import icon, goes missing in some scenarios.		 TECH41314 N/A
AD import fails if the name of the targeted Organizational Unit is longer than 255 characters
If an AD import rule is targeting an Organizational Unit with a name longer than 255 characters, the import rule will fail. This issue also occurs if the path of the targeted OU (that is, <parent OU>/ <child OU>/<sub child OU> etc.) is longer than 255 characters.		 TECH41310 N/A
The “Complete Resource Membership Update” schedule updates all filters
The “Complete Resource Membership Update” schedule currently updates the membership of all filters, including filters that have the Update Membership option set to Manual.		 TECH41329 N/A
Filters cannot be opened through the Resource Manager
The filters displayed in the Filter Summary page of the Resource Manager are not accessible through the context menu. If you attempt to open the context menu on any filter in the grid, a “Data could not be loaded” error message is displayed.		 TECH41271 N/A
Substitution parameters are not passed in a right-click action when it opens in a virtual window
If a right-click action (also known as an item task) is set to open in a virtual window, any substitution parameters that are defined for the action are not passed to the virtual window when the right-click action is performed.		 TECH41246 N/A
In a resource report, when you change the resource type, the context menu and Actions menu become unavailable
When you change the resource type, the query and the list of columns in the report change. This breaks the mapping for the drilldown action that opens the context menu.		 TECH41480 1583620
Filter pages timeout if left inactive for more than 20 minutes
If you leave a filter page open for a long time (more than 20 minutes) without any activity, when you try to resume work, the page fails with an error message “Object reference not set to an instance of an object.”		 TECH41482 1579750
If the Altiris Agent is using a proxy server, the client task agent may fail to register
When the Altiris Agent is using a proxy server, it fails to post events to Notification Server correctly. This results in the client task agent not being registered. Note that communication involving configuration updates, basic inventory, downloading package snapshots, and downloading packages is not affected.		 TECH41484 1585315
The Altiris Agent can only be pushed to small groups of managed computers
When pushing the Altiris Agent to managed computers (Actions > Agents/Plug-ins > Push Altiris Agent), you must select computers by clicking the Select Computers button. If you are pushing to many computers, they will all be added to the selected computers pane. When you press OK, these computers will be added to the List of Computers that can be pushed to, appearing as though the install will proceed for all the listed computers. However, only the computers that are currently displayed will be selected. Therefore, you must scroll through the entire list, 20 computers at a time, pushing to each set.		 TECH41485 1647638
You cannot push install the Altiris Agent to a computer if you do not have access to the Admin share on that computer
The Altiris Agent push install fails. Currently, no error message is displayed in the Symantec Management Console. An appropriate error message will be added in a future release.		 TECH41486 1576065
The Purging Maintenance page does not let you purge data from Notification Server 7.0 reports
The Purging Maintenance page currently allows only the purging of legacy Notification Server 6.x saved reports. It does not provide the ability to purge Notification Server 7.0 data snapshots. To work around this issue, you can make use of a server task (provided with the Symantec Management Platform) that lets you purge the data from a specific report.		 TECH41488 1583305
When you right-click a tree node, there is a delay before the context menu appears
When you right-click on a tree node (in the left pane) to open the context menu, there is no indication that any activity is in process. When you open the context menu in other ways, a “Loading” message displays while the context menu is being loaded.		 TECH41490 1579715
The user name for the Altiris Agent Connectivity Credential cannot include any special characters
The user name for the Altiris Agent Connectivity Credential cannot include any of the following characters: ~!#$%^&(){}. If you attempt to specify an invalid user name in the Global Altiris Agent Settings policy (menu path: Settings > Agents/Plug-ins > Global Settings), an error message is displayed when you click Save Changes.		 TECH41492 1583029
In some circumstances the Symantec Management Console displays the Resource Manager portal page
If you open the Resource Manager while the Symantec Management Console is open, and then refresh the Console page, the Console displays the Resource Manager portal page. To restore the original page in the Symantec Management Console, you need to select the appropriate menu option.		 TECH41499 1584179
NSSetup.aspx is no longer a supported method for reconfiguring the database from a corrupted console
Symantec Installation Manager (SIM) does not handle this scenario either. You need to use the aexconfig /configureall command.		 HOWTO9821 N/A
Misleading error message displayed in the Add Hierarchy Node Wizard
When using the Add Hierarchy Node Wizard to add a new hierarchy node, the account that you specify in the Access Credentials section must be a member of the Symantec Administrator security role on the target Notification Server. If you specify an account that is not a Symantec Administrator, the Wizard displays an error message indicating that the account does not have the Manage Hierarchy privilege. This is not correct. The message should state that the account that you have specified does not have sufficient rights on the target Notification Server. The Manage Hierarchy privilege is required by the logged-in user (you, the user adding the new hierarchy node) and is irrelevant to the account that the local Notification Server uses to access the target Notification Server (a non-administrator account that has the Manage Hierarchy privilege would still fail - it must be a Symantec Administrator account).		 N/A 1582510
The Item Selector in the Security Role Manager does not correctly indicate broken security inheritance
When using the Security Role Manager to assign item permissions for a security role, the security inheritance indicated by the Item Selector (accessed by clicking the Edit symbol) may not be correct.		 TECH41957 1583425
Replication does not remove resource associations from the destination Notification Server when they have been removed at the source
When resource associations are replicated, only Add and Update changes are made at the destination. Only new items and changes to existing items on the source Notification Server are replicated to the destination. If a resource association is deleted from the source, it is not removed from the destination.		 TECH41960 1584753
Reconfiguring the database does not delete the Agent Upgrade policy
After the database reconfiguration process has completed, two Agent Upgrade policies exist.		 TECH41962 1585213
The Save As > Spreadsheet option does not work within drilldown reports
When you view a drilldown report, you can drill down to second level reports that provide more detailed information. However, if you attempt to save a second level report as a spreadsheet (using the Save As > Spreadsheet option), the Save dialog box does not appear. The report window closes without saving anything.		 N/A 1585870
Maintenance windows that have their repeat schedule set to “No Repeat” may not run
If you configure a maintenance window policy (menu path: Settings > Agents/Plug-ins > Maintenance Windows) and set the repeat schedule to “No Repeat”, the maintenance window next activation time and duration values are not passed on to the Altiris Agent.		 TECH41964 1585897
Whenever a site is edited, a System.NullReferenceException error message is displayed in the log
The error message is related to the Edit a Site dialog box. There is no impact on system performance or functionality.		 N/A 1585966
A Replication job is not retried or aborted when the “connect back” credentials have insufficient rights
When you set up a stand-alone replication rule you need to specify the credentials for both the destination server (“connect to” credentials) and the sending server (“connect back” credentials). If the account that you specify for the Sending Server Credentials is not a Symantec Administrator, the replication job fails. However, instead of a warning and message saying that the replication job will be restarted, an error is added to the log and no further action is taken. A retry back-off is not initiated and the replication job never completes.		 TECH41969 1585830
The Symantec Management Console does not provide a way to purge old Audit Inventory information from the database
The Inv_Audit table will continue to grow as resources are added. To remove old and unwanted data from this table, you need to follow the manual process described in the linked knowledgebase article.		 TECH41981 1630894
Checking the list of exclusions in the Resource Target Builder clears the list
When specifying a filtering rule in the Resource Target Builder control, if you specify some items to exclude from the target, and then click the drop-down list to check the selection, all of the selected items are cleared from the list. You need to reselect all of the items that you want to exclude, and save the resource target without clicking on the drop-down list. The Resource Target Builder control appears when you click Apply To in a policy or task. It lets you specify the target of the policy or task. The window title of the Resource Target Builder control may be any of the following: Select Computers, Select Users, or Select Resources.		 N/A 1671753
When using the Query Builder to create or modify a report, clicking Apply disables some of the functionality of the Fields tab
After you have clicked Apply, an error message appears when you attempt to add any new fields, or edit an existing field. To restore the full functionality of the Fields tab, you need to click Save Changes to save the report, and then click Edit to return to editing mode.		 TECH42155 1675711
Incorrect message may be displayed when you save report results as a static filter
When you save the results of a report as a static filter (Save As > Static Filter), you can select the items (rows in the results grid) that you want to include. In the Save As dialog box you specify the new filter name, and choose whether to include all of the report results or just the selected rows. If you did not select any rows in the results grid, and then select the Save 0 selected rows option in the Save As dialog box, there are no items to include in the new filter, and hence no filter is created. However, in this scenario, a message is displayed stating that the new filter has been created successfully and giving the location at which the new filter is stored. This message is incorrect and should be ignored.		 N/A 1664903
Double-clicking a filter in the left pane sometimes makes the Filter tree unusable
If you click a filter in the left pane (the Filter tree) and then, before the filter loads in the right pane, click the filter name again to make it editable, the Filter tree becomes unusable. When the selected filter loads in the right pane, the filter name in the left pane is highlighted and is no longer editable. Clicking any other item in the Filter tree produces an error message (“undefined is null or not an object”) in the browser. You need to refresh the entire page in order to restore the left pane to normal functionality.		 N/A 1667465
The Edit option is incorrectly enabled when you select a default (system) resource target
System resource targets are not editable. If you click Edit, the Resource Target Builder window opens, but all options are disabled so you cannot make any changes.		 N/A 1676434
Report filter conditions are sometimes lost when you edit the report in the Query Builder
When you create a report using the Query Builder, you can specify filter conditions in the Filter Expressions tab. However, when you later edit the report, some filter conditions may be dropped from the report query. This happens whether or not you opened the Filter Expressions tab: when you save the modified report, some conditions may no longer appear in the report query.		 TECH42219 1677523
Invalid “Virtual dir Altiris has subkeys” error sometimes appears in the log
You may see a “Virtual dir Altiris has subkeys” error in the log during the full refresh of the package server (which runs at regular intervals). If the Notification Server is installed on the same computer as the package server, this message is invalid. This is a supported scenario in Symantec Management Platform 7.0, so the error message can be ignored.		 TECH42267 1709000
The DataTable parameter in legacy 6.0 reports is not fully supported in 7.0
The DataTable parameter in 6.0 reports allows you to select the appropriate Table Type: Inventory, Event or Database. When you run a legacy 6.0 report that contains the DataTable parameter in 7.0, only the Database option is supported. If you set the DataTable parameter to Inventory or Event, the table cannot be located and an error message is displayed (“you do not have data in your database”). This issue affects only legacy 6.0 reports that use the DataTable parameter type.		 N/A 1715807
An error and a warning level message are logged when you create an Automation Policy
When you create an Automation Policy, an error and a warning level message are logged. After you create the policy, you can access the policy, changes its settings, and save the policy and no additional messages are logged.		    2131251
UNIX/Linux/Mac issues    
If you select a service action for AIX inittab services in a UNIX/Linux/Mac Service Control task, the task fails with an error message
The AIX inittab service does not support any of the actions that are available in the Service Action drop-down list. When AIX inittab services is checked, the Service Action field should be grayed out and not selectable. At present this field is (incorrectly) functional in the Symantec Management Console.To avoid errors in your Service Control task, you need to set the Service Action field to No action. This prevents any attempt to execute Start, Stop, Restart, or Get Status commands for AIX inittab services.Note that currently the No action setting is incorrectly processed and cannot be used for task creation. As a result, all Service Control tasks that are created for the inittab service control system will be reported as failed, with the error message “Missing or invalid service action” displayed. This is regardless of whether or not the specified process/service was successfully modified.		 TECH46454 1779028
Support for DMG packages is limited
DMG packages (also known as Disk Images or .dmg files) that have a simple structure are supported. A simple structure is where the installation file (.app, .mpkg, or .pkg) is in the root directory of the DMG package.Examples of these packages include the following:
  • Firefox 3.5.2 .dmg
  • ExpressCard_Update.dmg
  • iTunes8.2.1.dmg
  • Messenger702.dmg
  • QuickTime762Tiger.dmg
  • QuickTime762Leopard.dmg
  • VMware-Fusion-2.0.2-147997.dmg
  • vpnclient-darwin-4.9.01.0080-universal-k9.dmg
However, complex DMG packages where the installation file is not in the root directory are not supported.Examples of these packages include Adobe Photoshop CS4 and Adobe Creative Suite 4.		  N/A 1806994
Push-installing the Altiris Agent for UNIX, Linux, and Mac to a computer that has the secondary shell configured in .profile may fail with timeout errors
If you attempt to push install the Altiris Agent for UNIX, Linux, and Mac to a computer system that has a secondary shell configured in .profile, the push install may fail due to a timeout error.The secondary shell is any shell other than the configured shell in /etc/passwd for user root in /etc/profile, .profile, or .bash_profile.		 TECH44831 1825969
RTE Command Line Builder generates an incorrect install command
When you manually create a software package that contains .rte files, and use RTE Command Line Builder to generate the appropriate installation command line (the command to execute the installation file on client systems), the package installation may fail. This is because the generated command line contains the %SIFNAME% token, which is added as a part of the command and is NOT replaced on the client system with the software installation file name. This issue results in a failing installation of the software on client systems.For manually created packages containing .rte files, you need to replace the %SIFNAME% token with the appropriate proper file name.		 TECH46206 1820844
Upgrading the Altiris Agent for UNIX, Linux, and Mac from SP2 or SP2 HF2 to SP3 using the Upgrade policy is sometimes corrupted and replaced with a forced reinstall
In some scenarios, the heavy load on the system results in the update of the upgrade job status being delayed, which in turn causes a re-launch of the upgrade code. The conflict between two instances of the upgrade corrupts the upgrade process and forces the reinstall. The installation log (aex-nsclt-install.log) on a client machine displays the following entry:WARNING! You have two or more versions of Altiris Agent for UNIX, Linux and Mac already installed.
This means that the current installation is corrupted and may not be upgraded.
Forcing reinstall.		 TECH44677 1827411, 1832571
Non-administrator roles cannot access the Altiris Agent Install page
When a non-administrator role attempts to access the Altiris Agent Install page (menu path: Actions > Agents/Plug-ins > Push Altiris Agent) the page fails to load, with the following error message: “The file '/Altiris/NS/Admin/ClientManagement/Error.aspx' does not exist.” This error occurs even when the role has all of the necessary security permissions (Read/Write permission to the Altiris Agent Install page, and all Management privileges). This issue occurs only when the Altiris Agent for UNIX, Linux, and Mac is installed.		 N/A 1585952
Installing the Altiris Agent for UNIX, Linux, and Mac on an HP-UX 11.00 computer produces a “Memory fault (coredump)” error
This is due to a defect in the dynamic linker on the HP-UX 11.00 computer. You need to apply the appropriate patch.		 TECH42006 THD 31378
You cannot use an upgrade policy to upgrade the Altiris Agent for UNIX and Linux to version 7.0 from version 6.2.1378 on HP-UX computers with IPv6 enabled
The simplest way to work around this issue is to upgrade to Altiris Agent 7.0 using the push install method. Alternatively, you can disable IPv6 on the target computer.		 TECH42029 THD 31164
UNIX/Linux/Mac Service Control Task cannot return the service status on HP-UX systems
When you run a UNIX/Linux/Mac Service Control Task on HP-UX systems, the service status is reported as Unknown. This issue is because the service control scripts on HP-UX usually do not include the option to return the service status. If you want to verify the service status, you should check whether the process is running.		 N/A THD 31311
Some configuration policies are not migrated from Notification Server 6.0 to Symantec Management Platform 7.0
Any configuration policies that were created by copying the default UNIX configuration policy (“All UNIX/Linux Computers (excluding ‘Package Servers’)”) are not migrated. However, any new policies that you created are migrated properly.		 N/A THD 31563
Daemons running on Mac 10.6 in root bootstrap context cannot execute commands using the nohup utility
This is a system limitation caused by Mac OS 10.6 OS design and can't be overridden. This limitation may affect commands that are executed by SWD/SMF tasks, or Script tasks.		 TECH47689 1888557
The Altiris Agent Upgrade and Uninstallation policy pages crash if you attempt to defer the upgrade or uninstallation for more than 32767 minutes
This issue applies to both Windows and ULM upgrade and uninstallation policies. In the Altiris Agent for Windows or UNIX/Linux/Mac - Upgrade policy page, you can defer the action by checking Warn before running and then set the appropriate can defer for XX minutes value. However, if you specify a value higher than 32767, the page crashes when you click Save Changes to save the policy.The page crashes with a Server Error message: Value was too large for an Int16.Note that this field also incorrectly lets you specify and successfully save a negative value.		 TECH47696 1907000
When the ULM Agent is upgraded from Unix Agent 6.2 to ULM Agent 7.0 SP4 on AIX systems, the $PATH variable has no defined value (paths) in the agent's environment
If no absolute path is allocated, the execution of commands under the agent's environment will fail.		 TECH122232 1947560
Upgrading the ULM Agent from 6.2.1319 to 7.0.7416 (SP4) fails on Mac 10.6 computers
A policy-based upgrade from Mac Add-On 6.2.1319 to Altiris Agent for UNIX, Linux and Mac 7.0.7416 SP4 will fail on Mac OS 10.6 if no agent or system restarts were performed before the upgrade.After the upgrade crash, you will see the following error messages in the aex-nsclt-install.log on the Mac 10.6 system:Installing Altiris Agent for UNIX, Linux and Mac 7.0 on the system.
Discovered installation of the 6.2.1319 package.
Trying upgrade 6.2.1319 package...
-E installer: Package name is Altiris Agent for UNIX, Linux and Mac
-E installer: Upgrading at base path /
-E installer: The upgrade failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
-E installer: Package name is Altiris Agent for UNIX, Linux and Mac...
-E launchctl bsexec failed: Inappropriate ioctl for device		 TECH122233 1957645

Back to top

Legacy ID



53345


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


Terms of use for this information are found in Legal Notices

Please Sign In

Login using SymAccount.

Knowledge Base Search

Knowledge Base Search

Rate this Article

Help us improve your support experience.

MySymantec

MySymantec

Contacting Support

Contacting Support