Install packages are created in Pharos Administrator
The process of creating install packages involves the following steps:
1. Prepare the web site that packages and modules will be written to (if one is used)
2. Make sure that printer drivers are configured correctly for all Spool Queues and print servers
3. Set up Package Definitions and global properties in Pharos Administrator
4. Build packages based on the definitions
Preparing the Web Site (Optional)
If packages are to be made available for download, or if Lite packages (which download the necessary modules from a web server) are being used, the web server that will host the packages and/or modules should be set up before creating packages.
If a web site is already present, all that needs to be done is designate a location for the packages. If a web site does not already exist, one can be set up from the Pharos installers. Select “Web Server” from the Select Role screen, then select “Uniprint Web Site” on the Select Components screen. When the Uniprint Web Site is installed, the Package Root Path and Module URL properties (see below) are automatically set to the Uniprint Web site Site’s directory and URL.
Note: The Package Root Path property is set to the full path to the Uniprint directory, e.g. \\SERVER\C\Inetpub\wwwroot\Uniprint\. For security reasons, it is best to make the Uniprint directory into a network share with appropriate permissions, then change the Package Root Path to this share name, e.g. \\SERVER\UniprintWebSiteShare\.
Note: Even if you do not need the Uniprint Web Site, it may be a good idea to install and use it for testing, then set up the real web site once everything is working.
Setting up Printer Drivers
Before creating install packages, make sure that all Spool Queues are using the correct drivers (check the Driver property on the Device tab of the Spool Queues context). The drivers specified for each queue must match the drivers in use on the printers that the queues forward jobs to.
The operating systems supported by each package created depend on the drivers found on each Print Server. To ensure that install packages are available for all operating systems, ensure that drivers for all operating systems are installed on all Print Servers:
1. On each Print Server, open Control Panel > Printers and Faxes.
2. For each printer that users can print to:
a. Right-click on the printer and select Properties.
b. On the Sharing tab, click Additional Drivers.
c. In the Additional Drivers dialog box, select the check boxes for the additional environments and operating systems you need, then click OK.
Note: Windows NT4 printer drivers can be used on Windows 2000/XP/2003. If Windows 2000 drivers are not available, but NT4 drivers are, packages will be created for Windows 2000/XP/2003 using the NT4 drivers.
Setting up Package Definitions and Global Properties
Install packages are created according to Package Definitions, which contain information on the contents and properties of install packages. Package Definitions are set up in Pharos Administrator at Distribution System > Package Definitions.
Two options are available when creating Package Definitions:
You can use the Package Definition Insert Wizard to create one definition for each Spool Queue in the Pharos Database by clicking the button.
You can use the Package Definition Insert Wizard to create a single definition, which may contain multiple Spool Queue modules, by clicking the button.
Note: If you wish to include an EULA in your install packages, have it ready as a text file before creating Package Definitions.
When creating Package Definitions, you must specify the following:
1. A name for the definition. If you are creating definitions based on Spool Queues, each definition will automatically be named for the Print Server and Spool Queue it relates to.
2. The Spool Queue modules to include in the package. If you are creating definitions based on Spool Queues, each definition will contain only the Spool Queue module for the queue it applies to.
3. Whether or not to include an un installer in the package
4. The full UNC path to the text file containing the EULA (if one is to be used).
All Package Definition properties can be edited in the Package Definitions context after creation, with the exception of the OSes Supported and Last Build Time properties.
Note: When Package Definitions are first created, the OSes Supported field contains “<Must rebuild>”. Available operating systems are not known until the package creator is run (see below).
In addition to the information contained in the Package Definitions, two global properties affecting install packages are available on the Packages tab of the System Properties dialog (File menu):
The Package Root Path property determines the location that install packages will be placed in when they are created.
The Module URL property sets the URL that Lite packages will download modules from.
Note: These properties are automatically configured if the Uniprint Web Site is installed.
The Package Definition Insert Wizard gives the option of building packages as soon as the wizard is complete. Packages based on all Package Definitions can be built at any time by clicking the button on the Package Definitions context toolbar.
The package creator is a separate executable launched by Pharos Administrator. This executable, PackageCreator.exe is located in the Pharos\bin directory, and can also be run from the command line—see below for details on command line options.
The package creator checks the Print Server(s) for all Spool Queues specified in the Package Definitions to determine which operating systems printer drivers are available for.
Note: For this reason, the account running the package creator must have rights to read files on all Print Servers.
Driver files are copied and included in the relevant packages as they are built. For each Package Definition, the following files are created:
Full packages for each available operating system.
One Lite package.
Modules for all components and operating systems included in the full packages.
In addition, a “manifest” containing details of all modules and packages is created. This file, called Manifest.xml, is an XML document used by the package updater to determine what the latest versions are. It is formatted with an XSL style sheet, and can be viewed in a web browser. When viewed in this way, it contains links to all packages created, organized by operating system. Packages can be grouped together on the web page by specifying a Web Page Group value for Package Definitions.
Note: Click the internet page button on the Package Definitions toolbar to view the manifest as a web page.
Packages are created in the directory specified by the Package Root Path property (File menu > System Properties dialog > Packages tab). Modules for the Lite installers are created in a sub-directory under the main packages directory called modules. Clicking the Show Files button on the package creator’s progress dialog opens Windows Explorer to this location.