Symantec 14541094 Administration Guide - Page 42

Testing packages, To build a package

Get Symantec 14541094 - pcAnywhere Host & Remote PDF manuals and user guides
UPC - 037648640480
View all Symantec 14541094 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

42 Creating custom installation packages Testing packages To build a package 1 In the Symantec Packager window, on the Configure Packages tab, select the package definition file that you want to build. 2 On the File menu, click Build. The Package Build Status window appears, which provides information about the progress of the build and logs any problems that have occurred. If the package build is successful, the last line in the Build Status window reads as follows: Package was built successfully. 3 In the Build Status dialog box, click Close. Testing packages It is important to test packages before you deploy them to end users to ensure proper functionality. You should test package installation and deployment in an isolated, controlled environment. One to two test computers should be sufficient to conduct testing. Although some error checking occurs during the build process, some errors cannot be detected until installation. This is especially true if the package includes a product that requires a third-party product or if the package includes a custom command. During installation, Symantec Packager checks for product conflicts and verifies that required products are present on the target computer. The installation fails if Symantec Packager encounters a conflict that it cannot resolve. You should test packages to verify that product requirements are met and that the installation sequence is correct. You should also open each installed program to ensure that it functions correctly. Ensure that the features that you want are present. This step is especially important if you customize a product to reduce the installation footprint. Product testing ensures that you have not overlooked an important feature. Once you thoroughly test the package, you can deploy it to users.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
To build a package
1
In the Symantec Packager window, on the Configure Packages tab, select the
package definition file that you want to build.
2
On the File menu, click
Build
.
The Package Build Status window appears, which provides information about
the progress of the build and logs any problems that have occurred. If the
package build is successful, the last line in the Build Status window reads as
follows:
Package was built successfully.
3
In the Build Status dialog box, click
Close
.
Testing packages
It is important to test packages before you deploy them to end users to ensure
proper functionality. You should test package installation and deployment in an
isolated, controlled environment. One to two test computers should be sufficient
to conduct testing.
Although some error checking occurs during the build process, some errors cannot
be detected until installation. This is especially true if the package includes a
product that requires a third-party product or if the package includes a custom
command.
During installation, Symantec Packager checks for product conflicts and verifies
that required products are present on the target computer. The installation fails
if Symantec Packager encounters a conflict that it cannot resolve. You should test
packages to verify that product requirements are met and that the installation
sequence is correct.
You should also open each installed program to ensure that it functions correctly.
Ensure that the features that you want are present. This step is especially
important if you customize a product to reduce the installation footprint. Product
testing ensures that you have not overlooked an important feature. Once you
thoroughly test the package, you can deploy it to users.
Creating custom installation packages
Testing packages
42