Last Updated 09/20/06

Pharos Systems
illuminate

T E C H N O T E

Pharos Install Packages and Mobile Printing

Pharos install packages simplify the process of installing Pharos Popups and Notify on client
PCs, and allow for the implementation of a “mobile printing” system, where users are able to
print to Pharos from their personal laptop PCs. This document explains how install packages
are created, distributed, and updated in Pharos 7.2 and later.

About Install Packages

Install packages automate the process of setting up Pharos Popups and Notify on client PCs. As well
as installing the client application(s), they can set up one or more Pharos Spool Queues as printers
on the local PC. Because they are completely self-contained, they can be distributed to users, who
download and install them on their personal laptops or PCs, allowing them to print to the Pharos
system without the need for a staff member to install Pharos software for them. Install packages can
be created for Windows 2000, XP and 2003.

Packages are created from Pharos Administrator, based on the print drivers available on Pharos
Print Servers. An install package consists of a collection of modules. The modules included in a
package are chosen in Pharos Administrator (see below), but a package usually contains the
installer modules for the Popup and Notify Client and one or more Spool Queue modules, which set
up the relevant printer(s).

Install packages are self-contained and need only be copied/downloaded to client PCs and run.
“Lite” versions of the install packages are also available, which are smaller executables that detect
the operating system and any existing modules, then download only those modules that are needed.

Once created, packages can be distributed by whatever means you prefer. This may mean copying
the packages to a share that all users have access to, or placing them on a website where users can
download them themselves (a website is required to make use of Lite packages, or if you want the
installed components to be able to automatically download updates).

Packages can optionally include an End User License Agreement (EULA), which users must read
and accept before the package installs any files.

Creating Install Packages

Install packages are created in Pharos Administrator. The process of creating install packages
involves the following steps:

1. Install/prepare the website that packages and modules will be written to (if one is used)
2. Set package-related properties for Spool Queues
3. Configure global properties in Pharos Administrator
4. Set up Package Definitions
5. Build packages based on the definitions

Once created, install packages can be made available for end users to download and install, or they
can be distributed to client PCs by whatever method you prefer, e.g. installing manually or using an
automated software installation utility like Microsoft Systems Management Server (SMS).

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

Preparing the Web Site (Optional)

If packages are to be made available for download, or if you want to use Lite packages or automatic
updates (which download the necessary modules from a web server or network share), 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 Build Location and Package Download &
Update Location properties on the System Properties dialog (see below) are automatically set to
the Uniprint Website Site’s directory and URL.

Note: The Package Build Location 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 Build
Location to this share name, e.g. \\SERVER\UniprintWebSiteShare\.

Note: If the web site uses a different port than the default (80), this must be included in the URL, e.g.
http://SERVER:81/Uniprint/.

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. To migrate to the real site, you must update
the Package Build Location and Package Download & Update Location properties and
regenerate all packages.

Note: Packages and modules can be made available for download from a network share, rather than
a web server. In this case, the Package Download & Update Location should start with file://, rather
than http://.

Setting up Spool Queues

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.

When install packages create a Windows printer object for a Spool Queue on a client PC, they can
attempt to give the new printer the same settings as the Spool Queue’s printer, i.e. the printer object
on the Print Server that is created when the Spool Queue is first inserted. If you want install
packages to duplicate the Spool Queue printer’s settings, select “yes” for the Copy Printer Settings
option on the Details tab of the Spool Queues context.

Note: This may not work in all cases. For this reason, the property is set to "No" by default.

Note: Printer object settings are configured at Start Menu > Settings > Printers. Right-click on the
desired printer and select Properties. Note that the properties on the General tab of the Properties
dialog only affect the current user, and will not be picked up by the Package builder. To change the
settings for all users, click the Printing Defaults button on the Advanced tab, and configure the
options on the dialog that appears.

Finally, you can also specify the name that will be given to printers installed for each spool queue by
editing the Popup Printer Name property on the Device tab (if no name is specified, the installed
printer's name will default to "<spool queue> on <server>").

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

Configuring Global Properties

Global properties affecting install packages are available on the Packages tab of the System
Properties dialog (File menu). Three properties relate to the creation of install packages:

 The Package Build Location property determines the location that install packages will be
placed in when they are created.
 The Package Download & Update Location property sets the URL that packages and
modules will be available from. This is the URL that Lite packages will download modules
from. It is also used by the updater module (see “Updating Packages” below). The URL
specified must include the port used, if it is not the default HTTP port (80).
 The Shared Directory property determines the location where source files such as EULA
files and custom modules (see below) are copied.

The Package Build Location and Package Download & Update Location properties are automatically
configured if the Uniprint Web Site is installed. Ideally, they should point to the same location—this
way, files are generated straight into the directory where they will be downloaded from. If they are
not the same, you must copy files from the build location to the download location manually. In this
case, you must preserve the directory structure set up in the build location (i.e. packages in the root
directory, modules in a subdirectory called modules).

Note: Packages and modules can be made available for download from a network share, rather than
a web server. In this case, the Package Download & Update Location should start with file://, rather
than http://.

On the Packages tab you can also specify how often components should check to see if updated
components are available (see ”Updating Packages” below).

Setting up Package Definitions

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 > Packages > 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 End User License Agreement (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:

 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.
 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.
 The text file containing the EULA (if one is to be used). This file will be copied to the Shard
Directory (see above).
 The Pharos-supplied modules to include. The Notify module is always included; Popups, the
uninstaller and the updater are optional—see “Which Modules to Include?” below.
3

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

All Package Definition properties can be edited in the Package Definitions context after creation, with
the exception of the Last Build Time property.
Which Pharos Modules to Include?
For a mobile printing environment where users install packages on their personal laptops, the
uninstaller module should be included. If packages are available on a permanently accessible web
site, including the updater module is also a good idea (see ”Updating Packages” below).

In a printer lab environment where Pharos software is used on PCs owned by your organization, the
uninstaller should not be included. In such situations, updates are usually conducted by updating a
master image, then pushing it to all PCs, so the updater module is probably not needed either.

Building Packages
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. A single Package Definition can be built by
selecting the definition you want and clicking the button.

The package builder is a separate executable launched by Pharos Administrator. This executable,
PackageBuilder.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 builder 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 builder must have rights to read files on all
Print Servers.

The package builder performs three steps:

Verify
This process checks the integrity of the data that will be used to build packages. Any problems, e.g.
missing information, are reported during this phase (see “Package Builder Warning and Error
Messages” below for information on the messages generated by the package builder.
Build
Once the Verify phase is complete, the package builder waits for you to click the Start button before
starting the build phase. In this phase, all modules and packages are built. The Package builder will
produce new module files where required and overwrite the old ones. For each Package Definition,
the following files are created:

 Full packages for each available operating system.

 One Lite package.
 Modules for all components, printers 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.

Packages are created in the directory specified by the Package Build Location 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.
4

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

Note: Clicking the Show Files button on the package builder’s progress dialog opens Windows
Explorer to this location.
Synchronize
Once all modules and packages are built, the package builder examines all package definitions
(even if only one was built) and synchronizes the data contained in the Manifest.xml file and
Uniprint Web Site with the Package Definitions defined in the database, ensuring that what is in the
manifest and Package Build Location matches what is in the database. The synchronization phase
performs the following actions:

 Reloads all package and module definitions as defined in the database

 Produces warnings when module definitions are not found in the manifest
 Removes entries in the manifest that are not found in the database
 Produces warnings when package definitions are not found in the manifest
 Deletes all modules and executable files in the Package Build Location that are not defined
in the database

Distributing and Using Packages

Note: There is always the possibility that packages will fail on some operating systems, due to
problems with printer drivers or incomplete information provided by the operating system. Make sure
to test install packages on all operating systems before distributing them. Contact Pharos
Support if you encounter any problems running install packages.

Once created, packages are distributed to client PCs by whatever means you prefer. In a mobile
printing environment, they can 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. Other distribution methods can be used in other situations.
For example, packages can be picked up and pushed to client PCs by an automated software
installation utility like Microsoft SMS.

Setting the Package Build Location 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 (the Package Download & Update Location property must
specify this location). 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 (see below) can be used to create a series of web pages
containing links to Lite packages.
 Users can be given access to the Uniprint Web Site, which contains links to all available
packages and maps. Only Lite packages are displayed by default (with the OS listed as
“Autodetect”), but links to all packages and all individual modules are available.

Note: The button on the Package Definitions toolbar opens the Uniprint Web Site if it is installed;
if not, it opens the manifest file as a web page.
Creating Print Maps
The Pharos Print Map Builder produces a series of web pages containing a graphical representation
of the location of all printers in your organization. Each printer icon contains a link to the Lite
package that installs a Spool Queue for that printer. Users can then browse the map to find the
printer they want to print to and download the install package for that printer.

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

The Pharos Print Map Builder is opened from Pharos Administrator by clicking the button on
Package Definitions toolbar, and includes its own online Help.

Running Packages
Packages are run by double-clicking on them. If a EULA was specified for the package, the user
must accept its terms before the installation can proceed. Full packages install the Pharos
components and Spool Queue printer(s) immediately. If the same package is run twice, it will re-
install all modules; however, if two different packages are run, the second will not attempt to re-install
any existing modules installed by the first.

Note: Command line options are available to make packages run silently and to prevent packages
from re-installing components—see “Advanced Options” below. The -quiet option may be useful if
you want to automate the deployment of packages across many client PCs.

Lite packages detect the operating system and any existing Pharos components, then download and
install only those modules that are needed. (Lite packages contact the URL specified by the
Package Download & Update Location property to download modules.) Depending on the client
PC’s operating system and the modules installed, a reboot may be necessary following the install.

Install packages create one printer on the client PC for each Spool Queue included in the package.
By default, these printers are named "<spool queue> on <server>". To specify a different name for
the printers, edit the Popup Printer Name property (Device tab) for each Spool Queue.

Updating Packages
An updater module is optionally included in 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 (see below).

Note: In order for automatic updates to work, a web site or network share containing the manifest
and modules must be available. If this is not the case, PCs can only be updated by running a new
full package—this will install updated components over top of the existing ones.

If updated modules are detected, the updater downloads and runs the relevant Lite installer. Running
the Lite install ensures that only those modules that have changed are downloaded. The updater
also keeps track of the last time Popups was used on the client PC.

Note: Automatic updates will not work on PCs that use Deep Freeze, Clean Slate or other security
software that restores the hard drive to a known state on reboot—the updates will be overwritten
when the hard drive is restored. To upgrade PCs that use security software like Deep Freeze, you
must use a new full package to create an updated default hard drive image.

The updater component is controlled by the Update Frequency property on the System Properties
dialog in Pharos Administrator (File menu), which determines how often components should check to
see if updated components are available. Components check for updates whenever they are used,
provided that the amount of time specified here has passed since they were last used. For example,
if the Update Frequency is set to one day, and a user prints five times in a day, the components will
only check for updates once that day. However, if the user goes more than one day without printing,
the components will not check for updates until the next time the user prints.

This setting is copied to the manifest file, so that if it is changed, the changes will be propagated to
the updater components on all client PCs the next time they check for updates.

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

Advanced Options
The following advanced options are available when creating and running packages.

Custom Drivers
Printer drivers for Spool Queues are normally obtained by querying the Print Server during the
creation of install packages; however, you can supply custom driver installers for Spool Queues if
this process fails, or if you do not want to query the Print Server for any reason.

A custom driver installer must have the following features:

 It must create a printer object on the client PC and install the drivers for the printer.
o This printer must have the name specified by the Popup Printer Name property for
the Spool Queue that it relates to (see “Setting up Spool Queues” above).
 It must not ask the user to reboot (this will interrupt the rest of the install package).
 It must not spawn a child process that runs while the main process terminates (otherwise the
rest of the package will try to run while the driver installer is still running).
 It should run silently, with no user prompts.

Note: If you are hosting packages on a web server running IIS 6.0, you may need to adjust the
security settings to allow certain file types (e.g. batch files) to be downloaded. By default, IIS6.0
won’t allow downloads of file types that are not explicitly allowed. See the following Microsoft
Knowledge Base article for details: http://support.microsoft.com/default.aspx?scid=kb;en-us;326965

To use custom drivers:

1. Open Pharos Administrator and go to the Spool Queues context.

2. For each Spool Queue you want to install, configure the Popup Printer Name property on
the Device tab. This name must match the name of the printer object that is installed by the
custom module.
3. For each Spool Queue you want to install, go to the Custom Drivers tab and configure the
following properties:
a. Click the editing box at the end of the Filename property and specify the custom
module file. If you are relying on users to manually install printers, and do not need
the package to do anything, leave this field blank.
b. Click the editing box at the end of the Module Behavior property and tick any
attributes that apply. You will most likely have to tick the “Module does not write a
results.txt file” attribute, unless your module produces such an output file. See the
Pharos Help for more information on custom module attributes.

You are now ready to build and distribute packages.

Custom Modules
In addition to installing Pharos components and Spool Queues, install packages can also run custom
user-created modules. Custom modules can be used to add customized functionality to install
packages.

Custom modules can run any sort of executable, batch file, etc. The function of these files does not
have to be limited to installing printers—custom modules can be added to install packages to
perform any other sort of function you might want the package to do. For example, you could create
a custom module that installs other third-party applications along with the Pharos components, or
runs a program that displays a more detailed list of Terms and Conditions than can be displayed in a

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

simple EULA text file, or runs a program to send a message back to the system administrator, telling
them that the package has been run on the client PC.

Custom modules are inserted and configured in Pharos Administrator at Distribution System >
Packages > Custom Modules. Once inserted, custom modules must be manually added to
Package Definitions by configuring the Custom Modules property of the relevant definitions.

Note: If you are hosting packages on a web server running IIS 6.0, you may need to adjust the
security settings to allow certain file types (e.g. batch files) to be downloaded. By default, IIS6.0
won’t allow downloads of file types that are not explicitly allowed. See the following Microsoft
Knowledge Base article for details: http://support.microsoft.com/default.aspx?scid=kb;en-us;326965

Using SSL in Lite Packages

Lite packages, which download modules from a web site, can run in an environment that uses SSL
to encrypt web communications. In order to use SSL with Lite packages:

 Make sure that the Package Download & Update Location on the System Properties dialog
starts with https://—this will instruct the packages to use SSL. (Remember to re-build all
packages after changing this property.)
 Make sure that all client PCs running Lite packages have an SSL certificate installed on
them. If your site uses SSL certificates from a certification authority such as Verisign, this
should already be the case. If you are using Pharos-supplied SSL certificates, you must
install the Pharos CA certificate on all client PCs. This certificate, PharosCACertificate.crt,
is available on the Pharos CD in the server\edi.net directory.

Command Line Options

The PackageBuilder.exe executable can be run from the command line to build packages:

packagebuilder.exe packageID

Where packageID is the ID number of the Package Definition to be built. If no ID is specified, or if

an ID of -1 is passed, the package builder will build all packages.

Note: To find the package ID for a package, run the open SQL Query Analyzer and run the following
query against the Pharos Database:

select * from packages

The following additional command line options are available for the package builder:

/v /b /s (Verify, Build, Synchronize)

These three options specify which steps in the package creation process the package builder should
perform (see above for details of each step). If none of them are specified, the package builder will
perform all three steps; otherwise it will perform only the steps specified.

/d (Debug mode)
This displays extra debug information on the package builder dialog as the package builder runs.

/q (Quiet mode)
Specifying this option means that the progress bar dialog is not displayed. This option overrides
debug mode.

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

The following command line options are available for package executables:

–autoreboot
Specifying this option means that the package will automatically reboot the PC after installation, if a
reboot is required.

–norepair
Specifying this option means that the package will not re-install any existing modules.

–quiet
Specifying this option causes the package to run silently, i.e. no dialogs are displayed to the user.

Diagnostics and Logging

The package builder and Map Builder executables produces debug logs using standard Pharos
logging. Use the Log Setter utility (available on the Pharos CD at tools\utilities\logsetter) to
configure and activate logging for Pharos Administrator—this activates logging for the package
builder and Map Builder as well. The package builder can also run in debug mode (see above).

When packages are run, they produce a log file called ControllerLog.txt in the Documents and
Settings\[username]\Local Settings\Temp\Pharos directory of the client PC. If the package install
failed, this file will contain an error message.

A file called [packagename]_instructions.xml is also created in the temp directory. This file lists
the modules that the package attempted to install.

Package Builder Warning and Error Messages

The package builder can display a variety of warning messages if it encounters anything suspect. All
messages are displayed on the package builder’s main progress dialog.
Warnings
These warnings are not necessarily error messages, and in most cases do not stop the package
creation process, although they may mean that certain modules or packages are not created.

Full Packages are created without an updater module. Lte packages are not created.
This indicates that the Package Download & Update Location property is blank (Pharos
Administrator > File menu > System Properties > Packages tab). In this case the package
builder will not create Lite packages and will not include the Updater in full packages.

The Package Build Location is not defined as a shared UNC. Access to package files may be a
problem.
This warning is generated if the Package Build Location property (Pharos Administrator > File
menu > System Properties > Packages tab) does not start with "\\", suggesting that it is not a
network share. This can cause issues when running the package builder on another PC, and it will
cause replication problems on Cluster servers if the Package Build Location is not shared.

Driver mismatch detected between QUEUENAME queue and associated printer PRINTERNAME
This warning is generated when a Printer associated with a Spool Queue uses a different driver than
the Spool Queue. This is not necessarily a problem, as there are driver families that are different but
still downwards compatible.

Print Server PRINTSERVERNAME needs a LPD server on the same machine

This warning is generated if the package builder cannot make a test connection to the Pharos LPD
Server on a Print Server. Every Pharos Print Server is expected to have an associated LPD Server.
9

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

Print Server PRINTSERVERNAME needs a Popup server on the same machine

This warning is generated if the package builder cannot find a Popup Server in the Pharos Database
for a Print Server. Every Pharos Print Server is expected to have an associated Popup Server.

There are no printers defined for queue QUEUENAME. Check "Related Printers" property in
administrator.
This warning is generated when the package builder does not find any Printers in the Pharos
Database that are associated with a Spool Queue. This does not affect package creation, but may
mean that the Popup Client installed by the affected package(s) will not be able to print to Pharos.

Printer \\SERVERNAME\PRINTERNAME is not shared. This module will not be built.

This indicates that a Spool Queue is not shared on its Print Server. Spool Queues used for packages
must be shared—the package builder will not build a module for this Spool Queue, and as a result,
packages that use this module will not be built either.

No Drivers included
The affected package contains no drivers, probably because it uses a Custom Module that has no
files specified for any of its operating systems. The package will still be built, and will install the
specified printer(s), but will not install the driver—it must be present before the package is run.

No Spool Queues included in package PACKAGE

A package usually needs Spool Queue modules, especially if it is installing Popups. The affected
package will still be built, but may not be suitable for deployment.

Module MODULE for OS is not mentioned in the manifest. This could mean that the packages using
this module have never been built.
Package PACKAGE for OS is not mentioned in the manifest. This could mean that the package has
never been built.
This warning appears during the Synchronization phase. A known module/package does not appear
in the Manifest.xml document. The usual reason for this is that it has not been built yet.

Module MODULE for OS is not defined in the database and therefore removed from the manifest.
Package PACKAGE for OS is not defined in the database and therefore removed from the manifest.
This warning appears during the Synchronization phase. A module/package has been removed from
the Manifest.xml document, as it appears to have been deleted.

File FILENAME is deleted because it is not known as one of the modules defined in the
administrator.
File FILENAME is deleted because it is not known as one of the packages defined in the
administrator.
This warning appears during the Synchronization phase. A file in the Package Build Location has
been deleted, as it does not appear to be a module/package.

The Spool Queue name “QUEUENAME” contains illegal characters from the following set:
/:*?<>|[]^%%"''=#@\!,. The module will not be built.
Spool Queue names must not contain any illegal characters; otherwise a printer object cannot be
created for the queues on client PCs. The module for the named Spool Queue will not be built, and
as a result, packages that use this module will not be built either.

10

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E
 Pharos Systems International TechNote: Pharos Install Packages and Mobile Printing
_____________________________________________________________________________________________________________

Errors
Queue name QUEUE may not contain a "\"
Package name PACKAGE may not contain a "\"
The backslash character (“\”) is not allowed in Spool Queue or package names. Any packages
whose names include a “\” and any packages containing Spool Queues with a “\” in their name will
not be built.

Missing package account details for print server SERVERNAME

A user name and/or domain name needs to be recorded for the Print Server at Printing > Print
Services > Packages tab. These details are needed to install printer drivers using PrintUI.
Packages cannot be created if these details are missing.

© 2006 Pharos Systems International. All rights reserved. Pharos and Uniprint are registered trademarks and SignUp, Off-
The-Glass and Blueprint are trademarks of Pharos Systems International. All other brands and their products are
trademarks of their respective holders and should be noted as such.

11

T
T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O T E T
E T E
T E C
E C H
C H N
H N O
N O T
O T E
T E T E C H N O
E