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

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

Wise Package Studio Reference 266
Preflight Deployment
Files Installed Reports the number of files that would be installed on
the computer and also reports the total number of files
contained in the package. Example: If a file is slated to
be installed, but does not get installed because the same
file already exists, then the cause might be the
versioning rules that apply to that file. This test is
informational only.
Find Valid Patch Target Checks if the computer contains any of the valid patch
targets that are recorded within the patch. If it fails to
find a valid target, this test fails. This test only applies if
the package being tested is a patch.
Launch Conditions Determines which launch conditions succeed and which
fail.
Local File Execution Evaluates custom actions that use a command line to
run a file that is expected to exist on the target
computer.
Managed File Check Not available unless the Professional Edition is installed
in addition to the Quality Assurance module.
Checks for unmanaged files and returns a warning if any
are found. Unmanaged files are files that are not
recorded in the Wise Software Repository. Specifically,
an unmanaged file is a file on the target computer that
has the same name and location, but differing attributes,
as a file in the preflight package.
The presence of unmanaged files indicates that software
outside the packaging process is installed on target
computers, which might invalidate previous conflict
analysis and installation testing. To resolve this, do one
of the following:
z
Import the package associated with the unmanaged
files into the Software Manager database for conflict
analysis and installation testing.
z
Remove the unauthorized software from target
computers.
.NET Framework Determines if the .NET Framework is required by this
installation, and if so, if the .NET Framework is installed
on the target computer. This test is placed after the
launch condition test.
Preflight Instrumentation determines if this test is
required by checking the MsiAssembly table for any
entries with a 0 in the Attributes column. If the test is
not required, the Preflight Instrumentation tool does not
add it.
Open Document Check Builds a list of document extensions from any
OpenDocument custom actions and saves the list in a
table. When the preflight package runs, this test checks
the registry for support for each extension.