Software Management Framework 7.0 SP3 Release Notes

Article:DOC1866  |  Created: 2009-07-29  |  Updated: 2009-07-29  |  Article URL http://www.symantec.com/docs/DOC1866
Article Type
Documentation



Description



Build number 7.0.7270

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 SP3. For release notes, see knowledgebase article 49356.

This document contains the following topics:

Back to top

New features

The new features of this release are as follows:

Wise Connector support

Wise Connector lets you import software packages and their associated metadata from a Wise Software Repository into Software Management Framework. When you import a software package, it is imported into the Software Library. When you import the metadata associated with a package, a software resource is created in the Software Catalog if it does not already exist. After you import software packages with their metadata from the Wise Software Repository, those responsible for distributing software can easily deliver and manage them.

You can import data manually or on a schedule. For more control over the resources that are imported, import them manually. You can also configure precedence settings for Wise Connector. Precedence settings determine whether Wise Connector can update the metadata of a software resource in the Software Catalog. Precedence settings also determine whether other data providers can update the Wise Connector data.

You install Wise Connector on the same computer where Symantec Management Platform is installed. You install it with Symantec Installation Manager. You must have Wise Package Studio 8.0 or later to import packages with Wise Connector. After you install Wise Connector, you must add a Wise Package Studio data provider before you can import data from a Wise Software Repository.

For more information, see the Wise Connector 7.0 Release Notes.

For information about the Software Data Provider Status report and the Data Providers Web part see the Software Management Framework 7.0 SP2 Release Notes or the Symantec Management Platform Help. 

Version column in the Software Catalog

In the Software Catalog, the Type column has been replaced with a Version column. A tool tip on the software icon now displays the software resource type.

Managed Rollout policy

Solutions that integrate with Symantec Management Platform 7.0 SP3 or later can use a Managed Rollout policy to roll out their plug-ins to client computers. If a solution uses a Managed Rollout policy, you can then take advantage of its features when you roll out plug-ins to client computers. If a solution does not use a Managed Rollout policy, then there is no change in how you deliver its plug-ins.

The benefits of using a Managed Rollout policy are as follows:

  • One policy with multiple functions

A Managed Rollout policy lets you install a specific version of a plug-in and uninstall it. When a service pack or update of the plug-in is released, it automatically becomes available for use in the same policy. If the policy supersedes previous installations, those installations are listed in the policy so that the policy can be used to upgrade them.

  • Compliance check

A Managed Rollout policy performs a compliance check that checks for the presence of the plug-in on the client computer. The check returns True if the plug-in is installed and False if the plug-in is not installed. A Managed Rollout policy is considered compliant if the plug-in is in the correct state on the client computer. Normally, the correct state is to have the plug-in installed. However, if the policy uninstalls the plug-in, then the correct state is to not have the plug-in installed. If the plug-in is not in the correct state, the compliance check fails and remediation occurs.

  • Remediation

Remediation brings the policy’s software that is out of compliance on the client computer back into compliance. The nature of the remediation depends on the command-line action that the Managed Rollout policy performs.  If the policy installs the plug-in, then remediation reinstalls it. If the policy uninstalls the plug-in, then remediation uninstalls it.

  • Recurring schedules

Compliance and remediation in a Managed Rollout policy are especially effective when you schedule the policy to run on a recurring basis. The recurring policy ensures that the policy’s software remains in the correct state on the client computers. For example, a policy that installs a plug-in checks on a recurring basis that the plug-in is installed. If it discovers that the plug-in is not installed, it reinstalls it.

Back to top

Installation and upgrade

Prerequisites

See the Symantec Management Platform 7.0 SP3 requirements. See knowledgebase article 49356.

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 offline installation packages.

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

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 denied access to Symantec Management Console

If a user is only a member of the Symantec Software Librarian security role, they were then denied access to the Symantec Management Console.

   1666026
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
Server error when creating software filters

When creating an Installed Software Filter, a server error occurred.

 47952  1736940
Data not sent to new server

If the Software Management Framework agent was redirected to a new server, it did not resend data to that server.

   1739182
Software releases only appeared in the Software Catalog in English

In the Software Catalog, for filtered views (for example, Deliverable Software > Releases) or any custom Software Catalog view, the software resources only appeared in English.

   1720725
Software Discovery    
Software Discovery unable to discover software in a deactivated virtual software layer

The Software Discovery policy could not discover software that was in a deactivated virtual software layer.

   
Software Discovery sometimes opened Windows Installer dialog boxes on the client computers

When Software Discovery iterated through the components of a product and the source for the component was not available, a Windows Installer source dialog opened for user input for the source location.

 48856  1829041
Software Discovery did not report every program found in Windows Add/Remove Programs list

The information found through Software Discovery was not reporting some programs that were found in the Windows Add/Remove Programs list.

 48044  1804612
Duplicate Add/Remove Program entries

The Add/Remove Program data could display duplicate entries for software.

 49388  1854629
Multiple entries in the Inv_AddRemovePrograms table

The Inv_AddRemovePrograms table contained multiple entries for software that was installed and uninstalled.

   1741141
Software Discovery did not report the uninstall path from Add/Remove Programs

The Add/Remove Programs data collected by Software Discovery was not reporting the uninstall path.

 49120  1840694
Software Discovery failed to return an estimated size for some applications

When the Software Discovery ran on client computers, a NULL value was returned for the estimated size of some applications even though the size value was available from Add/Remove Programs.

   1762397

Software package issues

   
Software package problems when Symantec Installation Manager, IIS, and SQL were installed using non-default settings

If you installed Symantec Installation Manager, IIS, and SQL using non-default settings, you could not do the following:

  • Import software packages into the Software Library.
  • Source packages from a directory on the Notification Server or from an existing UNC path.
  • Add a new software resource into the Software Catalog.
   1749473

 1736491

 1736534

A Notification Server that uses https with a custom port caused problems with importing software packages

If your Notification Server uses https with a custom port, you could not import software packages into the Software Library or source them from a directory on the Notification Server.

   1713682
Unable to import a file into the Software Library that had a Danish character in its name

If a file had a Danish character in its name, you could not import the file into the Software Library.

 47448  1679554

Managed Software Delivery issues

   
A Managed Software Delivery failed with exit code 2147024891

A Managed Software Delivery of Office 2007 failed with an exit code 2147024891.

 48636

 1804546
Problems with the Managed Delivery wizard when the software resource had dependencies

If a software resource had dependencies, the Managed Delivery wizard either hung or did not let you save the policy.

 48217  1764733
Browser language issues    
Unable to save changes on the Software Library Configuration page

When the browser language was set to French, you were unable to save changes on the Software Library Configuration page.

   1792741
Unable to import software into the Software Catalog

When the browser language was set to French, you could not import software into the Software Catalog.

   1834056

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  
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
Symantec Software Libarian security role does not let users edit software resources

The Symantec Software Librarian security role is setup incorrectly. Users who are assigned to this security role do not have the ability to edit software related resources.

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

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

   1983436
Unable to add a very large package to the Software Library

When you try to add a very large package to the Software Library, it eventually errors out. If you increase the timeout value on the Software Library Configuration page it might resolve this problem. You can also use a URL/USC based package instead of adding the package to the Software Library.

 49112  1840638
Software resources are not populating the With Unassigned Type folder

When you run Software Discovery, software resources with an unassigned type are not populating the With Unassigned Type folder in the Software Catalog.

   1877558
Software delivery fails when the client is 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 fails if the client is pointed to a child Notification Server. This problem occurs with a Quick Delivery task and a Package Delivery task.

 48542  1794571
Replicated software packages are not visible on child Notification Server

After your run complete replication, software packages are not visible on the child Notification Server at All Resources > Package > Software Package.

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

In the Software Catalog, on the Rules tab, if you create a new rule and delete the "And" operator, you can then no longer add expressions to the rule.

   1878007
Changes made to the Assign package to drop-down list are not saved

In the Add or Edit Package dialog box, on the Package Server tab, if you make changes to the Assign package to drop-down list and click OK, the changes are not saved. To save the changes, click OK on the Details tab.

   1782468
Software Package and Delivery Event Replication Rule

On the Replication tab of the Hierarchy Management page, the Software Package and Delivery Event Replication Rule is checked by default. To reduce the load on the parent Notification Server uncheck this replication rule.

   1886355
Selecting a folder when adding a package to a software resource

When you add a software resource to the Software Catalog, if you source its package from the Software Library and add the package by selecting a folder, any command line you add to the software resource fails when the software resource is delivered. 

   1800720
A software resource appears multiple times on the Data Provider Summary page

If you import a software resource into the Software Catalog from the Wise Software Repository and then perform a gather, the software resource that you imported appears multiple times on the Data Provider Summary page.

 49919  1862308
Software Catalog Data Provider Inventory task

The first time the Software Catalog Data Provider Inventory task runs, none of the installed software resources that it identifies appear in the Installed Software folder in the Software catalog. The software resources do not appear until the task runs a second time.

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

   
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
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    
Managed Delivery Settings to delete package from client computer

If you specify to delete a package immediately on the Download tab of the Managed Delivery Settings page, the packages of a newly created Managed Software Delivery are not deleted.

   1735833
Managed Delivery Settings to download the package to a specified location

If you specify a custom download location on the Download tab of the Managed Delivery Settings page, the packages of a newly created Managed Software Delivery are downloaded to the specified destination. However, if a package has a depends on relationship, the dependent software is downloaded to the default location and not to the specified location.

   1723485
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
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
The Managed Software Delivery option to continue the execution of the policy after a failure does not work

If you create a Managed Software Delivery policy and you select Continue in the Upon failure drop-down list on the Results-based actions tab of the Advanced options, the policy does not continue after it encounters a failure. For example, if the policy installs multiple software resources and one of them fails to install, then it does not install any subsequent software resources.

   1799845
A Managed Software Delivery policy that updates another software resource does not perform a detection check

If you create a Managed Software Delivery that updates another software resource, the policy does not perform a detection check before it installs the update. Consequently, it attempts to install the update even if the software resource that it updates is not installed.

   1873264
A Managed Software Delivery policy fails to execute after a restart

If a Managed Software Delivery policy delivers multiple software resources and if the client computer is restarted after one software resource is installed, then the policy is unable to install subsequent software resources.

   1765146
A Managed Software Delivery policy with a specific user fails on a Windows 7 Enterprise client computer

With a Managed Software Delivery policy, if you specify the user on the Run tab of the Advanced options, the policy fails on a Windows 7 Enterprise client computer. 

   1904760
A Managed Software Delivery policy cannot install an EXE installation file into a virtual layer

If you use Managed Software Delivery to deliver a software resource that has an EXE installation file and you check the option to install the policy’s software into a virtual layer, the software is installed on the base operating system and not in the virtual layer.

   1736338
A Managed Software Delivery policy fails after you change the detection rule of its software resource

If you change the detection rule of a software resource of a Managed Delivery Policy that is already enabled, the policy fails the next time it runs because its detection task is lost.

   1856326
A Managed Software Delivery policy fails on a computer running Windows 7

If a Managed Software Delivery policy has the advanced download option Run from server if bandwidth is above checked, the policy fails to execute on a computer running Windows 7.

   1902855
Quick Delivery task    
A Quick Delivery task on a child Notification Server fails

If a Quick Delivery task on a child Notification Server is set to run now and terminate after X amount of time, it fails if the package is not replicated down in time.

 48544  1797709
Package Delivery task    
The package and command lines of a Package Delivery task are not replicated with the task

When a Package Delivery task is replicated to another Notification Server, the package and command line associated with the Package Delivery task are not replicated.

 48037  1670451
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
A Package Delivery task does not download a package to an alternate location

With a Package Delivery task, if you specify a download location on the Download Options tab of the Advanced options, the task runs successfully but the package is not downloaded to the specified location.

   1870672
Command line issues    
Changes made to the command line of a software resource are not reflected in an existing task or policy

If you make changes to the command line of a software resource, those changes are not sent to the client computers that are already running the task or policy.

 49387  1853623
A long command line can cause software delivery problems

A very long command line can cause a Quick Delivery task or a Managed Software Delivery policy to fail.

 49459  1856488
Using a leading “.” when specifying a subfolder in a command line causes the execution to fail

If a software resource has an installation file that is in a subfolder that is not in the root of the package, you cannot use a leading “.” to specify the subfolder in a command line. 

 49385  1853565

Back to top


Legacy ID



48303


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


Terms of use for this information are found in Legal Notices