Notification Server 7.0 SP1 Release Notes

Article:DOC1713  |  Created: 2008-11-24  |  Updated: 2009-01-20  |  Article URL http://www.symantec.com/docs/DOC1713
Article Type
Documentation



Description



Question
What's new in Notification Server 7.0 SP1?

Answer

Notification Server 7.0 SP1
Release Notes

Build number 4739

Introduction

Features in this Release

Known Issues in this Release

Resolved Issues in this Release

Introduction

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

Features in this Release

There are no new features in this release.

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
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
.NET 3.5 SP1 is not supported
The minimum requirement for Notification Server is .NET 3.5.
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
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.
N/A
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.
N/A
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
"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
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
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.
N/A
Distribution Domain Local groups cannot be added to Notification Server security roles
N/A
Non-administrator users cannot successfully use hierarchy management pickers
If a user other than an administrator (who only has read permissions to some resources and items) tries to use pickers within the hierarchy management page, all items that are not visible to the current user will be deselected upon applying changes.
N/A
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".
N/A
"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.
N/A
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.
N/A
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.
N/A
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.
N/A
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
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
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
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
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
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
The Shared Schedules page can only be accessed if you are logged in as Symantec Administrator
The Shared Schedules page (accessed through menu path: Settings > Notification Server > Shared Schedules) can only be accessed by users who are logged in with the Symantec Administrator security role. Any users who are logged in with other (non-administrator) security roles are unable to view, create, modify, or delete any shared schedules.
45352
The Symantec Supervisor role cannot delete Automation policies
Users logged in with the Symantec Supervisor role cannot delete Automation policies, even though the Symantec Supervisor role has the appropriate permission grants.
45354
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
N/A
In a resource report, when you change the resource type, the context menu and Actions menu become unavailable
When you change the resource type, the query and the list of columns in the report changes. This breaks the mapping for the drilldown action that opens the context menu.
45711
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
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
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
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
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
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
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
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
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
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
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
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
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
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
You cannot enable or disable any Targeted Agent Settings policies from the context (right-click) menu in the left pane
Any attempt to enable or disable a policy from the context menu fails with an error message. The workaround is to use the On/Off drop-down menu that you access via the policy status indicator in the policy page (the right pane).
46290

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
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.
N/A
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.
N/A
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.
N/A
The "Upon failure" Continue / Restart rules for Managed Software Delivery do not work on Solaris and Mac
Managed Software Delivery aborts if there is any failure with the previous task.
N/A
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.

N/A
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

N/A
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).
N/A
Passwords with the ";" character are not supported
The 'Use privileged account multiple passwords" option does not support passwords with the ";" (semicolon) character.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
"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.
N/A
HTTPS support
The Altiris Agent for UNIX, Linux and Mac does not support HTTPS when Notification Server is configured to require a client certificate.
N/A
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.
N/A
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.”

N/A
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.
N/A
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 (http://www.vmware.com/pdf/vi3_server_config.pdf).

N/A
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\.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
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.
N/A
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

Resolved Issues in this Release

The following are resolved issues in this release.

Altiris Agent issues

Database (CMDB) issues

Dell-specific issues

Filters and Resource Targets issues

Hierarchy issues

Localization issues

Migration/Upgrade issues

Organizational Views and Groups issues

Replication issues

Reports issues

Scheduling issues

Security issues

Site Server issues

User Interface issues

Miscellaneous issues

Altiris Agent issues

Resolved Issue Help Desk Defect ID
A Power Management issue has been fixed. The Altiris Agent now successfully receives tickles from Notification Server when an alias (a preferred name for the Notification Server) is being used. 24784
You can now specify blank entries in the TCP/IP Multicast Address and TCP/IP Multicast Port fields under the Tickle / Power Management heading in the Altiris Agent Settings - Global page. Note that if you specify a value in either one of these fields, you must also specify a value in the other - you cannot leave just one of these fields empty. Previously, if you attempted to specify blank entries in both of these fields, the updated settings could not be saved. 31794
The Altiris Agent is now correctly shown in the Installed Agents window on 64-bit computers. Previously, due to a registry redirection, the Altiris Agent did not appear. 31841
The AexAgent /Clean command now removes all registry keys correctly. Previously, this command did not remove all registry keys correctly. If this command was being used to change the installation location of an agent, this issue would make the scheduler unavailable. 32695
The Altiris Agent now recognizes when a proxy has closed the connection. The Altiris Agent now correctly closes the HTTP connection and establishes a new one. Previously, in some circumstances, communication between the Altiris Agent and Notification Server would fail. 34936
On the Targeted Agent Settings page, on the Advanced tab, under Alternate URL for accessing NS, the current server name and URL are provided as default values. 35209
The Altiris Agent now reliably determines the preferred language of the user UI. Previously, there were some scenarios where the incorrect language was used. 37307
The 7.0 Altiris Agent now uninstalls old versions of platform agents (Task Server, Software Management Framework, and IRM) automatically when the Altiris Agent is being upgraded. 37563
When upgrading from 6.0 SP3 to 7.0 SP1, the Altiris Agent no longer requires the policy cache to be cleared. The necessary password encryption update is performed as part of the upgrade. Previously, the Altiris Agent would report errors (due to using the 6.0 password encryption key) until it received its 7.0 configuration containing its new encryption key. 38010
The Altiris Agent can now reliably download package snapshots from Package Servers via proxy. Previously, the Agent was unable to download the snapshot and logged an error stating that the snapshot was invalid. 38149
The Altiris Agent on a package server no longer crashes when attempting to process large IIS logs. The IIS log is now processed correctly. 38317
The Altiris Agent no longer crashes on shutdown if the Client Task Agent (CTA) is unresponsive or unavailable. 38797
The Altiris Agent no longer crashes if it is restarted while downloading a package. The file download now resumes from the correct position when the Altiris Agent restarts. Previously, the Altiris Agent crash deleted the partially downloaded file, and the download had to be restarted from the beginning. 38960, 38964
Invalid computer names can no longer be added to the computer list on the Altiris Agent Install page. Any computer name that contains a special character, a space, or a comma, cannot be added to the page. Previously, invalid computer names could be added and selected. 39045, 39046
The Altiris Agent now uninstalls properly on Windows XP computers. Previously, the uninstallation occasionally failed with a Runtime Error message. 39163
The Altiris Agent Install page now displays resources correctly in the targeted computers grid. Previously, when you changed the view from "Target" to "Resources", the grid was not populated automatically and had to be refreshed manually. 39225
The Altiris Agent Upgrade task and the Package Server Agent Upgrade task now have different task GUIDs (internal IDs). Previously, both tasks had the same GUID. This change allows users to reliably upgrade their agents using the Run ASAP option on these tasks. Previously, if the Run ASAP option had already been used prior to the upgrade, it could not be run again. 39229
The Windows Package Server Agent Upgrade policy is now disabled by default. The resource target that this policy applies to has also been modified so that it contains only the 7.0 package servers that need to be upgraded. A new policy titled Legacy Windows Package Server Agent Upgrade Policy has also been created (along with the appropriate new resource target) and is enabled by default. This new policy applies to any 7.0 Altiris Agents with 6.0 package servers. When a 6.0 Altiris Agent is upgraded to 7.0, all the sub-agents stop working. If you upgraded a 6.0 Altiris Agent that had a package server agent installed to 7.0, the 6.0 package server would stop working. This new policy will handle this scenario by upgrading the 6.0 package servers to 7.0 so that they are still functional. 39311
The AeXAgentUtil /restart command now works reliably. The Altiris Agent is restarted correctly. Previously, in some circumstances, this command failed. 39362
Upgrading the Altiris Agent via the Altiris Agent Upgrade policy now works reliably. Previously, in some circumstances, after the upgrade started, the Altiris Agent failed to start with an error message. 39427
You can now access the agent/plug-in page for each installed solution reliably. Previously, in some circumstances, the page failed to open and an error message was displayed. 39433
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. 39648

Database (CMDB) issues

Resolved Issue Help Desk Defect ID
Importing the same item multiple times no longer creates multiple instances of the same item in the CMDB. Previously, in some circumstances, multiple instances of items such as web parts were added to a portal page, which caused javascript errors on the portal page. 32685
Error messages are no longer displayed when the CMDB is being reconfigured. Previously, some error messages were displayed even when the reconfiguration was successful. 33520
Changing the database name no longer disables the "Reports > All Reports" menu option or the Filter pages. Previously, if you changed the database name (on the Database Settings page), this menu option was disabled, and all filter pages became inaccessible. 37975
Upgrading Notification Server with installed solutions no longer deletes solution data from the database (CMDB). All solution data is preserved during the upgrade. 38105
You can now specify alternate Reporting database credentials reliably in the Reports tab in the Database Settings page (Settings > Notification Server > Database Settings). Previously, the password was not saved, and attempts to save changes sometimes resulted in an error on the page. 39515

Dell-specific issues

Resolved Issue Help Desk Defect ID
The All Settings page now opens reliably. In some circumstances (as described in the resolution of defect #37975), the last cached/opened page was opened instead of All Settings. 37743
The Resource Discovery reports now function correctly. Previously, in some circumstances, the report did not show any of the discovered computers. 37858
You can now reliably save reports as snapshots, even if some report parameters have been changed. Previously, if any of the report parameters had been changed since the previous snapshot, attempting to save a snapshot failed with an error message. 38396
Computers that have the Client Task agent installed are no longer duplicated in the Resource Manager. Previously some computers were assigned two GUIDs, and each GUID had a separate instance of the computer resource. 38468
The Monitor Universal Metric report now functions correctly. Previously, this report showed an error message when executed, and no data was displayed. 38562
All web parts are now displayed correctly on the Site Administration portal page. 38879
The Resource Manager home page now displays correctly if opened with no resource loaded. Previously, a report would try to run even if the required database items were missing, and would fail. Now a check is performed before attempting to run the report. If any required database objects are missing, a warning message is displayed and the report is not executed. 38897
The Database Utilization reports now function correctly. A change was made to the way that raw SQL data source queries are run, so this resolution may apply to other reports that use raw SQL data sources. 38909
(Japanese only) Dell Servers filters pages are now localized correctly. Previously, these pages were displayed in English. 38920
DMC reports that include "Dell Computer" resource types now function correctly. Previously, some of these reports failed to display in the Dell Management Console. 39007
The Item Reference report now includes a description that outlines the purpose of the report. Previously, no description was shown. 39047
Administration consoles that need to be opened in a new window are now opened correctly. 39148
When you clone a report, any changes to the clone are now saved reliably when you click Save Changes on the report page. Previously, the changes were lost the first time that you attempted to save the report, and you had to repeat the process. 39238
If you attempt to move (using the Move option on the context menu) a resource out of the All Devices organizational view, the following message now appears:
"Resource cannot physically reside in Organizational Views or Organizational Groups"
You can only move resources between organizational groups within the same organizational view.
39280
There are no longer any errors recorded in the log when loading the Resource Manager for the printer resource from the All Devices organizational view. When the language is changed, the Resource Manager still loads correctly and shows the correct localized strings. Previously, when a Printer Resource (Dell's derived DMC Printer Resource) was loaded in the Resource Manager, various localization error messages appeared. 39309
The Group drop-down list box has been removed from the Filter Selection window (used when configuring filter queries). It was not relevant to the filter selection procedure and had no effect on the displayed list of filters. 39500

Filters and Resource Targets issues

Resolved Issue Help Desk Defect ID
When you access the Agent Install Policy page using a remote Symantec Management Platform console, you can now select new resource targets to apply to the policy correctly. Previously, in this scenario, new resource targets could not be selected and applied to the policy. 33371
When you select Edit Filter from the drop-down list to the left of the filter name in the right pane, the Edit Filter window that opens is now fully functional. Previously, the links in the new window failed with errors. 37314
The resource target builder (the Add Target window) now displays the appropriate computer names when you filter computers by excluding computers not in a computer list. Previously, there were scenarios where the computer drop-down list displayed a list of resources rather than computers. 38539
Saving a resource target under a new name (the Save As option) now functions reliably. Previously, there were some scenarios in which this operation would fail with an error message. 38578
If TP4 was installed, the Quick Apply option (to apply a target or filter to a policy or task) didn't work. The user received a message saying "Data could not be loaded". This error has been fixed, and the Quick Apply option now works correctly. 39036
The filter exclusion list can now be modified reliably. Previously, in some circumstances, when you clicked the Edit button on the filter page the modified exclusion list was reset to the previous selection. 39085
When you create a new filter by using the right-click menu on the Filters page (the root node of the Filters tree), the new filter page now opens in the same Console window. This lets you specify inclusions and exclusions reliably. Previously, the new filter opened in a new window, which disabled the ability to specify inclusions or exclusions. 39146
The IPv6 Hardware filter now identifies the correct computers. Previously, some Windows 2000 computers that were not IPv6 enabled were also included. 39208
The 'Delta Resource Membership Update' schedule now updates the appropriate filters. Previously, the "not in use" filters were also being updated. 39538
The Delta Update schedule now supports filters that contain raw SQL queries that are more complex than a single select statement. These filters now have a full update. Note that the update is full, rather than delta, which may carry a performance penalty. A warning message is logged. Previously, any such filters were not updated at all. 39645

Hierarchy issues

Resolved Issue Help Desk Defect ID
When working on the Hierarchy Management page, you require the following security privileges:
To add, edit, or delete nodes in the Topology tab, you require the 'Manage Hierarchy Topology' privilege.
To add, edit, or delete rules in the Replication tab, you require the 'Manage Hierarchy Replication' privilege.
Previously, in some circumstances, some items were still editable when you did not have the necessary privilege.
37405
A javascript error message is no longer displayed when you add a child Notification Server to a hierarchy on the Hierarchy page. 38915
Policies that are replicated down a hierarchy with the "Enable" property not set as an editable property now function correctly. The user cannot change the Enable/Disable setting on the destination computer. Previously, the context menu contained the Enable/Disable option for all policies. This option is no longer displayed for policies that do not have the "Enable" property set as an editable property. 39083

Localization issues

Resolved Issue Help Desk Defect ID
(Spanish only) The Altiris Agent dialog boxes are now localized correctly. Previously, when Spanish International Sort was selected, the dialog boxes were displayed in English. 38085
When viewing reports, the "Showing computer" text in the report parameter bar and the "Failed to save the report" error message are now correctly localized. 38339
The text associated with Update Client Configuration and Send Basic Inventory fields on SMP Task pages is now localized correctly. Previously, these strings were hardcoded in English. 38366
(Portuguese only) The Hierarchy Management Wizard is now localized correctly. Previously, there was an error in the title of the "Finish" dialog box. 38368
When using the Move Item task, the tree structure that is displayed when you select items to move is now localized correctly. Previously, the tree structure was hardcoded in English. 38492
(French only) Opening any of the default filters for the first time no longer causes errors. Previously, after installing the Symantec Management Platform, any attempt to open a default filter failed with an error message. The problem required a restart of the computer to resolve. 38574
(Turkish only) The Software Portal is now localized correctly. Previously, this page was displayed in English. 38580
(French only) Filter pages now load correctly. Previously, any attempt to load a filter page failed with an error message. 38599
The Client Task Agent is now correctly localized. Previously, in some circumstances, the Client Task Agent could not obtain the correct UI language from the client computer so would default to English. When this happened, the Task Status tab in the Altiris Agent UI was displayed in English instead of the correct language. 38907
The Edit Attribute dialog box  is now localized correctly. Previously, the dialog box text was English only. 38908
If an unsupported language is chosen on the Symantec Management Console browser, the console now falls back to the appropriate base culture. If the base culture is also unsupported, the invariant (English) is used. Previously, the console did not always fall back correctly, and in some cases no characters were shown for unsupported languages. 39156
The Altiris Agent UI online help now displays the appropriate localized version. Previously, in some circumstances, an incorrect language version was displayed. 39679
(French only) The menu bar on the Symantec Management Console now displays correctly. 39700

Migration/Upgrade issues

Resolved Issue Help Desk Defect ID
Resource history settings are now migrated correctly when you upgrade from Notification Server 6.0 to Notification Server 7.0. 37890
When you are repairing Resource Management via the Symantec Installation Manager, no services are started during the process. Previously, the Altiris Client Message Dispatcher, Altiris File Receiver, and Altiris Service were all started. 38848
The Notification Server Migration Wizard no longer fails with an error if the logged on user is not the application identity account. However, the logged on user must have the "Impersonate a client after authentication" privilege and must be a member of the Symantec Administrators role in the Symantec Management Platform. 38944
When the Platform is configured to use a custom Web site instead of the default IIS website, the Platform upgrade now functions correctly. Previously the upgrade installed new virtual folders in the default IIS website instead of the custom Web site. 38957
When you upgrade the Symantec Management Platform, both the original platform and the update are now listed correctly in the Symantec Installation Manager (SIM). 38985
You can now migrate from Notification Server SP3 R9 hotfix to Notification Server 7.0. Previously an error message was displayed stating that an earlier version of Notification Server should be used. 38997
When installing the Symantec Management Platform, the "Some MSI could not be loaded" error message no longer appears in the log viewer. Previously, when the installation and configuration was successful, this error message sometimes appeared. 39062
Package distribution points are updated automatically each time a package is updated as part of any hotfix, service pack, or tech preview build. 39065
When you uninstall the Symantec Management Platform upgrade, the text in the Uninstall window now displays correctly. 39167
Only local administrators can now run the Migration Wizard to upgrade the Symantec Management Platform. If the current user is not a local administrator, the Migration Wizard will now show a warning message and will not allow the user to proceed. Previously, a non-local administrator could start the Migration Wizard, but the upgrade process would fail during the migration. 39257
When you upgrade the Symantec Management Platform, the Altiris Agent now reliably switches to the upgraded Notification Server. Previously, in some circumstances, the Altiris Agent remained pointing at the old Notification Server. 39269
Custom Resource History and Resource Association History settings are no longer reset to default when you upgrade from version 7.0 to 7.0 SP1. Previously, these settings were reset to the defaults. The affected settings included both the enabled\disabled state and the retention period. 39517

Organizational Views and Groups issues

Resolved Issue Help Desk Defect ID
The Add to Organizational Group and Delete Item dialog boxes now display an error message if the target item no longer exists (has already been deleted). Previously, the Console page failed with a server error and provided no indication of the cause of the problem. 38313
Item links can no longer be created under organizational views. Item links in organizational views are not supported by the resource target feature, which was causing errors in some circumstances. 39176

Replication issues

Resolved Issue Help Desk Defect ID
Merged resources (as may be created when resources are replicated) can now have only one status association. Previously, in some circumstances, if you merged two resources that had different status values, the merged resource had both values. This made the item invalid and unable to be modified. 32296
If you attempt to replicate privileges for a solution that does not exist on the destination Symantec Management Platform, the solution-specific privileges are not imported. Previously, importing privileges that did not exist on the destination computer caused the Security Role pages to fail. 35846
Automation policies can now be individually selected for replication and are replicated reliably. Previously, all automation policies were stored in a hidden folder and could not be selected manually. 37623
When you delete a folder and replicate the change down the hierarchy, only the replicated items in the folder are deleted on the children. If any items are created on a child and placed in the corresponding folder, the folder itself is not deleted on the child, and the custom items are preserved. Previously, there was no check on the items within the folder, so the entire folder was deleted, which sometimes deleted non-replicated items. 37870
When you are adding items to an Item Replication rule, the Search function in the Replication Item picker window now functions correctly. 37929
Differential or complete replication schedules can now be run by using a shared schedule. Previously, if a replication schedule was set to run on any shared schedule, the replication was not triggered when the shared schedule was run. 38253
The context menu no longer displays the "Replicate Now" option for any resources. This option is supported for configuration and management items only. Previously, this option was displayed for some resources. 38878
Items that have the "No Replication" attribute are no longer displayed when you are selecting items to replicate with an item replication rule. Previously, all items were displayed in the Select Items dialog box, which allowed you to select items that could be replicated. 38961
The DataClassSummaryGenerator table no longer keeps multiple rows of the same agent details. This will improve replication performance, which would otherwise have degraded over time. 39081
Resource target/owner trustee relationships are now being synched correctly as part of the complete replication process.  Previously, replication did not include the correct security applied to resource targets, so they were not updates at the destination Notification Server. 39448

Reports issues

Resolved Issue Help Desk Defect ID
Computer reports now correctly display the operating system names of Vista and 2008 computers in the results grid. Previously, both Vista and 2008 computers had two entries in the results grid. The operating system names were different for managed and unmanaged discovered computers. 34332
The "Object Marked for replication" report now returns results within a reasonable time. Previously, in some circumstances, this report took about 30 seconds to load. 34393
The Altiris Agent 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. 36669
When you create a drilldown to a report, a report picker is now used to select the target report. Previously, you were required to enter the Guid of the report. 36821
Drill-down reports and URLs now receive the necessary report parameters from the parent report correctly. Previously, some drill-down reports and URLs were not receiving the required parameters from the parent report. 37545, 39375, 39417
The drill-down report "Microsoft Active Directory Import Rule Task Runs Details" now returns the correct results. 37594
When viewing reports in chart view, the labels are now displayed correctly and can be turned off when not wanted. 37958
Creating a new report no longer causes other reports in the Report tree to fail to load when selected. Previously, in some circumstances, the other reports in the tree became unavailable and, when selected, would fail to load with an error message. 38101
Navigating to reports in the Symantec Management Console now works reliably. Previously, users experienced occasional failures when the selected report did not appear, and an "Unknown Error" message was displayed. You can now reliably open a report in a new window. Previously, opening a report in a new window sometimes failed with an error message. 38179
The "Computers with Agent Installed" report now functions correctly when set to display all computers (i.e. the "Number of computers to show" parameter = All). 38288
Drill-down reports opened in a new window displayed javascript errors when right-click actions were attempted. Right-click actions now function correctly in all report windows. 38507
When viewing reports in chart view, the X- and Y-axis attributes are now shown correctly. 38639
The "Discovered Computers" report now functions correctly. 38899
Task server reports for failed jobs and tasks are now displayed correctly. Previously, some reports showed an error message when selected, and no data was displayed. 38937
Right-click actions now work reliably on resources listed in report grids that are grouped by one or more columns. The action is always applied to the selected resource. Previously, in some circumstances, the action was applied to a different resource in the report grid. 39018
A script block error that sometimes prevented you from creating new reports has been resolved. This issue affected TP4 only. 39034
A new chart label type, "X Axis Only", has been added to the chart view. 39040
Reports that include chart views that set the X and Y axes automatically now run correctly the first time that they are executed. Previously, these reports failed with an error the first time, but they ran correctly the next time they were executed. 39041
The Query Builder used in reports and filters now loads correctly even if the SQL that it contains is invalid. This allows you to make the necessary corrections to the SQL. Previously, the Query Builder page would fail to load and display an error message. 39130
Hierarchy summary (drill-down) reports now include virtual machines. 39131
You can now reliably save a snapshot of a report after changing the report parameters. Previously, for some reports, attempting to save a snapshot after changing parameters failed with an error message. 39182
Reports with chart views now show the correct results when re-run after changing parameter values. Previously, no results were displayed in this scenario. You needed to navigate away from the report, and then return to it, in order to successfully run the report with the new changed parameters. 39195
The resource reports in the 6.0 Legacy Reports tree now function correctly. Previously, if you attempted to schedule a legacy resource report, the attempt failed and an error message was displayed. 39221
If a report execution times out, an error message is now shown on the report page to inform the user that the report execution has stopped. 39277
When you right-click on an item in the report results grid, the context menu now reliably displays the correct set of options. Previously, in some circumstances, some options were not displayed. 39336, 39349
When you are adding fields to a new user report via the Add Fields and DataClassAttributes dialog box, the Field drop-down list now is cleared when you add the selected item to the list of Fields to be included. 39399
In the Query Builder, when you specify a parameter as 'Required', the 'Test' and 'Default' values are set automatically. Previously, in some circumstances, it was possible to set a "Null" value for a required parameter. This caused a non-recoverable error in the query and all unsaved changes to the report configuration were lost. 39462
You are now able to edit a report that is not runable (for example, if the report query uses an object that does not exist). Previously, in some circumstances, such a report could not be edited to make the necessary corrections. 39463
The "Save As" feature for a report now functions correctly when you have selected particular rows in the results grid. Previously, in some circumstances, this operation failed. 39471
You can now open the context menu from report results grid when the report contains resource type associations. Previously, if the report contained any resource type associations, the context menu failed to appear. 39474

Scheduling issues

Resolved Issue Help Desk Defect ID
When you set the user-logon modifiers for a schedule (in the Advanced Options dialog box) the settings are now applied correctly. Previously, the settings in the Advanced Options dialog were ignored. 33144
Shared schedules that are scheduled to run only on February 29 now function correctly, and are run only on the appropriate day. Previously, any such schedule was run on the 29th day of every month. 36201
In some circumstances, updating a schedule caused tasks on the previous schedule to run immediately, instead of on the updated schedule. This was by design, but new functionality has been added to ensure that this scenario can be avoided. 38124
A task that is scheduled to run at the same time as it starts now runs correctly. Previously, in this scenario, the task was not run. 39244
The start date of some default schedules cannot be changed. This is as designed. 39232
Shared schedules that are set to "Run at user logon" or "Run at system startup" now run at the appropriate times. Previously, in some circumstances, these schedules were running at the default times (each day at 9 am.). 39472
The Agent Scheduler now correctly displays the next run time. Previously, in some circumstances, the displayed next run time was after the schedule end date and time. 39555

Security issues

Resolved Issue Help Desk Defect ID
The Search functionality no longer allows users to access items that they do not have security permissions for. Previously, a user could open the Console without being a member of any security role and use the Search function. Now the user must be a member of a security role in order to open the Symantec Management Console, and all search results are filtered according to the user role. 29353
Enhancements have been made to the process that validates user input in SQL. This further reduces the possibility of SQL input causing application instability or gaining unauthorized access to data or system resources. 33683
When a user attempts to create a site or subnet, but does not have the necessary security permissions, an appropriate error message is displayed. Previously, in this scenario, the operation would fail with an unknown error. 34552
A security vulnerability in the "Hierarchy Alerts by last N days" report has been fixed. Previously, this report was vulnerable to XSS attack. 35447
An XSS vulnerability in the report controls has been resolved. Any javascript that is entered in the Parameter edit boxes can no longer have any effect. 35507
An XSS vulnerability on the Edit Menu page (Settings > Console > Menus) has been resolved. Any HTML or script that is entered in the Name text box is now escaped. 35542
An XSS vulnerability in the Right-Click Action expression builder (Settings > Console > Right-Click Actions) has been resolved. Any HTML or script that is added to the expression is now escaped. 35543
The Altiris Level 1 security role is now able to access the Monitoring and Alerting portal page when appropriate permissions are assigned. Previously, this page displayed a server error when an Altiris Level 1 user tried to access it. 36637
An XSS vulnerability in the Filters tree has been resolved. 38110
Having read permission on a folder now reliably allows you to view reports that are contained in that folder. Previously, there were some circumstances when access to a report was denied with a security exception error, even when the user role had read permission on the appropriate folder. 38186
Security on automation policies is now implemented correctly for the default security roles. Level 1 and Level 2 workers have read permission only, and they now get the same view in the UI (all the options are greyed out and they are unable to edit anything). Supervisors have write permission so they can create and edit policies. 38769
All Altiris Agent binaries (exe, dll) are now signed with the Symantec key. Previously, unsigned binaries were being reported in the Altiris Agent folder. 38771
The Altiris Agent Install page is now displayed correctly for all user roles that have the appropriate Read and Write permissions. Previously, only the Symantec Admin role was able to access this page. 38935
IE7 ActiveX controls are now signed to ensure your security. 39206
Adding new users to security roles in the Security Role Manager now functions reliably. Previously, in some circumstances, attempting to add a new user to a security role failed with an error message. 39254
A user with local admin rights and the Symantec Level 2 security role can now use the context menu correctly. Previously, in some circumstances, an error was logged in the error log each time such a user accessed an item with the context menu. 39387
The "Symantec Level 2 Workers" security role now has Write access to the Policies Folder (accessed via the Manage > Policies menu option). 39684

Site Server issues

Resolved Issue Help Desk Defect ID
The Services pages for a Site Server did not function in the Japanese version of the Symantec Management Console. These pages are now displayed correctly. 38453
Uninstalling solutions now has no effect on the Symantec Management Platform site server infrastructure. Previously, uninstalling a solution that had a site service introduced errors and required a restart of the Altiris service. 38777
By default, each external package is now assigned to the package server that hosts the package. Previously, in some circumstances, this issue was preventing replicated external packages from being downloaded by the destination Package Servers. 39165

User Interface issues

Resolved Issue Help Desk Defect ID
When you reopen the Symantec Management Console, the last page that you viewed in the previous Console session is now restored reliably. 32683
An Internet Explorer script error message is no longer shown if you cancel changes to a page when you have already navigated to another Console page. Previously, an error message was sometimes displayed in this scenario. The Console functionality was not affected. 36806
The Security Role Manager now displays content reliably when the Advanced button is clicked. Previously, when the Advanced dialog box was opened, the left panel content was hidden and was not refreshed when the Advanced dialog box was closed. 37889
The Altiris Notification Server Migration Wizard now displays the full text of each product's name correctly. 37894
The left pane of the Resource Manager now has a vertical scroll bar that appears when necessary to ensure that all data can be viewed. All text is now correctly wrapped within the left pane. 37957
Resource targets are now visible to users logged in as Patch Manager Administrators. Previously, when applying targets to Patch policies, the drop-down list of available targets was empty. 38166
Reports that contained a large amount of data were not displayed correctly when the data was plotted as a line chart. All line charts are now rendered correctly. 38407
When you are working in the Symantec Management Console, if you navigate to a new page without saving the changes on the current page, you are prompted for confirmation. Clicking Cancel at this prompt (to cancel the move and remain on the same page) now works reliably. Previously, in some circumstances, a runtime error occurred. 38408
The drop-down menu from the breadcrumb bar now functions correctly. Previously, some reports did not appear on the menu. 38427
The software build number is now displayed correctly in the Online Help (accessed by clicking Help > About Symantec Management). 38662
An error message appears if incorrect proxy server settings are specified in the Proxy tab. This message is now cleared correctly. When the correct proxy settings are specified, only the "Proxy settings tested successfully" message is displayed. 38686
When you are viewing report pages, the drop-down menu is now cleared correctly. Previously, in some circumstances, the menu remained visible and could not be closed. 38989
In the Security Role Manager, the "Altiris" prefix has been removed from all permission groups. The "Task Permissions" heading has been renamed "Policy Permissions". 39014
Drop-down menus are now cleared correctly when you are viewing a portal page. 39020
A "Service and Asset Management" folder has been added to the Symantec Management Console folder structure. This folder is used by Asset Management Solution, Barcode Solution, CMDB Solution, Connector Solution, and Service Desk Solution. 39246
New menu items can now be added to the menu structure reliably. Previously, in some circumstances, when you customized the menu structure, the new menu items were lost when you attempted to save the changes. This issue affected the top level menus only, and did not affect the Home menu. 39372
The context help in the Symantec Management Console now opens reliably. Previously, in some circumstances, the Documentation Library opened instead of the relevant context help topic. 39377
The link to the Data Loss Prevention Portal page from the Home menu now works reliably. Previously, this link did not work in some circumstances. 39392
When you uninstall all site services from a site server, the site server is now correctly removed from the Site Servers tree in the Console. Previously, in some circumstances, the uninstalled site server would remain visible in the Console and, if you selected it, would display an "Invalid ID" error message. 39438
The Documentation Library (accessed menu option: Help > Documentation Library), now lets you access the PDF and HTML versions of the Symantec Management Platform User's Guide reliably. 39464

Miscellaneous issues

Resolved Issue Help Desk Defect ID
Checkpoint recovery now functions correctly if the network is disconnected while throttling a package download. The download now continues from where it was interrupted, instead of restarting from the beginning. 28447
The Resource Type page can now display resource types with multiple data classes that have the same name. The duplicated data class names are identified by the platform type (Win32, Unix, Common) that is appended to the name. Previously, if two data classes with the same name were associated with a computer resource type, the Resource Type Edit page failed to load. 34784
When you manually edit the domain of a user, the update is saved correctly. This applies to a user resource in the CMDB that was created manually using CMDB Solution, or imported via Connector Solution. Previously, the appropriate database table was not being updated correctly and the changes were lost. 35919
The Hierarchy Structure Change automation policy now reports only on the changes that were made in the last day. The report runs on a daily schedule so all changes are captured once only. Previously, this policy reported older changes as well, which resulted in repeated actions (email sent to administrator) for the same changes. 37470
You can now reliably import inventory forwarding rules into the Symantec Management Platform CMDB as replication rules. Previously, if any data class items in the inventory forwarding rule did not exist in the CMDB, the import failed. 37738
Domain Discovery now shows the correct icon when the discovery process is successful. Previously, there were some scenarios where a failure icon was displayed when the discovery had been successful. 37829
Log files are now displayed correctly in the log viewer after upgrading the Altiris Agent. 37879
Discovery methods now reliably identify the operating system of each discovered computer. 38349
When you open the Documentation Library from the Resource Manager console, the Documentation Library page now appears in a new window (instead of inside the Resource Manager). When you open further pages from the Resource Manager console menu, the pages now appear inside the Resource Manager (instead of inside the parent Symantec Management Console). 38364
A cache has been added for reverse DNS lookups carried out during web requests. This improves the Symantec Management Console performance by reducing the time it takes for right-click options to load. 38571
You can now create new resource types when you create an external package. 38622
A cache has been added for reverse DNS lookups carried out during web requests. This improves the Symantec Management Console performance by reducing the time it takes for pages to load. Some pages, such as those accessed via links on portal pages, sometimes took a long time to load. 38426, 38663, 38665
The Resource Summary tab in the Resource Manager has been modified to show the information that is now reported by Inventory Solution. Some obsolete fields have been removed. 38829
The performance of the Symantec Management Platform is no longer being degraded by repeated Licensing checks when pcAnywhere Solution is installed. 38941
Forwarding inventory from Notification Server 6.0 to 7.0 now functions reliably. Previously, in some circumstances, some settings were not transferred correctly. 38948
Taking ownership of a custom item in the Console by clicking "Owner" in the Take Ownership window now functions correctly. Previously, the Symantec Management Console locked up when you clicked this button. 38955
The Resource Association page of the Resource Manager console now loads correctly. Previously, this page occasionally failed to load for some resources. 38990
MSI custom actions have been modified to run silently. Previously, some command windows were displayed while installing the Symantec Management Platform. 39021
The Resource Manager console now opens reliably when accessed directly from a resource. Previously, this failed for some resource types due to a non-existent URL. 39099
License checking for Console users logged on with the Level 2 Worker security role now functions correctly. Previously, an error occurred and the Console displayed a blank page or licensing errors. 39249
Basic inventory information is now collected reliably on Windows 2000 SP4 computers. Previously, some inventory information was not being collected correctly. This issue applied to Windows 2000 SP4 computers only. 39276
You can no longer delete the Notification Server computer resource as part of a multiple selection deletion. If you select just the Notification Server computer resource for deletion, a warning message is displayed. Deleting the Notification Server computer resource can cause system instability, so it is not recommended. 38595, 39328
The links on the First Time Setup page in the Symantec Management Console now open properly. Previously, in some circumstances, when you clicked a link an error message was displayed at the bottom of the page and no action took place. 39356
The License framework now reclaims licenses correctly when an asset status is changed to retired or disposed. 39407
When you have installed Client Management Suite, an exception error pertaining to AltirisSupportService.exe with the description: "Unhandled exception in Support Service Service Monitor timed event." no longer appears every minute in the logs. 39456
When two resources are merged, if one is managed and the other is unmanaged, the unmanaged resource is merged into the managed resource. This ensures that the merged resource is managed. Previously, in some circumstances, the managed resource was merged into the unmanaged resource, resulting in the merged resource being unmanaged. 39531
In some circumstances, temporary database logs were filling up the disk space and impacting the performance of the Symantec Management Platform. This issue was caused by an internal stored procedure and has been resolved. 39703
Right-Click actions now work reliably when you are selecting Network Resources. Previously, in some circumstances, the action failed with an error. 75922


Legacy ID



44542


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


Terms of use for this information are found in Legal Notices