Importing A Group Policy Object File - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Importing a Group Policy Object File

Software Manager Reference
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.
6. To assign the imported package to one or more groups:
a. Click Groups on the Import Type page. The Select Groups dialog box appears.
b. Mark the check boxes of the groups to assign the package to.
c. Click OK.
Note
If you will use Group Distribution, it is best to add packages to groups on the Group
Properties dialog box. The order in which you add packages to a group on the Group
Properties dialog box can affect the state of the package check boxes during
distribution.
7. Click Finish on the Import Type page.
You do not have to specify an application and package name because .INF files are
imported using the manufacturer as the application name and the device as the
package name.
If you perform a local import and a .CAB referenced in the .INF file could not be
found, you are prompted to insert the manufacturer's installation disk and specify
the source file location. If the .INF does not contain a reference to the .CAB, you are
prompted to browse for the source file. If you perform the import on the Wise
Package Studio Server, no prompts appear and these errors are added to the log file
for the import.
The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your
work in Wise Package Studio. From this dialog box, you can view a log file for the
import.
The device driver you selected is imported to the active Software Manager
database. During the import process, errors are displayed as they are encountered.
See also:
Importing Multiple Files on page 68
Package Import on page 34
Wise Task Manager in the Wise Package Studio Help
You can import registry-based group policies found in administrative templates into the
Software Manager database from a network or local drive. Policies in an administrative
template (.ADM) file relate to registry settings that control the behavior and appearance
of the desktop and components of the operating system. To import the policies to
Software Manager, you must export the .ADM file to a .POL file, using the Group Policy
snap-in. For more information about group policy and administrative templates, see
Administrative Template File Format and Registry Policy File Format in the MSDN Library
(msdn.microsoft.com/library/), or refer to the Group Policy snap-in Help.
Importing Packages
62