Deploying Install Packages

After creating install packages, the next step is to distribute the packages to client PCs. Install packages can be distributed to users using the following methods:

  • Shared Location
  • Automated Software Installation Utility
  • Uniprint Website

Shared Locations

This may be a network share known to all users or a web site containing links to the package files. This allows you to set up a "mobile printing" environment, where users can print to Pharos services from their personal PCs or laptops. No staff intervention is required because users can locate and install the software they need by themselves.

Automated Software Installation Utility

Packages can be picked up and distributed to client PCs by an automated installation utility such as Microsoft SMS.

Uniprint Website

If the Uniprint Website is installed, the Package Build Location is automatically set to generate packages to the web server that the Uniprint Web Site is installed on.  The Uniprint Website contains links to all available packages and maps.

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.
  • The Pharos Print Map Builder can be used to create a series of web pages containing links to Lite packages.

Packages can be run silently from the command line by specifying the -quiet option.When run, packages create a log file called ControllerLog.txt in the Documents and Settings\[username]\Local Settings\Temp\Pharos directory of the client PC.