Unable to deliver a package that was added to a software resource by selecting a folder

When adding a software resource to the Software Catalog, if you sourced its package from the Software Library and added the package by selecting a folder, any command line you added to the software resource failed when the software resource was delivered.

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

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

Add Remove program data class reported the size of some software resources in bytes

Add Remove data class reported the size of some software resources in bytes instead of kilobytes. It now always reports the size of software using kilobytes.

A Package Delivery task did not download a package to an alternate location

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

Data from the Software Management Framework NSE(s) was taking a long time to load

The data from the Software Management Framework NSE(s) was taking a long time to load and this caused performance degradation. Changes were made that improved the performance considerably.

Symantec Management Agent used a large amount of virtual memory

Sometimes the Symantec Management Agent used a large amount of virtual memory.

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.

Managed Software Delivery

A Managed Software Delivery policy failed to execute after a restart

If a Managed Software Delivery policy delivered multiple software resources and if the policy restarts the client computer after one of the software resources is installed, then the policy was unable to install subsequent software resources.

 1893908

A Managed Software Delivery policy failed on a computer running Windows 7

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

Applicability rules of a Managed Software Delivery policy were not always applied

If a Managed Software Delivery policy had multiple software resources and some of the resources did not have applicability rules, the applicability rules of the other software resources did not always get applied.

Applicability rules of a Managed Software Delivery policy were not applied if the rule had already been used in the policy

If an applicability rule had already been used in a Managed Software Delivery policy for one software resource, the same applicability rule failed when applied to other software resources in the policy.

The advanced "Task can run" option of a Managed Software Delivery did not initialize correctly 

With a Managed Software Delivery policy, the advanced Task can run option was not initialized correctly when the option to run as Current logged-on user was selected.

The Managed Software Delivery option to continue the execution of the policy after a failure did not work

If you created a Managed Software Delivery policy and you selected Continue in the Upon failure drop-down list on the Results-based actions tab of the Advanced options, the policy did not continue after it encountered a failure. For example, if the policy installed multiple software resources and one of them failed to install, then it did not install any subsequent software resources.

A Managed Software Delivery policy failed after you changed the detection rule of its software resource

If you changed the detection rule of a software resource of a Managed Delivery Policy that was already enabled, the policy failed the next time it ran because its detection task was lost.

A Managed Software Delivery policy with a custom detection rule

A Managed Software Delivery policy with a custom detection rule did not execute.

Managed Delivery Settings to delete package from client computer

On the Download tab of the Managed Delivery Settings page, if you selected the option to delete a package immediately, it was never deleted.

A Managed Software Delivery policy that is scheduled to run at a specific time runs when the agent is updated

If you schedule a Managed Software Delivery policy to run at a specific time, it runs as soon as the agent on the client computer is updated regardless of the scheduled time.

Changes made to the command line of a software resource were not reflected in an existing task or policy

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

A long command line caused software delivery problems

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

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

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

Unable to add a very large package to the Software Library

If you tried to add a very large package to the Software Library, it eventually errored out. Several changes have been made to resolve this problem.

Using the Software Library as a package source

If you created a subfolder inside the Software Library location and copied a package into the subfolder, you could not source the package from its location in the Software Library with Software Management Framework 7.0 SP2 and Software Management Solution 7.0 SP1.

Software resources were not populating the With Unassigned Type folder

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

Data missing from the Name and Product Name fields in the Software Catalog

After a Software Discovery scan, the Name and Product Name fields of software resources in the Software Catalog could be blank. To help resolve this issue, the default schedule for the “Clean up File Resources” server task now runs daily at 2:10 instead of every Sunday at 2:40.  Changes were also made to speed up the consumption of the Software Management Framework NSE files.

 1929732

The dependencies of Package Delivery or Quick Delivery task were not replicated with the task

When a Package Delivery or Quick Delivery task was replicated to another Notification Server, any dependencies that were needed to complete the task were not replicated.

Software Package and Delivery Event Replication Rule

On the Replication tab of the Hierarchy Management page, the Software Package and Delivery Event Replication Rule was checked by default. It is now unchecked by default to reduce the load on the parent Notification Server.

Replicated software packages were not visible on child Notification Server

After you ran a complete replication, software packages were not visible on the child Notification Server at All Resources > Package > Software Package.

Software Catalog Data Provider Inventory task

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

A software resource appeared multiple times on the Data Provider Summary page

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

Terminology

A list of terminology used in Software Management Framework.

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.

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.

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.

An EXE-based software resource that is delivered with a Managed Software Delivery policy has a non-compliant status

With an EXE-based software resource a detection rule is needed for the compliance check of a Managed Software Delivery policy to work.

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. 

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.

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.

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, a Package Delivery task, and a Managed Software Delivery policy.

Data provider plug-ins use known-as information for the company name

When a data provider plug-in creates a software resource, known-as information is used for the company name instead of using the data that data provider supplies. This results in duplicate software resource entries in the Software Catalog when the software resource is detected on client computers. This issue was fixed in the 7.0 SP4 Hotfix 1 release.

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

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

Incomplete command line for imported VSA file

If you select a subfolder when you import a VSA file into the Software Catalog, the Import command line does not include the subfolder in the path to the VSA file. Because the subfolder is not included in the path, the command line fails when the package is delivered. The workaround is to edit the Import command line and to include the subfolder in the path.

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

If you run a complete hierarchy replication, the product name of some software resources may not be replicated to the child Notification Server.

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.

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

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.

A Managed Software Delivery policy that is 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.

A Managed Software Delivery policy does not run when using a schedule window

If you schedule a Managed Software Delivery with a schedule window, the policy does not run on the client computer. A workaround is to configure the policy so that it can be run manually on the client computer. 

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

If you create a Managed Software Delivery policy 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.

A Managed Software Delivery policy does not execute after powering on a computer

If a Managed Software Delivery policy powers on a computer, the policy does not run at the scheduled time if Current logged-on user is selected on the Run tab of the Advanced options.

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. 

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

If you use a Managed Software Delivery policy 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. This issue was fixed in the 7.0 SP4 Hotfix 1 release.

Applicability check issues with a Managed Software Delivery

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.

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

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. This issue was fixed in the 7.0 SP4 Hotfix 1 release.

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 does not get executed in the hidden mode.

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

If you create a Quick Delivery task on a parent Notification Server, you cannot assign a target that is managed by a child Notification Server to the task. You receive an erroneous message that the target does not have the Software Management Solution Agent plug-in. After the Quick Delivery task replicates to the child Notification Server, you can then assign the target from the child Notification Server.

Replication of a Quick Delivery task replicates all software resources

If you select a Quick Delivery task and on the the right-click menu, click Hierarchy > Replicate Now, all software resources are replicated. This replication option should only replicate the software resource associated with the Quick Delivery task. This issue was fixed in the 7.0 SP4 Hotfix 1 release.

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.

Replication of a Package Delivery task replicates all software resources

If you select a Package Delivery task and on the the right-click menu, click Hierarchy > Replicate Now, all software resources are replicated. This replication option should only replicate the software resource associated with the Package Delivery task. This issue was fixed in the 7.0 SP4 Hotfix 1 release.