System Client

CirrusPrint system client software must be installed at each remote location that will receive jobs from the server.  Each client can be configured to connect to one or more CirrusPrint servers, login as a location, and accept jobs for that location.  The location ID can be considered an physical location such as an office or home, servicing printers and files for all users of a system.  In either case, the client receives jobs and delivers them to local printers or files.

Internally, the system client provides two services: a local web server for monitoring and configuration, and a web client working with a CirrusPrint server to receive jobs, and if configured, a file and port monitor to collection jobs to upload via the server to devices at other locations.

To access the local web server to monitor and configure the client, open http://localhost:27084 in your web browser.  When this is opened, you will be prompted for a passcode.  This code can be generated by the Windows client manager running in admin mode, or by a command line run by an administrator or root user.  Passcodes are short-term and must be used shortly after generated.

The client is available on both 64-bit Linux and Windows.

Profiles

The client supports multiple profiles, if needed, to enable it to connect to multiple CirrusPrint servers.  Each profile maintains its own server configuration and queue settings, enabling one client to receive documents from different companies or different CirrusPrint servers.  All clients have a "default" profile that cannot be deleted or disabled, so that is the initial profile to define.

Profiles are configured using the Settings button in the browser interface.

On the server, when a system location is defined, a deployment button is available to email setup information to a user who has access to the machine where the client is installed.  This email includes a link to download the client software and configure it.

Windows

The Windows client installs itself as a service, running under the Local System account.  There is a management tool, CirrusPrint 3.0 Client (cp30c.exe), that can be used for easy access to the browser client and to start/stop the service.  You must run cp30c as an administrator in order to control the service, or you can use the Windows Services application.  There is a 'Run as Admin' button available for this purpose.

The Windows client will auto-update itself when the server it connects to is updated.  If there are multiple profiles, the lowest client version is maintained.

Note if the client requires access to network resources, such as remote UNC printer shares, you can modify the service to login as a regular user.  Automatic updates cannot be performed in this circumstance, so instead the update is downloaded automatically and the CirrusPrint 3.0 Client app offers an update button that can be run by an administrative  user.

Linux

The Linux client installs itself as a systemd or init.d service, and is managed with the /usr/bin/cp30c command line tool.  The installer creates a user "cp30c" for the service, so it must be granted permission to resources that are explicitly blocked by the system, such as client-hosted input source paths.  You can use chmod on specific paths or add cp30c to specific groups if necessary.

The Linux client will auto-install updates as long as it is running on a system with the systemd service (check this by looking for the file /etc/systemd/system/cp30c.service).  If the update can't be installed, it will be downloaded and both client and server logs will indicate the presence of the update.  Running sudo cp30c restart will then install the update before starting the client process.  If there are multiple profiles, the lowest client version is maintained.

Access Restrictions

The client should be installed only on private machines operated by the user.  It does not provide https protocol or login-based session management.  Access to the browser interface is limited by firewall and by IP restrictions that can be manually configured if necessary.  The settings are found in config.ini, in the [httpd] section.

[httpd]

port=27084

allow=local | network | any

The values for allow=name mean this:

•local - only connections from localhost or 127.0.0.1 are accepted.
 

•network - only connections from the local network are accepted.  The list of networks in CIDR format is 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16.
 

•any - connections from anywhere are accepted.  Do not use this value unless you have a firewall that will block unknown addresses.