Build number 7.0.7270.0

This document contains the following topics:

Back to top

Introduction

This document contains information about the currently known issues and the issues that were resolved in Symantec Management Platform 7.0 Service Pack 3.

New features

The new features of this release are as follows:

Ability to disable backward compatibility with 6.x Altiris Agents

You now have the ability to disable backward compatibility for Notification Server 6.x agents. The encryption used to protect credentials sent to the Altiris Agent has been updated to 3DES, which is a more secure protocol.

The Symantec Management Platform administrator would typically use this setting to disable support for Notification Server 6.x agents once all the installed Altiris Agents have been upgraded to Notification Server 7. This reduces the surface area of possible attacks.

You can enable and disable this feature by setting the boolean key AllowLegacyAgentCommunicationsKeyUsage inside the CoreSettings.config file. By default, this key is set to True. You must restart the World Wide Web Publishing Service before the Altiris Agent can start to receive the updated policy.

Item Update Optimizations

The Item Update functionality has been enhanced. Any solution that makes use of this functionality for installation, specifically for updating item security, portal item web parts, resource type item’s data classes, and data class item actions, will benefit. This enhancement should reduce the installation time required for both the Notification Server and the solutions.

Back to top

Installation and upgrade

Prerequisites

The following must be installed before you can install this service pack:

  • Symantec Management Platform 7.0. See knowledge base article 37648.

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 knowledge base article 45732).
 

Upgrade

You can upgrade this product from 6x versions if you run the Symantec Installation Manager on a Notification Server 6x computer. To upgrade from the 6x version, you must first upgrade your 6x 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 knowledge base article 45732).
 

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, click the Article ID link.

Issue Article ID Internal ID
Altiris Agent issues    
ULM Agent data is now preserved correctly when you upgrade from SMP SP2 to a newer Service Pack

The installation configuration file has been modified to ensure no database tables are dropped when Symantec Management Platform is upgraded to a new version.

Previously, two tables were dropped when you upgraded from Symantec Management Platform SP2 to Symantec Management Platform SP2 HF2, and consequently the ULM Agent domain name, OS, version and IP address information were lost. The affected computers (those that contained a domain name in their hostname) became “unidentified” in the installation table on the Altiris Agent Install page. The physical computers still had an agent installed and were successfully communicating with the Notification Server, but any push install or push reinstall actions were not successful.

Note that the Agent Upgrade policy filter displayed the computers as expected (which indicated that the resources were present in the DB) and indicated incorrectly that the upgrade of the ULM Agent was performed successfully. In order to perform push-reinstall or push-install actions on any of these computers, you had to manually delete the computer from the installation table and then add it again.

  48952 1826202
Filters and Resource Targets issues    
Newly created resource targets are now available in the appropriate selection windows immediately

When you create a new resource target, the target grid in the selection window is refreshed automatically to ensure that the new target is available for selection.

This issue affected selection pages under the Settings > Notification Server menu path, as follows: pages under Replication > Events, pages under Replication > Resources, the Hierarchy > Hierarchy Management page, and under Site Server Settings, the Manually Assigned Agents page for any site server.

  N/A 1678962
User-defined filters and reports now reliably preserve their names during an upgrade or reconfigure of the database

Previously, when you ran an upgrade or reconfigure of the database, some user-defined filters and reports lost their names. The affected filters and reports were displayed in the console with the default name 'New Filter' or 'New Report'.

 48288 1706406
Filters and organizational groups that have been used as policy or task targets can now be deleted

You can now delete an item that is being used by another item, such as a filter or organizational group that is being used by a policy. Previously, when you attempted to remove a filter from a policy (so that it is no longer being used by any tasks or policies), the filter still could not be deleted. When you attempted to delete the filter, a message indicated that it was still in use. The References Dependency Check report indicated that the filter was still being used by itself.

 N/A 1826890
Hierarchy and Replication issues    
Differential Item Replication schedule corrected

When you run the Differential Item Replication schedule in a hierarchy, the schedule now correctly synchronizes security and deleted items between Notification Servers. Previously the schedule also attempted to synchronize the deletion of resources.

  N/A 1670371
Hierarchy item delete functionality improved

The Hierarchy item delete functionality has been enhanced and is now more reliable. Previously, in some circumstances, some items could not be deleted.

  N/A 1780874
Security roles can now be tracked when they are replicated within a hierarchy

You control this feature via the CoreSettings.config file, in the TrackRoleDeletionForHierarchy setting. When this setting is true, deleting a security role on a Notification Server records an entry to delete the corresponding security role down the hierarchy during the next replication. Deleting a role also removes the corresponding entry from the HierarchyPublished table.

  N/A 1780922
Password validation has been implemented where appropriate

Password validation has been added to the Add Hierarchy Node Wizard, Edit Hierarchy Node Wizard, and the Return Credential Setting dialog. Previously, there was no check to verify that the user entered the same character string in both the Password and Confirm Password fields.

  N/A 1584332
Virtual machines can now be replicated up a hierarchy reliably

Previously, when a Virtual Machine resource type was replicated up a hierarchy, if the same resource already existed at the parent as a Computer resource type, the two resources were merged. There is now a check to ensure that the duplicate resource is the same type before the two resources are merged.

 45259 1583364
Grid controls and Search functionality now available for hierarchy managed organizational views and groups

When you are viewing hierarchy managed organizational views and groups on a child Notification Server (those that have been replicated from the parent Notification Server), you can now use the grid controls and the search function. Previously, both the grid controls and the search function were disabled for hierarchy managed organizational views and groups.

 N/A 1679950
Last Replicated date is now shown correctly

When items are replicated within a hierarchy, the Hierarchy tab of the Item Properties dialog now shows the correct Last Replicated date. Previously, the date shown was the last time that an item replication job was run, which was not necessarily the last time that the particular item was replicated.

 N/A 1583543
Security role membership can now be synchronized during hierarchy replication

You can now allow security role replication to synchronize role membership on child Notification Servers with the membership of the corresponding role on the parent. You control this feature via the CoreSettings.config file, in the SyncRoleMembershipExactlyDuringReplication setting.

When this setting is true, security role memberships are synchronized during hierarchy replication. If a member is removed from a security role on the parent Notification Server, the same member is removed from the corresponding role on all child Notification Servers.

Previously, if a security role member was removed at the parent, it was not removed from any child Notification Servers during hierarchy replication. You had to remove the member from the child Notification Server manually.

  49914 1780935, 1806177
Low level alerts no longer included in reports

The Hierarchy Alert Summary and Hierarchy Server Alerts reports no longer include Low level alerts. This is because the Low alert state indicates that the replication was completed successfully, so it is not a warning of a possible problem. Including Low level alerts in these reports was potentially misleading to end users.

 N/A 1585873
Last Replication Date now displayed correctly

The Hierarchy Management page now displays the Last Replication Date using the correct local time. Previously, the displayed time was the UTC time rather than the local server time. This issue has been fixed for both the graphical view and grid view on the Hierarchy Management page.

 N/A 1583937
Hierarchy context menu is now correctly removed when appropriate

When a child Notification Server is removed from a hierarchy, the Hierarchy context menu is now correctly removed from all of its items and resources. In addition, the items and resources on the now standalone Notification Server become deletable. Previously, the Hierarchy context menu was still displayed for some items and resources after the Notification Server had been removed from a hierarchy.

 N/A 1669047
Alert level now displayed in words

The Hierarchy Alerts report and the Alert State column inside the grid view on the Hierarchy Topology page now display the alert level in words that are meaningful to the user (Low, Medium, High, or Critical). Previously, the alert level was shown as a number.

 N/A 1588271
Enabled checkboxes for replication rules are now displayed correctly for all users

On the Replication tab of the Hierarchy Management page, the Enabled checkboxes for replication rules are now displayed correctly for all users. Previously, an under-privileged user (a user without the Managed Hierarchy Replication privilege) saw the words True or False instead of a selected (enabled) or unselected (disabled) checkbox.

 N/A 1585386
Hierarchy Replication reports now uniquely identify items of the same type

Hierarchy Replication reports have been enhanced to uniquely identify items of the same type that have the same name. Previously, such items appeared to be duplicated entries on the report.

Note that all items are identified within the Notification Server by a unique GUID, so it is possible to have any number of items of the same type sharing the same name.

 N/A 1577025
Replication schedule default dates are now set to the current date

When you configure Differential and Complete replication schedules in the Hierarchy Node Wizard, the default schedule date is now set to the current date by default. Previously, the default date for both of these schedules was hard coded as January 1, 2005.

 N/A 1585527
Minor UI change in Notification Servers dialog

The Notification Servers dialog that appears when you specify the destination for a standalone replication rule has been corrected: the Forward To column has been renamed Replicate To.

 N/A 1585878
Replicate Now command now adds the appropriate items to the Custom replication schedule

If Custom replication has been enabled, when you use the Replicate Now command to replicate selected items, the selected items and their descendents are added to the Custom replication schedule.

 N/A 1780907
The replication rule page now correctly displays the number of selected items

When you are creating a new replication rule, you specify the items to replicate and the destination Notification Server, typically in that order. The replication rule page now correctly displays the number of selected items. Previously, when you selected the destination Notification Server, the replication rule page temporarily displayed the number of selected items as 0 (zero). This was a UI issue only. The selected items were still selected, and the correct count was restored in the replication rule page when you clicked Save Changes.

Note that this was a known issue for SP2, but was incorrectly listed as a resolved issue in the SP2 Release Notes.

 N/A 1678904
Altiris Agent Install and Upgrade policies that were replicated down a hierarchy with Hierarchy Properties set to Enabled can now be switched on or off at child Notification Servers

Previously, any changes that you made to the policy state via the policy page were not saved. You had to right-click on the policy in the left pane and change the setting via the context menu.

 N/A 1835487
Merging subnets now correctly merges resource associations that exist for those subnets
When subnets are replicated down a hierarchy, some subnets may already exist on the destination. These duplicate subnets are merged automatically. Any resource associations belonging to those subnets (such as the site assignment - the site that the subnet belongs to) are also merged. Previously, the resource associations were not merged correctly, which could result in invalid scenarios on the destination Notification Server.		 46831 1584448
Localization issues    
The Altiris Agent for Windows - Upgrade policy is now correctly localization enabled

Previously the Altris Agent for Windows - Upgrade policy was not localized after upgrading.

 N/A 1830086
Migration/Upgrade issues    
The full database configuration that is performed as part of an SMP service pack installation now reliably preserves all data

Previously, in some scenarios, when you upgraded your Symantec Management Platform by installing a service pack, some database tables may have been dropped and some of your data may have been lost.

For information on the tables that were affected and the symptoms that you may have observed, refer to the associated knowledge base article.

 48951 1821361, 1821293, 1821298, 1821333, 1821337, 1821342, 1821353, 1821357
Notification Server activities are no longer paused after upgrading from an earlier version to SP3

Previously activities were left paused after performing an upgrade to SP3. The PauseActivities, PauseNSMessaging, and PauseTaskManagers flags were all set as part of the uninstall of the previous version, and the install of the new version retained the same settings.

 N/A 1835084
Reports issues    
Filters and reports are no longer affected by uninstalling solutions

Some solutions install custom data classes that are used in filters and reports. Previously, when such a solution was uninstalled, some unrelated Notification Server filters and reports sometimes failed to load and could not be used. This issue has been resolved, and all filters and reports now load correctly.

 N/A 1780208
Notification Server reports saved as HTML now open reliably on Japanese operating systems

The format of the HTML saved reports has been modified so that the Context-Type meta tag is now before the title tag. This ensures that the HTML is rendered correctly in all operating systems. Previously, an HTML report file displayed as a blank page when viewed on a Japanese operating system.

 N/A 1707106
Support for right-click events for chart regions has been implemented

It is now possible to define a drill down that displays a context menu when the user right-clicks the chart (an individual column or other region).

Previously setting the option to Show Context Menu for drill downs on reports did not function on a chart view.

 N/A 1584073
Scheduling issues    
Automation policies are now correctly displayed in the Shared Schedules page

Previously, when you assigned an automation policy to a shared schedule, the policy was correctly executed on the schedule, but was not included on the Items currently using list for the assigned shared schedule.

 N/A 1585363
Site Server issues    
Package Server now correctly increments package version numbers when an external package is modified

If the local package content is different from the last snapshot, package server will create a new snapshot from local content and increment the package version number.

Previously, if an external package was modified on the package server, a new entry was created in SWDPackage representing the change, but the package snapshot version within the SWDPackage table was not updated.

 N/A 1583420
User Interface issues    
The Altiris Agent has been renamed the Symantec Management Agent

The Agent User Interface (now the Symantec Management Agent window) has been updated accordingly (to open this window, right-click the Symantec Management Agent icon in the task bar, and then click Symantec Management Agent). All instances of the string “Altiris Agent” have been replaced with “Symantec Management Agent.”

 N/A 1724858
Minor changes have been made to the About Symantec Management Agent window

The following changes have been made to the About Symantec Management Agent window (to open this window, right-click the Symantec Management Agent icon in the task bar, and then click About Symantec Management Agent):

  • You can now select only one item at a time from the Installed Agents/Plug-ins grid. The appropriate Agent/Plug-in information is displayed under the Agent/Plug-in Details heading.
    Previously you could select two or more items in the grid, and the details of the most recently selected Agent/Plug-in were displayed.
  • The grid title name has been changed from “Installed Products and Modules” to “Installed Agents/Plug-ins”.
  • In the Installed Agents/Plug-ins grid, the first column label has been changed from “Installed Agents” to “Agents/Plug-ins”.
  • The line spacing for the text under the Agent/Plug-in details heading has been reduced to be consistent with other windows in the Symantec Management Agent UI.
 N/A 1723025, 1723090, 1723059, 1726598
Miscellaneous issues    
Task exception errors are now handled correctly

In some scenarios, executing a task caused exception errors. These were due to an incorrectly formatted internal error message. The error message is now formatted correctly, and now correctly writes an entry to the Notification Server error log when required.

 N/A 1731830
The Resource Manager: Resource Summary page now shows the correct Disk Capacity field value

Previously, the value displayed in the Disk Capacity field was the number of bytes, rather than the number of MB as indicated by the field label.

 N/A 1584758
Symantec Supervisors now have the following permissions on the Automation Policies folder: Read, Write, Delete, Create Children

Symantec Supervisors can also create, modify, and delete custom automation policies using either the context menu or toolbar. Previously, the Symantec Supervisor role could not delete Automation Policies. The role had all the correct privileges, but did not have the necessary permission on the Automation Policies folder.

 45354 1585387
Clicking the Merge Resource link in the Resource Manager now displays an appropriate error message

When you click this link, a dialog displaying the message “This action is not supported. Please select at least two resource to merge” is now displayed. Previously, an exception error was displayed, which was meaningless to most users.

Note that the Merge Resources option is not relevant to the Resource Manager, as Resource Manager displays only one resource.

 N/A 1630115

Back to top

Known Issues in this Release

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

Issue Article ID Internal ID
Windows Issues    
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.
 48688 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.

 48689 1739975
Application identity user security may not seem to be set correctly on your file structure when SMP is installed on a Windows 2008 Server R2 computer

When you install Symantec Management Platform 7.0 on a Windows 2008 Server R2 computer and set up the domain user as the application identity, the domain user does not get permission to access all resources.

This is because some files are installed before the application identity is specified. These files can be accessed only by the user account that is installing Notification Server. To work around this issue you need to manually change the permissions on the affected directory.

 48959 1723137
You cannot create a custom schedule that contains an invalid character in its name

You can create new custom schedules from the Shared Schedule page (menu path: Settings > Notification Server > Shared Schedules) by clicking the Add Schedule button to open the Schedule Editor. The schedule name that you specify (in the Name box in the Schedule Editor) must not contain any of the following characters: \, /, |,>,<,",?, :, or *. These characters are invalid in schedule names.

If the schedule name contains an invalid character, when you click OK to save the new schedule an error message appears: Failed to add a new schedule.

 48960 1829235
Resource replication rules cannot contain more than 60 resource types

When creating resource replication rules, you need to specify the resource types and the data classes to replicate. However, if you select a large number of resource types, an error may occur when you attempt to select the appropriate data classes. When you click on the Data Classes link, the following error message is displayed:

Failed to construct the dynamic Virtual Window.

Do not select more than 60 resource types in a resource replication rule. If you need to replicate more than 60 resource types, you need to create multiple replication rules.

 49813 1585854
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
IIS logging is automatically enabled when Package Server is installed

This is by design. IIS logging is enabled by default, but you can switch it off if appropriate. However, when the Package Server agent is installed, IIS logging will be switched on automatically. This is required so that the event table Evt_AeX_Package_Server_IIS_Status can be populated (although this table is not currently used by anything).

 49826 1806323
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.

 49828 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.

 49831 1841146
You cannot create a new hierarchy relationship via remote console from a Notification Server with a non-default port

If you are on a Notification Server that is using a non-default port, and you remote console into another Notification Server and attempt to create a new hierarchy relationship (menu path: Settings > Notification Server > Hierarchy to open the Add Hierarchy Node Wizard), the attempt fails.

When you complete the Add Hierarchy Node Wizard and click Finish, the Hierarchy Node Progress dialog appears with the error “Hierarchy Node Process failed. Please review the log for details.” The log viewer logs the error “Failed to retrieve remote server guid.”

Note that this issue affects only the specific scenario described here. The operation 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
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.

 49833 1850593
Explicitly excluded resources cannot be removed from a filter

When you attempt to remove an excluded resource from a filter (menu path: Manage > Filters, then select the filter in the left pane. In the Filter page, click Edit, and under Explicit Inclusions and Exclusions, click the Resources excluded in this filter link), the changes are not applied to the filter. The original list of excluded resources remains in place. Updating the filter membership has no effect.

Note that this issue does not affect explicitly excluded filters. You can remove any number of filter exclusions from the filter at any time.

 N/A 1852504, 1870092
The OK and Cancel buttons in the Edit Attribute dialog box are not functioning

When you edit a substitution parameter in a right-click action (menu path: Settings > Console > Right-click Actions, then in the Right-click Action page, select the substitution parameter and click Edit to open the Edit Attribute dialog box), the OK and Cancel buttons in the Edit Attribute dialog box do not function. You cannot confirm the changes nor close the dialog box.

This issue affects the French version only.

 N/A 1866298
The Subnet column name in the New Site window reverts to English after you add a new subnet to the site

If you create a new site and then add a new subnet to it, the Subnet column name in the New Site window reverts to English. (menu path: 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 click OK in the New Subnet dialog box, the new subnet is added to the New Site window, but the Subnet column name is now displayed in English.

This issue affects all languages.

 N/A 1868836
In the Report Query Builder, the registry path that you specify for a report parameter may not be saved

When you create or edit a report, if you use a Registry Parameter Value Edit Control as the value provider for a report parameter, the path that you specify is 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 reopen the Parameter Editing\Creation Dialog, the Registry Path box is empty. If you add the parameter to the report query, the report will fail to run.

 N/A 1870221
The Altiris Agent Build Version Parameter Value Edit Control and Package Server Build Version Parameter Value Edit Control do not function correctly in report queries

When you create or edit a report, if you use an Altiris Agent Build Version Parameter Value Edit Control or a Package Server Build Version Parameter Value Edit Control as the value provider for a report parameter, the registration key value is changed from String to DWORD. (In the Report Parameters tab within the Query Builder, open the Parameter Editing\Creation Dialog, and under Value Provider, select Altiris Agent Build Version Parameter Value Edit Control or Package Server Build Version Parameter Value Edit Control. The Registry Path box is automatically populated with the appropriate valid registry value. Note that the registry value is a String.)

If you add the parameter to the report query and save the report, when you run the report, no results are returned. This is because the registry value in the report query has been changed from a String to a DWORD. The report query cannot identify the agent or package server version from the registry key.

 N/A 1870304
Unable to add more than one IP address in the Altiris Agent Install page

When you want to push the Altiris Agent to multiple computers, you can 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 may be unable to add more than one IP address. Clicking the Add button to add a second IP address has no effect.

You can work around this limitation by clicking Save Changes after adding each IP address. In some cases, running the Domain Membership/WINS Import function (by clicking the Discover Computers link in the Altiris Agent Install page) also resolves this issue.

 N/A 1843039
Previewing a URL-based web part on the Web Part Configuration page fails if you are using both IE8 and SSL

If you create or edit a web part via the Web Part Configuration page (menu path: Settings > Console > Web Parts), you can view the web part in the Preview panel (click Show Preview) before saving the changes. However, if the web part content is a URL (you specify the URL in the Show URL box), and you are using both Internet Explorer 8 and SSL, the preview fails. A message saying “Navigation to the webpage was canceled” is displayed.

This issue does 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
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 In stallion
  • 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.

 49174 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 knowledge base article.		 46872 1630894
Non-Latin characters are not displayed correctly when used in custom dataclass 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.

 49913 1871461
Delivery of a software package may not run if the package server assignment is Package Servers automatically with manual prestaging

This issue arises in the following scenario:

  • A Hierarchy has been configured.
  • A user at the parent Notification Server creates a SWD package for distribution at the child Notification Server.
  • The package has been set with Package Server assignment option Package Servers automatically with manual prestaging.
  • No Altiris Agents within the parent Notification Server site have been assigned the associated task to run.
    As a result, no Package Servers within the parent Notification Server site will download the package.

After the package is replicated down the hierarchy, the child Notification Server Package Servers will attempt to download the package from Package Servers within the parent Notification Server site. However, as outlined above, no Package Servers within the parent Notification Server site have been assigned the package for download.

This stops the distribution of the SWD Package at the child Notification Server location.

 49931 1826347
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.

 50039 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.

 50183 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.

 45344 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.		 45377 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.		 45380 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.		 45381 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.		 45268 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.		 45342 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.

 45346 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.		 45351 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.		 45353 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.		 28873 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.		 45407 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.		 45326 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.		 45379 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.		 45375 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.		 45406 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.		 45323 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.		 45288 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 drill down action that opens the context menu.		 45711 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.”		 45713 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.		 45715 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.		 45716 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.		 45717 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.		 45719 1583305
Importing a Console menu from an XML file does not work
If you attempt to import new Console menu items from an XML file, you may receive a warning message saying that the items you are importing already exist in the system under a different folder. If you click OK to continue with the import, the process appears to proceed normally, but no new menu items are imported.		 45720 1585391
When you right-click on 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.		 45721 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.

 45723 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.

 45736 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.		 45844 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 Administrators 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.		 46830 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.		 46834 1584753
Reconfiguring the database does not delete the Agent Upgrade policy
After the database reconfiguration process has completed, two Agent Upgrade polices exist.		 46836 1585213
The Save As > Spreadsheet option does not work within drill down reports
When you view a drill down 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 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.		 46838 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
Tasks that are scheduled to run at logon do not run on some 64-bit computers
For more information, refer to the linked knowledge base article.		 46843 1630923
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.		 46845 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 knowledge base article.		 46872 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.		 47310 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, 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.		 47436 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.		 47563 1709000
Packages may go missing when you upgrade SMP to SP3
When you upgrade Symantec Management Platform to SP3, tasks that involve downloading a package via HTTP may fail. This issue does not affect packages that are available via a UNC path.

To resolve this issue you need to update the package distribution points after installing SP3.

 47671 1678272
Security Roles do not display correctly after you reconfigure the CMDB
As part of the SP1 to SP2 upgrade process, you may want to reconfigure or upgrade the CMDB. You can manually reconfigure the CMDB via the Database Settings page of the Symantec Management Console (you select the appropriate database and then click Reconfigure Database). However, when you have done this, the security roles are not displayed correctly: when you view the list of available security roles (menu path: Settings > Security > Roles), none of the security roles are shown.

To resolve this issue, you need to navigate to another menu option, and then return to the Security Roles page. The list of security roles is then displayed correctly.

 47672 1710256
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
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.

 49950 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.

 49037 1825969
Passwords with the “;” character are not supported
The “Use privileged account multiple passwords” option does not support passwords with the “;” (semicolon) character. This character is always treated as a separator between passwords.		 N/A 1775542
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 contents check for volatile files.

 49814 1777842
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.

 49827 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.

 48961 1827411, 1832571
Slow ULM Agent response on AIX systems due to DNS settings

If the following files on the AIX system are configured correctly:

  • /etc/resolv.conf
  • /etc/hosts
  • /etc/netsvc.conf

then the issue is with the reverse lookup of your Notification Server server. You need to reduce the system-wide timeout value to speed up the agent’s response.

 49991 1883570
Passwords with the “;” character are not supported
The “Use privileged account multiple passwords” option does not support passwords with the “;” (semicolon) character.		 N/A 1775542
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.		 46921 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.		 46975 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.		 50640 1888557
Push or pull install of Altiris Agent to RedHat 3 computers sometimes fails
The following error message is logged:

.data/AltirisAgentInstaller.bin: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

The reason for the failure is glibc-2.3.2-95.30. That package does not install libraries into /lib directory. This issue affects any install to RH3 computers that have an outdated version of glibc.

 50641 1906065
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.

 50643 1907000

Back to top

Where to get more information

The product installation includes the following documentation:

Document Description Location

User’s Guide

Information about how to use this product, including detailed technical information and instructions for performing common tasks.

This information is available in PDF format.

Help

Information about how to use this product. This information is the same as in the User’s Guide.

Help is available at the solution level and at the suite level.

This information is available in HTML help format.

The Documentation Library, which is available in the Symantec Management Console on the Help menu.

Context-sensitive help is available for most screens in the Symantec Management Console.

You can open context-sensitive help in the following ways:

  • The F1 key.
  • The Context command, which is available in the Symantec Management Console on the Help menu.

For more information, you can use the following resources:

Resource Description Location

Implementation Guide

Information about how to install, configure, and implement this product.

This information is available in PDF format.

Symantec Management Platform Release Notes

Information about new features and important issues in the Symantec Management Platform.

This information is available as an article in the knowledge base.

https://kb.altiris.com/article.asp?article=45141&p=1

You can also search for the product name under Release Notes.

Installing the Symantec Management Platform products

Information about using Symantec Installation Manager to install the Symantec Management Platform products.

This information is available as an article in the knowledge base.

https://kb.altiris.com/article.asp?article=45732&p=1

Altiris 7 Planning and Implementation Guide

Information about capacity recommendations, design models, scenarios, test results, and optimization best practices to consider when planning or customizing an Altiris 7 Infrastructure for your organization.

This information is available as an article in the knowledge base.

https://kb.altiris.com/article.asp?article=45803&p=1

Knowledge base

Articles, incidents, and issues about this product.

http://kb.altiris.com/

Symantec Connect (formerly the Altiris Juice)

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

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

Online Forums

Forums for users of this product.

http://forums.altiris.com/

Back to top

Imported Document ID: DOC1816
Legacy ID: 46976

Thanks for your feedback. Let us know if you have additional comments below. (requires login)

    © 1995-2019 Symantec Corporation