Software Management Framework 7.0 SP5 Release Notes

Article:DOC2068  |  Created: 2010-02-10  |  Updated: 2010-11-09  |  Article URL http://www.symantec.com/docs/DOC2068
Article Type
Documentation


Description



Build number 7.0.8641

AltirisTM Software Management Framework from Symantec provides a structure in which to store, access, and identify software in a common manner. It enhances software manageability by promoting integration between functions such as software delivery and inventory. Software Management Framework integrates closely with Software Management Solution.

This component is part of Symantec Management Platform 7.0 SP5. For release notes, see knowledgebase article 49812.

This document contains the following topics:

Back to top

New features

The new features of this release are as follows:

Settings section on the Software Discovery page

The Software Discovery page now has a Settings section. In this section, you can configure the policy to send all software resources or only software resources that changed since the last time software inventory was collected. The option to send only software resources that changed is selected by default. You would select the option to send all of the software resources if some of the data that was previously sent to the server was lost. If the management of a client computer moves from one Notification Server to another, sometimes the new server does not have all of the software resource data. 

New install command lines for MSIs

When you import an MSI into the Software Catalog, the following two additional command lines are automatically generated for the software package:

  • msiexec.exe /i "install file" /qn ALLUSERS=2 (This is the new default install command line.)
  • msiexec.exe /i "install file" ALLUSERS=2

Back to top

Installation and upgrade

Prerequisites

See the Symantec Management Platform 7.0 SP5 requirements. See knowledgebase article 49812.

New installation

Software Management Framework is included in the Symantec Management Platform installation.

You can install this product by using the Symantec Installation Manager. You can download the installation files directly to your server or you can create an offline installation package.

For more information, see the Symantec Management Platform Installation Guide and knowledgebase article 45732.

Upgrade

This section is not applicable to Software Management Framework 7.0 SP5.

Back to top

Fixed Issues in This Release

The following are previous issues that were fixed in this release. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID
Symantec Software Librarian security role did not let users edit software resources

The Symantec Software Librarian security role was setup incorrectly. Users who were assigned to this security role could not edit software related resources.

   1922934
Symantec Software Librarian security role did not properly scope the viewing of software resources

When a Symantec Software Librarian security role was assigned an organizational view, a user assigned to that security role could view software resources outside of the scope of that organizational view.

   1983436
Software Discovery consumed excessive amounts of the system CPU

When you ran the Software Discovery policy, it could consume 45-60% of the system CPU on a managed computer. Software Discovery's CPU usage has been reduced.

   1919445
Memory leak with Software Discovery

Software Discovery caused a memory link. This memory leak has been reduced.

   1980012
An application's install date and display version didn't appear on the Software Summary page

When some applications were installed on a Vista or Windows 7 client computer, the install date and display version of the application were not displayed on the Software Summary page in Resource Manager.

   1938942

Hierarchy and Replication

   
Clients of a child Notification Server consumed the licenses of the parent Notification

When a Quick Delivery or Package Delivery task was scheduled within an hierarchy environment, Software Management Framework requested a license for each computer resource. However, the parent Notification Server should only request a license for the resources that it owns and not the child resources that are owned by child Notification Servers. This issue has been fixed so that the parent Notification Server only requests a license if it owns the targeted resource.

   1949802
Software delivery failed when the client was pointed to a child Notification Server

If the package of a software resource is assigned to a package server automatically with manual prestaging, the delivery of the software resource failed if the client is pointed to a child Notification Server. This problem occurred with a Quick Delivery task and a Package Delivery task. Retry logic has been added so that the task does not fail if the package is downloaded within 30 minutes.

 48542  1794571
Deletion of a software resources applicability or detection rules was not replicated

If you removed a software resource association such as a detection rule or an applicability rule on a parent server, the resource association was not removed from a child server when the software resource was replicated.

   2034871
The product name of a software resource did not always replicate to a child Notification Server

If you ran a complete hierarchy replication, the product name of some software resources did not replicate to the child Notification Server.

   1932526
Replication of software resources created duplicate software resources

When a software resource was replicated down or up the hierarchy, if the resource key of the software resource matched that of an existing software resource, the two software resources were not merged but a duplicate software resource was created. The duplicate software resources are now automatically merged.

   2004732
Unable to assign targets to a Quick Delivery task from parent Notification Server

If you created a Quick Delivery task on a parent Notification Server, you could not assign a target to the task if the target was managed by a child Notification Server. You received an erroneous message that the target did not have the Software Management Solution Agent plug-in. After the Quick Delivery task replicated to the child Notification Server, you could then assign the target from the child Notification Server.

   1952313
Duplicate entries of a software resource appeared in the Software Catalog of a child Notification Server

If you replicated a software resource to a child Notification Server and then changed the Software Product field of the software resource on the parent Notification Server, a duplicate software resource was created on the child Notification Server when you replicated the software resource again.

   2032408
Managed Software Delivery and Quick Delivery    
A Managed Software Delivery policy that was set to run manually ran automatically instead

With a Managed Software Delivery policy, if you checked the User must turn on from Altiris Agent option, the policy ran immediately. It should not have run until the user clicked the task in the agent user interface.

   2025324
A Managed Software Delivery policy failed when delivering a software resource with a Windows Version rule expression

A Managed Software Delivery policy failed if it delivered a software resource with an associated detection or applicability rule that used a Windows Version rule expression.

   1959962
A Managed Software Delivery policy that started in a blockout continually tried to restart before the blockout period ended

If a Managed Software Delivery policy was executed during a blockout period, the policy did not wait until the blockout period was over before trying to execute the policy. Instead, it repeatedly tried to execute the policy during the blockout period.

   1904054
Package and task properties of a Managed Software Delivery policy disappeared after restarting the Symantec Management Agent

If you restarted the Symantec Management Agent on a client computer and then double-clicked a Managed Delivery policy on the Software Delivery tab of the Symantec Management Agent window, all of the package and task properties disappeared except the Download History.

   2008613
Changes made to the success or failure codes of a software resource after a Managed Software Delivery policy runs were not applied to the policy

If you delivered a software resource with a Managed Software Delivery policy and then modified the success or failure codes in the command line of the software resource, any changes you made to the success or failure codes in the command line were not applied to the Managed Software Delivery policy.

   2062460
Description missing on the dialog box where a user could defer the execution of a Managed Software Delivery policy

If you upgraded from Software Delivery 6x to Software Management Solution 7.0 and you created a Managed Software Delivery policy that let the user defer the execution of the policy, the description was missing on the dialog box where the user deferred the execution of the policy.

   2044579
The Software Management Framework Agent hung when evaluating a Managed Software Delivery policy

If a Managed Software Delivery policy had an if/else condition that did not have the necessary input parameters, the Software Management Framework Agent went into an infinite loop.

   2018795
A deferred Managed Software Delivery installation failed if the deferral expired while the user was logged off 

If you created a Managed Software Delivery policy that let the user defer the installation and the user deferred the installation, logged off, and logged on after the deferral expired, the defer dialog was not shown to the user when they logged back in and the installation did not run.

   2055179
A deferred Managed Software Delivery policy failed if the user deferred the policy and restarted the computer before the deferred time expired

If you created a Managed Software Delivery policy that let the user defer the installation of the software, the policy failed if the user deferred the policy and then restarted their computer before the deferred time expired. 

   2029242
A deferred Managed Software Delivery installation failed when deferred for more than 30 minutes

If you created a Managed Software Delivery policy that let the user defer the installation for more then 30 minutes, the installation failed if the user deferred the installation for more than 30 minutes.

   2082034
An item in a Managed Software Delivery policy executed before the post action reboot of the previous item was finished

Under certain situations it was possible, due to timing issues, for a subsequent item within a Managed Software Delivery policy to execute before the post action reboot task of the previous item finished.

   2080240
The installation date of an MSI installed with a Managed Software Delivery policy was not always reliable

The InstallDate in the INV_AddRemoveProgram table in the Symantec_CMDB database is now always reliable for an MSI that is installed with a Managed Software Delivery policy.

   2012498
A Managed Software Delivery policy or a Quick Delivery task failed when user was specified

With UAC enabled on a client computer, a Managed Software Delivery policy or a Quick Delivery task failed to execute if you specified the user.

   1904760
Performance problems in an environment with a very large number of resources

In an environment that had a very large number of resources in the CMDB, Internet Explorer could hang when you tried to create a new Managed Software Delivery policy or a new Quick Delivery task.

   1943166
An unused Quick Delivery package was not deleted after the specified amount of time

For a Quick Delivery, if you selected the advanced option to delete the package from the client computer if it was unused for 1 day, the package was actually deleted after 1 hour.

   1919073
"Test advert" appeared as the value for "Task policy name" on the Details tab of the Package and task properties dialog box

In the Symantec Management Agent dialog box on a managed computer, if you clicked on a Managed Software Delivery policy, the Package and task properties dialog box appeared. On this dialog box, "Test Advert" appeared as the value for "Task policy name".

   2036452
A Managed Software Delivery policy caused high hard disk utilization on client computers running various languages of the Windows operating system

With a Managed Software Delivery policy that had remediation set to At next maintenance window, high hard disk utilization occured on client computers running various languages of the Windows operating system.

   2064469
Software Catalog and Software Library    
Microsoft was listed twice as a company you can select for a software resource

Two different company resources were created for "Microsoft." One was created by Resource Management and one was created by Software Management Framework. Software Management Framework now uses the company resource that is created by Resource Management.

   1934465
An imported CMD file had a non-working command line

If you created a software resource in the Software Catalog by importing a CMD file, the command line for the package did not include a c/ switch and consequently did not work.

   2032412
Incomplete command line for imported VSA file

If you selected a subfolder when you imported a VSA file into the Software Catalog, the Import command line did not include the subfolder in the path to the VSA file. Because the subfolder was not included in the path, the command line failed when the package was delivered.

   1945601
Unable to add expressions to a rule in the Software Catalog

In the Software Catalog, on the Rules tab, if you created a new rule and deleted the "And" operator from the root node, you could not add expressions to the rule. You can no longer delete the "And" operator from the root node.

   1878007
Unable to specify a version range when creating a rule

In the Software Catalog, on the Rules tab, if you selected [ ] when you defined the version for a rule that you were creating, the field to enter the lower version was not displayed. For example, when you created a Standard Rule and selected Registry Key to File Version, you could select [ ] in the drop-down list to define the version, but the lower version field did not appear.

   1957706
A detection rule that contained a Software File Expression smart rule did not work

If you created a detection rule for a software resource that included a Software File Expression smart rule, the detection rule did not work correctly when you delivered the software resource with a Managed Software Delivery policy.

   1959664
A version number in a Static File Expression smart rule could not contain a period

In the Software Catalog, on the Rules tab of a software resource, you could not create a Static File Expression smart rule that contained a version number that contained a period.

   1953792
An alphabetical value in a software version number caused error with Inventory Solution

The MinorVersion column of the Inv_Software_Component table could not accept alphanumeric characters and this caused errors with Inventory Solution. Changes were made to suppress the minor or major version value if it contained a string. Instead, an error message displays in the log with a severity level of 8.

 51608  1949694
Adding an inventory file to a software resource created duplicate file resources

In the Software Catalog, on the Inventory tab, when you added a file that was already in the database to a software resource, duplicate file resources were created.

   1946243
Unable to change the value in the second drop-down list of an Advanced Search in the Software Catalog

In the Software Catalog, when you clicked the magnifying glass to perform an Advanced Search and selected values in the first two drop-down lists, you could then not select a different value from the second drop-down list. To change the value of the second drop-down list, you first had to delete the current value.

   1780829
Unable to import an XML file created with a Detailed Export

If you used Detailed Export to export a software resource that had at least one association with a package resource and Package & command-line information was checked on the Detailed Export dialog box, the resulting XML file would have the "Software Installation file" resource before the package resource within the file. You could then not import this XML file.

   2054312
Packages with multiple instances of the same file were not imported correctly into the Software Library

If a software package contained the same file multiple times and the file was over 5 MB, only the initial occurrence of the file was uploaded to the Software Library. The software package was then invalid and could not be installed correctly.

   2091868
A Detailed Export of a software resource threw an exception

A Detailed Export of a software resource threw an exception when the software resource had dependent software and the dependencies were included in the export.

 48015  1656234
Could not import a software resource created with a Detailed Export

If you used the Detailed Export in Software Management Framework to export a software resource, you could not import the software resource into the Software Catalog on another Notification Server. 

   2038354

Back to top

Things to Know

The following are things to know about in this release. If additional information about an issue is available, click the Article ID link.

Things to know Article ID Internal ID
Terminology

A list of terminology used in Software Management Framework.

 44629  
Software Discovery policy enabled by default

By default, the Software Discovery policy is scheduled to run two times per week on all the computers that contain the Software Management Framework agent.

   
Java runtime required for importing packages into the Software Management Framework

If you do not have JRE 1.6 or higher installed, you get an error message when you try to import or add a package into the Software Management Framework.

 46264  
Accessing the Symantec Management Console remotely can cause some Software Catalog functionality not to work

If you access the Symantec Management Console remotely from a computer that is not part of the Notification Server admin domain, some of the functionality in the Software Catalog does not work.

 52231  1945150

 1947529

Replicating a single resource does not replicate dependent resources

When you replicate a single resource, any dependent resources are not automatically replicated. If you want dependent resources to be replicated, you must replicate them as well. For example, if you replicate a Managed Software Delivery policy that has a detection rule, you must also replicate the detection rule or the policy will fail.

 49794  1827458
Powering on a computer with a Managed Software Delivery

When you schedule a Managed Software Delivery, the Power on if necessary option only powers on a client computer when the policy is initially enabled and saved. It does not wake up a client computer after the policy is on the client computer.

   1736308
When a data provider task is identified by its description

If you create a new schedule for a data provider task that includes a description and you schedule the task to run in the future, the task is not identified by the description until the task runs. 

   1649801
A Quick Delivery task does not execute in hidden mode for an EXE

If you deliver an EXE with a Quick Delivery task and you select Hidden in the Display window drop-down list on the Run Options tab of the Advanced options, the task may not get executed in the hidden mode. Whether the installation is hidden depends on whether the EXE obeys the request to hide the installation.

   1845141
Symbolic links are lost if TAR/TAR.GZ/TAR/Z packages are unzipped or repackaged on a Windows computer

To preserve symbolic links, do not unzip or repackage these packages on a non-UNIX computer.

   

Back to top

Known Issues in This Release

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

Issue Article ID Internal ID
Scroll bar in the Software Finder Web part does not work

The scroll bar in the Software Finder Web part does not work. You can display the Software Finder Web part on the My Portal page, which you can access from the Home menu.

   2089267
When a Symantec Software Librarian user first logs into the Symantec Management Console they cannot access the My Portal page

The necessary security rights are not being given to the Symantec Software Librarian user to view the My Portal page. However, the Symantec Software Librarian can perform any of the Software Librarian roles.

   2131364
Cannot use the Import Export Utility to import a software resource created with a Detailed Export

If you used the Detailed Export in Software Management Framework to export a software resource, you cannot import the software resource using ImportExportUtil.exe.

   2038353
Some software types are not created for the Software Catalog Data Provider

When the Software Catalog Data provider is configured, some of the new software types are not created. 

   2123320
A Legacy Software delivery fails when run for a specified user

With a Legacy Software delivery, if you select Logged on user in the Run with rights drop-down list on the Advance tab, the policy fails on the client computer.

   
The auto generated TAR extraction command line does not work on some UNIX computers

The command line generator creates the following command line for TAR archives: “tar xvfz <package>”. This command will not run on some UNIX and Linux computers that do not support the “z” option. For these computers, create the command line manually.

   
Managed Software Delivery policy and Quick Delivery task    
A Managed Software Delivery policy that is scheduled to run when a computer starts up can fail

With a Managed Software Delivery policy, if you select the scheduling option At computer startup, the policy could fail to run when the computer restarts.

  47861  1650409

 1799792

A Managed Software Delivery policy that was scheduled to run once runs whenever the user logs on

A Managed Software Delivery policy that targeted a user and was scheduled to run once runs each time the targeted user logged on.

   1650312
Applicability check issues with a Managed Software Delivery policy

If a Managed Software Delivery delivers two software resources and the second software resource is dependent on the first software resource, the applicability check for the second resource fails because this check runs before the first software resource is installed.

   1806464
A user initiated Managed Software Delivery policy can consume large amounts of CPU

When a user initiated Managed Software Delivery policy runs, it is possible for the policy to go into an endless loop if the start date for the policy is in the past and if the policy is stuck within a reboot defer. When the policy goes into an endless loop, it consumes large amounts of CPU.

   2051322
Applications with large installation paths fail to execute

With a Managed Software Delivery policy or Quick Delivery task, applications with large installation paths fail to execute.

 53761  2057292
A Managed Software Delivery policy is not activated when user logs on

A Managed Software Delivery policy is not activated on a client computer when the target is user-based and the policy is scheduled to run At user login.

   1944601
With a Managed Software Delivery policy, you cannot download a package without specifying a command line for the package

If a Managed Software Delivery policy downloads a package that does not have a specified command line, the package does not get downloaded successfully.

   1676572
Detection rules of Managed Software Delivery Policies that have the same schedule run at the same time

If two Managed Software Delivery policies are scheduled to run at the same time and both policies have detection rules, the detection rules for both policies run at the same time. This can cause issues if the detection rule of one policy is checking to see if the software of the other policy is installed.

   1962368
Unable to change the default time that a Managed Software Delivery policy runs before it terminates

With a Managed Software Delivery policy, it was not possible to change the default maximum execution time of 30 minutes. You set the execution time in the Advanced options dialog box on the Results-based actions tab in the Terminate after option.

    2030059
A Managed Software Delivery policy does not resume after a reboot task

If a Managed Software Delivery policy includes a task server reboot task, the job item that follows the reboot task tries to execute immediately instead of waiting until after the reboot.

   2080235
A Managed Software Delivery policy that was scheduled to run once runs whenever the user logs on

A Managed Software Delivery policy that targeted a user and was scheduled to run once runs each time the targeted user logged on.

   1650312
Users can select software resources form the Quick Delivery Task dialog box that they do not have permission to view

In the Quick Delivery Task dialog box, the software resources that are listed in the software resource dropdown are not scoped. Consequently, a user can select software resources when they do not have permission to view those resources. You can access Quickly Delivery Task dialog box from the Actions menu when you click Software > Software Delivery Task.

   2082665
Package Delivery task    
Package Delivery does not work with the Run from the server if bandwidth is above option

If you create a Package Delivery task and you check the Run from the server if bandwidth is above option on the Download Options tab of the Advanced options, the task fails.

   1873215
Unable to associate a command line with a Package Delivery task

When you create a Package Delivery task, if you create a command line and uncheck the Command line requires a package option, you end up with a command line that cannot be associated with a Package Delivery package. To avoid this issue, don't uncheck Command line requires a package or edit the package's command line before creating the Package Delivery task.

   2041169 
 Software Catalog and Software Library    
Issues with importing very large packages into the Software Catalog

When you try to import a very large packages into the Software Catalog, the import can fail or take a very long time.

   2052090
Export of a software package can sometimes fail

When a software package is exported any files that were within the root directory of the package are being created as software installation files, which is not correct and in some cases causes the export to throw an exception.

   2131618
An Installed Software Filter created from a software resource includes the resource's dependencies

If a software resource has dependencies and you create an Installed Software Filter from the right-click menu of the software resource, the filter includes the dependencies.

   2075950
Unable to modify a software package using a French console

If you try to edit a software package on a French console everything is grayed out and you cannot change the settings.

   2106978
Multiple detection and applicability rules could have the same name

In the Software Catalog, you could create multiple detection and applicability rules with the same name, which created confusion. A check is now performed to prevent the creation of rules with the same name.

   2070836
Software Catalog and Software Library settings don't replicate with 'Replicate now' or 'Replicate to' methods

Changes made to any of the settings found in the Software Catalog and Software Library Settings folder are not replicated when a 'Replicate now' or 'Replicate to' method of replication is invoked.

   2034899
A software resource is not updated when key values are changed

In the Software Catalog, when the name, version, or company of a software resource is changed, the resource key of the software resource is not updated with these new key values.

   2107363
Cannot edit a Patch Management Linux rule in the Software Catalog

Normally, you can edit Patch Management rules in the Software Catalog by double-clicking the software resource, clicking the Rules tab, and then clicking the rule to edit. However, when you try to edit a Linux-based rule for Patch Management, an exception error appears.

   1698682

Back to top


Legacy ID



51388


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


Terms of use for this information are found in Legal Notices