Symantec Management Platform 7.1 Release...

Symantec ManagementPlatform 7.1 Release Notes

The software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Documentation version: 7.1

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in theU.S. and other countries. Other namesmaybe trademarksof their respective owners.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web siteat the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level



■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Support agreement resourcesIf youwant to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

mailto:[email protected]



Symantec ManagementPlatform 7.1 Release Notes

This document includes the following topics:

■ About Symantec Management Platform 7.1

■ What’s new in Symantec Management Platform 7.1

■ General installation and upgrade information

■ System requirements

■ Known issues

■ Fixed issues

■ Other things to know

■ Documentation that is installed

■ Other information

About Symantec Management Platform 7.1Build number 7.1.5359

The Symantec Management Platform is a group of foundation services that areleveraged by IT-related solutions. Solutions integrate with the platform and takeadvantage of the shared services, such as security, reporting, communications,package deployment, theConfigurationManagementDatabase (CMDB), andmore.

What’s new in Symantec Management Platform 7.1The following table lists the features that are new in Symantec ManagementPlatform 7.1.

Table 1-1 New features in Symantec Management Platform 7.1

DescriptionFeature

Symantec Management Platform 7.1 has its own user accounts. Previousversions of Symantec Management Platform used Windows users andgroups for user security. Windows users are still used, but they are nolonger the only security mechanism.

Before Symantec Management Platform 7.1, role management involvedcreating Windows local groups on the Symantec Management Platformserver for roles and then adding Windows users to them. In SymantecManagement Platform 7.1 onwards, the Symantec Management Platformmaintains its own list of user accounts and roles. These accounts and rolescan be imported from Windows. This import occurs if you upgrade toSymantec Management Platform 7.1 so access is not interrupted andsecurity is maintained.

User accounts, which are sometimes referred to as users, are not the sameas user resources in Symantec Management Platform. A user resource isan entity that is used to associate managed devices with the owner of thedevice. The existing user resources and the user accounts that can log onto the Symantec Management Console or run a workflow are separateentities.

EachSymantecManagementPlatformuser account contains the credentialsthat the user needs to access the SymantecManagement Console or to runa workflow. The credentials may be internal Symantec ManagementPlatform user names and passwords or Windows accounts.

Internal credentials are currently used for workflow integration only.Windows credentials are required to access the Symantec ManagementConsole.

The Everyone role is a top-level role that contains all roles and useraccounts. This role replaces the Windows built-in groups Everyone andAuthenticated Users.

Security roles can now be nested. You can add a role to multiple securityroles. Amember ofmultiple security roles has the union of all the privilegesand permissions that those roles grant.

Changes to security roles

Symantec Management Platform 7.1 Release NotesWhat’s new in Symantec Management Platform 7.1

8

Table 1-1 New features in Symantec Management Platform 7.1 (continued)

DescriptionFeature

You must install Symantec Management Platform 7.1 on a computerrunning Windows Server 2008 R2. Windows Server 2008 R2 requires a64-bit computer. If you upgrade to Symantec Management Platform 7.1,Symantec recommends that you upgrade on a new computer. However, ifyour current computer is a 64-bit computer, you can upgrade on thatcomputer. Before you upgrade, you must back up all of your data andupgrade your operating system.

Windows Server 2008 R2 required

You must enable SSL for the Notification Server Web site before installingthe Symantec Management Platform products. You can have SymantecInstallation Manager configure SSL during the installation or you canconfigure SSL before you begin the installation.

SSL must be enabled

The top-level network administrator can now delegate discovery tasks toother users who are not administrators. Admin-level roles in SymantecManagement Platform security are Administrator and SymantecSupervisors. These are default, or predefined, security roles. Now theadministrator can delegate discovery tasks to non-administrator roles.Some of the predefined security roles are Symantec Level 1 Worker andSymantec Level 2 Worker.

To enable users to discover network devices and work with connectionprofiles and credentials, you set permissions. You also assign privileges touser roles to enable them to create connection profiles and credentials.You set permissions on the items that youwant the users to work with: theconnection profiles and credentials. Then, you select a non-administratoruser role to which you assign users. You then limit or augment the scopeof the role by removing or assigning specific privileges.

DelegatingNetworkDiscovery tasks tonon-administrators

Pluggable ProtocolsArchitecture (PPA) includes a policy that can remotelyinstall the Pluggable Protocols Architecture (PPA) client computercomponent on a site server. Youmust install this component on a site serverbefore you can add monitor service to the site server. When the PluggableProtocols Architecture (PPA) client computer component is installed, thecredentialmanager client computer component is also installed. The policythat installs the credentialmanager client computer component configuresthe agent to automatically import credentials from Notification Server.

Policy for remote installation ofPluggable ProtocolsArchitecture (PPA)

UNIX, Linux,Mac supports concurrent packagedownloadingwithManagedSoftware Delivery if the policy contains more than one package.

Concurrent package downloadingwithUNIX, Linux, and Mac

9Symantec Management Platform 7.1 Release NotesWhat’s new in Symantec Management Platform 7.1

Table 1-1 New features in Symantec Management Platform 7.1 (continued)

DescriptionFeature

When you upgrade fromSymantecManagement Platform7.0 to SymantecManagement Platform 7.1, you can migrate all of the data in the CMDB.You migrate the data in the database by pointing to the database duringinstallation. You can also migrate Notification Server settings and thegeneral settings that are not in the CMDB with the Altiris NotificationServer Migration Wizard. For example, you can migrate KMS keys,credential manager keys, and security roles.

Data migration

If you do not have SQL Server installed, you can let Symantec InstallationManager install Windows SQL Server Express near the beginning of theinstallation process. You can use SQL Server Express if you manage lessthan 500 computers.

Installation of SQL Server Express

General installation and upgrade informationYouuseSymantec InstallationManager to install SymantecManagementPlatformandall of theproducts that runon theplatform.YoualsouseSymantec InstallationManager to install updates, apply licenses, and repair installations.

The following third-party plug-ins are prerequisites for Symantec ManagementPlatform 7.1:

■ Sun Java Runtime 6Java JRE is required for LiveState and Altiris Package Conversion. Java JRE isalso required on any computer that remotely accesses the SymantecManagement Consolewhen the Software Library is used as the package source.

■ Microsoft Silverlight 3.0Silverlight is required for the deployment portal of Deployment Solution andthe First Time Setup page in the Symantec Management Console.

■ Adobe Flash Player 10The Adobe Flash Player plug-in for Internet Explorer is required for theResource Association Diagram in the Asset Management Suite.

When you upgrade from Symantec Management Platform 7.0, you can migrateall of the data in the 7.0 Configuration Management Database (CMDB). Becausethe 7.0 database is compatible with SymantecManagement Platform 7.1, you canconnect to an instance of the database tomigrate the data. Symantec recommendsthat you connect to the 7.0 database during installation. You can connect to thedatabase on theDatabaseConfigurationpage in Symantec InstallationManager.

Symantec Management Platform 7.1 Release NotesGeneral installation and upgrade information

10

However, the following Notification Server data is not stored in the database andmust be migrated separately:

■ Notification Server security settings and some general settingsYou can migrate these settings with the Altiris Notification Server MigrationWizard.

■ Windows Server user accountsYou must recreate the user accounts on the new computer.

■ Some solution-specific files and settingsYou must manually move some solution-specific files and settings.

■ Hierarchical relationshipsIf you use hierarchical relationships, you must recreate them and enablereplication.

For more information about upgrading, see the documents athttps://www-secure.symantec.com/connect/articles/altiris-endpoint-management-migrations-and-upgrades-71.

System requirementsSymantec Management Platform 7.1 requires Windows Server 2008 R2 (64-bit).

The recommended system requirements vary depending on the size of theenvironment. The size of the environment also affects how you configure theplatform.

For more information, see the documents athttps://www-secure.symantec.com/connect/articles/altiris-endpoint-management-migrations-and-upgrades-71

Known issuesThe known issues are separated into the following components:

■ Symantec Installation ManagerSee Table 1-2 on page 12.

■ Notification ServerSee Table 1-3 on page 13.

■ Task ServerSee Table 1-4 on page 22.

■ Software Management FrameworkSee Table 1-5 on page 24.

11Symantec Management Platform 7.1 Release NotesSystem requirements

https://www-secure.symantec.com/connect/articles/altiris-endpoint-management-migrations-and-upgrades-71




■ Data ConnectorSee Table 1-6 on page 25.

■ Credential Manager, Connection Profiles, and the Pluggable ProtocolsArchitectureSee Table 1-7 on page 29.

■ UNIX/Linux/MacSee Table 1-8 on page 29.

Table 1-2 Known Issues for Symantec Installation Manager

Article LinkDescriptionIssue

N/AIf you have installed optional components(docs, languages,and migration) to a server and then attempt to create aninstallation package on that server, you will not be able toadd those components.

Unable to add optionalcomponents to aninstallation package ifcomponentsalready installedon server

N/AIf youdonothave the latest versionof Symantec InstallationManager installed, you cannotuninstall anyproductwithoutfirst installing the latest version of Symantec InstallationManager.

Unable to uninstall a productwithout updating SymantecInstallation Manager to thelatest version

N/ASymantec Installation Manager attempts to configure twoproducts at the same time and the installation or upgradefails.

Symantec InstallationManager attempts toconfigure twoproducts at thesame time

N/AWhenno network is enabled, the SQL Server name does notget populated automatically on theDatabaseConfigurationpage.

To resolve this issue, you can do one of the following:

■ Enter the SQL Server name manually.

■ Have SQL Server Browser enabled (Microsoft KB:http://msdn.microsoft.com/en-us/library/ms181087.aspx).

■ Enable Named-Pipe Protocol.

SQL Server name does notpopulate on the DatabaseConfiguration page duringinstallation

N/AAfter uninstalling the Symantec Management Platformproducts, many files, registry keys and values, anddirectories are not uninstalled. You can remove these itemswith the SmpZap command line utility. The Article ID linkaccesses a knowledgebase articlewith instructions for usingthis utility and with the utility's files attached.

Uninstall leaves many filesand folders

Symantec Management Platform 7.1 Release NotesKnown issues

12

Table 1-2 Known Issues for Symantec Installation Manager (continued)


N/AAfter uninstalling a suite, some items of the suite's productsare left in the treeview pane of the management console.

The treeview pane of themanagement consoledisplays items foruninstalledproducts

N/AIf there are problems with SQL Server during installation,Symantec InstallationManager installs the product but theconfiguration of the product fails.

Problems with SQL Servercause the configuration of aproduct to fail

N/ASymantec Management Platform products cannot beinstalled when Symantec Endpoint Protection 11.0 isenabled.

Install fails with SymantecEndpoint Protection 11.0enabled

N/AWith an on-box upgrade, if you don't select any of the itemson theOptional Installs page and you cancel the installationwhen the migration wizard starts, Symantec InstallationManager opens to the Optional Installs page the next timeit starts. To determine what products are being installed,click Back to access the Install New Products page or clickNext to access the End User License Agreement page.

Relaunching SymantecInstallation Manager aftercanceling the migrationwizard opens the OptionalInstalls page

N/AOn theNotification Server Configuration page, if you selecta non-default Web site and bind it to the default SSL port,an error appears.

A non-default Web site withthe default SSL port causeserrors

N/AIf you check the IE proxy setting By pass proxy settingsand thencheckUseSSLtoaccesstheManagementPlatformon the Notification Server Configuration page, youencounter problems accessing the console. To access theconsole you have to use a short name and ‘localhost’ in theURL. You cannot access the console with a fully qualifieddomain name or IP in the URL.

Console does not launchwhenSymantecManagementPlatform is installed usingproxy settings which arebypassed

Table 1-3 Known Issues for Notification Server


N/AWhen upgrading from DMC 1.1 to DMC 2.0, if you connectto the old database on the Database Settings page in theconsole, you must restart the Notification Server servicesbefore you can execute any tasks. Symantec recommendsthat you connect to your restored 7.0 CMDB from theDatabase Configuration page in Symantec InstallationManager and not from the console.

Restart ofNotificationServerservices is required afterreconfiguring the databasefrom the console

13Symantec Management Platform 7.1 Release NotesKnown issues

Table 1-3 Known Issues for Notification Server (continued)


N/AIf you upgrade to DMC 2.0 and use a different SQL Servercollation with the new instance of the CMDB, thereconfiguration of the database fails. Youmust use the sameSQL Server collation with DMC 2.0 that you used with DMC1.1.

Database reconfigurationfailed due to collationconflict

N/ASymantec recommends that you limit new hierarchies totwo levels. A Notification Server that is a child should notalso be a parent.

Limit newhierarchies to onlytwo levels

N/AWith DMC 2.0, the context sensitive help does not work forInventory for Network Discovery

Context-sensitive help doesnot work for Inventory forNetwork Discovery

N/AWhen you attempt to save such a policy to a local folderwith full permissions, the following message is displayed:"You don’t have permission to save in this location...Wouldyou like to save in the My Documents folder instead?" Thisissue occurs only when Internet Explorer ESC (EnhancedSecurity Configuration) is turned on forAdministrators. Towork around this issue, turn off Internet Explorer ESC.

You cannot export a policy toa local folder with fullpermissions on a Windows2008r2 x64 server computerif you are using a consoleopened on localhost and if IEESC (Enhanced SecurityConfiguration) is turned onfor Administrators

N/AThis is the expected behavior if the name of a computerchanges at the same time as itsMACaddress or BIOSuniqueidentifier. In this scenario it cannot be identified as the samecomputer. This issue is much more common for virtualmachines because by default they use randomly generatedMACaddresses, which can change. Theworkaround for thisissue is to ensure that all VM computers havestatically-defined MAC addresses before you change themachine name/domain.

The Manage Computers listsometimes shows duplicateentries of the same computerafter SOI task

TECH142534The following information is displayed:

■ For filters containingComputers only: full set of columnsin grid

■ For filters containing both Computers and VirtualMachines: full set of columns in grid

■ For filters containing Virtual Machines only: Only theComputer Name column is shown

Filters do not display thesame information for virtualcomputers and computers


14

http://www.symantec.com/docs/tech142534



N/ASMP 7.1 has the ability to track certain resource deletionswithin a hierarchy. However, in the scenario where theNotification Servers in a hierarchy are mixed versions dueto a phased upgrade (i.e. the parent is 7.0 SP5 and the childis 7.1) the Resource Type definitions themselves arereplicated down during item replication. This causes theResource Type definitions at the child to be completelyoverridden with the 7.0 SP5 version of the resource typedefinitions. This overwrites any new elements that existedat the child. This issue affects the following resource types:Package, Software Package, and Software Command Line.It does not affect the new security resources as theseresource types do not exist on SMP 7.0 SP5. Additionally,this is an issue only in a hierarchy that is three or morelevels deep. If the hierarchy is only a parent and child, thechild does not need to track deletions to lower nodes as noneexist. Resource deletion tracking will not function forexisting resource types at child > sub-child levels until theparent Notification Server is upgraded to SMP 7.1 and hasreplicated the correct properties back down again.

Resource deletion trackingmaynot function properly ina Hierarchy

N/APackage Server does not support hosting packages withina non-default Web site. The default Web site must existwithin IIS for the Package Server to function normally.When no default Web site exists within IIS, the SymantecManagement Agent will crash even if 'Publish HTTP(s)codebases' option is disabled, and only 'Publish UNCcodebases' option is enabled within the Package Servicesettings. This issue will be resolved in a future release.

The Symantec ManagementAgent crasheswhenPackageServer is installed on acomputer where the defaultWeb site inside IIS has beenremoved

Tech144089If you attempt to add a domain user to a security role (menupath: Settings > Security > Roles, on the Membership tab)an error message is displayed on the Add User dialog box.This is because addingdomaingroupsdirectly into a securityrole is no longer a supported scenario. SymantecManagement Platform 7.1 only supports adding an SMProle or an SMP account into a role.

You cannot add domaingroups to SymantecManagement PlatformSecurity roles

N/AThese errormessages say that SMP is Unable to resolve thespecified owner of the item being imported. These errorsare non-critical and will result in the specific items beingownedby the service account of the destinationNotificationServer. This should not cause any issue and thus can beignored.

During some hierarchyoperations betweenNotification Servers wherethe child is 7.1 and theparent is pre-7.1, log errorsappear





N/ASymantec Management Platform does not supportupgrading across different collations. If you attempt to dothis, the database reconfiguration fails with an errormessage saying “Cannot resolve the collation conflict”. Thedatabase and database server collations must match.

Database upgrades can notbe performed acrossdifferent collations

N/AWhen you create a new automation policy, an error isgenerated and warning message are logged.However, afteryou create the policy you can load it, change settings, andsave it without the error recurring.This is a known issue forthis release.

Creating new AP createserror and a warning-levelmessage is logged

N/AIn some cases the Run once ASAP option is checked in thelegacy SWD task. This option supersedes any scheduledtimeormaintenancewindow.This is bydesign. If this optionis not deselected, the software delivery taskwill be executedas soon as a policy arrives on the client systems, overridingany schedule. When you are adding schedules to a LegacySoftware Delivery task, you should uncheck the Run OnceASAP option unless you intend the task to execute at thefirst opportunity.

Legacy 6.x SWD taskssometimes ignore schedulingand execute as soon as theyarrive on ULM 7.1 clientsystems

N/AAnyuser that has the permissionApply toResourceTargetscan create resource targets. Enabling or disabling theCreateResource Targets privilege (menu path: Settings > Security> Roles, then select the Privileges tab) has no effect. If youwant to prevent a user from creating resource targets youneed to remove the Apply to Resource Targets permissionfrom that user. Removing this permission means that theuser cannot open the resource selector dialog box.

TheCreateResourceTargetsprivilege is not currentlyutilized

TECH121988If the Symantec Management Console is set up to use anon-default port, when you try to add computers on theAgent Push page of the console by FQDN (non-localhost),an exception error occurs. The following error message isdisplayed: Data for the page you are currently viewing hasexpired. To resolve this issue, use the appropriate IP addressin the console URL instead of FQDN.

Attempts to access theSymantec ManagementConsole using the FQDN inthe console URL may failwith an error message


16




TECH44030Whenyouuninstall the SymantecManagementAgent froma Windows 7 computer, the Symantec Management Agenticon is not removed. TheSymantecManagementAgent iconremains listed in the Customize Icons list. To view theCustomize Icons list on a Windows 7 computer, do one ofthe following:

■ Right-click the Task Bar and then select Properties >Customize.

■ Click the Show hidden icons button on the toolbar.

Symantec ManagementAgent icon may not beremovedwhen theSymantecManagement Agent isuninstalled

TECH44034When you install the Symantec Management Agent, youcan choose to display the Symantec Management Agenticon in the system tray on the client computer. However,onWindows7computers, theSymantecManagementAgenticon does not appear in the system tray.

Symantec ManagementAgent icon may not appearin the system tray

N/AIf you replicate the Symantec Management Agent Settings- Targetedpolicy to childNotificationServers, the replicatedpolicy is editable on the children. This behavior is notcorrect. Replicated system policies should be read-only onchild Notification Servers, and you should not be able tomodify or delete them.Note that any changes that youmaketo this policy on a child Notification Server will beoverwrittenon thenext replication schedule,when the samepolicy is replicated again from the parent. You can accessthis policy on the Settings menu at Agents/Plug-ins >Targeted Agent Settings.

Replicated SymantecManagement Agent Settings- Targeted policy can beedited or deleted on childNotification Servers

TECH46209If you perform a push install of the SymantecManagementAgent to a computer thathas its timebehind theNotificationServer time (that is, the computer time is in the past relativeto theNotification Server time), the install status displayedin theSymantecManagementAgent Install page is incorrect.The install status for aWindows agent is shownas “StartingSymantecManagementAgent install service” and for aULMagent is shown as “Starting bootstrap.”This is an issuewiththe Symantec Management Agent Install page, and can beignored. The Symantec Management Agent is correctlyinstalled.

Incorrect agent installationstatus is shown when theclient time is behind theNotification Server time







TECH46224If you create a new resource type (left pane: Settings >Notification Server > Resource and Data Class Settings >Resource Types > Asset Types, then right-click and selectNew > Resource Type) and then in the Resource Type Editpage, click the Add Data Classes button, a script errormessage is displayed. Note that you must have CMDBSolution installed to access the New Resource Type page.This issue is related to your Internet Explorer browserconfiguration which is preventing the necessary ActiveXcontrol from loading. To enable the data class picker (theAexTreeCtrl ActiveX control) to load successfully, you needto enable Automatic prompting for ActiveX controls underthe Internet Explorer security settings.

Attempting to add DataClasses to a new ResourceType sometimes fails with ascript error

N/AWhenyoucreate a customdata class (via InventorySolution,in the Manage Custom Dataclass page in the InventorySolution Setting folder) and specify attribute names thatcontain non-Latin characters, the characters are initiallydisplayed correctly in the console page.However,whenyouclick Save Changes to save the new data class, the namesare replacedwith “??”. This issue affects only the languagesthat use non-Latin characters. Inventory Solution must beinstalled to access the custom data class functionality.

Non-Latin characters are notdisplayed correctly whenused in custom data classattribute names

TECH46377If youhave ahierarchy ofNotificationServers, some reportsdisplay summary data for each Notification Server and letyou drill down into the results (by clicking on theappropriate row in the results grid) for detailed data on aparticular Notification Server. However, if a NotificationServer is installed to a non-default Web site and port, itssummary data is displayed correctly in the summary reportbut any attempt to drill down to display the detailed datafails. A new browser window opens to display the reportresults, but it contains a Server Error message telling youthat the resource cannot be found.

Drill-down reports fail whenthe drill-down targets aremote Notification Serverthat uses a non-default port

TECH46641If you are running Notification Server in secure mode(https), youmust ensure that youhaveAdobeFlash installed.

Adobe Flash must beinstalled in order for theTopology Viewer control tofunction correctly


18






TECH41316Setting the sort direction of a field in a report query has noeffect unless the sort order is also specified. There iscurrently no check on this so, if you set a sort directionwithno sort order, the sort direction setting is reset to thedefault.

The Sort Direction of a Fieldin a report query is not savedunless a Sort Order is alsospecified

TECH41287To work around this issue, when you create a new securityrole, ensure that the new role name is different from anypreviously deleted security roles.

If a new security role has thesame name as a deleted role,the membership of thedeleted role is automaticallyapplied to the new role

N/AThe migration wizard automatically enables the exportersand importers of all solutions, whether or not the solutionsare installed inNotificationServer 6.x orNotificationServer7.1. You need to manually disable the solutions that youdon’t want to migrate. Failure to do this gives errors in thelog for the product readiness check.

The migration wizard doesnot detect which solutionsare installed

TECH41293In the Diagnostics tool, the Store browser table namecontains only the GUID of each item. The item name is notshown, which can make it difficult for you to check whichitems are being exported.

Thedata in theStore browsershows only the item GUIDs

TECH41295Notification Server 7.1 fails to create a database if thedatabase name includes any special characters (specialcharacters are any of the following: @#$%^&*()_! ). Ensurethat you specify a database name that does not include anyspecial characters.

The Database name cannotinclude special characters

TECH24075The only way to work around this issue is to eitherimplement WINS in the company infrastructure or disablethe UNC codebase generation.

There is currently no way togenerate the FQDN (FullyQualified Domain Name) forthe UNC codebases

TECH41330Package Replication Solution will not work on NotificationServer 7.1 because the package replication rules createdusing this solution on Notification Server 6.0 SP3 cannotbe upgraded to the Replication Rules equivalent that existsin Notification Server 7.1. Errors appear when you attemptto use the package replication importer found in themigration wizard .

PackageReplicationSolutionwill notwork onNotificationServer 7.1










TECH41310If an AD import rule is targeting an Organizational Unitwith a name longer than 255 characters, the import rulewill fail. This issue also occurs if the path of the targetedOU (that is, <parent OU>/ <child OU>/<sub child OU> etc.)is longer than 255 characters.

AD import fails if the nameof the targetedOrganizationalUnit is longerthan 255 characters

TECH41329The “Complete Resource Membership Update” schedulecurrently updates the membership of all filters, includingfilters that have the Update Membership option set toManual.

The “Complete ResourceMembership Update”schedule updates all filters

TECH41271The filters displayed in the Filter Summary page of theResource Manager are not accessible through the contextmenu. If you attempt to open the contextmenuonany filterin the grid, a “Data could not be loaded” error message isdisplayed.

Filters cannot be openedthrough the ResourceManager

TECH41482If you leave a filter page open for a long time (more than 20minutes)without any activity,whenyou try to resumework,the page fails with an error message “Object reference notset to an instance of an object.”

Filter pages timeout if leftinactive for more than 20minutes

TECH41484When the Symantec Management Agent is using a proxyserver, it fails to post events toNotificationServer correctly.This results in the client task agent not being registered.Note that communication involving configuration updates,basic inventory, downloading package snapshots, anddownloading packages is not affected.

If theSymantecManagementAgent is using aproxy server,the client task agentmay failto register

TECH41486The Symantec Management Agent push install fails.Currently, no error message is displayed in the SymantecManagement Console. An appropriate error message willbe added in a future release.

You cannot push install theSymantec ManagementAgent to a computer if youdo not have access to theAdmin share on thatcomputer

TECH41492The user name for the Symantec Management AgentConnectivity Credential cannot include any of the followingcharacters: ~!#$%^&(){}. If you attempt to specify an invaliduser name in the Symantec Agent Settings - Global policy,an errormessage is displayedwhenyou clickSaveChanges.You can access this policy on the Settings menu atAgents/Plug-ins > Global Settings.

The user name for theSymantec ManagementAgent ConnectivityCredential cannot includeany special characters


20










TECH41499If you open the Resource Manager while the SymantecManagement Console is open, and then refresh the Consolepage, the Console displays the Resource Manager portalpage. To restore the original page in the SymantecManagement Console, you need to select the appropriatemenu option.

In some circumstances theSymantec ManagementConsole displays theResource Manager portalpage

HOWTO9821Symantec Installation Manager (SIM) does not handle thisscenario either. Youneed to use the aexconfig /configureallcommand.

NSSetup.aspx is no longer asupported method forreconfiguring the databasefrom a corrupted console

TECH41957When using the Security Role Manager to assign itempermissions for a security role, the security inheritanceindicated by the ItemSelector (accessed by clicking the Editsymbol) may not be correct.

The Item Selector in theSecurity Role Manager doesnot correctly indicate brokensecurity inheritance

TECH41960When resource associations are replicated, only Add andUpdate changes aremade at the destination.Onlynew itemsand changes to existing items on the source NotificationServer are replicated to the destination. If a resourceassociation is deleted from the source, it is not removedfrom the destination.

Replication does not removeresource associations fromthe destination NotificationServer when they have beenremoved at the source

N/AWhen you save the results of a report as a static filter (SaveAs > Static Filter), you can select the items (rows in theresults grid) that you want to include. In the Save As dialogbox you specify the new filter name, and choose whether toinclude all of the report results or just the selected rows. Ifyou did not select any rows in the results grid, and thenselect the Save 0 selected rows option in the Save As dialogbox, there are no items to include in the new filter, andhence no filter is created. However, in this scenario, amessage is displayed stating that the new filter has beencreated successfully and giving the location at which thenew filter is stored. This message is incorrect and shouldbe ignored.

Incorrect message may bedisplayed when you savereport results as a staticfilter



http://www.symantec.com/docs/howto9821





TECH42219When you create a report using the Query Builder, you canspecify filter conditions in the Filter Expressions tab.However, when you later edit the report, some filterconditions may be dropped from the report query. Thishappens whether or not you opened the Filter Expressionstab: when you save the modified report, some conditionsmay no longer appear in the report query.

Report filter conditions aresometimes lostwhenyoueditthe report in the QueryBuilder

Table 1-4 Known Issues for Task Server


N/ASometimes, after you enable the appropriate Task ServerUpgrade policy, the policy runs and the client Task Serverappears to be upgraded. However, the ATRSHOST is notregistered and installed as a service and the Task Serverdoes not function. The workaround is to reinstall the TaskService. You can either run a manual repair of the MSI oruninstall and reinstall the Task Service on the SiteManagement page in the console.

ATRSHOST service is notalways created during TaskService upgrade

N/AWhen you upgrade and point to the old database on theDatabase Settings page, you cannot run any server tasksuntil you manually restart the Altiris, ATRSHOST, andCTDataload services. If you point to the old database on theDatabase Configuration page in Symantec InstallationManager during installation, you do not encounter thisissue.

Server tasks do not workwhen you reconfigure thedatabase from the DatabaseSettings page

N/AThe virtual directory of an upgraded remote Task Serverstill references C:\Program Files(x86) after SymantecManagementAgent is successfully upgraded to 64 bit. Untilthe virtual directories are manually re-directed to the newphysical location (C:\Program Files\Altiris\Altiris Agent)inside IIS, the upgraded Task Server does not work.

Upgraded remote TaskServer on 64-bit computerdoes not work until virtualdirectory is redirected

N/AThe replication of tasks and task instances within ahierarchyhas inconsistentbehaviorwith tasksand instancessometimes being replicated immediately when the task isrun, but other times waiting for the hierarchy schedules tobe run.

Inconsistent replication oftasks in a hierarchy


22


Table 1-4 Known Issues for Task Server (continued)


N/AAfter you upgrade to Symantec Management Platform 7.1,youmust upgrade your 7.0 Task Servers before you can usethem to run tasks.

Task Server unable to runtasks using 7.0 Task Serversafter you upgrade toSymantec ManagementPlatform 7.1

N/ASome of the tasks are not running on agentless clients aftermigration from DMC 1.x to DMC 2.0 (for example: BMCconfiguration task and LC Configuration task). To resolvethis issue, run the Update Task Service Assignments task.You can access this task on the Settings menu at Settings>Notification Server >Task Settings >Update Task ServiceAssignments. If the user doesn’t take any action tomanuallyrun the task, it runs by default daily at 2 AM.

Some of the Dell tasks arenot running after migration

N/AIn some cases the agent cannot register with task server,preventing users from running tasks on agent computers.For more information seehttp://support.microsoft.com/kb/960718.

System.Net.Sockets.SocketExceptionobserved while trying torestart the Task serverservices (Altiris Object Hostservice)

N/ATasks created in the 7.0 Task Servers are not supported in7.1 environment.

Unable to run the Taskscreated in 7.0 Task Serversafter Network Server isupgraded to 7.1

N/AThis issue applies only to some operating systems, such asWindow XP SP2 and Windows 2003. It does not apply topre-Vista versions such as Windows 7 or Windows VistaUltimate SP2

Initial use of ‘.\username’causes any script tasksspecified asMachinename\username) tofail with error ‘Unable toopen the file’ because ofProfile loading problem.

N/AIf you create a task and uncheck the option Allow othertasks to run while running this task, other tasks can stillrun.

Task Server Task runs eventhough "Allow other tasks torun while running this task"is checked.


http://support.microsoft.com/kb/960718

Table 1-4 Known Issues for Task Server (continued)


N/AA new Windows 2008 security feature called "Sessionisolation" most likely causes this error. .

A window is not displayedwhen cmd.exe is running inTask Manager as Systemeven though the ShowScriptin a Normal Window optionis selected

If you change the tickle port under Site Server settings, orin the config from the default of 50123, the change is notmade. The server will continue trying to open 50123 whichcauses 'unable to connect to tickle server' errors in the log.

Changing the tickle port inconfig and UI does not causethe tickle port to actuallychange.

TECH45090When you create a new database, you need to restart TaskServer (Altiris Object Host Service) from the Windowsservice console. This is required to make the previouslyscheduled PM import task run.

Task Server needs to berestarted after a newdatabase has been created

N/AWhen you migrate a job from 6.0 to 7.1, you also need tomigrate the associated tasks. The tasks that are included inthe job are not migrated automatically with the job.

Tasks that are containedwithin jobsmust bemigratedseparately

Table 1-5 Known Issues for Software Management Framework


N/AIf you used the Detailed Export in Software ManagementFramework to export a software resource, you cannot importthe software resource using ImportExportUtil.exe.

Cannot use the ImportExport Utility to import asoftware resource createdwith a Detailed Export

N/AWith a Legacy Software Delivery , if you select Logged onuser in the Run with rights drop-down list on the Advancetab, the policy fails on the client computer.

A Legacy Software Deliveryfailswhen run for a specifieduser

N/AThecommand linegenerator creates the followingcommandline for TARarchives: “tar xvfz <package>”. This commandwill not run on someUNIX andLinux computers that donotsupport the “z” option. For these computers, create thecommand line manually.

The auto generated TARextraction command linedoes notwork on someUNIXcomputers

N/AA Managed Software Delivery policy that targeted a userand was scheduled to run once runs each time the targeteduser logged on.

A Managed SoftwareDelivery policy that wasscheduled to run once runswhenever the user logs on


24


Table 1-5 Known Issues for Software Management Framework (continued)


N/AIf a Managed Software Delivery delivers two softwareresources and the second software resource is dependenton the first software resource, the applicability check forthe second resource fails because this check runs before thefirst software resource is installed.

Applicability check issueswith a Managed SoftwareDelivery policy

N/AWith aManagedSoftwareDelivery policy orQuickDeliverytask, applications with large installation paths fail toexecute.

Applications with largeinstallation paths fail toexecute

N/AA Managed Software Delivery policy is not activated on aclient computerwhen the target is user-based and thepolicyis scheduled to run At user login.

A Managed SoftwareDelivery policy is notactivated when user logs on

N/AChanges made to any of the settings found in the SoftwareCatalog and Software Library Settings folder are notreplicatedwhena “Replicate now”or “Replicate to”methodof replication is invoked.

Software Catalog andSoftware Library settings donot replicate with “Replicatenow” or “Replicate to”methods

Table 1-6 Known Issues for Data Connector


N/AFor the data connector rule pages in the SymantecManagement Console, there is a Run History section thatdisplays information in a table. If you click certain columnheading to sort the data by that column, you get an errorthat results in no data being displayed in the table. Thecolumns that cause this problem are Run Time, Log File,and Test Run. Note that not all rule types have thesecolumns.

Error sorting Run Historydata for adata connector rule

N/AWith a few data connector or CMDB rules created, if yourun the Connector Rules Health Check Task or CMDB RuleHealth Check Task, you will get an error if you click on acolumn to sort the data in the Output section of the Detailsdialog box of the task.

Error sorting test results ofa health check task test


Table 1-6 Known Issues for Data Connector (continued)


N/AIf you are configuring an OLEDB data source and theconfiguration is incomplete and you use the “Test datasource” feature before saving the page, the page crashesand displays an unhandled exception message. If you savethe page before using “Test data source,” the page properlyreports the incomplete configuration without crashing. Ifthe page crashes, changes made in the page might be lost.However, you can re-enter the configuration informationby reloading the page.

Unhandled exception occurswhen testing an incompleteOLEDB data source

N/AIf you create an organizational group import rule that cancreate newgroups and resources in the CMDB if they do notexist and you import data that requires the creation of newgroups, the number of groups created, as reported by a testrun of the rule is not correct and does not match the valuereported by the actual running of the rule, which is correct.

Status reported from a testrun of an organizational ruleis incorrect

N/AWhenyou configure aResource Import/ExportRule, if thereare already data class or association mappings configuredon the page and you change the data replication direction(import to export or export to import), the page will crashwith an unhandled exception error. You cannot change thedata replication direction for a configured and saved rule.You must create a new rule instead.

Unhandled exception “Failedto load viewstate” whenswitching data sourcetransfer direction

N/AIf you configure a rule with some data classes andsubsequently delete some of these data classes from theCMDB and run the Connector rules health check task, thetask reports that the rule is healthy. This is because whenthe health check task runs each rule as a test, missing dataclasses are ignored.

Connector ruleshealth checktask reports a healthy statuseven after data classes aredeleted

N/AAfter running "Connector rules Health Check Task," if youselect “Task InstanceDetails” to view the details of runningthe task and then click on a rule to open the ruleconfiguration page, you get the error "top.windowManageris null or not an object" and you will not be able to modifythe rule.

Script errors with connectorrules opened from"Connector rules healthcheck Task"

N/AStagger rule schedules to avoid contention andperformanceproblems.

Avoid running rulesconcurrently


26



N/AData connector v6.x could have CMDB Rules, ResourceExport Rules, and Bulk Resource Export Rules which use“Collections”. During the migration process, the“Collections”used by those rules are converted to “ResourceTargets”, and “Resource Targets” that are converted fromthe “Collections” should contain the same memberships asthe legacy “Collections”. In this release, the convertingprocess is not functioning properly; the “Resource targets”converted from the legacy “Collections” do not containmemberships. To work around, you need to recreate the“Resource Targets” for those rules by using the legacy“Collections” to make them work properly.

Collection migration issue




N/AThe help and user guide documentation is missing theinformation for virtual data classes. Virtual data classes letyou integrate 3rd party system data with the SymantecManagement Platform CMDB without the need to importthe data into the CMDB.

External data that is mapped to a virtual data class appearsas a normal resource data class in the CMDB. Virtual dataclasses provide seamless integration with the SymantecManagement Platform reporting features; you can createresource reports based on virtual data classes using thereport builder just like reportswith any other resource dataclasses. The report queries the data directly from theexternal data source at the time you run the report.

The following provides some brief information on usingvirtual data classes.More informationwill bemade availablein anupdated versionof theDataConnector documentation.

The virtual data class feature uses theMicrosoft SQLServerLinked Server functionality to connect to 3rd party systemdata. Linked servers to these systems must initially be setup in SQL Server before you can use virtual data classes.

To create an editable virtual data class do the following:

■ .In the Symantec Management Console, on the Settingsmenu, click All Settings.

■ In the left pane, click Settings > Notification Server >Resources and Data Class Settings > Data Classes.

■ Right-click Data Class, and click New > Virtual DataClass.

■ In the right pane, configure the virtual data class.

■ Click Save changes.

Virtual data classdocumentation missing


28

Table 1-7 Known Issues for Credential Manager, Connection Profiles, and thePluggable Protocols Architecture


TECH140507Youmust enableWCFActivation to allow forusingprotocolsother than HTTPS.

2008R2 x64 - Impossible toperform monitoring, usingWMI,HTTP,SNMPprotocols,because it fails to resolvecredentials from CredentialManager with Innerexception.

TECH142631You must ensure that if you choose a custom Web site , youremove multiple identities.

WMI, WSMAN, and othermonitoring plug-ins becomeunavailable if multipleweb-service identities areused.

N/AThe discovery of devices is slow and not consistent whenVMware protocol is enabled.

The discovery of devices isslow when VMware protocolis enabled

Table 1-8 Known Issues for UNIX/Linux/Mac


N/AIn some cases the 'Run once ASAP' option is checked in thelegacy SWD task. This option supersedes any scheduledtimeormaintenancewindow.This is bydesign. If this optionis not deselected, the software delivery taskwill be executedas soon as a policy arrives on the client systems, overridingany schedule. When you are adding schedules to a LegacySoftware Delivery task, you should uncheck the 'Run OnceASAP' option unless you intend the task to execute at thefirst opportunity.

Legacy 6.x SWD taskssometimes ignore schedulingand execute as soon as theyarrive on ULM 7.1 clientsystems

N/ATo avoid this issue, you should disable or change proxysettings from the Symantec Management Console only. Ifyou loose connectivity because of this issue, reinstall theSymantecManagementAgent byperformingaPUSH installfrom theSymantecManagementConsole.Whenyoudo this,specify to not save the current configuration by uncheckingthe "Keep the currentSymantecManagementAgent settingsif possible" option. TheAgentwill be successfully reinstalledwithout using proxy settings, and connectivity will berestored.

If you attempt to disableproxy usage by running"aex-configure" from theclient, proxy settings are notreset and you may loseconnectivity for the client




Table 1-8 Known Issues for UNIX/Linux/Mac (continued)


N/AIn some cases the uninstall process does not functioncorrectly and the following files are not removed:

■ /var/db/receipts/com.altiris.AltirisAgent.bom

■ /var/db/receipts/com.altiris.AltirisAgent.plist

These files cause the pull install to fail.

To work around this issue, do one of the following:

■ Perform a PUSH install without saving the currentsettings.

■ Before performing the PULL install, execute thefollowing command line on Mac 10.6 client: 'pkgutil--forget com.altiris.AltirisAgent'

PULL install may fail onMacOS X 10.6 systems ifSymantec ManagementAgent was previouslyuninstalled from clientmachine

N/AWhen you run a UNIX/Linux/Mac Service Control Task onHP-UX systems, the service status is reported as Unknown.This issue is because the service control scripts on HP-UXusually donot include the option to return the service status.If you want to verify the service status, you should checkwhether the process is running.

UNIX/Linux/Mac ServiceControl Task cannot returnthe service status on HP-UXsystems

TECH46454The AIX inittab service does not support any of the actionsthat are available in theServiceActiondrop-down list.WhenAIX inittab services is checked, the Service Action fieldshould be grayed out andnot selectable. At present this fieldis (incorrectly) functional in the Symantec ManagementConsole.To avoid errors in your Service Control task, youneed to set the Service Action field to No action. Thisprevents any attempt to execute Start, Stop, Restart, or GetStatus commands for AIX inittab services. Note thatcurrently theNo action setting is incorrectly processed andcannot be used for task creation. As a result, all ServiceControl tasks that are created for the inittab service controlsystem will be reported as failed, with the error message“Missing or invalid service action” displayed. This isregardless of whether or not the specified process/servicewas successfully modified.

If you select a service actionfor AIX inittab services in aUNIX/Linux/Mac ServiceControl task, the task failswith an error message


30




N/ADMG packages (also known as Disk Images or .dmg files)that have a simple structure are supported. A simplestructure is where the installation file (.app, .mpkg, or .pkg)is in the root directory of the DMG package. Examples ofthese packages include the following:

■ Firefox 3.5.2 .dmg

■ ExpressCard_Update.dmg

■ iTunes8.2.1.dmg

■ Messenger702.dmg

■ QuickTime762Tiger.dmg

■ QuickTime762Leopard.dmg

■ VMware-Fusion-2.0.2-147997.dmg

■ vpnclient-darwin-4.9.01.0080-universal-k9.dmg

However, complex DMG packages where the installationfile is not in the root directory are not supported. Examplesof these packages include Adobe Photoshop CS4 and AdobeCreative Suite 4.

Support for DMG packagesis limited

TECH44831If you attempt to push install the Symantec ManagementAgent for UNIX, Linux, and Mac to a computer system thathas a secondary shell configured in .profile, the push installmay fail due to a timeout error. The secondary shell is anyshell other than the configured shell in /etc/passwd for userroot in /etc/profile, .profile, or .bash_profile.

Push-installing theSymantecManagement Agent forUNIX, Linux, and Mac to acomputer that has thesecondary shell configuredin .profile may fail withtimeout errors

TECH46206Whenyoumanually create a software package that contains.rte files, and use RTE Command Line Builder to generatethe appropriate installation command line (the commandto execute the installation file on client systems), thepackage installationmay fail. This is because the generatedcommand line contains the %SIFNAME% token, which isadded as a part of the command and is NOT replaced on theclient system with the software installation file name. Thisissue results in a failing installation of the software on clientsystems. For manually created packages containing .rtefiles, you need to replace the %SIFNAME% token with theappropriate proper file name.

RTE Command Line Buildergenerates an incorrect installcommand






TECH44677In some scenarios, the heavy load on the system results inthe update of the upgrade job status being delayed, whichin turn causes a re-launch of the upgrade code. The conflictbetween two instances of the upgrade corrupts the upgradeprocess and forces the reinstall. The installation log(aex-nsclt-install.log) on a client computer displays thefollowing entry:WARNING! You have two or more versionsof Symantec Management Agent for UNIX, Linux and Macalready installed. This means that the current installationis corrupted and may not be upgraded. Forcing reinstall.

Upgrading the SymantecManagement Agent forUNIX, Linux, and Mac fromSP2 or SP2 HF2 to SP3 usingthe Upgrade policy issometimes corrupted andreplaced with a forcedreinstall

TECH42006This is due to a defect in the dynamic linker on the HP-UX11.00 computer. You need to apply the appropriate patch.

Installing the SymantecManagement Agent forUNIX, Linux, and Mac on anHP-UX 11.00 computerproduces a “Memory fault(coredump)” error

TECH42029The simplest way to work around this issue is to upgradeto Symantec Management Agent 7.1 using the push installmethod. Alternatively, you can disable IPv6 on the targetcomputer.

You cannot use an upgradepolicy to upgrade theSymantec ManagementAgent for UNIX and Linux toversion 7.1 from version6.2.1378 on HP-UXcomputerswith IPv6 enabled

N/AAny configuration policies thatwere created by copying thedefault UNIX configuration policy (“All UNIX/LinuxComputers (excluding ‘PackageServers’)”) are notmigrated.However, any new policies that you created are migratedproperly.

Some configuration policiesare not migrated fromNotification Server 6.0 toSymantec ManagementPlatform 7.1

TECH47689This is a system limitation caused byMacOS10.6OSdesignand can't be overridden. This limitation may affectcommands that are executed by SWD/SMF tasks, or Scripttasks.

Daemons running on Mac10.6 in root bootstrapcontext cannot executecommands using the nohuputility


32







TECH47696This issue applies to both Windows and ULM upgrade anduninstallationpolicies. In theSymantecManagementAgentfor Windows or UNIX/Linux/Mac - Upgrade policy page,you can defer the action by checking Warn before runningand then set the appropriate candefer forXXminutes value.However, if you specify a value higher than 32767, the pagecrasheswhen you click Save Changes to save the policy. Thepage crashes with a Server Error message: Value was toolarge for an Int16.Note that this field also incorrectly letsyou specify and successfully save a negative value.

The Symantec ManagementAgent Upgrade andUninstallation policy pagescrash if you attempt to defertheupgradeoruninstallationformore than32767minutes

TECH137859Managedandquick softwaredeliveries that contain a tar.bz2or .bz2 related command line may fail on some HP-UXsystems.

Managed and quick softwaredeliveries may fail on someHP-UX systems

Fixed issuesThe fixed issues are separated into the following components:





■ Data ConnectorSee Table 1-13 on page 45.

■ Network DiscoverySee Table 1-14 on page 45.

■ Credential manager, Connection Profiles, and the Pluggable ProtocolsArchitectureSee Table 1-15 on page 46.

33Symantec Management Platform 7.1 Release NotesFixed issues



Table 1-9 Fixed Issues for Symantec Installation Manager


N/ASQL server information was not updated in the Help.SQL server information isnow updated in the Help

N/AAny suite could not be installed on 64 bit OS if at least oneproduct has 32-bit package . This issue is fixed.

Offline installationswerenotsupported.

N/AWhen you run installation of Symantec ManagementPlatform, and choose SQL Express DB Server, a dialog boxappearswith themessage, You should install onSQLServer2005.

Now the dialog box text is changed to You should installNotification Server on Microsoft SQL Server 2005 orMicrosoft SQL Server 2008 for best performance.

Add recommendation toinstall SQL Server 2008 inthe dialog box

N/ASIM now lets you install the migration wizard and buildmigration packages before Notification Server is installed.

To create migration packages and install the migrationwizard before Notification Server is installed, do thefollowing:

■ Install SIM version 7.1 or greater on the new computer.

■ Run SIM

■ Choose Install option components on the InstalledProducts view.

■ Check the Install Migration Wizard components formigrating Notification Server six data.

■ Follow the rest of the prompts.

This process provides you amigrationpackage that you cantake to the old computer and get the KMS data to put on thenew computer before installing the Notification Server. IfNotification Server is already installed or if the PL does notcontain the correctmigration product, SIMmay indicate toyou that nothing is available to install after step 3.

Need to export KMS databefore installing 7.1

N/AThe check boxUse SSL to access theManagement Platformwas not enabled in the SSL settings of IIS Web Site. Theissue is fixed.

The check box Use SSL toaccess the ManagementPlatform is not enabled inthe SSL settings of IIS WebSite

Symantec Management Platform 7.1 Release NotesFixed issues

34

Table 1-9 Fixed Issues for Symantec Installation Manager (continued)


N/AInstall Readiness check panel now showsWindows 2008R2as the recommended operating system.

Install Readiness checkpanelshows Windows 2003 as therecommended operatingsystem

N/AThe hyperlink for Microsoft IIS in Install Readiness checkpanel opens an irrelevant page. This issue is fixed.

The hyperlink for MicrosoftIIS in Install Readiness checkpanel opens an irrelevantpage

N/ASIM Installation failed due to SID errors. This issue is fixed.Unable to install SIM withSMP on OS with localizedAdministrators localgroup

Table 1-10 Fixed Issues for Notification Server


N/AThis issue has been fixed with proper CSV escaping of thecolumn names and the column values when the CSV file isgenerated. Previously the Save As Spreadsheet option didnot save correctly when any data values included commas.The resulting spreadsheet contained jumbled column data.

Saving a report as aspreadsheet now functionsproperlywhencolumnvaluesinclude commas

N/AThis is by design. The Add Licenses link was removed forsecurity reasons.

Whenyouperformanon-boxupgrade from SMP 6.x, theAdd Licenses link is missing

N/APreviously, when you saved a report that containednon-English characters as a spreadsheet, HTML, or XMLfile, the non-English characters did not display correctly.This issue has been resolved by correcting the UTF8encoding so that CSV files are loaded properly.

Reports that containnon-English characters nowdisplay correctly when theyare saved in spreadsheet,HTML, or XML format

N/APreviously if you attempted to specify a raw SQL query asthe data source for an automation policy, the querywas notsaved correctly. This issue also affected some SQL queriesin filters and reports: in some cases the changes that youmade when editing a query were not saved.

You can now specify a rawSQLquery as the data sourcein an automation policy

N/APreviously the list was restricted to only 10 items and thescroll bars appeared when more items were available. Thelist did not resize correctly and part of the page was leftempty.

The list of SymantecManagement Agent Policiesin the Targeted AgentSettings page now displayscorrectly


Table 1-10 Fixed Issues for Notification Server (continued)


N/APreviously the Notification Server Web root was theNotification Server installation directory, which was apotential security issue.

The Notification ServerWebis now installed as asubdirectory of theNotification Serverinstallation folder

N/APreviously, if you had a multi-NIC environment and someNICs did not have DNS entries, Basic Inventory wouldincorrectly identify them as having DNS.

NICs without DNS in amulti-NIC environment arenowcorrectly reportedasnothaving DNS entries

N/APreviously only the computer name was stored in thepackage server as part of the codebase cache, so you wereunable to use the FQDN. This issue did not affect HTTPcodebase: the FQDN was fully recorded in package servers.

The path names for UNCcodebase in package serversare now fully qualified

N/APreviously, in some cases where a user belonged to manysecurity roles and only one of those roles had access to areport, the user may have been unable to access the report.Multiple security role IDs were passed to the report: if thelist of IDs exceeded a particular threshold, some IDs werelost. Linked to Known Issue KB #49971.

Users that belong tomultiplesecurity roles cannowaccessreports reliably

N/APreviously, packages that had file dates newer than thosein the snapshot were not downloaded. This scenariosometimeoccurredwhen files inside a package on apackageserver were modified by an out of scope operation such asa virus scanner updating them. Those files were given a filedate that was greater than what was expected in thesnapshot for that package.

Packages are nowdownloaded to packageservers if the timestampdoesnot match the currentsnapshot

N/APreviously, on some operating systems, the Agent versionwas not reliably reported to Basic Inventory, so did notappear in the Resource Summary page in the ResourceManager.

The Symantec ManagementAgent now correctly showsthe Agent version

N/APreviously, the NSE priority was ignored when an NSE wasdelivered to Notification Server, causing an unacceptabledelay in the delivery of critical alerts.

NSE priority is nowrecognized and handledcorrectly


36



N/ASite services such as package server and task server requirecertain conditions to be met to work correctly on IIS7.

The following conditions must be met:

■ IIS6 compatibility modules are installed (to allowcreating virtual directories)

■ The default Web site works in the "Classic .NETApplication Pool" mode

The warning message alerts you to the additionalconfiguration requirements and gives you the option toproceed or cancel the site service rollout process.

A warning is displayed whenyou attempt to assign anysite service to an IIS7computer

N/APreviously, if you attempted to search on a custom SQLreport and did not specify any search text, the Edit reportpage appeared. Only the user-created reportswere affected.The predefined reports were not affected.

The Search feature nowoperates correctly on customSQL reports

N/APreviously, in some cases the GUID synchronization at thechildNotificationServer failed and the resource flip-floppedbetween two GUIDs. When the resource flip-flopped, bothGUIDs were blacklisted, including the currently active one.The resultwas that the affected agent cannot communicatewith the Notification Server. Attempt was made to create anewresource for the blacklisted itembutwas given the sameGUID again.

Resources are now mergedcorrectly when duplicateGUIDs are created inHierarchy replication

N/APreviously, the default values displayed in the descriptionfields for the following items did not match the actualdefault values:

■ MaxConCurrentConfigRequests

■ ReplicationProcessorActivityInterval

■ ReplicationMaxJobThreadCount

■ ReplicationMaxEventRows

In the NS Configurator, thedefault values in thedescription fields are nowcorrect

N/APreviously, when you created a report based on a raw SQLquery and named one of the columns as a number, none ofthe data in that column was displayed.

The reporting grid nowsupports the column namesthat are integers

N/APreviously partitioned resources can be deleted by anyuser.Therewas no check on the user’s security permissions. Thispresented both an administration threat, as resources canbe lost from the console, and a security threat, as anunregistered user can attack all partitioned resources.

Partitioned resources cannow be deleted only by userswho have appropriatesecurity roles




N/AFor Replication rules with System attributes set, specificcontrols instead of whole sections are disabled. This alsoallows links to the resources anddata classes to be clickablebut prevents modifications. For Relocation rules, theVerification section is hidden. Previously all sections ofhierarchy ruleswere editable, even for the predefined rulesthat had System attributes set.

Hierarchy Rules now haveread-only sections whereappropriate

N/APreviously the new languages that were introduced in IE8werenot supportedandwerenot defaultingback to standardEN-US. No text strings were displayed in the console. Onlythe icons were visible.

This issue affected the following languages:

■ English (India) [en-IN]

■ English (Malaysia) [en-MY]

■ English (Singapore) [en-SG]

New languages that wereintroduced in IE8 are nowcorrectly displayed in theSymantec ManagementConsole

N/APreviously, any files that were added to a package were notdownloaded to anagent if the agenthadalreadydownloadedthe package previously. Once a package had beendownloaded to an agent, the agent was not getting anyupdates to that package properlywhen the packagewas runat subsequent times.

The Symantec ManagementAgent now reliablydownloads anynew files thathave beenadded to apackagebefore running it

N/APreviously, when you performed a Managed SoftwareDelivery rollout, the Domain Controller received a largenumber of Kerberos TGT (ticket granting ticket) requests.This sometimes caused the DC to stop responding to otherclients on the network that were trying to map networkdrives, which also requires a TGT from the KDC.

Performance enhancement:NotificationServerno longersends multiple Kerberosticket requests to theDomainController

N/AThe Item state size is now controlled by theCoreSettings.config setting ItemStateMaxSizeInKB. Thedefault is 65536 (64MB). You cannot create or save an itemthat exceeds the maximum size. Previously the itemframework allowed the Item State size to grow in anunconstrainedmanner. These large items could get too largeto be loaded and could cause other issues.

Item state sizes are nowconfigurable and can belimited to a reasonable size

N/APreviously, in some scenarios the Summary page failed toopen for a newly discovered resource.

The Resource ExplorerSummaryPagesnowoperatecorrectly


38



N/AIf you usemultiple replication schedules, your SQLdisk sizewill grow rapidly. The replication schedules are generallyspaced out during the day so it does not make sense toperform the clean up only at one point during the day.Performing this clean up more often can save SQL diskspace. It alsomeans lesswork in regular chunks, rather thanone large delete during the Daily schedule.

The Item to delete schedulehas had its shared schedulechanged from Daily toQuarter Hourly

N/APreviouslyHierarchy replication did not scale tomore thanabout 200,000 resources. Large amounts of SQL disk spacewas used and in some cases replication job items werecreated that could not be loaded, causing OutOfMemoryexceptions. Those exceptions had the knock-on effect ofleaving behind the data containers and manifests whichnever get cleaned up.

Hierarchy performance hasbeen improved

N/APreviously the LicensingRefresh schedule checked securitypermissions for every action that is taken. When this wasfirst implemented this was not an issue because thesesecurity checks would take place against a cache on theNotification Server. However with Windows 2003 ActiveDirectory the local security cache is only checked as abackup. This means that the AD is being flooded withsecurity checks every time that a new security context isrequested. In the case of the Licensing Refresh policy thisis happening more then a 1000 times a minute. This iscausing issues by overloading the AD.

The Licensing Refreshschedule has been modifiedto improve performance

N/APreviously, the Symantec Management Agent sometimescrashed when it attempted to log a message that includeda % sign. This issue was caused by the % sign not beingescaped correctly.

Messages that contain %signs are now loggedcorrectly

N/APreviously theAgentPush status grid failed to load correctlywhen two push events were present for the same computerwith the same _eventTime. This issue effectively disabledthe entire push functionality.

The Agent Push page nowoperates reliably

TECH140499Windows 2003domains allowmultiple groups (security anddistribution type) to have the same name within differentparts of the AD tree. Previously, if these "duplicate" groupswere present, AD connector would fail to import them.

Multiple Active Directorysecurity and distributiongroups with the same nameare now supported


http://www.symantec.com/docs/TECH140499



N/APreviously changes to replicated packages could take 24hours to trickle down. During this time the packagewas notavailable to site servers and therefore did not make it toendpoints.Whenpackage folder content has beenmodified,once the parent has replicated the package, the child’sNotification Server’s package serverwill reflect the changesthe next time the agent updates its configuration.

Package changes in ahierarchy environment arenow reflected at childpackage servers in areasonable time

N/APreviouslyyouwereunable to install SymantecManagementPlatform on non-English operating systems. This was dueto a localization issue in the MSI file.

Symantec ManagementPlatform installs correctly oninternational operatingsystems (Spanish, French,German, etc.)

N/AThe previous method of importing groups was veryinefficient, as the LDAP query simply requested objects ofa specific type and then filtered the results. If ActiveDirectory contained a large number of groups, somequeriescausedOut ofMemory exceptions. The LDAPquerymethodhas been modified to explicitly request the groups that theimport rule is configured for. This results in speedimprovements, lower CPU and memory requirements andimproved scalability.

LDAP queries are nowfiltered to explicitly requestthe groups that the importrule is configured for

N/APreviously only the Complete Update schedule checked forcircular references in filters. Circular references in filterswere not detected or handled by theDeltaUpdate schedule.This sometimes caused delta updates to consume memoryuntil the service failed.

The Delta Update schedulenow detects circularreferences in filters andcancels the update ifnecessary

N/APreviously, in some cases when you attempted to addcomputers to thegrid, amessage "DataCouldNotBeLoaded"appeared.

The Symantec ManagementAgent Push Install page nowlets you load computersreliably

N/AIf this error occurs, incorrect or incomplete informationabout agents or packages may be stored. This is a knownissue for this release. N/A

"Unspecified DataloaderException encountered forevent data class AeX SWDPackage" error message islogged to NS log duringplug-ins rollout


40



TECH41981The Inv_Audit table continued to grow as resources wereadded. To remove old and unwanted data from this table,youhad to follow themanual process described in the linkedknowledgebase article.

The Symantec ManagementConsole did not provide away to purge old AuditInventory information fromthe database

TECH41488The PurgingMaintenance page only allowed the purging oflegacy Notification Server 6.x saved reports. It did notprovide the ability to purge Notification Server 7.0 datasnapshots.

The Purging Maintenancepage did not let you purgedata fromNotificationServer7.0 reports

N/AIf no absolute path was allocated, the execution ofcommands under the agent's environment would fail.

When the ULM Agent wasupgraded from Unix Agent6.2 to ULM Agent 7.0 SP4 onAIX systems, the $PATHvariablehadnodefinedvalue(paths) in the agent'senvironment

Table 1-11 Fixed Issues for Task Server


N/AThe CTA library code caused this issue. Now, the true agentSDK call is used to write the script file as it honors allplatforms correctly.

Command Scripts thatcontainedCyrillic charactersnow work

N/AA script that had%, caused an access violation in the agentand an error message was displayed. The problem wascaused by CTA.

CTA logging messages with%signsnowdonot cause theagent to crash

N/APreviously, a script task that included reserved characterswould not execute on the client machine and an errormessage was displayed. The issue is fixed.

Now you can schedule scripttasks that include reservedcharacters

N/AIf you create a hierarchy between two Notification Servers,then after complete replication, the advanced options forall tasks were editable.

NowAdvancedoptions for alltasks cannot be edited on thechild Notification Serverafter complete replication

N/AThis was a generic problem. The issue is fixed.Job or Task Status Detailreport now return results




Table 1-12 Fixed Issues for Software Management Framework


NAThe scroll bar in the Software FinderWebpart did notwork.Scroll bar in the SoftwareFinderWebpart didnotwork

NAThe necessary security rights were not given to theSymantec Software Librarian user to view the My Portalpage. Now, the user can access the My Portal page.

When a Symantec SoftwareLibrarian user first loggedinto the SymantecManagement Console theycould not access the MyPortal page

NAWhen the Software Catalog Data provider was configured,some of the new software types were not created.

Some software types werenot created for the SoftwareCatalog Data Provider

NAWith a Managed Software Delivery policy, if you selectedthe schedulingoption,At computer startup, thepolicywouldfail to run when the computer restarted.

A Managed SoftwareDelivery policy that wasscheduled to run when acomputer starts up could fail

NAWhen a user initiated Managed Software Delivery policyran, the policywould go into an endless loop if the start datefor the policy was in the past and if the policy was stuckwithin a reboot defer.When the policywent into an endlessloop, it consumed large amounts of CPU.

A user initiated ManagedSoftware Delivery policycould consume largeamounts of CPU

NAIf aManagedSoftwareDeliverypolicydownloadedapackagethat did not have a specified command line, the package didnot download successfully.

With a Managed SoftwareDelivery policy, you couldnot download a packagewithout specifying acommand line for thepackage

N/AIf two Managed Software Delivery policies were scheduledto run at the same time and both policies had detectionrules, the detection rules for both policies ran at the sametime. This caused issues if the detection rule of one policywas checking to see if the software of the other policy wasinstalled.

Detection rules of ManagedSoftware Delivery Policiesthat had the same schedulerun at the same time

N/AWhenadding a command line inMSICommandLineBuilderfor a package that was added using "Access package froma directory on the Notification Server," the Add button foradding a transform was disabled

Add button for transformswas disabled in MSICommand Line Builderwindow


42

Table 1-12 Fixed Issues for Software Management Framework (continued)


N/AWhen the "Runwith rights" optionwithin a Legacy softwaredelivery policywas set to "Specified user" the passwordwasencrypted incorrectly, and this caused the execution of theprogram to fail .

A legacy software deliveryfailed if you selected the“Run with rights” option

N/AWithaManagedSoftwareDeliverypolicy, itwasnot possibleto change the default maximum execution time of 30minutes. You set the execution time in theAdvancedoptionsdialog box on theResults-based actions tab in theTerminateafter option.

Unable to change the defaulttime that a ManagedSoftware Delivery policy ranbefore it terminated

N/AIf you were tracking down the memory leak and disabledthe OLE Automation string cache by setting the systemvariable OANOCACHE=1 and then restarted the computer,your computer crashed.

Invalid cast in SMFAgentcaused crash when OLEAutomation string cachingwas disabled

N/AWhen you tried to import a very large package into theSoftware Catalog, the import could or take a very long time.

Issues with importing verylarge packages into theSoftware Catalog

N/AIf you created a Managed Software Delivery policy that letthe user defer the installation and the user deferred theinstallation, logged off, and logged on after the deferralexpired, the defer dialog was not shown to the user whenthey logged back in and the installation did not run.

A deferred ManagedSoftware Deliveryinstallation failed if thedeferral expired while theuser was logged off

N/AIn the Software Catalog, you can create multiple detectionand applicability rules with the same name, which createdconfusion.A check is nowperformed to prevent the creationof rules with the same name.

Multiple detection andapplicability rules couldhavethe same name

N/AIf a software resource had dependencies and you createdan Installed Software Filter from the right-click menu ofthe software resource, the filter included the dependencies.

An Installed Software Filtercreated from a softwareresource included theresource’s dependencies

N/AIf a Managed Software Delivery policy included a serverreboot task, the job item that followed the reboot task triedto execute immediately instead of waiting until after thereboot.

A Managed SoftwareDelivery policy did notresume after a reboot task


Table 1-12 Fixed Issues for Software Management Framework (continued)


N/AIn the Quick Delivery Task dialog box, the softwareresources that were listed in the software resourcedrop-downwere not scoped. Consequently, a user can selectsoftware resources when they did not have permission toview those resources.

Users could select softwareresources form the QuickDeliveryTaskdialog box thatthey did not have permissionto view

N/AIf you tried to edit a software package on a French consoleeverything was grayed out and you could not change thesettings.

Unable to modify a softwarepackage using a Frenchconsole

N/AIn the Software Catalog, when the name, version, orcompany of a software resource was changed, the resourcekey of the software resource was not updated with thesenew key values.

A software resource was notupdated when key valueswere changed

N/AWith a Managed Software Delivery, when the contents of asoftware package changed, the Software ManagementFramework agent did not download the new files before asubsequent execution of the policy.

Changes to software packagedid not get downloaded bythe Software ManagementFramework agent

N/AWhen a software package is exported, any files that werewithin the root directory of the package were being createdas software installation files, which is not correct and insome cases caused the export to throw an exception.

Export of a software packagecan sometimes fail

N/AIf you used fr-FR as the IE language and you edited asoftware resource on the File Inventory tab in the SoftwareCatalog, an error occurred when you tried to add a file.

Unable to add File Inventorywhen using fr-FR as IELanguage

N/AWhen different threads accessed the software cache at thesame time, the SoftwareCache.xml was reset to a size of 0which caused SoftwareDiscoverynot to be able to complete.

Under certain conditions,Software Discovery was notable to complete

N/AIf you created a software resource that had a package andassigned it to aManaged Software Delivery policy and thencreated a new package for the same softwareresource,disassociated the original package from theManaged Software Delivery policy and assigned the newpackage to the policy, the old package could not be deleted.It still appeared as associated to the policy. Even if youremoved the software resource from the policy you couldnot delete the package.

Unable to delete a packagefrom a Managed SoftwareDelivery policy


44

Table 1-13 Fixed Issues for Data Connector


N/APreviously, you were not able to create an OLEDB or anODBC Data Source in x64. An error message was displayedwhen you tried to create anOLEDB or anODBCData Sourcein x64.

You have to download a component fromhttp://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=c06b8369-60dd-4b64-a44b-84b371ede16d for the datasources to work.

Now you can create anOLEDB or an ODBC DataSource in x64

N/AThis is by design. You cannot add columns to a virtual dataclass because it is a representation of an external datasource. If you want to add a column, then go to thedatasource and either add a column to the base table orcreate a view.

Cannot add columns to aVirtual Data Class

Table 1-14 Fixed Issues for Network Discovery


N/AVM created in the ESX server was not getting discovered.This issue is fixed.

VMcreated in the ESX serveris now getting discovered

N/ADiscovery and Inventory cannot correctly handle thecommand sets that had multiple commands. This issue isfixed and now the command-set option can be set for bothDiscovery and Inventory in the common Discovery engine.

Discoveryand Inventorynowcorrectly handle thecommand sets that havemultiple commands

N/AThe VMware MIBs used previously did not find relevantinformation. This issue is fixed.

Network Discovery nowsupports newVMwareMIBs.

N/AThe dataclass ‘Device Identification’ used varchars insteadof nvarchars. This created issues with the connector as theconnector handles nvarchars for import. This issue is fixed.

Dataclass ‘DeviceIdentification’ now usesnvarchars

N/AEmbedded VMware ESX servers were not classified as theVirtual servers and the virtual machines associated withthe VMware ESX servers were not discovered. This issue isfixed.

Embedded ESX servers arenow classified as VirtualServers

N/AIncorrect session attribute now caused hyper discovery tofail. This issue is fixed.

Incorrect session attributenow does not cause hyperdiscovery to fail


http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=c06b8369-60dd-4b64-a44b-84b371ede16d



Table 1-15 Fixed Issues for Credential Manager, Connection Profiles, and thePluggable Protocols Architecture


N/AYouwereunable to use event receiver formore than severalhours. The Memory leaks resulted in the system notresponding in about five hours.

Memory leak inAltiris EventReceiver service does nothappen now

N/AWSMAN plugin took 25 to 30 seconds for enumeratinginstances of certain classes.

The WSMAN plugin used totake long time forEnumerateInstances command

N/AThe Notification Server error appeared for passwordcontaining some special characters. This issue is fixed.

Certain characters that arevalid as AMT passwordcharacterswerenot acceptedin theAltiris AMTcredentialdialog

N/AIf you installed Symantec platform into custom installationpath such as drive letter:\somecustomfolder\altiris stillcertain files were found in the default C:\ProgramFiles\Altiris\AltirisAgent\Agents\PluggableProtocolsAgentfolder. Ideally, all the files and folders should install intocustom installation path.

PPAused to install some filesinto default location whenSymantec platform isinstalled into custom path

N/ABy default, Windows generates a certificate with .cerextension, while Connection Profile dialog did not acceptsuch extensions. This issue is fixed.

Now you can specify validcertificate file to WS-MANprotocol in ConnectionProfile settings

N/AAfter discovering 500 devices,memory leakswere observedin Windows 2008. After few days the CPU would stopresponding.

MemoryLeakswereobservedin Windows 2008 afterdiscovering 500 devices

N/AEqualLogic device inventory was not displayed in theHardware summary page. The inventory task runssuccessfully but tables were not displayed in the HardwareSummary page. Now,the Hardware Summary page of anEqualLogic device displays the inventory of the device.

EqualLogic inventory taskruns successfully butinventory was not displayed


46

Table 1-15 Fixed Issues for Credential Manager, Connection Profiles, and thePluggable Protocols Architecture (continued)


N/AEven if the VM was turned off , the Operational Status ofthe VM was shown as turned on . The Enabled Stateappeared blank.

The column Operational Status is renamed as VM PowerState. The column Enabled State is removed.

A columnGuestOSState is added.However, this info is onlyobtained through the SNMP and VMware protocols. WhenWS-MAN or WMI is used, this column is always et tounknown.

The Hardware Summarypage for theVMstatus of theHyper V server displayedincorrect status

Other things to knowThe other things to know about this release are separated into the followingcomponents





■ Network DiscoverySee Table 1-20 on page 50.

Table 1-16 Things to know about Symantec Installation Manager


TECH41187If the logged in user is not a member of the LocalAdministrator group, the data migration wizard does notwork.

User requirements formigratingNotificationServerdata to SymantecManagement Platform 7.1

TECH41182You cannot install Symantec Installation Manager if thecomputer does not have a Temp folder.

Installation requirements forinstalling SymantecInstallation Manager

47Symantec Management Platform 7.1 Release NotesOther things to know



Table 1-16 Things to know about Symantec Installation Manager (continued)


TECH41306The ability tomodify an installation is not supported in thecurrent release of Symantec Installation Manager.

Modify button on theInstalled Products page isdisabled

TECH41584You cannot reduce the number of licenses that are appliedto a product.

Number of applied licensescannot be reduced

TECH41323Symantec Installation Manager does not support licensefiles that contain multiple certificates.

Symantec InstallationManager rejects some 6.xlicenses

N/AThemaximumlengthof thename for theNotificationServercomputer is 64 characters.

Maximum computer namelength for the NotificationServer

N/AOn the Product Licensing page, the "In use" count candisplay a number that is smaller than the actual number oflicenses that are in use for a product if the client computersare in sleep mode or turned off.

Inaccurate "In use" count onthe Product Licensing page

Table 1-17 Things to know about Notification Server


N/ATypical error: Pop-up dialog box is blank when selectingEdit/New icon on "Update summary data" dialog. This isjust one example of errors that canoccur if Internet Explorersettings prevent the ActiveX control from running. ForNotification Server to run properly, you must be able toinstall (or beprompted to install) ActiveXobjects. Otherwise,you may see errors with jobs and task, among otherfunctions. (This is by design.)

You must configure webcontrols to support ActiveX

N/AWhen you modify a report query using the Query Builderin Basic mode, be careful when you change the firstcondition of a Filter expression. When you change the firstcondition, the operator drop-down list reloads its contents.Youmight need to re-select the correct operator in order tosuccessfully resolve the report query. Note that suchunresolvable filter expressions are shown as “Blue” in theQuery Builder.

Take care when using theQuery Builder in Basic mode

Symantec Management Platform 7.1 Release NotesOther things to know

48




Table 1-17 Things to know about Notification Server (continued)


TECH133272Whenyoupush-install theULMagentontoHP-UXmachinesthat have CSH set as boot-shell for root, links to the agent'sbinaries location (commands) are created.However, on somesystems such as HP-UX ia64 11.23-11.31, thesebinaries/commands cannot be executed in user sessions.The absolute path needs to be specified.

ULM agent cannot beinstalled onto HP-UX if CSHis set as root shell

N/ABecause Symantec Management Platform 7.1 does notsupport Windows 2000 clients, these clients are notupgraded when you upgrade to Symantec ManagementPlatform 7.1.

Symantec ManagementPlatform 7.1 does notsupport Windows 2000clients

Table 1-18 Things to know about Task Server


N/AFor Notification Server to run properly, you must be ableto install (or be prompted to install) ActiveX objects. If yourIE settings prevent the ActiveX control from running, youwill see errors when working with jobs and tasks. This is bydesign.

Pop-up dialog box is blankwhenselectingEdit/New iconon "Update summary data"dialog

Table 1-19 Things to know about Software Management Framework


DOC1717A list of terminology used in Software ManagementFramework.

Terminology

N/ABy default, the Software Discovery policy is scheduled torun two times per week on all the computers that containthe Software Management Framework agent.

Software Discovery policyenabled by default

HOWTO9940If you do not have JRE 1.6 or higher installed, you get anerrormessagewhen you try to import or add a package intothe Software Management Framework.

Java runtime required forimporting packages into theSoftware ManagementFramework

TECH127274If you access the Symantec Management Console remotelyfrom a computer that is not part of the Notification Serveradmin domain, some of the functionality in the SoftwareCatalog does not work.

Accessing the SymantecManagement Consoleremotely can cause someSoftware Catalogfunctionality not to work

49Symantec Management Platform 7.1 Release NotesOther things to know


http://www.symantec.com/docs/DOC1717



Table 1-19 Things to know about Software Management Framework (continued)


TECH46168When you replicate a single resource, any dependentresources are not automatically replicated. If you wantdependent resources to be replicated, you must replicatethem as well. For example, if you replicate a ManagedSoftwareDelivery policy that has a detection rule, youmustalso replicate the detection rule or the policy will fail.

Replicating a single resourcedoes not replicate dependentresources

N/AWhenyou schedule aManagedSoftwareDelivery, thePoweron if necessary option only powers on a client computerwhen the policy is initially enabled and saved. It does notwake up a client computer after the policy is on the clientcomputer.

Poweringona computerwithaManagedSoftwareDelivery

N/AIf you create a new schedule for a data provider task thatincludes a description and you schedule the task to run inthe future, the task is not identified by the description untilthe task runs.

When a data provider task isidentified by its description

N/AIf you deliver an EXE with a Quick Delivery task and youselect Hidden in the Display window drop-down list on theRun Options tab of the Advanced options, the task may notget executed in the hidden mode. Whether the installationis hidden depends on whether the EXE obeys the request tohide the installation.

A Quick Delivery task doesnot execute in hidden modefor an EXE

N/ATopreserve symbolic links, donot unzip or repackage thesepackages on a non-UNIX computer.

Symbolic links are lost ifTAR/TAR.GZ/TAR/Zpackages are unzipped orrepackaged on a Windowscomputer

Table 1-20 Things to know about Network Discovery


HOWTO9348Connection Profiles to configure the protocols that are usedto communicate with network devices.

Using Connection ProfilesNetworkDiscovery tasks use

HOWTO9709Importing .MIB files onSymantec ManagementPlatform 7.0

DOC1740Symantec ManagementPlatform Security Privileges

Symantec Management Platform 7.1 Release NotesOther things to know

50




http://www.symantec.com/docs/doc1740

Table 1-20 Things to know about Network Discovery (continued)


N/AIf you schedule a Network Discovery task to run on arecurring basis, you won’t be able to stop that task unlessyou either delete the task or cancel the schedule by deletingthe next scheduled occurrence of it in Manage > Jobs andTasks.

Scheduling a NetworkDiscovery task

Documentation that is installedTable 1-21 The product installation includes the following documentation:

LocationDescriptionDocument

The Documentation Library,which is available in theSymantec ManagementConsole on the Help menu.

Context-sensitive help isavailable for most screens inthe Symantec ManagementConsole.

You can opencontext-sensitive help in thefollowing ways:

■ TheF1keywhen the pageis active.

■ The Context command,which is available in theSymantec ManagementConsole on the Helpmenu.

Informationabouthowtousethe Symantec ManagementPlatform

This information is availablein HTML help format and asa PDF.

Symantec ManagementPlatform Help

51Symantec Management Platform 7.1 Release NotesDocumentation that is installed

Other informationTable 1-22 For more information, you can use the following resources:

LocationDescriptionDocument

Product support pageThe Supported Products page list allsupported products with links toadditional documentation.

Product support documents

Endpoint Management Migration pageThis site contains articles aboutupgradingto Symantec Management Platform 7.1and aboutmigrating your data during theupgrade.

Upgrade and migrationdocuments

SymWISE Support pageThis site contains articles, incidents, andissues about this product.

SymWISE SupportKnowledgebase

Symantec Connect pageAn online magazine that contains bestpractices, tips, tricks, and articles forusers of this product.

Symantec Connect (formerlythe Altiris Juice)

Symantec Management Platform 7.1 Release NotesOther information

52

http://www.symantec.com/business/support/all_products.jsp


http://www.symantec.com/business/theme.jsp?themeid=support-knowledgebase

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

Symantec Management Platform 7.1 Release...

Documents

Transcript of Symantec Management Platform 7.1 Release...