Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
6Activity
0 of .
Results for:
No results containing your search query
P. 1
Pharos Install Packages and Mobile Printing

Pharos Install Packages and Mobile Printing

Ratings:

4.33

(3)
|Views: 1,732|Likes:
Published by Kevin Severud
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.
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.

More info:

Published by: Kevin Severud on Jul 20, 2007
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

10/23/2012

pdf

text

original

 
 
Last Updated 09/20/06
TECHNOTE
 
EEECCCHHHNNNOOOTTTEEETECHNOTETTTEEECCCHHHNNNOOOTTTEEETECHNOTETTTEEECCCHHHNNNOOOTTTEEETECHNO
Pharos Systems
illuminate
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 wellas installing the client application(s), they can set up one or more Pharos Spool Queues as printerson the local PC. Because they are completely self-contained, they can be distributed to users, whodownload and install them on their personal laptops or PCs, allowing them to print to the Pharossystem without the need for a staff member to install Pharos software for them. Install packages canbe created for Windows 2000, XP and 2003.Packages are created from Pharos Administrator, based on the print drivers available on PharosPrint Servers. An install package consists of a collection of
modules 
. The modules included in apackage are chosen in Pharos Administrator (see below), but a package usually contains theinstaller modules for the Popup and Notify Client and one or more Spool Queue modules, which setup 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 detectthe 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 copyingthe packages to a share that all users have access to, or placing them on a website where users candownload them themselves (a website is required to make use of Lite packages, or if you want theinstalled components to be able to automatically download updates).Packages can optionally include an End User License Agreement (EULA), which users must readand accept before the package installs any files.
Creating Install Packages
Install packages are created in Pharos Administrator. The process of creating install packagesinvolves 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 Queues3. Configure global properties in Pharos Administrator4. Set up Package Definitions5. Build packages based on the definitionsOnce created, install packages can be made available for end users to download and install, or theycan be distributed to client PCs by whatever method you prefer, e.g. installing manually or using anautomated software installation utility like Microsoft Systems Management Server (SMS).
 
Pharos Systems International
TechNote: Pharos Install Packages and Mobile Printing  _____________________________________________________________________________________________________________
 
2
Preparing the Web Site (Optional)
If packages are to be made available for download, or if you want to use Lite packages or automaticupdates (which download the necessary modules from a web server or network share), the webserver 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. Ifa 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 tothe 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 Uniprintdirectory into a network share with appropriate permissions, then change the
Package BuildLocation
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 updatethe
Package Build Location
and
Package Download & Update Location
properties andregenerate all packages.
Note:
Packages and modules can be made available for download from a network share, rather thana web server. In this case, the Package Download & Update Location should start with
file://
, ratherthan
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 foreach 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 canattempt to give the new printer the same settings as the Spool Queue’s printer, i.e. the printer objecton the Print Server that is created when the Spool Queue is first inserted. If you want installpackages 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 thedesired printer and select
Properties
. Note that the properties on the General tab of the Propertiesdialog only affect the current user, and will not be picked up by the Package builder. To change thesettings for all users, click the
Printing Defaults
button on the Advanced tab, and configure theoptions on the dialog that appears.Finally, you can also specify the name that will be given to printers installed for each spool queue byediting the
Popup Printer Name
property on the Device tab (if no name is specified, the installedprinter's name will default to "<spool queue> on <server>").
EEECCCHHHNNNOOOTTTEEETECHNOTETTTEEECCCHHHNNNOOOTTTEEETECHNOTETTTEEECCCHHHNNNOOOTTTEEETECHNO
 
Pharos Systems International
TechNote: Pharos Install Packages and Mobile Printing  _____________________________________________________________________________________________________________
 
3
Configuring Global Properties
Global properties affecting install packages are available on the Packages tab of the SystemProperties dialog (File menu). Three properties relate to the creation of install packages:
 The
Package Build Location
property determines the location that install packages will beplaced in when they are created.
 The
Package Download & Update Location
property sets the URL that packages andmodules will be available from. This is the URL that Lite packages will download modulesfrom. It is also used by the updater module (see “Updating Packages” below). The URLspecified 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 EULAfiles and custom modules (see below) are copied.The Package Build Location and Package Download & Update Location properties are automaticallyconfigured if the Uniprint Web Site is installed. Ideally, they should point to the same location—thisway, files are generated straight into the directory where they will be downloaded from. If they arenot the same, you must copy files from the build location to the download location manually. In thiscase, you must preserve the directory structure set up in the build location (i.e. packages in the rootdirectory, modules in a subdirectory called
modules
).
Note:
Packages and modules can be made available for download from a network share, rather thana web server. In this case, the Package Download & Update Location should start with
file://
, ratherthan
http://
.On the Packages tab you can also specify how often components should check to see if updatedcomponents are available (see ”Updating Packages” below).
Setting up Package Definitions
Install packages are created according to Package Definitions, which contain information on thecontents and properties of install packages. Package Definitions are set up in Pharos Administratorat
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 SpoolQueue in the Pharos Database by clicking the button.
 You can use the Package Definition Insert Wizard to create a single definition, which maycontain 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 itready 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, eachdefinition 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 basedon Spool Queues, each definition will contain only the Spool Queue module for the queue itapplies to.
 The text file containing the EULA (if one is to be used). This file will be copied to the ShardDirectory (see above).
 The Pharos-supplied modules to include. The Notify module is always included; Popups, theuninstaller and the updater are optional—see “Which Modules to Include?” below.
EEECCCHHHNNNOOOTTTEEETECHNOTETTTEEECCCHHHNNNOOOTTTEEETECHNOTETTTEEECCCHHHNNNOOOTTTEEETECHNO

Activity (6)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Ole Seim liked this
Austin Lockman liked this
Piotr Korkuz liked this
hasnan_atm liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->