Importing A Device Driver File - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Importing a Device Driver File

Software Manager Reference
You can import device driver information contained in an .INF file into the Software
Manager database from a network or local drive. This lets you:
Identify file and registry conflicts that could occur if you were to introduce a specific
device into your desktop environment. You cannot resolve conflicts in or export a
device driver package, because the changes would not be supported by the vendor.
However, you can change packages that conflict with the device driver.
Distribute a device driver package as part of a group for easy deployment by a
distribution system. To do so, import the device driver, create a package definition
file, and then add it to a group for deployment.
See Creating a Package Definition
page 88.
An .INF file can contain multiple manufacturers and devices. When you import the driver
information, an application is created for each manufacturer, and a package is created
for each device. The device ID is appended to each device name. File information
(example: version, date, time, and so on) is obtained from .CAB files that are referenced
by the .INF file. Enumerated registry keys are identified in Software Manager and
ConflictManager as ENUM(0000). Enumerated entries do not cause conflicts because
their values are set at run time.
To import a single device driver 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 an .INF 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.
on page 115 and Creating Package Groups
Importing Packages
on
61