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

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

Wise Package Studio Reference 264
Preflight Deployment
z
On the Tools tab, double-click Preflight Analysis.
OR
z
On the Projects tab, click the Run link to the right of the task or tool associated with
Preflight Analysis.
Preflight Analysis opens. Use the links and buttons provided to view results and
navigate.
If Workbench cannot connect to the computer that is hosting the Preflight Analysis Web
application, the Connection Failed dialog box appears.
See Connecting to a Web Application on page 79.
Interpreting preflight results and troubleshooting
The results you see in Preflight Analysis were sent from the target computer to the IIS
server by the preflight package. If you have unexpected results, there are several
possible causes.
z
Statuses of Incomplete
An incomplete in the Status column can indicate that the preflight .MSI failed with a
fatal error, network communication was interrupted, or the computer was powered
off. It could also be that the preflight testing is still in progress.
z
Network Communication Failures
If results from preflight packages do not appear in Preflight Analysis, then the target
computer might have not have network access to the IIS server. This can be caused
by a variety of network configuration problems, including name resolution problems,
cabling problems, operating system configuration, and so on. To avoid this problem,
you could locate preflight Web applications on the same computer as you use for
deployment, because the deployment computer has a history of successful
communication with target computers.
z
Fully Qualified Domain Names
Remote computers might have trouble connecting to the IIS server if they are
required to connect using fully qualified domain names. The URL to the Data
Collector Web application is embedded in the preflight package by the Package
Instrumentation tool, and usually defaults to something like this:
http://IIS_Server/Wise_Managed_Enterprise/wisewebservice.dll
If a fully qualified domain name is required, the URL would look something like this:
http://IIS_Server.company.com/Wise_Managed_Enterprise/wisewebservice.dll
z
Remote computers using Citrix
The preflight package cannot communicate over Citrix.
z
Custom Action Removal
Custom actions are removed because they could cause changes to the target
computer. However, sometimes this may cause results that differ from the original
package. Example: Suppose a custom action sets a property based on the contents
of the computer. In turn, the property is used in conditions that cause different
actions in the package. Because the custom action is removed, the property is not
set, and the conditional branches are not followed.
z
Permission Test Failures
Permission tests rely on the current user account having permission to read
permission data from the registry. If the user account does not, then permission
tests cannot be performed.