Detecting Conflicts For Impact And Risk Assessment - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Detecting Conflicts for Impact and Risk Assessment

Software Manager Reference
The Impact and Risk Assessment dialog box appears.
4. In Package, select the patch or hotfix.
5. Mark Isolated Files at Risk.
The list displays the packages that contain isolated files that will not be updated by
the selected package.
To display isolated files that will not be updated, select a package in the list and
click the Files tab.
To display conflicts between the selected package and the displayed packages,
select a package in the list and click the Conflicts tab.
To generate a report of the risk information, click Report.
6. To create a setup.exe that will update the isolated file with the version from the
selected package:
a. Click Risk Mitigation.
The Risk Mitigation wizard appears.
b. On the Select Files dialog box, mark the isolated files to be updated and click
Next.
c. On the .EXE File Path dialog box, specify the full path of the .EXE that will
update the isolated files and click Finish.
A WiseScript project (.WSE) is created and compiled to the .EXE that you
specified.
d. You can edit the .WSE file in WiseScript Editor if necessary. (Example: to update
additional files that are in other directories.) After you edit the .WSE, recompile
the .EXE.
Note
If the .EXE updates an isolated file that is in a virtual software layer, it will be copied to
the read-only sublayer. If the layer is reset, the updated file is not deleted from the
layer.
See also:
Impact and Risk Assessment
When you run Impact and Risk Assessment, the Detect Conflicts dialog box appears if
new packages have been imported but conflicts have not been detected for them.
To detect conflicts, select applications and click OK.
See Detecting Conflicts in the ConflictManager Help.
To run Impact and Risk Assessment without detecting conflicts, click Cancel.
Preparing Packages for Deployment
on page 125
127