Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0, Справочник

Страница: 252 / 302

Wise Package Studio Reference 252
Package Distribution
„
GPO Name
Enter a unique name for the Group Policy Object to be created. Adhere to
Microsoft Group Policy Object naming conventions.
„
Settings
Set the package to be deployed per machine or per user. This determines where
an application’s configuration information is stored.
„
Deployment Method
If you selected Per User above, you can set the package to be assigned or
published. If an application is assigned to a user, it appears installed, including
shortcuts, extensions, icons, and registry entries. Publishing can only occur
from a Windows Server and does not populate the interface. Publishing only
registers extensions and MIME types. In both cases, installation-on-demand
takes place when the user invokes an entry point to the application.
If you selected Per Machine in the Settings field, this field is set to Assign
and is unavailable, because of Active Directory restrictions.
6. Click Finish.
A new Group Policy Object is created that contains the installation. It is added to the list
of all Group Policy Objects stored in the domain but is not assigned to any organizational
unit—to add it, use the Active Directory management console.
Copying a Package to the Share Point Directory
You can use Package Distribution to copy a package or merge module to the share point
directory, for later importing into the Software Manager database. Distributing to the
share point directory also copies all of the package’s source files to the share point and
updates the source paths for those files, which means that after resolving conflicts you
can recompile the fixed package from its location on the share point.
Distributing to the share point directory does not actually import the package into the
Software Manager database, but copies it to a directory in a format that can be imported
into the Software Manager database. You use Software Manager to import it from the
share point.
When you distribute a .VSA file to the share point directory and import it into the
Software Manager database, it is converted to a .WVP file.
After you copy a package or merge module to the share point directory and import it
into the Software Manager database, you can use Software Manager to manage the
package and use ConflictManager to check the package for conflicts.
The following criteria determine whether this option is available.
You specify this type of file: .WSI, .MSI, .WSM, .MSM, .WSE, .WVP, .VSA
You run Package
Distribution from: Workbench only.
Other requirements:
z
Not available in Standard Edition.
z
Not available if distributing a preflight package
(generated with Preflight Instrumentation tool.)