Build number 7.0.7416

This document contains the following topics:

Introduction

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

Notification Server 7.0 SP4 is part of the Symantec Management Platform 7.0 SP4. For release notes, see knowledgebase article 49811.

Back to top

New features

There are no new features in this release.

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

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 45732).

Installation and Upgrade issues

The following issues 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.

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

Issue Article ID Internal ID
Altiris Agent issues    
New options have been added to the Maximum bandwidth to use for multicasting drop-down list

The new entries are 25kb/s, 50kb/s, and 100kb/s. This setting is on the Targeted Agent Settings page, on the Downloads tab, under Multicast Configuration Settings.

 N/A 1844830
You now have the ability to warn a user before launching a Software Management task or policy

You specify the appropriate time in the Warning Countdown duration field. This setting is on the Targeted Agent Settings page, on the User Control tab. The default value is 5 minutes.

N/A 1851052
Computers with the same IP address can no longer be added to the Altiris Agent Install page

Previously it was possible to add multiple computers with the same IP address to the grid in this page. Attempting to perform any actions on these duplicated entries caused error messages to appear in the log.

 N/A 1889511
The AeXAgentUtil.exe executable is now signed

Previously, when this utility was invoked to shut down the Altiris Agent (as sometimes happens during an Altiris Agent upgrade), a Tamper alert was raised by Symantec Endpoint Protection (SEP). SEP does this if the process that attempts to shut down the Altiris Agent is not signed by Symantec.

 N/A 1895519
CMDB issues    
The Resource Inventory History table is now purged correctly

All rows older than the specified maximum age are removed. Previously this table was never purged.

 N/A 1585034
The ResourceKeyChanged table (which contains all changes to the ResourceKey table) is now purged correctly

Previously this table was never purged.

 N/A 1633823
Filters and Resource Targets issues    
Active Directory imported computers now appear in the 'Windows Computers with no Altiris Agent Installed' filter

This filter is the default filter for rolling out the Altiris Agent, which is now installed successfully. Previously AD-imported computers were not included in this filter.

 N/A 1596027
Hierarchy and Replication issues    
When you specify credentials for replication rules, the user name may now include the . (period) and # (hash) characters

Previously any user name that contained either or both of these characters was rejected as being invalid.

 N/A 1669044
When you edit a replication rule and change the destination server setting, the new setting is saved correctly

Previously, in some scenarios, the new setting was not saved and the previous destination server setting was retained.

 N/A 1899832
Delivery of a software package now runs correctly if the package server assignment is Package Servers automatically with manual prestaging

The package is assigned to the Package Server on the NS Site regardless of whether or not it is in a hierarchy.

 49931 1826347
Hierarchy compatibility is now correctly enabled on all appropriate items

Previously, if you upgraded from SP2, hierarchy compatibility was turned off for some items. Note that this issue affected upgrades only. It did not affect fresh installations.

 N/A 1668972
Localization issues    
The Select Privileges window is now correctly localized

Previously, some UI strings displayed in this window were not localized.

 N/A 1882650
The Filter Expressions tab within the Query Builder is now correctly localized

Previously when you viewed this tab in any language other than English the Description field was not localized correctly.

 N/A 1845586
Migration/Upgrade issues    
New database is created successfully following an upgrade from an earlier service pack

If you upgrade from an earlier service pack and choose to create a new database, the new database is created successfully (menu path: Settings > Notification Server > Database Settings, then in the Database Settings page, in the General tab, under Database Name, select Create new database).

Previously, for upgrades from SP2 to SP3, this process sometimes failed. The new database was not accessible and a large number of errors were shown in the log.

 N/A 1873940
The Migration Wizard product readiness check now reliably detects all recent NS 6.0 rollup hotfixes

Previously, when you attempted to migrate from NS 6.0 with a recent rollup hotfix (R10, R11, R12) to Symantec Management Platform 7.0 SP3, the product readiness check gave the warning: No exporters defined for this product.

This warning incorrectly indicated the recent rollup hotfix was not supported for migration to NS 7.0.

 N/A 1879380
Standalone packages can now be created successfully following an upgrade from Notification Server 6.x

Previously standalone packages were not created. This affected users of Inventory Solution, as they could not execute standalone packages to gather inventory of unmanaged computers.

 N/A 1901940
When you upgrade the platform, the following core settings are no longer migrated: ReportsUseApplicationIdentity, ReportsUser, ReportsPassword

Previously, the Core Settings Exporter and Core Settings Importer migrated these settings. In scenarios where the Notification Server was configured to use SQL login rather than NT authentication this could cause issues with the upgraded version (such as errors in the filter membership update process).

 N/A 1907077
Targeted agent settings are now preserved during an upgrade

Previously when you upgraded from an earlier service pack, the user-defined settings in the "Altiris Agent Settings - Targeted Agent Settings" policy were reset to the default values.

 N/A 1826831
The Migration Wizard now operates correctly in cases where NS 6 is installed at a non-default location

Previously in this scenario the Migration Wizard failed to load all of the exporters, which could result in some data not being migrated.

 48935, 51122 1933391
Reports issues    
When you are creating a resource query in the Query Builder, changing the base resource type now operates correctly

Previously, if you changed the base resource type, the default GUID column was dropped from the query.

 N/A 1824104
The context menu now functions correctly in user reports

Previously, in some circumstances, right-clicking on a user in the report results failed to open the context menu.

 N/A 1853719
The Graphs Server, a third-party component that was used for chart reports in previous versions of Notification Server, has been removed

This component is not used in Symantec Management Platform 7.0, so it has been removed. It is not included in clean installs, but will still be present on an upgraded system.

N/A 1866269
You can now reliably run a report under a security role that has permissions for the report and appropriate resource types, but does not have full permissions on the base folders for Reports or the resource types

Previously, in this scenario, you were prompted for credentials and error messages were added to the log. These were incorrect, as you do not need full permissions. In order to use a report you need only the permissions to view the appropriate items.

 N/A 1871486
Reports with chart views now display correctly even when the report returned no results

Previously, in some circumstances, such a report crashed with an error when the result set was empty.

 N/A 1880939
The "Save As" option now works correctly for a report that was opened via the Actions or context (right-click) menu

Previously, when you attempted to save such a report under a new name, the Save As dialog box closed without saving the new file.

 N/A 1886072
The Objects Replicated drill-down report now returns the correct results

Previously this report sometimes returned no results. Note that this issue has been fixed for fresh installs only. It still exists on upgraded systems.

N/A 1892402
Empty data classes are now hidden in data class reports

Previously empty data classes were visible. In some scenarios (typically with Inventory Solution) this caused some pages of the Resource Manager to fail with an error message.

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

Previously the registry value in the report was incorrectly saved. Consequently, the report query was unable to identify the agent or package server version and returned no results.

 N/A 1870304
Scheduling issues    
The characters \, /, |,>,<,",?, :, and * are now valid in schedule names

Previously these characters were invalid and could not be used in schedule names. Attempting to create a new custom schedule failed when the name included any of these characters.

 48960 1829235
Security issues    
A potential security vulnerability in the RunCmd method of the Console Utilities ActiveX control has been closed
 N/A 1887028
The NS Configurator no longer includes the DbPassword value in the database settings

Previously, you could use the NS Configurator to change the database access password. However the new password was saved in the CoreSettings.config file as plain text instead of being encrypted.

 N/A 1889634
Site Server issues    
The IIS logging setting is now preserved when Package Server is installed

Installing Package Server does not change the logging state. Previously when the Package Server agent was installed, IIS logging was switched on automatically. If you wanted it disabled you had to switch it off manually.

 49826 1806323
User Interface issues    
The Command line field in the Programs tab of the Package page now accommodates 512 characters

Previously the maximum string length in this field was 255 characters.

 N/A 1896404
The On/Off button displayed on each policy page now indicates the correct state of the policy

Previously, in some scenarios, when you clicked the button to change the state of the policy, the policy state changed but the button did not reflect that change. Consequently you could not rely on the button appearance correctly indicating the current state of a policy.

 N/A 1911461
The performance of the SM Console has been improved

A memory leak has been resolved.

 N/A 1715959
Miscellaneous Windows issues    
The ImportExport.exe tool has been restored, and can be found in the Server\bin\tools directory

This tool is used by Symantec support to import large XML files. It had been removed from the Symantec Management Platform in an earlier service pack.

 N/A 1677656
The third-party component EasyMail .Net Edition (SMTP.net.dll) has been removed from the Symantec Management Platform

This component was placed in the GAC after installing Notification Server, but is no longer used.

 N/A 1830163
When creating or modifying a user-defined right-click action, you can now create an expression that includes an attribute that contains a space in its name

To create or modify a user-defined right-click action, click Settings > All Settings, then in the Settings > Notification Server > Right Click Menu > User Defined folder, right-click and select New > Right Click Action. To modify an expression, in the Right-Click Action page, in the Target Resources panel, under Expression, click Select. In the Select Attributes window, select the appropriate attribute.

Previously, when you attempted to select such an attribute (such as OS Name or Agent Name) a server error message was displayed.

 N/A 1858747
The Resource Summary view in the Resource Manager now reliably shows the correct value for the total physical memory (RAM)

Previously, in some scenarios, the memory value shown was less than the amount that the system actually had.

 N/A 1867422
You can now create any number of user-defined resource types

You can now create any number of user-defined resource types (menu path: Settings > All Settings, then in the Settings > Notification Server > Resource and Data Class Settings > Resource Types > Asset Types > User Defined folder, right-click on the appropriate folder and click New > Resource Type). Previously you could create only 35 new resource types. Any attempt to create any more resource types failed with an error message.

 N/A 1880780
Viewing inventory from the Resource Manager now operates reliably

Previously, when you attempted to view inventory from the Resource Manager (menu path: in the Resource Manager, on the View menu, click Inventory) you were prompted to enter credentials. Any credentials that you entered were rejected as invalid.

 N/A 1928872, 1924690
You can now move an organizational group within an organization view reliably

Previously when you did this, the move operation was successful but an error message was displayed in the console and an error logged in the log file. In some scenarios this issue had an impact on system performance.

 N/A 1922218
UNIX/Linux/Mac issues    
The Upgrade Policy GUIDs have been changed for SP4

This is to ensure that upgrades work properly. The policy GUIDs for Altiris Agent Upgrade had not changed since the 7.0 GA release.

 N/A 1860944
Push install of the ULM Altiris Agent now succeeds on all AIX computers

Previously, on AIX computers with KSH or SH as a default shell, a push install attempt sometimes failed with an error message:

Failed to install package. Agent install failed.

 N/A 1873385
An additional restart has been added to the end of the Altiris Agent installation in the SMP upgrade process

This was required to reset the ODMDIR variable to the correct value. Previously the ODMDIR variable was set to an incorrect value, which prevented the Inventory agent from accessing hardware information.

 N/A 1884863
Aex-bootstrap during push-install and push-upgrade now starts correctly on Solaris computers

Previously, in some scenarios, aex-bootstrap did not start on Solaris computers.

 N/A 1888292
The generated command line for AIX packages now supports the -X key

Previously some generated command lines for AIX packages in .BFF format did not work. The .bff package rollout failed with an error message.

 N/A 1897531
Upgrade from 7.0 SP3 now works correctly on MacOS 10.6
 N/A 1902076
The performance of the Altiris Agent Install page has been improved

A page refresh takes only a few seconds even when the CMDB contains a very large number of items. Previously in this scenario the page would take a minute or more to refresh.

 N/A 1903218
When upgrading SMP from SP3 to SP4 through HTTPS, the client task agent now functions correctly

Previously the client task agent was unable to register with the task server.

 N/A 1917686
Installing the ULM Agent on Mac 10.6 computers now functions correctly

Previously, in some scenarios the ULM Agent could not be installed due to an aex-bootstrap crash.

 N/A 1923039
Values for the DHCP Server and DHCPEnabled fields are now correctly read from RedHat lease files and reported/set on Notification Server
 N/A 1924907
The way that the hardware serial number is reported in basic inventory and the way that a unique ID is generated for resource keys have been modified

Previously, in some scenarios the hardware serial number was not collected. This could affect Deployment solution during the re-imaging process.

 N/A 1926332
The Altiris Agent Install page displays correctly for all users that have sufficient permissions

Previously, in some scenarios non-administrative users could not access the Altiris Agent Install page (both Windows and UNIX tabs) after the ULM Agent was installed.

 N/A 1934159

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

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

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

 51455 1941412
The Objects Replicated drill-down report sometimes returns no results

Note that this issue exists on upgraded systems only. It has been fixed for fresh installs.

 N/A 1892402
The Domain Picker does not load when accessed in a Windows XP FDCC locked environment

When you use the Domain Membership/WINS Import page (menu path: Actions > Discover > Import Domain Membership/WINS) and click Browse (the open folder icon) to select from the available domains, the Domain Picker dialog box opens. However, if you are running a Windows XP FDCC locked environment, the Domain Picker fails to load the relevant information. The dialog box hangs and displays a “Loading...” message.

This issue occurs only in a Windows XP FDCC locked environment.

 51583 1630095
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
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
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
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 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.

 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 knowledgebase article.		 46872 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.

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

 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 drilldown 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 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.		 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 policies exist.		 46836 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.		 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 knowledgebase 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 knowledgebase 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 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.		 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 content checks 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
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
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.

 51717 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

 51719 1957645

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

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

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

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: DOC2030
Legacy ID: 50719

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

    © 1995-2019 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.