Pharos Omega PS150: Release Notes
 2.2.2 revision 9197

This document contains the release notes for this firmware release of Pharos Omega PS150. If you encounter any problems or require further assistance, contact your Pharos Authorized Reseller.

This Omega PS150 release supports version 7.2 and later of the Pharos Uniprint Suite and versions 3.5 R2 and 4.1 of the Pharos Blueprint Enterprise.

 Install Notes

  1. IMPORTANT: Plugging in the wrong power supply connector will DAMAGE the Thin Client!

    There are 2 power supply connectors - make sure you plug the correct power supply connector into the Thin Client. Please follow the installation guide when assembling the Omega.

  2. Hardware version

    This firmware release applies to the Omega PS150 hardware. It cannot be used with older Omega PS100 hardware, and older firmware versions (prior to 2.0) cannot be used with the Omega PS150 hardware.

  3. Apply schema to Uniprint 7.2 Database

    If you are using Omega with Pharos Uniprint UP 7.2, apply the Omega configuration schema to the Pharos Database after upgrading firmware to ensure that all new properties featured in this firmware release will be available in Pharos Administrator. Apply the schema by clicking Test Connectivity on the 'pedi.ini' screen of the Touchscreen configuration menu.

  4. Apply schema to Blueprint 3.5 R2 Database

    If you are using Omega PS150 with Pharos Blueprint Enterprise 3.5 R2, the configuration schema must be updated manually

    1. Rename the file PS150.terminal.config in the Blueprint\bin directory of the Analyst server to PS150.terminal.config.old.
    2. Rename the file ini_schema.xml (included in the firmware package) to PS150.terminal.config.
    3. Copy the new PS150.terminal.config file to the Blueprint\bin directory of the Analyst server.

    It is always a good idea to back up the database before applying changes.

  5. Omega requires Pharos Server installed with SQL Server 2000

    While Pharos Uniprint can be installed on SQL Server 2000 or SQL Server 7, Omega installs must use SQL Server 2000 (or MSDE 2000). If SQL Server 7 is used, Omega terminals may be unable to obtain their configuration information from the Pharos Database, and the error "'getutcdate' is not a recognized function name" appears at Omega terminals.

  6. Omega Web Administrator browser support

    The Omega Administrator web application (see below) can be viewed with Microsoft Internet Explorer 7.0 or later and Mozilla Firefox 3.0 or later. Other browsers, e.g. Opera, may work, but are not officially supported.

    Omega Web Administrator's Remote Control application, which allows you to interact with the Touchscreen remotely, requires version 1.4 or later of the Sun Java Runtime Environment.

 What's New in this Release?

  1. Support for Policy Print

    This version supports the Policy Print feature introduced in Blueprint Enterprise 4.1. Policies are enforced at the Omega terminals for copying. When users attempt to copy that would trigger a rule that applies to them, the Omega terminal will display information regarding the policy and the corresponding rules. The Omega cannot enforce the Deny Color Copying Policy using the copier's FDI but it will display the deny message.

  2. Support Card Registration on Blueprint Servers

    Blueprint authentication scripts can be written to support registering a card swipe against an authenticated logon ID entered via the keyboard - contact Pharos Support for details.

  3. Improved security

    The configuration "Allowed Printer MAC Address" in the Omega Web Administrator at Network > PRINT restricts the printer that can connect to the PRINT port.

    Also, the SSH server and keyboard console interface have been turned off.

  4. Replicate configuration via USB drive

    A blank USB memory stick inserted into the Omega will be reformatted and with the Omega configuration. When the USB stick is inserted into another Omega, the configuration on the USB stick will be copied to the new Omega.

  5. Firewall mode opens all ports

    Firewall mode initially allows any PC to print to the printer. The Firewall can then be configured to restrict what PCs can print to the printer.

  6. Manually load a list of other Omegas

    A line separated list of other Omega hostnames can be manually loaded onto the Omega using Web Administrator > System > Transfer Files menu.

  7. "Users must have Cost Centers to Logon" configuration option

    A new configuration option Users must have Cost Centers to Logon has been added to restrict who can logon to Omega when a Charging Model is configured.

  8. Simpler view of demo.xml content

    The demo.xml content can be more easily viewed in the Web Administrator > Station > Show Demo Data menu.

  9. Set time zone for each terminal

    By default, the Omega uses the EDI server time zone. This can be overridden in the Session > Time Zone configuration option in the Pharos Administrator.

  10. Filter Recent Log

    Web Administrator > System > Recent Log can be filtered and downloaded for future analysis.

  11. Copier Learner tool supports more copiers

    The Copier Learner tool has been modified to support learning the Konica Minolta Foreign Device Interface (FDI).

 User Interface Changes

The following changes have been made to the end user interface at the Omega Touchscreen:

 Known Issues

  1. Upgrading from 2.2.0 requires manual migration

    The Pharos Server Administrator > Terminals > Logon > Authentication Method option must be set manually to Server Config after upgrading from 2.2.0.

  2. Using a Billing Gateway with Omega

    If Omega terminals are being used with a Pharos Billing Gateway and users do not have accounts in the Pharos system, a script with the following content must be created and attached to the Bank's Logon event:

    PlugIn.Result = true;

    A Billing script is also needed if you wish to use the Blackboard TIA gateway with arrears accounts - contact Pharos Support for details.

  3. Omega requires Pharos certificates for SSL

    The SSL certificates used by Omega are certified to have been generated by Pharos Systems. If your EDI Server is using a certificate generated by another certification authority, then the Omega devices that communicate with it will not work. Contact Pharos for assistance in adding a CA certificate to your Omega devices.

  4. Server name restrictions when using SSL

    When using SSL, server names cannot contain the underscore character ( _ ).

  5. Known Issues with Omega Web Administrator

    The following Known Issues exist for the Omega Web Administrator application:

    • Using the web browser's Back and Forward buttons is not recommended while using Omega Administrator.
    • If the Remote Control screen is left idle for a long time it may not respond well. Click the Remote Control link again to reload the page.
  6. Sixteen copy lines not supported

    Although it is possible to configure up to 16 copy lines, Omega supports a maximum of 8. Configuring 16 copy lines can cause the Omega to crash and reboot. If an Omega is in a corrupt state due to the use of 16 copy lines, you must use the copier training wizard at the Touchscreen to re-configure the copy lines (up to a maximum of 8).

  7. Possible time discrepancies

    When the Omega starts up, it reads the time from the BIOS. When it first contacts the Pharos EDI Server, it receives the correct system time; however, this does not update the BIOS time. This means that it is possible in some situations for the wrong time (i.e. the BIOS time) to be displayed. Any such discrepancies should not stay for long, as the correct time will be retrieved as soon as the EDI Server is contacted. If this does cause problems, you may need to update the BIOS with the correct time.

  8. Communication timeout may be longer than configured

    Since Omega re-tries to connect to the EDI Server if the first connection attempt is not successful, it may take longer for the communication attempt to timeout than the time configured for the Timeout option on the PEDI screen of the Touchscreen configuration menu.

Copyright © 2010 Pharos Systems International