1. Pharos Uniprint 8.3 Training
This training course explains new features in Uniprint 8.3, as well as how to upgrade to Uniprint 8.3. In addition, it also details impacts of an upgrade to your existing installation.
Pharos Systems International
June 2012

2. Agenda New Pre-requisites New Features
Changes in the Uniprint print engine
Changes in Pharos Administrator
New Administrator Tools
Changes in the installation and upgrade process
Removed Features
Welcome to the Pharos Uniprint 8.3 Training. This training session provides an overview of what’s new and what’s been changed in Pharos Uniprint.

3. Release Highlights Microsoft SQL Server 2012 Support
Mac OS X 10.7 support for Popup and SignUp clients
Support for Pharos MobilePrint
Print Engine redesign
Revised Administrative Permissions
Strong Passwords for User Accounts
Checking device state before sending print jobs

4. Uniprint 8.3 New Pre-requisites
.NET Framework 4.0 (for Print Servers) – in addition to the .NET 3.5 SP1
SQL Server 2012
Popup and SignUp clients now support MAC OS X 10.7
Uniprint 8.3 adds the following pre-requisites
In addition to the .NET Framework 3.5 SP1, Print Servers now require .NET Framework 4.0
SQL Server 2012 is now supported
MAC OS X 10.7 is now supported on Popup and SignUp clients

5. Pharos MobilePrint Overview
This section describes the components of a MobilePrint system and explains the MobilePrint workflow.

6. Support for Pharos MobilePrint 1.2.0
Students and staff can now print from a variety of mobile devices – smartphones, tablets, and laptops.
Students documents from any Mobile device to MobilePrint
Students register address*
Terminals show print jobs ready for release
Students collect their print job from the Device
Uniprint 8.3 has been redesigned to support Pharos MobilePrint. MobilePrint enables users to print securely from any mobile device such as a smartphone, tablet, or laptop to any Pharos managed printer within the campus.
The following scenario illustrates a typical user experience with Pharos MobilePrint:
Send documents to print - From any mobile device, the user sends or forwards documents to print (as attachments) to the address set up for MobilePrint (e.g.
Register Address – If user’s address is not recognized by MobilePrint, they will receive a reply to register their address. The contains a link to the MobilePrint registration website.
Release the documents - The user walks up to a Pharos Release Station (e.g. Omega Terminals, Pharos Station), authenticates, and then selects the document to print.
Pick-up the documents - The user picks up the document from the printer.
*First time MobilePrint users must register themselves for validation.

7. Benefits of Pharos MobilePrint
Easy to use
Supports a variety of mobile devices
Device Independent
Document security and confidentiality is maintained
Supports a large number of file formats
Benefits/Key Features of Pharos MobilePrint
Easy to use – No print drivers required and no software application needed to be installed on the user’s device. MobilePrint works virtually on any internet and capable devices. All the user needs is a valid user account.
Supports a variety of mobile devices – smartphones, tablets, and laptops. Supports Android, IOS, BlackBerry
Device independent – users will be able to release their print jobs anywhere on any device. It supports a variety of print vendors/manufacturers.
Document security and confidentiality is maintained because it works with Secure Release Here technology
Supports a large number of file formats (Word, Excel, Outlook, CSV, etc.).

8. MobilePrint Components
MobilePrint Workflow Service – index and download print job s.
MobilePrint Worker Service – converts documents to PDF and PDF to PDL
MobilePrint Authenticator – validating s
Before configuring MobilePrint, it is important to understand the components that make it up. MobilePrint is composed of the following components
Workflow Service - Manages MobilePrint Workflow. Its main task is to index and download print job s.
Worker Service - Allows documents to be printed. It converts different document types (.doc, xls, pptx, etc.) to Portable Document Format (PDF). It also converts print jobs from PDF to the Page Description Language (PDL).
Authenticator - Responsible for validating any s stored in Uniprint. In addition, it is also for authenticating user IDs and passwords for registration. The user can register extra accounts if their ID and password can be authenticated by Uniprint using this component.

9. MobilePrint and Uniprint integration
The following diagram illustrates the architecture of MobilePrint, showing a simple installation scenario of one MobilePrint Server and several Uniprint Print Servers.
The user sends and/or attachments from their smartphones/laptops/desktops to the address configured for MobilePrint (e.g.
The University Server receives the s. The “MobilePrint Workflow” Service polls the Server for new s and documents and then downloads them for rendering by the “MobilePrint Worker Service”.
The “MobilePrint Worker Service” converts the documents to Portable Document Format (PDF).
The “MobilePrint Worker Service” sends the converted documents to the Uniprint Print Server. If there are multiple Uniprint Print Servers, MobilePrint randomly selects one to hold the jobs.
The selected Uniprint Print Server holds the documents until they are released by the user.
The user walks to a Release Station, authenticates, and releases their documents.
When the documents are released, the Uniprint Print Server forwards them to the “MobilePrint Worker Service”.
The “MobilePrint Worker Service” converts the PDF document(s) to the Page Description Language (PDL) of the relevant print device.
The “MobilePrint Worker Service” sends the documents to the printer associated with the Release Station.

10. Uniprint Print Engine Redesign
One of the major changes in this version is the redesign of the print engine. This section will explain the changes made to the Uniprint architecture as well as its impact to an existing Uniprint installation.

11. Print Engine Redesign
Removed dependence from Windows spooler and its driver management
Jobs are no longer held in the Windows spooler
Job details cannot be seen by other users from the Windows Queues
New Secure Release Service
Job management
Page counting
New Print Groups concept
Maximum job holding time increased from 2 days to 7 days
Changes to Devices
Changes to Queues
Removal of dependence from the Windows Spooler
In Uniprint 8.3, secure jobs are no longer held in the Windows Spooler. After a user sends print jobs to the Queue, they are immediately transferred to the Application Data folder.
New Secure Release Service
Uniprint 8.3 introduces the new “Secure Release Service”. This is the component that handles print jobs. In previous versions, the Print Service controls all print and copy related processes on a site, including billing and authentication. In this version, the Secure Release Service takes over some of the print job management task from the Print Service.
Handling of jobs – The Print Server is no longer responsible for maintaining the list of jobs in its internal database; this is now handled by the Secure Release Service. Print jobs are stored in the Application Data Path until they are released by users or are purged after the Reprint Holding Period expires.
Page Counting - The Secure Release Service is now responsible for page counting jobs.
Maximum job holding time
In previous versions, the maximum Purge Time (length of time a Secure Release job is available for release after it is submitted) was set to 2 days. Now, you can set jobs to remain in the Secure Release job store for up to 7 days.
New Print Groups concept, changes to Devices, and changes to Queues will be discussed in the succeeding slides.

12. Earlier versions
Print Server centric - print jobs can only be released from devices belonging to the same Uniprint Print Server
Jobs are held in the “Held” Queues
Compatible Queues were introduced in 8.0
In earlier versions of Uniprint, print jobs can only be released from devices on the same Uniprint Print Server. Users send their document to a queue on one server and are able to release those jobs only on the devices associated to the Queue on the same print server.
To allow users to release jobs from devices controlled by any Uniprint Print Server, Compatible Queues were introduced in 8.0. It allowed queues to be specified as compatible so that a job submitted to one queue can be printed successfully by the other.
Uniprint 8.3 introduces the Print Groups concept to streamline the configuration of large group of printers particularly in multiple server environments.
The following slide provides more information about Print Groups.

13. New “Print Groups” concept
Enables users to release jobs at any device within the Print Group regardless of Print Server
Queue is now associated to a Device via a Print Group
Removed Devices and Uniprint Print Server relationship
Removed Compatible Queues concept
Uniprint 8.3 introduces the “Print Groups” concept. The idea is to group devices with compatible drivers. This enables users to release submitted jobs at any device within the group.
The introduction of Print Groups brought about these changes:
Replaced the Queue - Device relationship. Queue is now associated to a device via a Print Group
Removed Devices and Uniprint Print Server relationship
Removed Compatible Queues concept
All jobs sent to a Queue will be available at any device that is within the group. In the diagram shown, print jobs submitted to the Queues on either Print Server A or Print Server B can be released from any of the three devices within Print Group1.

14. New Print Groups concept
All printers in a Print Group must have compatible print drivers
Make sure that the “Queue” and the “Devices” have compatible print drivers
Direct Queues – likely to have one-to-one relationship
All printers in a group must have compatible printer drivers and capabilities. Uniprint does not check for this - you must ensure that any printer you associate with a Print Group is compatible with the other devices in the group.
Moreover, Queues and Devices in a Print Group must also use compatible printer drivers. The system does not check that the Queues and Devices you select have compatible drivers.

15. Mobile Print Group Default Print Group for Pharos MobilePrint
Each new device is added automatically to this group
Does not require a Queue like standard Print Groups
In order to seamlessly work with MobilePrint, Uniprint ships with a default Secure Print Group called Mobile Print Group. This Print Group is used if the Pharos MobilePrint Solution is installed.
Unlike standard Print Groups, you do not have to manually associate Devices to the Mobile Print Group – each time a new device is added to Uniprint, it is automatically added to the Mobile Print Group. However, devices can be removed from this group if necessary.
While standard Print Groups require a Queue, MobilePrint Group does not need a Queue.
For more information, refer to the “MobilePrint and Uniprint Integration” document.

16. Changes to Devices Only network printers are supported
Windows printer objects are no longer created for devices
Devices must now be associated to a Print Group instead of a Queue
Devices in Pharos Administrator no longer require print drivers
In Uniprint 8.3, only network printers are supported, therefore each device will require a Network Address (hostname or IP address) in order to print jobs.
As shown in the diagram, Windows printer objects are created only for Queues, but not for Devices.
While Windows queues are still used as a mechanism to receive print jobs from users, output devices no longer require a Windows printer object. In addition, devices no longer require print drivers association.

17. Pharos Administrator Changes
This section describes the changes made to Pharos Administrator, including new Administrator tools.

18. New Print Groups context
Added Print Groups context under Output Management
The following Queue properties are now in the Print Groups context: Queue Type (now called Print Type), Purge Time, Job Cost Method, and Banner.
The mode of printing (whether Secure or Direct) is now specified per Print Group instead of per Queue
A new Print Groups context has been added under Output Management. In this context, you can:
Insert New Print Groups
Select the Print Type (whether Secure Release or Direct).
Delete existing Print Groups
Add Related Printers and Queues
In older versions, the mode of printing (whether Held or Direct) was specified per Queue. This is now specified for Print Group.

19. New in Devices context - Device State Check before printing
Jobs sent only to “online” devices
Users are not wrongfully charged
New device property – “Execute online state check before printing”
View problematic devices from Pharos Administrator
Run manual device state check if necessary
Uniprint 8.3 has added a mechanism to check whether a device is online before sending print jobs to it. This is to make sure that jobs are sent only to “online” devices and to prevent wrongfully charging users.
Device state check is controlled by the new device property “Execute Online State Check before Printing”. If this property is enabled, the status of a device is determined before sending print jobs. Uniprint performs an SNMP query to determine the error state of a given device, and based on the response, it decides if it is “Online”, “Offline” or “Unknown”. This check is performed just before jobs are released to the device.
In Uniprint 8.3, the Pharos Administrator will now display an appropriate warning or information message based on whether the device is reporting Online, Offline or Unknown. This helps inform an administrator of any issues with the device which are preventing print jobs from being released. The display of a warning message about the state of a device will be visible on both the Devices and the Output Management > Overview contexts.
If a device is presumed to be not functioning or if a user reports printing related issues, a manual device state check can be run using the Run Online State check action from the Devices context.

20. New in Devices context – Retrieve Make and Model
Make and Model properties are required for Pharos MobilePrint
Method of Determining Make and Model property determines how to obtain these properties for a device – whether “Automatic” or “User Specified”
Added a new Retrieve Make/Model action
The Make and Model properties of a device are required for Pharos MobilePrint. They are used to map a device in Uniprint to a print driver in Pharos MobilePrint so that jobs can be released.
The new property called Method of Determining Make and Model indicates how the Make and Model of this device is determined. This information is retrieved using Simple Network Management Protocol (SNMP). The method of determining Make and Model can be any of the following:
Automatic - This is the default value. The Make and Model properties for this device are automatically retrieved based on its IP address and SNMP properties. Changing the IP address of a device will change the Make and Model of a device automatically. A warning message is shown if they cannot be retrieved. To retrieve Make and Model properties for a device:
Enter a valid IP address or hostname
Ensure device supports SNMP
SNMP is enabled/SNMP info is correct
SNMP port is open
User specified - Selecting this option lets you manually enter the Make and Model properties for this device.
Retrieving Make and Model Manually
Uniprint does not constantly poll the device for new SNMP information; therefore the values shown in Pharos Administrator may be inaccurate. For example, if an IP address has been assigned to a different device, the Make and Model shown will be that of the device originally assigned the IP address and not of the new one. Use the Retrieve Make and Model action to obtain the most recent Make and Model properties for a device.

21. New in Devices context – Sending a Test Page
Send a Test page from within Pharos Administrator
Confirms whether a device can receive jobs from the Uniprint Print Server
Test does not include checking the state of the device
It is now possible to print a test page for each device within Pharos Administrator using the new Send Test Page action in the Devices context. This is useful if you want to determine whether a printer can receive jobs from the Pharos Print Server.
In previous versions, this was accomplished using the Print Test Page in Microsoft® Windows. However, because Uniprint no longer creates Windows printer object for a device, so this is no longer possible.
Take note that this test does not include checking the state of a device.

22. Changes to Queues
Print Jobs are no longer held in the Queues. Jobs are held in the Application Data folder (set up during Print Service install).
The Windows printer object for a Queue were in “Paused” state in earlier versions, now it is in a “Ready” state.
Job Cost Method is no longer configured on a per Queue basis – it is now on a Print Group basis.
Jobs cannot be moved between Queues, they are now moved between Print Groups.
In previous versions, print jobs were held in the Queues. In Uniprint 8.3, jobs are held in the Application Data folder as shown in the image.
Costing for print jobs is now based on the Job Cost Method associated with a Print Group. However, the copy functionality of a device is not part of a Print Group. Job Cost Methods are still associated to copiers in the Devices context. This means that the costing for copy jobs is based on the Job Cost Method associated to the Copier.
If the device has both Print and Copy functions, the costing for print jobs will be based on the Job Cost Method defined for the Print Group while the costing for copy jobs will be based on the Job Cost Method associated with the Copier.

23. Changes to Job Management
Queued and printed jobs are retrieve by username and/or Print Group
In previous versions, Queued Jobs and Printed Jobs contexts used to display all jobs from all print servers. In Uniprint 8.3, a new panel is added, which retrieves jobs based on the username of the one who sent the job and the Print Group that it was sent to.

24. Changes to Job Management context – Saving Spool Files
Save spool files from Pharos Administrator
Spool files will be stored in the Pharos\Temp (e.g. C:\Program Files\Pharos\Temp) folder of the Uniprint Print Server owning the job
Uniprint enables you to easily save the spool file of specific print jobs directly from Pharos Administrator using the Save Spool File action in the Devices context.
The spool file for the selected print jobs will be stored in the Pharos\Temp (e.g. C:\Program Files\Pharos\Temp) folder of the Uniprint Print Server owning the job.
A report file called SpoolFileInfo-<date><time>.txt is also saved in the same location as the spool file. It shows a list of the jobs selected, including the Print Server where they belong, which will help you easily map the spool file with its Print Server. This is important for multiple server environments.

25. Changes to Permissions
New “Management Zone” concept introduced – for finer grained permissions
“Permission to Create objects” added
New Management Zones
The Server Management section has been removed and this functionality has been replaced by Management Zones. Each object in Uniprint belongs to a zone; you simply create administrative roles that have different levels of permissions to view, modify, create, or delete objects in the different zones. The Zone functionality allows you to easily delegate administrative duties to different departments (e.g. to manage their own devices) even when they are sharing the same server resource.
Three new actions related to Management Zones have been added: Insert Management Zone, Delete Management Zone, and Reassign Zone.
Permission to Create objects
The Permission to Create Objects section has been added to the Basic Permissions View. It enables you to control the objects (e.g. Devices, Print Groups) a given role can create. For example, you can grant a role the permission to create all the Output Management objects but not Packages and System objects.
It is also where you assign to which Management Zone the new objects will be grouped. This saves you from having to specify the Management Zone for each newly created object. When creating a new object, it automatically assigns the Management Zone that you have selected in this section.

26. Changes to Permissions
The Server Manager (Template) has been removed and replaced with the new Sub-Administrator (Template).
A new Access Context permission has been added to the Advanced Permissions View.
Sub-Administrator Template
The Server Manager template has been removed in 8.3 and has been replaced with the Sub-Administrator template.
The new Sub-Administrator template is suitable for cases where you want to create a role that has more privileges than a Cashier or Proctor but has fewer privileges than the Administrator. However, this template does not have all the privileges that the Server Manager used to have such as creating roles, changing privileges of roles, and copying permissions from another role. It also doesn’t allow creating or deleting zones.
Access Context
A new type of context-level permission called “Access Context” has been added to Permissions. It determines whether a Pharos Administrator context is visible in Pharos Administrator or not.
This is available only when editing a role from the Advanced Permissions view.

27. Changes to System Settings
Enforce strong passwords
A new section in the Security tab of the System > System Settings allows you to select whether to enforce strong password or to allow the Password field to be blank.
A new section in the Security tab has been added, which is used to define the password policy for User Accounts has been added. You can choose either or both of the following options:
Password cannot be blank
Enforce Strong Passwords
If the "Enforce Strong Passwords" setting is enabled, the password you set for a user account must meet the following requirements:
At least 6 characters long
The password should contain characters from at least three of the following:
upper-case (A - Z)
lower-case (a - z)
numerical digits (0-9)
special characters
Should not contain three or more characters from the user's Logon ID

28. New Administration Tools
New Insert Assistant
Instead of setting up components from several contexts in Output Management, the tool provides a single user interface to set up a device. It does not only gather device details such as Name, Device function (e.g. Print or Copy) and Network Address, it also enables you to associate the new device to respective Print Groups and Release Stations (if configuring Secure Release Here™).
The Insert Assistant can be accessed from the Overview or Devices context of Pharos Administrator.

29. Other Changes
This section describes the changes made to Pharos Administrator, including new Administrator tools.

30. Changes to the Scripts/Plug-ins
Due to the changes in the print engine, some scripts have changed.
The "MoveJob" plug-in has changed. In previous versions, jobs were moved between Queues. In 8.3, a job now belongs to a Print Group instead of a Queue; therefore jobs are now moved between Print Groups instead of Queues.
A new function "PrintJob.SaveTo(…)" is introduced to save a copy of the Print Job to a local path.
A new function "Plugin.JobType" is introduced to determine the type of job (whether Native or Mobile jobs).
"Win32.GetJob(…)" no longer supports retrieving values for PrintProcessor, DriveName, Priority and Position
"Win32.SetJob(…)" can only set two fields - username and job name.

31. Changes to the Installation Process
New Application Data directory
Location where jobs are temporarily stored
Accept default or specify new location
For clusters – shared disk location
After install or upgrade, the following folders will be created:
Database
JobOperationsPlugins
JobStore
PageCounting
During a Print Service install, you are required to enter an Application Data directory. This is where print jobs are temporarily stored until they are released by users or are purged as per the Purge Time period set in the Print Group. As mentioned earlier, in previous versions jobs were held in the Windows spooler.
You can either accept the default location or specify a different location. If specifying a new install path, the following rules apply:
Do not use Unicode characters
Do not use Network paths
For cluster installs, ensure that you use a shared disk location for both nodes.
The following Application Data folders will be created after install or upgrade of Uniprint 8.3:
Database- holds the Secure Release Service SQL Lite DB
JobOperationsPlugins- holds any plug-ins installed, For example if MP is installed, this folder contains all the MobilePrint plugins.
JobStore-holds the spool files
PageCounting- This holds the spool files when Page Counter fails. This depends on the StoreFiles registry entry. For more information, refer to the Online Help.

32. Changes to the Upgrade Process
New Print Migration Tool – helps identify Uniprint managed devices that:
Cannot be upgraded successfully
May need to be reconfigured
Can be run on the Principal Server or a Print Server which has access to all the other Print Servers
Any devices managed by Uniprint will be checked if the port of the device is a TCP/IP port. If the port is TCP/IP, then the device is compatible with the upgrade.
Devices of other port types such as older serial or parallel ports are not compatible with the upgrade and they cannot be used from 8.3 or later versions. The Print Migration Tool will generate a report showing a list of devices that are incompatible for the upgrade. These devices can be reconfigured (e.g. change devices with COM or LPT ports to use TCP/IP ports).

33. Upgrade Impacts – Output Management
Inbound Queues are redirected to use the new “Secure Release Port”.
New Print Groups will be created during upgrade. For every Queue in the system, Print Group is created automatically created based on the name of the Queue. The Print Type will be based on the Queue Type.
Queues will be retained, and will be associated with the newly created Print Groups.
Device and Queue relationships will be removed.
Compatible Queues will be removed.
Windows printer objects for devices are deleted unless it can’t confirm the port as TCP/IP.
Banner Template Type content will be migrated to the database.

34. Upgrade Impacts - Permissions
Existing roles will have “Access Context” permission on a context if they previously had any permission that allowed access to the context (e.g. Read or Update).
While user-created Roles are migrated in an upgrade, any changes to them may not work as expected in 8.3. It is best to create new roles when editing configuration or implementing new permission functionality such as additional zones.

35. Upgrade Impacts – Scripts/Plug-ins
If an existing installation has the MoveJob plug-in, the upgrader will stop.
If your current system uses plug-ins with the following script functions and you are integrating with Pharos MobilePrint, you have to modify your scripts to use the PlugIn.JobType function.
MessageBox
QuestionBoxInt
QuestionBoxList
QuestionBoxMoney
QuestionBoxString
BalloonBox