Pharos Uniprint Popup 9.0.10 for macOS/Mac OS X

• Log in as an administrator and run the Popup installer to install Popup on your Mac OS X computers.

• On each computer, use the Mac OS X Printer Setup Utility to add Popup printer queues.

• The latest Mac Popup updates can be obtained from the Pharos Community ( https://community.pharos.com/s/article/Macintosh-Updates-For-Uniprint).

Downloads

Requirements

Pharos Popup for Mac OS X has the following requirements:

• Mac OS X 64-bit version 10.7  to macOS 13.0.

• Big Sur (11.x) is supported on Intel and M1 using the package we provide.  Components of the package cannot be unpacked and repacked into new packages.  The individual components are not certified separately.

• Version Uniprint 8.2 or later server components. This update is supported on Uniprint 8.2 to Uniprint 9.2.

Installing Popup

To install Popup, obtain the Popup installer and run it:

1. Obtain the file Popup.dmg from Pharos Systems.

2. Double-click this file to create a new disk image in Finder. This disk contains the Popup installer, Popup.pkg.

3. Double-click the installer to run it. You may be requested to authenticate yourself as an administrator.

4. Select a destination disk. You will only be able to select the startup disk.

5. Click Install (or Upgrade). The installer automatically installs Popup and required support files.

Pharos Popup will now be running on the computer and will be automatically launched every time a user logs in.

Configuring Printers

To start using Popup for Mac OS X, add Popup printer queues on the computer:

1. Open System Preferences and click on the Printers & Scanners icon.

2. Click the + button.

3. Hold down the Control key on the keyboard and click anywhere on the toolbar. From the popup menu that appears, select Customize Toolbar...

4. Drag the Advanced icon to the toolbar and close the customization dialog.

5. Click on the Advanced button in the toolbar.

6. From the Type popup button, select Pharos Print Server.

7. In the URL field, enter the URL for the desired Popup queue on a Pharos Print Server. This value should have the format “popup://print_server_address/queue_name”. The “print_server_address” should be replaced with the domain name or IP address of the Pharos Print Server. The “queue_name” should be replaced with the name of the desired queue on the Pharos Print Server. If a Print Server has the host name “PharosServer” and a Popup queue named “MacQueue”, the device URL should be “popup://PharosServer/MacQueue”.

8. In the Name field, enter a name for the new printer queue. This is the name that will be shown to users on the computer.

9. From the Use popup button, select the type of printer associated with the Popup queue. If the desired printer is not available, selecting “Generic PostScript Printer” will work in most cases.

10. Click Add. The new Popup queue will now show up in the list of printers.

11. To print to the new queue, select it from the printer popup button in the print dialog of any application.

Removing Popup

To remove Popup from a computer, run the Pharos Uninstaller:

1. Launch the Uninstaller application in /Library/Application Support/Pharos/Utilities.

2. Select Pharos Popup and any other Pharos components that you would like to uninstall, then click Continue.

3. A list of the selected items will be shown. Click Continue.

4. Type in an administrator username and password when required to do so. The selected components will be removed from the computer.

Notes

If there are printers on the network that support Apple’s Bonjour technology, users may be able to bypass the Pharos printing system. To avoid this problem, disable the Bonjour features of any such printers.

If the software firewall (ipfw) on the computer is active, the following ports must be opened for TCP traffic for Popup to work:

1. 515

2. 28203

The firewall in Mac OS X is disabled by default. If it has not been manually activated, these ports will already be open.

Recent Changes

This update addresses the following issues:

Mar 2023:

• A change has been made to prevent an error showing on Ventura OS regarding 'Notify App Damage'. To fix this a step during install, to edit the uninstall script, has been removed.

Mar 2018:

• A supporting file was moved from a protected system location to avoid install problems.

Sep 2017:

• Developer ID Certificates have been renewed for the Mac Popup Client. This avoids an expiry warning that users might see when installing the Popup Client on a new Mac computer.

• Firewall exceptions have been added to the installer to avoid rare problems seen by some customers.

Feb 2017:

• A security issue has been discovered in the Mac Popup client by a researcher. We recommend that customers update their Mac Popup clients to address this vulnerability.

  Impacted versions

  All Mac Popup versions prior to 9.0.8. The Mac Popup was included with Uniprint 5.0, 5.1, 5.2, 5.3, 5.4, 6.0, 6.1, 7.0, 7.1, 7.2, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0 and 9.0R2

  Resolution

  Install the Popup client package 9.0.8 or greater.

  Security Detail

  Impact: A maliciously crafted packet sent to the Mac Popup client could result in memory corruption. Successful exploitation would result in arbitrary code being executed with root privileges on the workstation.
  Reference: CVE-2017-2785, CVE-2017-2787, CVE-2017-2788: Cisco - Talos Team.

  Impact: A maliciously crafted packet sent to the Mac Popup client could crash the Popup service on the workstation.
  Reference: CVE-2017-2786: Cisco - Talos Team.

Oct 2015:

Note for users of OS X 10.11 (El Capitan):

Apple introduced some protection for system locations (SIP) in this release that can prevent the Popup Client installing. This is due to a supporting file called pharos.convs that can only be written to a system location at this time. Apple also added an exception to allow the installer to bypass SIP for this particular file. The exceptions are not part of the base OS install, but are retrieved from an Apple network service. Machines that have automatic updates disabled may also not update the exception list.

Most machines operated by students should have had a chance to retrieve the list of SIP exceptions before an attempt to install the Popup Client. For machines being imaged automatically, the following commands can be used to force an update of the exception list:

sudo softwareupdate --schedule on

sudo softwareupdate --background-critical

The first command enables automatic background updates, if necessary. The second forces an update of critical system protection data, including the exclusion list for SIP. Note that this is currently an undocumented parameter for the softwareupdate tool. The best way to configure a single system is to make sure both the 'Automatically check for updates' and 'Install system data files and security updates' boxes are checked in the App Store pane of the System Preferences application.

Thanks to Gerrit DeWitt and Chris Axtell for their helpful contributions to our community on this topic.

• Corrected a bug when the SignUp 'User Login ID' setting was incorrectly set.

• Added support for Mac OS X 10.11 El Capitan.

Jul 2015:

• The Mac Popup Client has been updated with new Pharos branding.

• The Mac Popup Client now works properly with the Fast User Switching feature of Mac OS X.

Jan 2015:

• The prompt and description text for system questions are now displayed.

Dec 2014:

• Added support for Mac OS X 10.10 Yosemite.

Jul 2014:

• The Mac Popup Client now works correctly when no questions are assigned to the queue.

Jun 2014:

• Added "Apply last answers" feature. Each Popup Question has an option to control if the last answer can be saved and how it should be applied (i.e. Apply automatically, Don't re-use, or Offer as default). Note: This feature applies to Uniprint 8.4 or greater.

• Added Guest card question support.

• Addressed an issue relating to incomplete display of cost centers list when "Skip If One Choice" is set to "Yes".

Aug 2013:

• The Popup Client can automatically display all cost centers available to the end-user without requiring a search, by setting the ShowAllCostcenters global preference. Run the following command to configure this option:

  sudo defaults write /Library/Preferences/com.pharos.popup "ShowAllCostcenters" VALUE

  Replace VALUE with either 0 or 1, where 1 will display all cost centers regardless of the 'Hide History' cost center question settings in Administrator. The default for this preference is 0, so users do not generate unnecessary network traffic. It is not recommended to enable this option when users have a large number of cost centers available.

  Note: There is currently a known issue with this feature in combination with shortcuts. If you select the shortcut and click Print, the defined shortcut is not applied. Selecting the shortcut by double-clicking (or using the assigned shortcut key) still works as expected. This issue was fixed in Jun 2014 update.

May 2013:

• The Popup installer has been signed with a certificate that is appropriate for new OS X versions.

• Added support to ignore CUPS jobs, such as Supply Levels, that was causing unwanted Popup dialogs.

Jan 2013:

• Popup installer is updated to address an issue resolving the 'localhost' name in certain configurations. This avoids an unnecessary delay with Popup questions on affected systems.

• Previous versions of the Popup Client would pass a local IP address to the Print Server for Notify communications. In some cases, this address was not reachable by the Print Server, and would interfere with cost acceptance or Notify communication. In this version, the address sent matches the one already used to communicate with the Print Server.

• Broken uninstaller issue encountered after upgrading from 8.1 Popup and Notify Clients has also been addressed.

• Charge to User rather than Cost Center prompt now appears on Mac client.

Oct 2012:

• Popup installer is updated to sign the application.

• Note: When 8.3.2 Popup package is installed on 10.7, make sure it is up-to-date with the latest OS X updates. Otherwise, you might get an warning as "Popup.pkg was signed with an invalid certificate". It is safe to ignore and continue installation.