Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference page 63

Software Manager Reference
Importing a Group Policy Object lets you determine whether any of your packages will
change or conflict with policies on your desktops. Example: Suppose you set a group
policy to disable the Registry Editor (regedit.exe). You import that Group Policy Object
to Software Manager and, when you detect conflicts, you find that one of your packages
requires the use of regedit.exe. This isn't a typical conflict that you can resolve by
changing the registry keys; you cannot change or export a Group Policy Object.
However, the conflict provides information to help you manage your desktops; you can
make a decision about installing a package that will override your policy, or you might
work with your system administrator to change the group policy for end users who need
that package.
You can distribute a group policy package as part of a group for easy deployment by a
distribution system. To do so, import the group policy object, create a package definition
file, and then add it to a group for deployment.
See Creating a Package Definition
page 88.
To import a group policy object file
1. (Enterprise Management Server only.) If multiple databases are open, select a
database in the Applications/Packages pane.
2. Select Packages menu > Import.
The Import Type page appears.
3. Mark Import a single file into the Software Manager database.
4. In File, specify a .POL to import. Be sure to select the appropriate file type from the
Files of type drop-down list on the Open dialog box.
5. The following item becomes enabled:
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the
same application and package names.
If you clear this check box and the application and package names are already
in the database:
If the existing package has resources, the new package is not imported.
If the existing package does not have resources, the new package's
resources are added to the existing package. An existing package might not
have resources if it consists only of a package definition.
Perform this operation on the Wise Package Studio server
If you are working on a client computer, mark this to perform this operation on
the Wise Package Studio server. You must use a UNC path to specify the
imported package. If the package and the Software Manager database reside on
the server, this significantly improves the performance of this operation for
large packages. With Enterprise Management Server, Security Setup
determines whether this option appears.
Detect conflicts during package import
The default for this option is provided by the Detect conflicts during package
import check box in Conflict Settings. Mark or clear this to override the default.
If this is marked, conflict detection checks for conflicts between the imported
package and all other packages in the Software Manager database.
on page 115 and Creating Package Groups
Importing Packages
on
63