Notification Server 7.0 SP2 Release Notes

Article:DOC1766  |  Created: 2009-03-02  |  Updated: 2009-03-02  |  Article URL
Article Type


Notification Server 7.0 SP2
Release Notes

Build number 7.0.5201


Features in this Release

Known Issues in this Release

Resolved Issues in this Release


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

Features in this Release

The following are new features of this release:

Internet Explorer 8 can be used but is not supported

You are not blocked from installing the Symantec Management Platform on a computer with Internet Explorer 8 installed, nor are you blocked from running the Symantec Management Console in Internet Explorer 8. However, if loaded in Internet Explorer 8, the Symantec Management Console displays a warning message advising you that you are using an unsupported browser.

For more information, refer to the following KnowledgeBase article: Support for Internet Explorer 8 in Symantec Management Platform 7.0 SP2.

Active Directory Import changes

Active Directory Import now supports Windows 2008 domains, but no longer supports Windows NT domains. Existing NT Domain Import rules are now treated as legacy items: the rules will still function, but they are read-only and their properties cannot be edited in the Microsoft Active Directory Import page (menu path: Actions > Discover > Import Microsoft Active Directory). However, a user can still enable/disable, manually run, and delete these rules as necessary.

Caching framework enhancements: Warning messages are logged when cache sizes may need to be increased

The default cache size settings (specified in the coresettings.config file) may not be adequate for some environments, which can impact Symantec Management Platform performance. The cache framework has been extended to monitor cache usage and provide appropriate warning messages when the size of a cache may need to be increased. Previously there was no easy way for a user to determine when some cache sizes were inadequate, or which particular cache settings needed to be increased.

If a cache is at risk of flooding (indicated by an entry being removed from the cache soon after it was last used) a warning message is logged. The message identifies the cache size setting that needs to be increased and its current active value. By reviewing the log, the user can determine which caches need to be increased in size to suit the requirements of their environment, and then make the appropriate adjustments in the coresettings.config file.

For more information on the cache size settings in the coresettings.config file, refer to the following KnowledgeBase article: Symantec Management Platform cache sizes are now monitored by the cache framework.

The ULM Agent now supports proxy servers

Proxy server support for the ULM Agent was introduced in 7.0 SP2. However, some limitations apply.

For more information, refer to the following KnowledgeBase article: Limitations on using the ULM Agent with a proxy server

Known Issues in this Release

Known Windows Issues

Known Unix/Linux/Mac Issues

Known Windows Issues

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

Known Windows Issue Article ID Etrack Defect ID
Filter membership is not automatically updated for replicated or imported filters

When a filter is imported or replicated, its membership is not automatically updated on the destination Notification Server. This is by design.

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
When Notification Server is upgraded from 6.x to 7.0, the Migration Wizard writes any messages to the 6.x log file, rather than the 7.0 log file location
The 6.x log file location is C:\WINDOWS\system32\Altiris Logs. You need to look in this log file to see any migration errors. The log viewer displays only the log file at the default 7.0 location, so will not include the migration log entries.
When you generate reports using a specified date range, the time for both the start and end date is assumed to be 12:00 midnight on the previous day
Therefore, all the data for the start date will be included in the report, but no data for the end date. For example, if the end date is set as December 12, the report will include data up to midnight on December 11. No data from December 12 is included.
It is possible to delete any resources from the Default organizational view
When you delete a resource, the resource is removed from the CMDB. You should not delete any resources that are critical to the Symantec Management Platform activity and functionality. Critical resources include the Notification Server computer, sites, and subnets.

See also resolved issue #39328 - Warning message is now displayed when you attempt to delete the Notification Server computer resource.

N/A 1584600
"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 Symantec Management Platform installation fails if you have logged in with an apostrophe in your user name
This has been resolved as part of SP1 but will not be available until the next full release of the Symantec Management Platform.
46227 1584926
Console-based log file access is no longer provided
The Logview.asp page has also been removed. This may cause issues for solutions that still reference this page.
Distribution Domain Local groups cannot be added to Notification Server security roles
Non-administrators cannot create subnets or sites
If you are not an administrator and you try to create a site or subnet in the Site Server page (In the Symantec Management Console, click Settings > Site Server), you will receive the error "An unexpected error has occurred and the requested operation could not be completed".
"Use simple file sharing" option prevents push installation of the Altiris Agent
The Altiris Agent cannot be pushed to a Windows XP SP2 or VISTA client computer if the "use simple file sharing (Recommended)" setting is checked in Windows Folder Options > View tab > Advanced settings.
Task server Powershell scripts "Can't Find in Command path error" may appear
If you receive the error "can't Find in Command path", restart the Altiris Host Service to correct the problem.
A Notification Server cannot discover a domain when no trust relationship exists
When using the domain discovery method to discover a domain from a Notification Server, credentials will not be accepted if no trust relationship already exists between the two domains.
Task instance replication requires the same version of task management on all servers in a hierarchy
Task instances will not be replicated down a hierarchy if the same version of task management is not installed on all servers in your hierarchy.
Saving a report as HTML on Chinese and Japanese systems does not work correctly
When you open the HTML file in a browser, some text is rendered incorrectly. This is because the Symantec Management Platform creates the HTML report file using default Unicode encoding. Double-byte character systems (such as Chinese and Japanese) require UTF-8 encoding.
45339 1585436
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 (ie. <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
Active Directory Connector incorrectly identifies x64 computers as Win32 computers
When Active Directory Connector imports x64 computers, it incorrectly sets the System Type field to Win32. This can cause issues for tasks or policies that attempt to target only Win32 computers. The filter or resource target that is used to identify the Win32 computers will also include the x64 computers that have an incorrect system type.
45325 1584851
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
The context menu does not work on report chart views
You can configure a report drilldown to show the context menu on a chart view. However, when you save the report and attempt to show the context menu on the chart view, the menu does not appear.
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 changes. This breaks the mapping for the drilldown action that opens the context menu.
45711 1583620
Text operands that you add to a filter expression are not being applied correctly to the query
This issue occurs when you are specifying a filter query in the Query Builder and are configuring filter expressions on the Filter Expressions tab. If you switch to Advanced Mode you can specify the filter expression type, value, and operands. However, if you specify a text operand, it is not applied correctly to the query when you save the changes.
45712 1585402
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
The Altiris Agent crashes if you attempt to uninstall Symantec Installation Manager (SIM) using Add/Remove Programs
If you uninstall Symantec Installation Manager (SIM) using Add/Remove Programs, the Altiris Agent will crash. This issue occurs before you have upgraded your Altiris Agent to SP1.
45714 1585302
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
User policies are not being applied at user logon
The expected behavior is that whenever a user logs on, the Altiris Agent will immediately request the relevant user policies. However, the Altiris Agent is currently requesting user policies only when it performs a configuration update (which it does at the normal interval).
45718 1583311
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
No error message is shown when a shared schedule that has a policy associated with it is deleted
A warning message is shown when you attempt to delete a shared scedule that has a job or task associated with it. However, if the shared schedule has only a policy associated with it, no warning message is shown.
45722 1582341
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
Merging subnets does not correctly merge 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. However, any resource associations belonging to those subnets (such as the site assignment - the site that the subnet belongs to) are not merged. This can result in invalid scenarios on the destination Notification Server.
46831 1584448
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 Resource Manager fails to display anything if you do not make a selection in the Select Resource window
If the Select Resource window appears when you access the Resource Manager, you must explicitly select the resource that you want to view. There is no default selection in the Select Resource window, even when only one resource is listed in the grid. If you click OK without making a selection, the Resource Manager displays a blank page. If you are accessing the Resource Manager via a web part (such as from the Notification Server Management Home portal page) an error message displays in the web part and the Resource Manager does not open.
N/A 1585794
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 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
A Visual Studio Just-In-Time Debugger error "An unhandled win32 exception occurred in AeXNSAgent.exe" occurs intermittently while installing products
When installing Symantec products, such as CMS or SMS, this error message may appear on the Notification Server computer. This issue is seen only during or after a "fresh" installation. There is no visible instance of the error in the Altiris Log Viewer.
N/A 1585911
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
Hierarchy options are missing from the context menu of the Altiris Agent Upgrade policy
When a Notification Server is a parent in a hierarchy, the relevant hierarchy options are added to the context menu for appropriate items (those that are replicable). However, the context menu for the Altiris Agent Upgrade policy does not display any hierarchy options. Cloning the policy has no effect, as the clones also do not display any hierarchy options on their context menus. This issue affects the Altiris Agent Upgrade policy only. The Altiris Agent Uninstall policy shows the relevant hierarchy options on its context menu.

This issue is observed only when you upgrade from 7.0 to SP2. It does not affect upgrades from SP1 to SP2.

N/A 1588266
%% cannot be used as a date separator
If you specify the date separator as %%, Symantec Management Console pages that include a date control do not display correctly. An error message is shown, indicating that an input string was in the incorrect format.

You can specify the date separator in the Control Panel, under Regional and Language Options: 

  1. In the Regional and Language Options window, open the Regional Options tab and then click Customize.
  2. In the Customize Regional Options window, in the Date tab, in the Date Separator field, specify the appropriate value.
N/A 1591358
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, 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 Context menu sometimes fails to load for results of a new resource report
When you create a new resource report using the Query Builder, the context (right-click) menu is not available in the results until you have explicitly selected the ShowContextMenu drilldown item in the Drilldowns tab. If you do not open the Drilldowns tab when creating and configuring the new report, when you right-click on an item in the report results, the context menu fails to load.
47343 1667681
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 1672731, 1677523, 1676454
Any manual prestaging of a package to one or more sites is treated as an automatic assignment when the package is replicated
The package export functionality does not distinguish between manual and automatic assignment of sites when automatic assignment mode is selected (in the package page, in the Package Servers tab, in the Assign package to: drop-down list, click Package Servers automatically with manual prestaging). Therefore, when a package is replicated all site assignments specified in the package are assumed to be automatic assignments.
N/A 1676494
A new report name may not be saved correctly
When you create a new resource report or SQL report, you need to specify a suitable name for the report. If you then click Save Changes instead of Apply, the new report name is not saved correctly. The name displays correctly in the Symantec Management Console, but the new report name is not saved to the database. The default report name is saved to the database instead. To ensure that the new report name is saved correctly, you need to click Apply before you click Save Changes.
47561 1706372
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
Personalization of the Search field in the item picker is sometimes applied incorrectly
When you use the item picker (a common control that is usually titled Select Items) to select items, you can use the Search field to filter the items that are listed in the Available Items grid. Only the items that match the characters specified in the Search field are listed. However, if you click Cancel to close the item picker without saving the selection, and then reopen the item picker, the Search field is cleared correctly but the Available Items grid incorrectly displays the results of the last search. The Available Items grid should revert to displaying all items.
N/A 1667458
Packages may go missing when you upgrade SMP from SP1 to SP2
When you upgrade SMP SP1 to SP2, 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 SP2.

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
File names may not appear in the file selection dialog
When you attempt to import reports via the context menu (right-click on the destination report folder and then select Import from the context menu), the Choose the XML File to Import window (which is the standard Windows file selection dialog) does not display any file names. Note that you can manually type the name of the file that you want to import, and the file will be imported correctly.

This issue affects only Traditional Chinese versions of the Symantec Management Console. It does not affect any other localized versions.

N/A 1719772
The Altiris Agent installer does not identify NT4 operating systems on target computers that are joined to a workgroup
NT4 is unsupported in SMP 7.0, so any attempt to install the Altiris Agent will fail. For push installations to computers that are joined to a domain, and for pull installations, NT4 is correctly recognized as unsupported by the installer. In these scenarios the installer displays an appropriate error message telling the user that the minimum operating system required is Windows 2000. However, for computers that are joined to a workgroup, the operating system is not detected correctly, no error message is displayed and the installation process crashes.
N/A 1579655
Upgrading Symantec Management Platform by installing a service pack sometimes causes a loss of data

In some scenarios, when you upgrade your Symantec Management Platform by installing a service pack, some database tables may be dropped and some of your data may be lost.

For information on the tables that are affected and the symptoms that you may observe, refer to the associated KnowledgeBase article.

48951 1821361, 1821293, 1821298, 1821333, 1821337, 1821342, 1821353, 1821357
User-defined filters and reports may lose their names after an upgrade or reconfigure of the database

After running an upgrade or reconfigure of the database, some user-defined filters and reports are displayed in the console with the default name 'New Filter' or 'New Report'.

48288 1706406
Filters and reports may become unusable when you uninstall solutions

Some solutions install custom data classes that are used in filters and reports. When such a solution is uninstalled, some unrelated Notification Server filters and reports sometimes fail to load and can not be used.


Known Unix/Linux/Mac Issues

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

Known Unix/Linux/Mac Issue Article ID Etrack Defect ID
Package information may not be available
Information for packages listed in /Library/Receipts is not returned if the proper Contents/Info.plist file is not available or if the file does not contain valid package information. If this happens, the following warning message is displayed in the log file: "Failed to detect name for package_directory". This warning appears only for packages that are in the old format. Packages in the new format are listed correctly in the /Library/Receipts/boms directory.
You can no longer use inetd on Solaris 10
The Solaris services that were configured using this file are now configured in the Service Management Facility (SMF) using inetadm. Any changes that you make to inetd.conf have no effect. Any records that remain in the inetd file after installation or upgrade, or are later created by installing additional software, must be converted to SMF services and imported into the SMF repository using inetconv. If you don't convert these, some services may not be available.
ULM Agent cannot access the Task Server
When you upgrade to 7.0 SP1, the ULM Agent 7.0 cannot access the Task Server in HTTPS mode, so any attempt to run a task fails with a timeout. You need to enable the upgrade policy for the ULM Agent to ensure that it is also upgraded.
The "Allow user to interact with installing software" option does not function on Mac OS
When you set this option as part of a Managed Software Delivery for MAC, the option does not work. The notification pop-up may appear (if you are logged into the shell), but is non-functional.

If you are unable to close the pop-up (this is another known issue), you need to log off the computer and then log back on again to clear the pop-up from your screen.

This issue is specific to Macintosh computers.

Uninstall does not work correctly/completely when BASH is selected as a primary shell for ROOT account
The following error occurs in the final stage of uninstallation:

/opt/altiris/notification/nsagent/bin/aex-uninstall: pkgrm: not found

This behavior is specific to the Solaris platform only, and it applies only to when the uninstallation script "aex-uninstall" was started manually from the client. Uninstallation using the Uninstall policy works correctly.

The uninstallation reporting messages are not reliable. In this scenario the message says "Removal finished. Uninstallation has finished." and gives a false impression that uninstallation finished successfully.

Note: The following packages are uninstalled correctly prior to ULM Agent removal: ATRSbth, ATRSinv, ATRSsmf, ATRScta

Push install by IP address is not possible
You cannot push install the Altiris Agent for UNIX, Linux and Mac using an IP address, if the IP address cannot be resolved to any hostname (for example, the target computer is not registered in the DNS).
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
SSH protocol version 1 with ChallengeResponseAuthentication enabled is not supported by push install
SSH protocol version 1 with ChallengeResponseAuthentication enabled is not supported. To use SSH protocol version 1 for the push installation, switch off ChallengeResponseAuthentication and switch on PasswordAuthentication on the remote computer.
Unable to save SSH key on a remote computer
If you open the Symantec Management Console on a remote computer, access the SSH key generator page, and choose to save the key file, the Symantec Management Console will try to save the file on the actual Notification Server instead. If you specified a path that does not exist on the server, you will get the following error: Failed to create file on disk. You must specify a path valid for the Notification Server computer rather than for the remote computer.
Command-line prompt limitations during push install
For a push installation to succeed, target computers must be configured to use the default command-line prompt. Customized prompts containing colors or multiple lines may cause the push installation to fail or hang. Also, the installation path (including the prompt length) cannot be more than 220 symbols or the push installation will fail or hang. If you install using an unprivileged account, make sure that the root and non-privileged account prompts are different from each other. If they are the same, the installation will fail.
Agent may not work on minimum installation of 64-bit Red Hat Linux
The Altiris Agent for UNIX, Linux, and Mac cannot be installed on a computer running 64-bit Red Hat Linux if the operating system was installed with “Compatibility Arch Support” switched off. Before installing the Altiris Agent for UNIX, Linux and Mac, run the operating system upgrade and enable “Compatibility Arch Support”. This will install additional libraries required for the Altiris Agent for UNIX, Linux and Mac to work.
Issue when performing push install through Telnet using non-privileged user
If you perform a push installation through Telnet using a non-privileged user, make sure that the target computer's Telnet password prompts for non-privileged users and root users are the same. If one of these prompts does not match the prompt supplied by the Notification Server administrator in the Installation Settings dialog, the push installation will fail. To install the agent, try a push installation through SSH or use the pull installation method.
You cannot push the Altiris Agent to a computer that already has the Altiris Agent installed
If you push the Altiris Agent for UNIX, Linux and Mac to a computer that already has the same or higher version of the Altiris Agent installed, the installation will be cancelled and "Cancelled" will appear in the job status.
Simultaneous push install from two Symantec Management Consoles is not possible
You can open the Symantec Management Console remotely in a web browser on as many computers as you want. However, push installation is possible only from one console at a time.
Non-ASCII characters are not supported
Do not use non-ASCII characters in the files and directories names when configuring the Altiris Agent for UNIX, Linux and Mac installation settings.
Solaris 10 zones are not supported
Solaris 10 Zones are not supported. Solaris 10 global zone that has non-global zones installed is not supported. Solaris 10 that does not contain any non-global zones is supported.
"exec failed. errno=2." message in the installation log
The "exec failed. errno=2." message can appear in the aex-nsclt-install.log on Solaris. You can safely ignore this message.
HTTPS support
The Altiris Agent for UNIX, Linux and Mac does not support HTTPS when Notification Server is configured to require a client certificate.
Maximum log size being set to unlimited
If the maximum Altiris log size is set to 0 (unlimited), the log file could potentially use all the hard disk space and cause the agent to stop communicating with the Notification Server.
Issue if Notification Server uses different data format than client computer
If Notification Server is using a different data format than the client computer local setting, it is possible that the client computer might not get the list of files to download. The following message will be written to the log:

“INFO: Failed getting Package, Msg: Failed to obtain the list of files to download: Cannot convert the received data to Unicode.”

Issue when using foreign symbols in files and directories
A Notification Server administrator can create software delivery packages with files, folders, or alternate download destinations containing foreign symbols. Notification Server uses Unicode (UTF8) data format for client computer configuration policies, which preserves foreign symbols. However, for foreign symbols to be displayed correctly on the client computer side, you need to configure your client computers to have the correct mapping of character map and font to the file system. This way the client computer is able to convert UTF8 to the local character set.
Firewall on VMware ESX Server 3.0 prevents Altiris Agent for UNIX, Linux and Mac from communicating with Notification Server
The service console firewall on VMware ESX Server 3.0 is configured by default to block all incoming and outgoing traffic. To install the Altiris Agent for Linux and let it communicate with Notification Server, you must allow outgoing connections on the ports used by Notification Server. By default, Notification Server is configured to use TCP ports 80 for HTTP and 443 for HTTPS.

To allow outgoing connections on the default HTTP port, run this command on the ESX Server:

esxcfg-firewall --openport 80,tcp,out,http

Also, if you have Package Servers in your network environment you must allow outgoing connections on the ports used by the Package Servers. This will let the Altiris Agent for Linux installed on the ESX Server download software packages.

If you want to perform power management commands, you must allow incoming connections on ports used by Tickle / Power Management. By default, these are TCP port 52028 and UDP port 52029:

esxcfg-firewall --openport 52028,tcp,in,tickle

esxcfg-firewall --openport 52029,udp,in,tickle

For further instructions on how to modify firewall settings, see the ESX Server 3.0 Server Configuration Guide (

Previous versions of aex-bootstrap are not able to download and install the Altiris Agent for UNIX, Linux and Mac
Because the location of the Altiris Agent installation package on Notification Server has changed in this release, the aex-bootstrap binary supplied with previous versions of the Altiris Agent for UNIX, Linux and Mac cannot download the package any more. If you plan to install the Altiris Agent for UNIX, Linux and Mac using the pull installation method, make sure you update the aex-bootstrap binary stored on client computers first. You can find the updated aex-bootstrap binary in the Altiris Agent for UNIX, Linux and Mac installation package. In the case of a default Notification Server installation, its location is C:\Program Files\Altiris\Notification Server\NSCap\Bin\UNIX\AgentInstall\.
Upgrade to RPM 4.3 or later is recommended
We recommend that you upgrade RPM Package Manager on your Linux client computers running SLES 9 or RHEL 3 operating system to version 4.3 or later. With RPM 4.3 or earlier, locks can occur and installation or uninstallation of the Altiris Agent can fail.
Microsoft Text Driver required for .CSV file import to work
If Microsoft Text Driver is not installed on the Notification Server computer, you cannot import .CSV files on the Altiris Agent Installation page.
Launching a GUI application via Software Delivery on Mac is not recommended
To ensure the highest security, we recommend that you do not launch a GUI-based application through a Software Management or Inventory task. If the computer is at the login window, you may inadvertently provide root access to the computer through the application.
Login screen not responsive on Mac
If a software management task executes a GUI application on a client computer while the login window is visible, the login window can be locked out. After the GUI application is completed, the login window will be available again.
Special characters in Mac computer name prevent computers from responding
When special characters are used in computer names, the computers can stop responding. We recommend that computer names not have the following special characters: & (ampersand), # (pound), or “ (double-quotes). There may be other characters that cause problems as well.
Issue when migrating settings to another Mac computer
When the Altiris Agent is installed on a computer, it is given a unique identification in the form of a Globally Unique Identifier (/opt/altiris/notification/nsagent/etc/host.GUID). If you use the Apple Setup utilities to migrate settings to a different computer, the Altiris Agent's host.GUID will migrate as well. After this migration, two computers will now have the same host.GUID. This duplication will cause the two computers to update the same Notification Server computer resource. Delete the host.GUID file to let the Altiris Agent obtain a new one from Notification Server.
Duplicate resources may be created when using Network Discovery
When you have Network Discovery installed, Notification Server can sometimes create duplicates of a computer resource.
45324 N/A
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
ULM Agent data may not be preserved correctly when you upgrade from SMP SP2 to SMP SP2 HF2
When you upgrade from SMP SP2 to SMP SP2 HF2, the ULM Agent domain name, OS, version and IP address information are sometimes lost.
48952 1826202
Upgrading the ULM Agent from SP2 to SP2 HF2 using the push-install method does not preserve any current settings
The push-installation procedure first calls the uninstall and remove commands, and then performs a pure install of the SP2 HF2 Altiris Agent. As a result, all plug-ins (for example, the software management solution agent) are removed from the client.

If you want to preserve the current plug-ins and data for the Altiris Agent when you upgrade from SP2 to SP2 HF2, you should use the Altiris Agent Upgrade policy.

48963 1789763
Upgrading the Altiris Agent for UNIX, Linux and Mac from SP2 to SP2 HF2 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

Resolved Issues in this Release

The following are resolved issues in this release.

Altiris Agent issues

Database (CMDB) issues

Filters and Resource Targets issues

Hierarchy issues

Localization issues

Migration/Upgrade issues

Organizational Views and Groups issues

Replication issues

Reports issues

Resource Discovery issues

Scheduling issues

Security issues

Site Server issues

User Interface issues

Miscellaneous issues

Altiris Agent issues

Resolved Issue Etrack Defect ID
An error message is now displayed when you attempt to pull install the Altiris Agent using an unsupported browser. Note that only Internet Explorer is supported. Firefox and Netscape do not support loading and executing ActiveX controls that the pull install uses. 1583000, 1585654
When adding computer names to the computer list on the Altiris Agent Install page, the “&” character is now a valid character. Previously, if you included the “&” character in a computer name, the name was invalid. Additionally, when you attempted to delete the invalid computer name, an error message appeared: "The data cannot be loaded". 1584961
The Package Server Agent Upgrade policy is now being received by the Altiris Agent reliably. Previously, in some circumstances, some resource targets were not being updated correctly, resulting in this policy not being applied correctly. 1585286
When you push install the Altiris Agent to a Vista computer, errors no longer appear in the log. Previously, following a successful installation, the following error message sometimes appeared in the log:

StartRemoteSession: Unable to start user session ID: 1.

When a package is delivered by Software Delivery (SWD) and has its After Running options set to “Log off user” and “Force running applications to quit upon logoff”, the Altiris Agent continues to run correctly. Previously the Altiris Agent was stopped and didn’t restart until the user logged back on to the computer. 1577809
The Altiris Agent service on the Notification Server computer no longer crashes when you double-click in the "Deliveries available for this computer" panel on the Software Delivery tab of the Altiris Agent UI. Previously this action caused an unhandled exception error. Note that this issue occurred only on the Notification Server computer. It did not affect any client computers. 1585681
The performance of the Altiris Agent Installs to Computers grid in the Altiris Agent Install page (menu path: Actions > Agents/Plug-ins > Push Altiris Agent) has been improved. The grid can now load 10,000 computers in a few seconds, and lets you scroll through pages quickly and easily. Previously if you attempted to display 10,000 computers, the grid would take several minutes to load and scrolling through pages was very slow. 1581940
Querying the Altiris Agent WMI class no longer causes the Altiris Agent to crash. Previously any attempt to query the Altiris Agent WMI class (for example, when using the Real-Time System Monitor Solution) caused the Altiris Agent to crash. This issue affected Vista only. 1585662
The Push Details context menu option now correctly accessed the Agent Installation Status Details report for the selected computer.
When you push the Altiris Agent to computers, you can view the Agent Installation Status report (click View Installation Status Report in the Altiris Agent Install page). This report lists summary details of all computers. You can now obtain detailed information on a particular computer by right-clicking on the computer, and then selecting Push Details from the context menu. This opens the Agent Installation Status Details report for the selected computer. Previously this option incorrectly opened the Resource Manager for the selected computer.
The process of rolling out solution plug-ins to managed computers is now more reliable. Previously, in some cases, an error (“Altiris agent terminated unexpectedly") occurred during the plug-in installation. If this happened the Altiris Agent did not restart automatically and had to be manually restarted. 1585858

Database (CMDB) issues

Resolved Issue Etrack Defect ID

In the Resource Data History page (menu path: Settings > Notification Server > Purging Maintenance, then click Resource History in the left pane), the Keep History Duration value for data classes that have resource history disabled are now saved correctly. Previously, only the values that you set for enabled data classes were saved.


Importing data history from Notification Server 6 to Notification Server 7.0 no longer displays error messages. Previously, error messages appeared, saying that the IP V6 Address column did not exist in the destination table and that the data would be ignored.

A Database Integrity Check has been added to the data importing process. This check executes a SQL query to delete any Subnet -> Site resource associations for any subnet that is assigned to multiple sites. Previously, if multiple sites were associated with one subnet, the subnet was treated as belonging to one of those sites chosen at random. This process also caused a large number of errors to be added to the error log. 1583759
In the Database Settings page (menu path: Settings > Notification Server > Database Settings), the Database Upgrade dialog box no longer appears when you click Save Changes twice. Previously, if you clicked Save Changes twice in the Reports tab of the Database Settings page, the Database Upgrade dialog box sometimes appeared. 1585373
The “Reconfigure Database” button on the Database Setting page is now disabled if the user does not have Write access to the page. Previously the “Reconfigure Database” button was (incorrectly) available to users that had only Read permission on the page. 1583668

Filters and Resource Targets issues

Resolved Issue Etrack Defect ID

The Data Snapshots tab no longer appears when you are editing a filter in "Query Mode: Raw SQL". This tab was added as part of SP1, and is relevant only to report queries.


The Select a resource link no longer goes missing when you edit a filter. Previously, in some scenarios, this link (which is normally located between the number of computers and the import icon) would vanish from the page.

For more information, refer to KnowledgeBase article 45379.

Each Filter page now shows the number of records that the filter contains. The information is displayed at the bottom of the page (text in italics). 1583787
Hidden (solution-specific) filters are no longer shown in the Filter Selection dialog box. Previously the hidden filters created by Patch Management Solution were included in the list of available filters shown in the Filter Selection dialog box. For example, when you were selecting filters for reports or tasks the large number of irrelevant filters made it difficult for you to identify and select those that you wanted to use. 1585395
The Complete Resource Membership Update schedule no longer updates filters that are set to be updated manually. To set a filter to be updated manually, in the Filter page, in the Filter Membership panel, click the menu option: Update Membership > Manual. 1585288
The Run buttons in the Resource Membership Update page (menu path: Settings > Notification Server > Resource Membership Update) now function correctly. Previously, in some circumstances, clicking a Run button failed to run the corresponding schedule. The following error message was displayed: “There is no GUID associated with this page”. 1585481
When you view the computers in a resource target (for example, in the Applied To panel of a policy by setting the View drop-down list option to Computers), the Domain column now displays the appropriate domain for each computer. Note that the Apply Date is not set until you click Save Changes to confirm the changes to the policy (or item to which the resource target applies). This is the time at which the resource target is actually applied. 1585641
Two new filters have been created:
  • All Remotely Managed Computers
  • All Local Agent Managed Computers

If your Symantec Management Platform is part of a hierarchy, these filters allow you to identify and target computers that are managed by the local server, and the other (remote) servers, respectively. These filters are stored in the Computer Filters folder (menu path: Manage > Filters, then expand the Filters folder in the tree view).
Previously there was no way to see or apply a filter that included only locally managed computers. This made it difficult to manage local computers from a Notification Server in a hierarchy.

The Advanced Search feature has been removed from the Filter pages, as it is not relevant. Previously the Advanced Search box was included in the Filter Membership panel, and in the Select Resources dialog box (used for selecting resources to include or exclude in a filter), but was non-functional. 1580260
Autogenerated resource targets (targets that have been created without explicitly naming them, such as those created through QuickApply or through the Select Resources dialog box, without going to the Save option) are now editable in the policy in which they were created. Previously, any autogenerated resource target could not be edited after being saved. The only way to make any changes was to remove the resource target and recreate it. 1585683
Attempting to edit a default (read-only) resource target from the Altiris Agent Install page (menu path: Actions > Agents/Plug-ins > Push Altiris Agent) no longer causes the resource target builder control (the Edit Selected Group dialog box) to become unavailable. Previously, in some circumstances, the dialog box was frozen and could not be used to edit any resource targets. 1585646
The Windows Mobile filter now displays the correct results. Previously this filter also included some non-Windows mobile resources. 1585170
Newly created filters are now identified correctly in the log viewer. Previously, when you created a new filter and then ran the Complete Resource Membership Update schedule, the entries in the log identified the filter as “New Filter” instead of the name that you had given it. 1585345

Hierarchy issues

Resolved Issue Etrack Defect ID

You can now enable or disable Advanced Hierarchy replication rules (menu path: Settings > Notification Server > Hierarchy, then in the Hierarchy Management page, click the Replication tab and then expand the Advanced panel). Previously any changes that you made to the default settings were not saved.


Replicating solution-specific roles and privileges in a Notification Server hierarchy now functions correctly. If a particular solution is not installed on the destination Notification Server, any roles and privileges that are specific to that solution are not replicated. Also, on the Security Role page, a solution-specific privilege group is not displayed if no privileges currently exist on the Notification Server. Previously all solution-specific privileges were replicated (whether or not the solution was installed on the destination Notification Server) which caused the Security Role page to fail with an error.

1582300, 1585551

When security groups and their memberships are replicated between Notification Servers in a hierarchy, every security role that does not exist on the destination Notification Server is now created correctly. Previously, in some circumstances, some security roles were not being created on the destination Notification Server.

The “Objects marked for Replication” report now loads quickly when accessed from the Hierarchy Management page. (menu path: Settings > Notification Server > Hierarchy to open the Hierarchy Management page. In the Replication tab, in the Configuration and Management Items panel, click Review the current Item replication report.) Previously this report took up to 30 seconds to load and display the report results. 1581065
Hierarchy authentication no longer fails if you are logged in with a local computer account. Previously, you had to log in with a domain account that was a member of the Symantec Administrators security role. Using a local account failed, even if the account was an administrator and a member of the Symantec Administrators security role.

For more information, refer to KnowledgeBase article 45270.

Hierarchy resource rules are no longer duplicated in the Replication tab of the Hierarchy Management page. Previously some rules appeared in both the Advanced panel, and in either the Resources or Events panel. If a rule was duplicated, you had to enable or disable both instances of it in order to make the setting take effect.

For more information, refer to KnowledgeBase article 45271.

Differential replication within a hierarchy now works correctly. Previously, in some circumstances, some unchanged items (such as Event rules) were being replicated. 1578680
You can now remove a hierarchy relationship between two Notification Servers when the remote Notification Server is not available. In this situation, a warning message is displayed and you are prompted to confirm that you want to remove the hierarchy relationship from the local Notification Server. Previously both the remote and the local Notification Servers had to be available in order to remove the hierarchy relationship between them.

For more information, refer to KnowledgeBase article 45256.

The generic item picker is now used in the Hierarchy Management page. This allows all users to select items correctly. Previously, if a user other than an administrator (who only had read permissions to some resources and items) tried to use pickers within the Hierarchy Management page, all items that were not visible to the current user were deselected upon applying changes. 1580447

Localization issues

Resolved Issue Etrack Defect ID

The System Messages tab in the Automation Policies page is now correctly localized. Previously this tab contained hard-coded English strings.

The date displayed in the Calendar View for Internal NS Schedules page is now localized correctly. Previously the date was always displayed in English. 1581507
The Data Source > Query tab (in the Report page when in Edit mode) is now correctly localized. Previously some strings were displayed in English only. 1581912
When viewing report results, legends in stacked charts are now localized correctly. Previously this text was displayed in English only. 1584181
The Dependent Exporters and Dependent Importers message boxes that may appear during migration now display localized exporter/importer names. Previously these names were displayed in English only. 1585376
(Italian only) The Site Management page (menu path: Settings > Notification Server > Site Server Settings) now displays graphic labels correctly. Previously some text in the graphic labels was truncated. 1582497
Localized versions of the Count of Computers Reporting Events report (in the Reports > Notification Server Management > Server > Inventory Analysis Reports folder) no longer show any English strings. Previously, localized versions of this report showed some strings in English. These strings were intended for internal use only, and have now been hidden. 1585497
The default titles for new reports and automation policies are now localized correctly. Previously, in some cases, the default titles were in English only. 1584682
(French only) The buttons in the Computer Import Constraints dialog box are now correctly displayed. You access this dialog box from the Microsoft Active Directory Import page (menu path: Actions > Discover > Import Microsoft Active Directory), by clicking the All Computers link. 1583529
Report parameters are now localized correctly. 1584929
The date picker control that is used in report pages is now sized correctly. Previously, in some localized versions, the date display was truncated. 1585476

Migration/Upgrade issues

Resolved Issue Etrack Defect ID

Automation policies are now upgraded correctly. Previously (when Service Pack 1 was installed) some automation policies were not upgraded.


The Package Server installer has been updated to enable ASP during an installation or upgrade. Previously, when you attempted to roll out the Package Server to a Windows 2003 computer with a default IIS installation (which has ASP is disabled), the ASP pages that were required by package server failed to run.


Resource History settings are now migrated correctly when you upgrade from Notification Server 6 to Notification Server 7.0. The issue was caused by the Inventory Data Class Data Importer that was used to import the data into Notification Server 7.0. The importer turns history off so that it can import the data correctly (without generating history), but was not restoring the history setting. The importer now restores the history setting to the correct value.


The Symantec Installation Manager now correctly disables permission inheritance when the security identifier (SID) cannot be resolved. If the target folder should be protected, the folder is marked as not inheriting permissions, and a default permission is applied so that local administrators have full control. Previously the folder would have been available to all authenticated users.


Uninstalling Symantec Installation Manager from Add/Remove programs no longer displays an error message. This issue occurred if you had used a non-default web port for installing SIM. Previously the following error message was displayed: "Failed to configure NS. Failed to create the Altiris NS virtual directory under the IIS default web site.” Note that, when you clicked OK to dismiss the error pop-up, the uninstall completed successfully with no further errors. MSI custom actions now look for the appropriate IIS path in the registry, so having a non-default port number does not matter.

When you upgrade to Notification Server 7.0, any inventory forwarding rules that you import are automatically converted into replication rules. These new replication rules are now disabled by default. This is to eliminate the possibility of issues being caused by the new replication rules attempting to replicate items that should not be replicated. You can enable the replication rules manually, after you have verified that they replicate only the appropriate items. 1583929
The Notification Server and Resource Management MSIs have been modified to skip the custom actions that delete the registry and IIS virtual directories when uninstalled as a service pack. If the MSIs are installed standalone, rather than as part of a service pack, the registry and IIS virtual directories are deleted correctly. Previously, the uninstallation of the service pack ran custom actions that deleted the NS registry values and NS IIS virtual directories. This caused the uninstallation of other MSIs to fail because Symantec Installation Manager could not access core web services and expected registry values. 1585519
Symantec Installation Manager now logs the success or failure of product configuration. The messages that are added to the Notification Server log indicate when the configuration processes started and whether they have completed or failed. 1585552
The data import process has been modified to ensure that any shared schedules that are linked to Active Directory Connector items are imported correctly. Previously, in some circumstances, the required shared schedule was not imported and the default shared schedule was used instead. 1583849
In Symantec Installation Manager and the Licensing web part, the 'In use', 'Count', 'Licensing Usage', and 'License Total' fields now show the correct values. 1585010
The Start menu option (shortcut) to open the Symantec Management Console is now created correctly when Notification Server is installed with custom HTTP or HTTPS ports. Previously the shortcut used a hard-coded path to the default port, so was not correct for custom ports. 1578742
As part of a migration, when you import resource association data, resource association history is no longer generated. Previously the history was (incorrectly) generated and added to the CMDB. 1585335
Uninstalling the Symantec Management Platform via Symantec Installation Manager now completes reliably. Previously, in some circumstances, the uninstallation process got caught in an infinite loop and recorded a 'Failed to set coresetting' error message in the Notification Server log every few seconds. 1585507

Organizational Views and Groups issues

Resolved Issue Etrack Defect ID

When you open an Organizational Group page, the security role specified in the Role drop-down list defaults to the role that you logged in with. If you do not have a security role (i.e. user-based security has been applied rather than role-based) the setting defaults to None, which gives you the same access as the Symantec Administrators role.


You can now delete resources from the Default organizational view. Previously, in some circumstances, attempting to delete a resource failed with an error message.

You can no longer add resources to the Default organizational view with the 'Add to Organizational Group' action. The organizational groups in the Default organizational view are read-only. Previously, the Add to Organizational Group incorrectly allowed you to add resources to these groups. 1585485
The context menu for the organizational groups in the Default organizational view no longer include the 'Edit Group...' option. Previously this option was available for some organizational groups in the Default organizational view. This option is not relevant to any groups in the Default organizational view, and the membership of each of these groups is based on an SQL query. Manually adding resources to these groups is ineffective, as they will be removed the next time that the query runs to refresh the Default organizational view. 1585682
You can now set the asset status of a resource to retired correctly (menu path: Manage > All Resources and then, in the Default organizational view, select the All Resources > Asset > Network Resource > Computer group. In the Computer page (right pane), right-click on the appropriate computer and click Set Asset Status > Retired). Previously an error message was displayed and the asset status remained unchanged.

For more information, refer to KnowledgeBase article 45822.


Replication issues

Resolved Issue Etrack Defect ID
Error logging in replication can no longer crash the replication job. Previously, in some cases, the error log entry was so large that it caused the replication job to fail. Now, when an error occurs during replication, the resulting log entries are limited to a suitably small size.

For more information, refer to KnowledgeBase article 45348.

When you configure Replication or Hierarchy replication rules, you can now select only the replicable inventory classes. Previously you could select any available data class, whether or not it was replicable. Note that some existing replication rules may specify non-replicable data classes. This is not an issue, as the replication framework will not attempt to replicate any items that are flagged as non-replicable. 1585573
The Replication Rule pages now have the “Save Changes” button disabled if the user does not have Write permission. Previously the “Save Changes” button was (incorrectly) available to users that had only Read permission on the page. 1583410
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 displays the number of selected items, and the name of the destination Notification Server. However, when you select the destination Notification Server, the replication rule page temporarily displays the number of selected items as 0 (zero). This count is incorrect, but is a UI issue only. The selected items are still selected, and the correct count is restored in the replication rule page when you click Save Changes. 1678904

Reports issues

Resolved Issue Etrack Defect ID

The BreadCrumb control on the Report page now works correctly. Previously, clicking on an item in the breadcrumb control had no effect.


When a report grid is in edit/preview mode, the Toolbar buttons are disabled. These functions should not be performed in preview mode. Previously these buttons were active, but the function failed with an error message.


When you configure report parameters, the configuration settings for the Filter Chooser Parameter Control value provider are now saved correctly. Previously any changes that you made to the default values were not saved.


A tooltip has been added for each cell in the report grid. When you hover over a grid cell, the full text of the cell is displayed in a tooltip pop-up. This lets you easily read the contents of narrow cells where the visible text has been truncated.


When you are specifying source fields for a resource query in a report or filter, the Sort Order is automatically adjusted when you change the Sort Direction.

For more information, refer to KnowledgeBase article 45381.


The drilldown "Discovered Computers Sorted by Date" in the "Count of Discovered Agents by Domain" report now returns the correct result. Previously this drilldown was incorrectly linked to another report.


When you are running a report that has a collection filter, you can now select only one filter in the filter picker dialog box. Previously, the filter picker incorrectly let you select multiple filters, but only applied the first selection. No error message was displayed when multiple filters were selected.


When performing actions on report results in a grid, the double-click event now functions correctly (to trigger the appropriate action on the selected item). Previously, the double-click event failed if the order of columns in the grid had been changed.


The Always run report as a snapshot option (set in the Advanced tab on the Edit Report page) now functions reliably. When this option is checked, snapshots are generated when the user refreshes the report or navigates away from and then back to the report page.

The Action button in a drilldown report now operates correctly when the drilldown report is accessed from its parent report. The Action button displays the context menu of the selected record in the report results grid. Previously, in some scenarios, the Action button did not work on a drilldown report. 1584997
The “Objects marked for replication” report now functions correctly. Previously, in some circumstance, this report would fail to load. The page would hang with a progress bar and “Please Wait” message.

For more information, refer to KnowledgeBase article 45262.

When viewing a report pie chart that has a supplementary chart, the chart legend no longer displays duplicate items. 1585553
When you are using the Query Builder to define a report query, the Joins dialog box now displays a warning message if you attempt to save an incomplete join. The Joins dialog box is accessed from the Data Source > Query tab (in the Report page when in Edit mode), by clicking Create Joins in the Actions list. Previously there was no warning message and the Joins dialog box closed normally. However the settings that you had entered were not saved. 1581103
When you right-click a computer in the results grid of the Computers report (stored in the Reports > Notification Server Management > Server > Resource Reports folder), the context menu now shows all of the available options. Previously, in some circumstances, some options were missing from the context menu. 1585653
You can now reliably execute a Run Report task that saves the results as a filter. Previously, in some cases, the report failed to execute. 1585713
Keywords in report and filter queries are now parameterized. This eliminates the possibility of an SQL injection attack through filter expressions. An error message appears if the query parameter contains an invalid keyword. Previously these keywords were entered via a text box that allowed free-form text. 1580883
Creating a new report from the grid context menu no longer launches the new report in a new window. All the relevant report query editing functionality is available. Previously the new report was created in a new browser window and, in some cases, some functionality was unavailable. 1585244
The context menu (right-click) now work correctly for resources in reports that are opened from the View Discovery Reports page (menu path: Actions > Discover > Import Domain Membership/WINS and then, in the Domain Membership/WINS Import page, click View Discovery Reports.). Previously, any attempt to perform an action on any resources in these reports failed with an error. 1585493
Queries for report parameters are now run once only, when the report page loads. The parameters are not re-populated each time that the report page is refreshed. If a report has dependent parameters, the parameters are repopulated when any dependent parameter changes. Previously the queries for report parameters were sometimes run multiple times, which had an adverse impact on system performance. 1585017
Previewing new resource and SQL reports during editing no longer causes errors. Previously, in some circumstances, attempting to preview a new resource or SQL report failed with an error message. 1585503
Chart reports now display correctly. Previously, in some circumstances, when you attempted to open a chart report, the report failed to load with a browser error. 1585724
The Altiris Agent Summary Details report, which is a drill-down report that you access from the Altiris Agent Summary report, is now scoped correctly. Users can view only the resources to which they have access. Previously this report was not scoped, which potentially let users view and edit resources that they should not have been allowed to access. 1585331
If you have a report that has multiple views, you can now configure different drilldowns for each report view. Previously the drilldowns were not saved correctly and, in most cases, the drilldowns worked in only one report view. 1585631
The 'group by' function in the Report results page now works correctly. Previously, when there were a large number of items in the results grid, attempting to group the results did not work reliably. Sometimes the groups did not contain all of the appropriate members, and sometimes the groups appeared to be empty. 1582434
When you are configuring drilldown reports, the report selection feature now functions reliably. Previously, in some circumstances, a script error occurred and you were unable to select the report to drill down to. 1585604
The Altiris Agent Installation Status report (in the Altiris Agent Install page, click View Installation Status Report) now displays the last installation action and last installation status correctly. Previously, when pushing the Altiris Agent for Unix failed for any reason, the report did not show any data for the last install action or status.

Note that this item was incorrectly included in the Notification Server 7.0 SP1 Release Notes. This issue was not resolved in SP1.

When adding drilldowns to a report (on the Drilldowns tab on the Edit Report page), if you create and save multiple drilldowns, and then delete one of the drilldowns, the drilldown configuration functionality is not affected. You can continue to add and configure drilldowns as normal. Previously this scenario would result in an error message appearing on the page and you would not be able to configure any more drilldowns for the report. 1585141
The Remote Connection Log View now now displays correctly when you click View Log in the Altiris Agent Installation Status report. Previously, when you clicked this link the report failed to load. 1585689
SQL queries in pre-defined filters and reports now leverage resource partitioning correctly. This improves system performance. Previously, these queries were implemented in a way that caused unnecessary work on the SQL server and took longer to run. 1580475
The “Objects marked for Replication” report now displays only the items that can be replicated. Previously the report incorrectly included some items that could not be replicated. 1585052

Resource Discovery issues

Resolved Issue Etrack Defect ID

Active Directory Connector no longer incorrectly identifies x64 computers as Win32 computers. The System Type field is now set correctly. Previously, when Active Directory Connector imported x64 computers, it incorrectly set the System Type field to Win32.

For more information, refer to KnowledgeBase article 45325.


You can now reliably access the Domain Membership/WINS Import page from the Altiris Agent Install page. Previously, in some scenarios, when you clicked Discover Computers to access this page, the page would fail to load. The process that gets the list of domains has been made more robust. It now catches and logs any errors that occur (such as finding a domain that does not support being enumerated), and continues getting the list of available domains.


Scheduling issues

Resolved Issue Etrack Defect ID

The Schedule Editor dialog box now displays the correct values for calculated schedule durations. Previously, in some cases, an incorrect duration value was displayed.

The “If the task is still running, stop it at this time” option on the Advanced tab of the Schedule Editor dialog box has been removed. This option is no longer used. The Schedule Editor dialog box can be accessed from the Shared Schedules page (menu path: Settings > All Settings > Settings> Server Settings > Notification Server Settings > Shared Schedules). 1584422
Scheduled filter updates have been modified to ensure that all valid filters are updated correctly. Previously, an error occurred if the scheduler encountered a filter that contained an invalid item. This prevented the scheduler from processing any remaining (valid) filters. The scheduler no longer exits with an error if it fails to load an item, but continues to update the filters that it was able to load successfully. 1585097
When you delete a shared schedule that has a policy associated with it, a warning message may not be displayed. This is correct behavior. The association between a shared schedule and a policy is created only when the policy is enabled. If the policy has never been enabled, no association exists, and therefore no warning message will be displayed.

For more information, refer to KnowledgeBase article 45722.

The “At Startup” schedule trigger is now working correctly in Software Management Framework. Schedules that use this trigger now run only when the computer starts. Previously schedules with this trigger were running immediately instead of waiting until the next time the computer started. 1585785

Security issues

Resolved Issue Etrack Defect ID

Automation policies can now be edited by all roles that have the appropriate security permissions. Previously, some automation policies appeared disabled in the Symantec Management Console for a role even though the role had read and write permissions on them.

The Security Roles page no longer shows “Unhandled Exception” error messages. If the user does not have permission to read some items on the Security Roles page, the page loads correctly but the affected items are hidden from view. Previously this scenario caused a security exception that made the page fail to load. 1585366
The Notification Server Settings page (menu path: Settings > All Settings, and then click Notification Server Settings in the Settings tree) can no longer be edited by a user that does not have Write permission to the page. Previously, a user with Read permission to the page was able to edit some settings. 1583674
The Altiris Agent Install page (menu path: Actions > Agents/Plug-ins > Push Altiris Agent) now has improved security. If you have Write access to the page you can create new resource targets. If you have only Read access to the page you can edit existing resource targets but cannot create new ones. Previously you needed Write permission in order to do anything with resource targets - if you had only Read permission, the Select Resources window was unavailable. 1585711
If you are logged on as a lesser privileged (non-administrator) user, you can now view the Item Properties dialog box correctly. Previously, any attempt to view this dialog box, failed with an error. 1585684
Security permissions on the Maintenance Window pages (menu path: Settings > Agents/Plug-ins > Maintenance Windows) are now applied correctly. Previously the resource target view control (the View drop-down list in the Applied To panel) was incorrectly disabled if the user did not have the Apply To Resource Target permission. Any user that can access a Maintenance Window page (i.e. they have Read permission on the page) can now view the applied resource targets. However, they cannot create, modify, or apply resource targets unless they also have Write permission on the page and the Apply To Resource Targets permission. 1585710
Users that do not have the Edit SQL Directly privilege can no longer create or edit an SQL query. Previously, a user that had the Create Report privilege was able to create and edit SQL reports. A user that had Write and Create Children permission on the Automation Policy tree was able to create and edit an SQL query as the data source of an automation policy. 1584052
Security is now applied correctly on the Resource Membership Update schedule page. Previously a user that did not have Write permission on the page was still able to change the Schedule, Date, and Time fields. These fields are now disabled correctly when the user has only Read permission on the page. 1584242
The Shared Schedules page (menu path Settings > Notification Server > Shared Schedules) now works correctly for non-administrator user roles. Non-administrator users can now view shared schedules but cannot edit or create them. Previously only administrators could access this page. Non-administrators had no access to shared schedules. 1584941
Users in the Symantec Supervisors role now have the following permissions on the Automation Policies folder: Read, Write, Delete, and Create Children. Symantec Supervisors can also delete custom automation policies using either the context menu or toolbar. Previously, members of the Symantec Supervisor role could not delete automation policies: the Delete option was not available on the context menu or the toolbar. 1585387
Input validation has been added to the Multicast Configuration settings in the Targeted Agent Settings policy (menu path: Settings > Agents/Plug-ins > Targeted Agent Settings, and then select the Downloads tab). Previously the data that was entered in these fields was not verified, and invalid values were accepted. 1580127
If a role is created that has the same name as an existing user or role the following message is displayed:

"Unable to save the specified role. This is most likely caused by the role being created having the same name as one that already exists. Please choose a different name."

Previously the procedure failed with an unexpected error when trying to create a new security role with the same name as an existing local user.

Users can no longer create new automation policies if they do not have the Create Automation Policies privilege. Previously, in some circumstances, users could create new automation policies without having the required privilege. 1583176
The Targeted Agent Settings page now checks that the user has the Create New Agent Settings privilege. If the user does not have this privilege, the Create New and Clone options (page buttons and context menu options) are disabled. Previously these options were not disabled so a user without the required privilege could create a new targeted agent settings policy. 1583514

Site Server issues

Resolved Issue Etrack Defect ID
The Package Service page in the Symantec Management Console now correctly shows a package status as “Invalid” when the Agent Connectivity Credential specified on the Package Server cannot be authenticated. All of the packages on the affected Package Server are invalid. Previously these packages were still shown as “Available” on the Package Server computer. 1575225
Packages are now distributed to the correct Package Servers based on the membership of the pre-requisite filters. Previously the filters were ignored and the Package Servers received all packages. 1584641
You can now manually assign server computers to a site server. Previously, attempting to manually assign Server agents to a site server installed with the task service failed with an error message. 1585545

User Interface issues

Resolved Issue Etrack Defect ID
The Header images in the Symantec Management Console have been updated. 1585012, 1585321

The Symantec Management Console header and menu bar now displays correctly. Previously, in some circumstances, the header was pushed down and overwriting the menu bar.

1584953, 1583737

When you use a DateTimeValueEditControl in a report parameter, the UI control is now displayed correctly in the report page. Previously the date value was truncated.


The header of the Resource Manager console has been changed to the 7.0 format. Previously the header was still in the old Notification Server 6.5 format.


The Home menu in the Symantec Management Console now correctly hides any menu items that have no child items. Previously, the Security and Storage menu items were always visible, even when they had no child items.


All Item List View, Filter, Organizational View, Reporting, Site Server, and Security pages have now been updated to use the new web controls. Previously some pages still used the old controls. In some cases, when you selected items in a grid and attempted to perform an action on them, the action was performed only on the visible items, rather than on all the selected items.

1585337, 1585338, 1585339, 1585341, 1585342, 1585343, 1585344

You can now reliably access dialog boxes that use the organizational unit picker (such as the Resource Selection dialog box) from the Active Directory Import page. Previously, in some cases, when you clicked a relevant link in a resource import rule, the dialog box would fail to appear. The following error message was displayed: “An error occurred initializing the OU Picker”.


The Symantec Management Console header now displays correctly. Previously, in some circumstances, the menu and tool bar were overwritten and jumbled, and the menu items were not accessible. You had to refresh the console to make the menu display correctly.

The vertical scroll bar now appears reliably in the left pane (tree view). Previously, in some circumstances, the vertical scroll bar did not appear when the tree was expanded. This issue was observed in the Reports and Filters trees. You had to use the mouse wheel to scroll down the tree to view the hidden items. 1584683
A spelling error has been corrected on the General panel of the Status tab in the Data Class page (in the Resource Manager, menu path: View > Inventory, and then select an item in the Data Classes tree). 1585252
The Move Item dialog box has been modified to improve its layout and appearance. This dialog box appears when you select Move from the context (right-click) menu. 1584681
When configuring a proxy server, the error message that is displayed if you enter incorrect credentials is now cleared correctly when you enter the correct credentials. Previously the error message remained visible in the Symantec Management Console. 1585291
The standard package information page (shared by all packages) now loads within a reasonable time. For example, the Altiris Agent Package page. (Menu path: Settings > All Settings, then in the Tree view: Settings > Agents/Plug-ins > Altiris Agent > Windows > Altiris Agent Package.) Previously this page took a long time to load, and sometimes timed-out. 1583973, 1585263
The context-sensitive help link in the Hierarchy Management page now works correctly (menu path: Settings > Notification Server > Hierarchy, and then click Help > Context). Previously clicking this link opened the Documentation Library page. 1581356
The Domain Membership/WINS Import page (menu path: Actions > Discover > Import Domain Membership/WINS) now uses the new Server Schedule Control. 1582094
In the Resource Manager, selecting a data class via the breadcrumb control in the Inventory view now loads the appropriate page correctly. Previously when you clicked the breadcrumb control an error page appeared. 1585513
The UNIX/Linux/Mac menu no longer displays hidden items. Previously the resource targets that do not have any page associated with them were incorrectly appearing in the menu. If the user attempted to select any of those items on the menu, an error page appeared. 1583434
The My Portal portal page is now personalized for each user. First-time users are given a default My Portal page that includes only the Getting Started Web part. Any changes that the user makes, such as adding, editing, or removing Web parts, is personalized to that user (the changes are saved according to their user ID). When the user next logs on and selects the My Portal page option from the Console menu, their personalized My Portal page is automatically reloaded. Previously the same My Portal page was shared by all users and no personalization was applied. 1651638

Miscellaneous issues

Resolved Issue Etrack Defect ID

Installing a solution that includes a "First Time Setup" item does not cause issues with the Symantec Management Console. Previously, in some cases, the "First Time Setup" item caused an unhandled exception that crashed the Console.


The Refresh check box in a report-based web part in a portal page now remains checked when the portal page is refreshed. The Refresh check box specifies whether or not to refresh the web part report when the portal page is loaded. Previously, this check box was automatically unchecked on every page refresh.

Changes to the data source of an automation policy are now saved reliably. Previously, in some circumstances, the changes that you made in the Data Source dialog box were not saved when you clicked OK. This issue affected raw SQL queries only. 1584597
Errors are no longer recorded in the Notification Server error log when context-sensitive help pages are loaded. Previously, for some context-sensitive help pages, an error was added to the log each time the help page was loaded. These errors did not affect the functionality of the Symantec Management Platform online help system. 1583271
The Move option has been removed from the context menu that is available for automation policies. 1584681
You can now add an “At logon” shared schedule to a job or task. Previously, when you selected an “At logon” shared schedule, it was not added to the list in the Task Status panel. 1582677
The 'Computer To Site' and 'Computer Hosts Virtual Machines' resource association types are now displayed in the Resource Associations folder. Previously these items were (incorrectly) hidden. 1585671
When you add a new column to an existing data class, and specify a default value for the column, the default value is set in the new column for all of the existing rows in the data class table. Previously any existing rows had null values set in the new column. The default value was set only in new rows that you added to the table. 1585271
When you create a new Purge Report task (menu path: Manage > Jobs and Tasks, and then in the left pane, right-click and select New > Job or Task. In the Create New Task window, in the left pane, select Purge Report.), the report that you select is now saved correctly. Previously the selection that you made in the Select a Report dialog box was not added to the Create New Task window. 1585367
Empty hidden folders are no longer included in search results. Previously, some empty hidden folders were incorrectly included in the search results. 1582009
When you select a linked item within a custom view, if the item has been deleted an appropriate error message is displayed. Previously this scenario caused an unhandled exception and the page failed to load. 1583378
If you click a folder in the left pane (tree view) and then, before the corresponding page (in the right pane) has finished reloading, right-click to access the context menu, the context menu now displays correctly. Previously, in some cases, this scenario caused an exception and the context menu failed to load. 1584669
When you create a new folder in the Edit View dialog box (menu path: Settings > Console > Views, and then right-click on the appropriate view and click Edit View), the name that you give the new folder is now saved correctly. Previously, when you clicked OK to save the changes that you made in the Edit View dialog, the new folder name was not saved, and the new folder reverted to using the default name (New Folder). 1585723
The performance and reliability of the Symantec Management Platform when under heavy load during nightly schedules has been improved. 1585517
The time that it takes the Resource Manager to load has been reduced. Previously, when you attempted to access the Resource Manager via the context (right-click) menu, it took a long time to load. 1579904
You can now enable or disable any Targeted Agent Settings policy from the context (right-click) menu. Previously any attempt to do so failed with an error message. 1585901
The way in which Primary User data is handled has been improved. Primary User data can be preserved over a number of years, and its history can be saved (this feature is enabled by default). This data can also be viewed in the Resource Manager. Previously, any Primary User data that was more than one year old was overwritten, and its history was not recorded. 1576469
The EULA has been removed from both the Console "About" dialog and the Agent "About" dialog. 1585032
The Resource Manager summary pages now apply security correctly. Previously, in some circumstances, it was possible for user to view resources outside of their scope (resources that they didn’t have permission to access). 1582911

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices