Distributing and Using Packages
Once created, packages are distributed to client PCs by whatever means you prefer, although it is assumed they will be made available at a shared location, so that users can browse and install the packages relevant to them. This location may be a network share known to all users or a web site containing links to the packages.
Setting the Package Root Path property allows packages to be generated directly into a web server or share. Alternatively, packages can be generated in an export location, then transferred manually to a web server or share.
If packages are made available on a web site, several options are available for presenting the packages to users:
- You can write your own web pages, containing links to the package files.
- Users can be given access to the Manifest.xml file, which contains links to all available packages.
- Users can be given access to the Uniprint Web Site.
The Pharos Print Map Builder is opened from Pharos Administrator by clicking the button on Package Definitions toolbar.
Packages are run by double-clicking on them. Full packages install the Pharos components and Spool Queue printer(s) immediately. Lite packages detect the operating system and any existing Pharos components, then download and install only those modules that are needed. Depending on the modules installed, a reboot may be necessary following the install.
Note: Lite packages contact the URL specified by the Module URL property to download modules.
When running an installer, an Advanced button is available to show details of the install as it progresses.
An updater module is included in all install packages. The updater runs a service and checks the manifest file for updates whenever the Pharos components are used, provided a specified period has elapsed since they were last used.