Pharos MobilePrint 1.3.2: Release Notes

Version 3

    Welcome to Pharos MobilePrint 1.3.2. This Service Pack includes new features, several major enhancements, and bug fixes to improve the performance, security, and stability of Pharos MobilePrint.

    This Service Pack can be used to directly install MobilePrint or can be used to upgrade MobilePrint 1.3.1 General Release. If you encounter any problems or require further assistance, contact your Pharos Authorized Reseller.

     

    Notes

    • This Service Pack should be applied to all machines hosting MobilePrint server components (e.g. MobilePrint Worker, MobilePrint Workflow).
    • This Service Pack can be applied to MobilePrint 1.3.1 General Release only. If upgrading from MobilePrint 1.2.0, you must first upgrade to MobilePrint 1.3.1 General Release before upgrading to MobilePrint 1.3.2.

     

    Install and Upgrade Notes

    1. Ensure Windows Firewall Service is started before installing MobilePrint
    2. Supported Operating Systems
    3. Supported Pharos Servers
    4. Microsoft® Office as a document renderer
    5. Supported Web browsers
    6. HTML Support
    7. Install a CA signed certificate for the MobilePrint Website
    8. Windows 2008 Interactive Services Detection
    9. Verify that DNS is set up and working correctly

     

    New Features and Enhancements

    1. Support for Windows Server 2012
    2. Support for IBM® Lotus®  Domino®  Server and IBM®  Notes®  client
    3. New document types supported
    4. Simplified MobilePrint Configuration for Blueprint Enterprise integrations
    5. Improved Pharos MobilePrint Web Release website
    6. Improved email address registration
    7. Blueprint Guest Printing Changes
    8. Display status of Pharos Servers
    9. Whitelisting or blacklisting of email domain names

     

    Known Issues and Limitations

     

    1. Pharos MobilePrint does not support Google’s 2-step verification
    2. Print jobs forwarded multiple times via Microsoft Outlook App may fail to render properly
    3. Pharos Web Release does not support changing the finishing options for native jobs
    4. Pharos Uniprint Features unable to be supported by MobilePrint
    5. MobilePrint does not support Policy Print and Delegate Printing features of Blueprint
    6. Log file error messages when emails are discarded
    7. Duplicate images on iOS devices
    8. Known limitations when using billing gateways for charging MobilePrint jobs

     

    Install and Upgrade Notes

     

    Warning: Blocked Files

    Depending on how the MobilePrint installer files were copied to the target machine, some of the files may have been “blocked” by Windows. Trying to install or upgrade MobilePrint with a blocked file will most likely prevent that component from working correctly. To check whether a file is blocked and/or unblock it, right-click the file in Windows Explorer and select 'Properties'. If it is blocked, you must first unblock it before proceeding with the MobilePrint install. For more information, navigate to http://support.microsoft.com/kb/883260.

    • Ensure Windows Firewall Service is started before installing MobilePrint

    Before installing MobilePrint, make sure that the “Windows Firewall Service” is started; otherwise the installer will fail and will roll back the installation.


    • Supported Operating Systems

    MobilePrint 1.3.2 installation of services is supported on 32-bit and 64-bit versions of Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012.


    • Supported Pharos Servers

    Pharos MobilePrint 1.3.2 supports the following Pharos Servers:

      • Blueprint Enterprise versions 5.0 (with Service Pack 3)
      • Blueprint Enterprise 5.1 (with Directory Service Patch)
      • Pharos Uniprint 8.3 (with Service Pack 1)
      • Pharos Uniprint 8.4

    • Microsoft® Office as a document renderer

    Out of the box, MobilePrint works without Microsoft® Office and most documents will print exactly as the user would expect. Some complex documents created with MS Office specific tools or functions  may not. If you find that this is an issue, consider installing Microsoft Word on the MobilePrint  Worker Server (server on which MobilePrint Worker Service is installed). If Microsoft Office is installed, MobilePrint will use it to render documents and an even higher level of print quality and document fidelity can be achieved.

     

    Note: If you decide to install Microsoft Office for high document fidelity, please note of the following:    

            
    • If installing Office 2007, install the Microsoft  “Save as PDF Add-in”.  This converts Microsoft Office documents to PDF. You can download this add-in from: http://www.microsoft.com/en-us/download/details.aspx?id=7. Office 2010 natively supports converting documents to PDF format.
    • MobilePrint 1.3.2 does not support Microsoft Office 2013 as a render engine.
    • Make sure that the Microsoft® Office installed on your MobilePrint Server conforms to your licensing agreement with Microsoft.
    • If your MobilePrint deployment includes multiple Worker Servers, Pharos recommends installing Microsoft Office on every Worker Server to avoid possible inconsistencies in print quality.

    • Supported Web browsers

    Pharos MobilePrint Web Administrator and email address registration require web browsers. MobilePrint has been tested with the following browsers.

     

    • Internet Explorer 9.0 and 10.0
    • Mozilla Firefox 24
    • Google Chrome 29
    • Apple Safari 5.1.7

    • HTML Support

         MobilePrint supports printing HTML formatted emails, i.e. the body of the email itself is in HTML format. However, printing HTML attachments or links is not

    yet supported in this version.

     


    • Install a CA signed certificate for the MobilePrint Website

        MobilePrint websites should have a Certification Authority (CA) signed certificate installed.By default, MobilePrint installs a self-signed certificate, which causes the Pharos Web Release and Pharos Web Administrator websites showing security certificate errors. For more information on how to install CA-signed certificate for MobilePrint, refer to the "MobilePrint 1.3.2 Installation and Configuration Guide".

     


    • Windows 2008 Interactive Services Detection

    On Windows Server 2008, ensure that the Interactive Services Detection Service

    is not set to Disabled on all servers running the MobilePrint Worker Service.

     


    • Verify that DNS is set up and working correctly

    All servers communicate to each other as well as find each other using the name of the servers. Before installing MobilePrint, make sure that you have a properly working Domain Name System (DNS) for all machines on which you want to install MobilePrint Servers, Uniprint Print Servers, or Blueprint Analyst and Collectors. Name resolution issues caused by incorrectly configured DNS can potentially stop the MobilePrint Servers from working.

     


    New Features and Enhancements

    This Service Pack includes the following enhancements and new features:

      • Support for Windows Server 2012

    Pharos MobilePrint Servers can now be installed on Microsoft Windows Server 2012.


      • Support for IBM® Lotus®  Domino®  Server and IBM®  Notes® email  client

    Pharos MobilePrint now supports IBM Lotus Domino Mail Server and IBM Notes email client.


      • New document types supported

    Pharos MobilePrint has added support for the following document types:

        • .odg
        • .odf
        • .otg
        • .tiff
        • .ini
        • .cfg

      • Simplified MobilePrint Configuration for Blueprint Enterprise integrations

    If you are integrating MobilePrint 1.3.2 with Blueprint 5.1 or greater, you no longer have to configure the LDAP Server settings on MobilePrint Web Administrator. The Blueprint 5.1 Directory Service patch provides user authentication services to MobilePrint.


      • Improved Pharos MobilePrint Web Release website
        • All supported OpenDocument types can now be uploaded on the MobilePrint Web Release website. Previously, OpenDocument files could not be uploaded to the Web Release website.

    Note:

          This requires installation of open source office applications, such as Apache OpenOffice and LibreOffice on every MobilePrint Worker Server.
        • The Web Release logon page is now customizable. For example, you can change the Title, Logon ID, and Password prompts.
        • The Web Release logon page has been updated to accept special characters and other forms of logons, such as domain\username or username@company.com. This applies to Blueprint Enterprise 5.1 integrations only.
        • Improved printer search and selection functionality.
        • Allow adding links to webpages on the Web Release logon page. This is so that you can provide users with custom end-user documentation or other useful links.

      • Improved email address registration

    The email address of an authorized user is now automatically added to the list of registered email address in MobilePrint Web Release. Previously, users had to type in their email address the first time they log in to the Web Release page.


      • Blueprint Guest Printing Changes

    It is now possible to purge short term guest users from MobilePrint to free licenses.This is done by changing the

    Guest Password

        from the

    General Configuration > Email address registration

        menu of MobilePrint Web Administrator. Returning guests will need to re-register their email address to MobilePrint.

    WARNING!: Changing the Guest Password will purge ALL guest users from the MobilePrint cache.


      1. Display status of Pharos Servers
      2. You can now view the status (whether online or offline) of Pharos Servers on the MobilePrint Web Administrator.

      1. Whitelisting or blacklisting of domain names
        • Replaced Restricted Mail Servers to Restricted Email Address Domains (i.e. blacklist) in MobilePrint Web Administrator. You can now add domain names that you want MobilePrint to ignore email messages from.
        • Added Allowed Email Address Domains (i.e. whitelist) in MobilePrint Web Administrator. This allows you to set up domain names that MobilePrint can trust.

    Issues addressed

    This Service Pack addresses the following issues:

    • Web Release fails on Pharos Uniprint with fully qualified domain server names (FQDNs).
    • Because MobilePrint connects to SMTP and IMAP in ‘Implicit’ mode for SSL connections by default, sites using the ‘Explicit’ mode on their mail servers fail when the ‘Use SSL/TLS’ box is checked(i.e. enabled).
    • Double counting for MobilePrint jobs on Blueprint 5.0 SP2. When MobilePrint (MP) Service and Blueprint 5.0 SP2 (BP) Collector are both installed on the same PC, MobilePrint jobs were double counted. This issue has been fixed on Blueprint Enterprise 5.1.
    • Misleading reply messages when users submit non-supported document types.

     

    Known Issues/Limitations

      1. Pharos MobilePrint does not support Google’s 2-step verification

    The Pharos Web Release UI shows both native jobs (those sent to the Pharos Secure Queues) and MobilePrint jobs (sent via email to MobilePrint). Pharos Web Release allows users to change the finishing options of MobilePrint jobs, but not native jobs.

    To fix this issue, you can either turn off 2-step verification or generate an application specific password, whichever you prefer. For more information, please refer to the “MobilePrint 1.3.1 Installation and Configuration Guide for Blueprint”.


      1. Print jobs forwarded multiple times via Microsoft Outlook App may fail to render properly

    On Microsoft Outlook App for Exchange Server 2010, email messages that have been forwarded multiple times may fail to render. MobilePrint will send a reply email to the user as per usual, but will print out garbage characters. This is a known issue with Microsoft Outlook App where email messages that have been forwarded multiple times corrupt the html format of the email body.


      1. Pharos Web Release does not support changing the finishing options for native jobs
      2. The Pharos Web Release UI shows both native jobs (those sent to the Pharos Secure Queues) and MobilePrint jobs (sent via email to MobilePrint). Pharos Web Release allows users to change the finishing options of MobilePrint jobs, but not native jobs.

      1. Pharos Uniprint features unable to be supported by MobilePrint
        • Password protected jobs cannot be released from the Pharos Web Release UI.
        • Pharos Web Release does not yet fully support Cost Centers and Grants. Web Release does not support selecting the Cost Center or Grant at the time of release just like the Terminal Release does.  As soon as the Print button is clicked in the Web Release UI, the documents will be printed immediately. The jobs will be charged to the Cost Center that was selected from the Pharos Popups.
        • MobilePrint does not support the Guest Cards feature of Uniprint. Email registration in MobilePrint requires both the user's Logon ID and password. Guest users typically do not have this information. Therefore, accounts created using Guest Cards cannot be used with MobilePrint.
        • Printing banners is not supported.

      1. MobilePrint does not support Policy Print and Delegate Printing features of Blueprint
        • Policy Print is a Blueprint feature to inform, warn, or deny a print based on certain criteria.   This is not supported in MobilePrint Web Release, but works with terminal release.
        • Delegate Print is a Blueprint feature to allow one user to allow others to release their print jobs.  This is not supported in MobilePrint Web Release, but works with terminal release.

      1. Log file error messages when emails are discarded
      2. When MobilePrint discards an email, such as when the email body doesn’t meet the Email Message Filter requirements, several warnings and error messages will be visible in MobilePrint’s logs if logging is turned on. These “error messages” are intended for diagnostic information only, and your system is working perfectly.

      1. Duplicate images on iOS devices
      2. Reply emails that users receive from MobilePrint show duplicate images (e.g. organization’s logo) on iOS devices. This is an iOS feature – images are shown within the email as well as at the bottom of the email. The workaround is to edit the relevant email template by adding multiple line breaks at the end of the message (between the </body> and </html> tags).  This will make the bottom image disappear when viewing email messages in portrait mode. For more information on how to customize email messages using the default email templates, refer to the “MobilePrint Installation and Configuration Guide”.

      1. Using billing gateways to charge MobilePrint jobs
      2. To allow Pharos Web Release and/or older Terminals/iMFPs (i.e. no card registration feature) to work with Billing Gateways, Pharos MobilePrint 1.3.2 requires the script called "Billing-Pharos Accounts Plus Online Accounts.txt" found on the Uniprint install media. This script can be customized as desired.  However, you must take note of the following when using this script for billing gateways:
        • Card ID fields must be pre-populated for each user account in the Pharos Database.
        • Pharos Web Release does not show the gateway balance if 3 Uniprint purses are available.
        For more details, refer to the "MobilePrint 1.3.2 Integration for Uniprint" in the

    Documents

      folder of the Pharos MobilePrint installation media disk.

     

    Copyright © 2013 Pharos Systems International