Refreshing Package Subscriptions; Breaking Links To Subscribed Packages - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Refreshing Package Subscriptions

Breaking Links to Subscribed Packages

Software Manager Reference
Enterprise Management Server only.
Refreshing package subscriptions consists of re-importing all subscribed packages to the
local database. Do this when:
The source installation files change.
The original package is deleted from the source database.
You make changes on the Package Subscriptions dialog box.
Options on the Package Subscription Details dialog box determine whether a specific
subscription is updated when subscriptions are refreshed.
See Subscribing to Packages in Another Database
Device driver and Group Policy Object subscriptions are not linked to the source file. If
the source file changes for these types of packages, the changes are not re-imported.
Refreshing Subscriptions Manually
Do one of the following:
Click Update on the Software Manager toolbar.
Select Packages menu > Refresh Subscriptions.
Refreshing Subscriptions Automatically
You can run a Windows scheduled task that refreshes package subscriptions. The Wise
Package Subscriptions task periodically searches the external databases for changes to
the source installation files or for subscription packages that have been deleted from the
source database. When it finds subscription changes, the service refreshes the
subscriptions by re-importing the subscribed packages.
To run the Wise Package Subscriptions task, schedule it in the Wise Task Scheduler. For
requirements and information on scheduling the task, see
Tasks on page 28.
Enterprise Management Server only.
You cannot export subscribed packages, because multiple databases cannot export to
the same installation file and because the source installations for subscribed packages
typically have been approved and deployed and should not be changed. Exporting of
packages is prevented by the Prevent Package Export check box on the Package
Attributes dialog box, which is marked by default for subscribed packages.
There are situations in which you might need to update a subscribed package. Example:
Suppose your corporate repackaging team maintains a package for Microsoft Office. You
subscribe to the Office package to resolve conflicts between it and packages in your
regional database. Now, suppose you want to make changes to the Office package, but
you don't have permission to change the corporate version. If you break the link to the
original Microsoft Office package, change the path to the installation file, and
redistribute the installation to the new location, you can change and export the Office
package.
Importing Packages
on page 75.
Scheduling Software Manager
77