Yes, both 32- and 64-bit drivers are supported. Since drivers are never installed on the Cirrato server, they are just stored there, Cirrato can handle any combination of 32- and 64-bit drivers, operating system specific drivers and different driver versions.
Yes, the Cirrato database can share an SQL Server instance or SQL Server with other databases and systems. Keep in mind that when using followprint, end-user tolerance for delays is less than with direct printing since the user will be waiting by the device for the printout. Therefore it is important that the performance of the Cirrato database is not affected by other software using the same hardware or SQL Server instance.
Yes, users can print from their laptops. If the users shuts the laptop down, Follow Print jobs will not be available for printing until the laptop is powered on and available on the network again. For customers with a lot of laptop users we recommend that Cirrato Handover Points be set up that will handle the file transfer to the printer on behalf of the laptop.
Yes. Scanning to our own or someone elses email address is possible on most platforms where Cirrato followprint is available. In a lot of cases restrictions can be put on who you may send emails to.
Yes, printouts and in some cases copying, scanning and faxing can be charged to a Client Billing code. A Client Billing code can represent a project or department. Reports are available that show how much has been printed for a given client billing code. If the user´s department is available as an attribute in LDAP, the attribute value can be used as the client billing code.
The Cirrato printing service is not cluster-aware. DNS failover can be used to direct clients to a live server or a secondary server can be brought online using the same IP address. The database may be mirrored or may use log shipping for redundancy. Driver files can be placed on shared high-availability storage.
Yes, the Cirrato services and database can be run on a virtual machine. The virtual machine must meet the same requirements in terms of performance as dedicated hardware. Keep in mind that when using followprint, end-user tolerance for delays is less than with direct printing since the user will be waiting by the device for the printout. Therefore it is important that the performance of the virtual machine is not affected by other software using the same hardware.
Please refer to our pre-requisites document, available via your sales representative. In general, you will need Windows Server, IIS, SQL (Express version is sufficient for small installations and if you don't need to log reports for longer periods).
Cirrato One provides software to accept print jobs originating from Citrix, Terminal Server, Mainframe, SAP, Oracle or other data center applications. Cirrato will compress these print jobs, transmit them over the WAN, uncompress and print at the remote location. This speeds up printing and is excellent for clients using Thin Client Terminals, Virtual Desktop and remote desktop access.
SQL Server 2008 / 2008 R2 / Enterprise / Standard / 32 / 64, they all are OK for small scale deployment (test environment) For production, the capacity must be asessed based on number of transactions.
No. The Database / IIS may run on any other server the cirrato server has TCP/IP connection to. For testing purposes, its simpler to have all on one server. For deployments, the SQL server is usually in a consolidated SQL server running other databases. IIS run on the cirrato server and reporting services run on the report server used by the common SQL server. For testing purposes, all 4 components may be on the same server to reduce the time needed for installation. For production, Cirrato server, IIS, SQL , Reporting services (actually an IIS application that may very well run on the IIS server) may be splitted on 3 or 4 servers.
Whether authentication at the printer using cryptographic smart cards is possible is highly dependent on the MFD and what card is used. Please contact Cirrato for inquiries about PKI and smart card support.
Yes, Cirrato can work with nearly all native print drivers. Bi-directional communication between printer and driver is also supported by Cirrato. Some drivers which send print job meta-data as a small print job might not work.
Currently embedded Follow Print is available for Canon, Fuji Xerox, HP, Konica Minolta, Kyocera Mita, Lexmark, Ricoh, Samsung, Sharp, Toshiba and Xerox. Click here for an overview of our supported devices per manufacturer. We are rapidly adding support for new models. Models where embedded Follow Print is not yet supported may use the external Cirrato terminal which works with any printer or MFD.
Cirrato can query an LDAP server for the card number, read the card number from the Cirrato database or from an external database. When using LDAP, the customer is responsible for updating the card number. If the pager field isn't used, this is usually where we recommend storing the card number to avoid schema changes. When the Cirrato database is used it is possible to use the automatic card database feature which prints a registration page when an unknown card is swiped. This registration page contains a web URL and a temporary code. The user then goes to this web URL (part of the Cirrato webGUI) and logs in using his credentials and then inputs the temporary code, this connects the user with the card number. The next time the user swipes his card at a printer terminal, he is logged in.
Cirrato can be configured to display an authentication dialog to users printing from computers with specific IP addresses or subnets. The guest user may then authenticate using an account available in LDAP or a custom user database. To this account a short ID can be associated, which allows the user to authenticate and retrieve his printout at a followprint terminal (embedded or external). Cirrato client software should be installed on the public computer or made available for download to guests who bring their own laptops. Alternatively, one PC with the Cirrato client installed could be configured to share printers using IPP (Internet Printing) with authentication.
The migration MSI package is installed on to the XP clients. On each workstation, it creates an inventory of the existing printers and configurations and uploads this to the Cirrato server. Once the new workstation (Windows 7) is in place, the operator / user runs the migration tool in restore mode. This restores all printers and configurations on each workstation. This will provide the user with the same printers and (if driver is the same) the same configurations as previously.
The Cirrato client can send information regarding installed printer queues to the Cirrato server. There is also a stand alone binary called cirratoinventory.exe that fulfills the same purpose. If no local TCP/IP-port printers are installed on workstations, this inventory only needs to take place on print spool servers, if not, the workstations also need to execute the inventory. Cirratoinventory.exe can be placed on a network share end executed from a logon script (negating the need to install the Cirrato client software in order to perform the inventory). When the inventory is complete, Cirrato provides administrative tools to view and use the inventoried data to create printer queues in Cirrato. It is also possible to configure the Cirrato server to instruct the Cirrato clients to delete the old printer queues or UNC-printer connections when installing the corresponding Cirrato queues. Printer drivers are not extracted in the inventory process, these need to be manually uploaded to the Cirrato server using a wizard application called CirratoPak. The same is true for printer configuration settings.
Cirrato keeps the print job local on the user workstation. Only a small ticket with all the information about the print job is sent to the Cirrato server. When the ticket is 'approved', it is sent back to the user workstation and the job is released to the printer. So it only travels over the local area network.
Cirrato saves information in an SQL database. We provide a set of standard reports created in SQL Reporting Services. These reports cover most our customers' needs. Using SQL Reporting Services, you can schedule reports that are generated and sent out in various formats automatically. Of course, you can contact us if you want to create custom reports.
About 1 kB of application layer data is transmitted between the Cirrato server and client during a basic direct printout. As more functions are added, a few more kilobytes are added. 1 kB/s is communicated between the Cirrato printing service and the database continuously. About 20 kB of TDS data is transmitted between the Cirrato printing service and the database during a printout. If you have Follow Print, then an additional 3.5 kB per followprint job is communicated between the printer and the Web Service API.
Cirrato is very suitable for managed print services (MPS) environments. Particularly for those large enterprises with multiple locations. These organizations can really benefit from Cirrato for three reasons:
- They can eliminate their print servers for instant cost reductions.
- The IT department can control printing from one centralized location, so on site troubleshooting is no longer required.
- Even when the Cirrato server cannot be reached, users can continue to print.
In addition, Cirrato offers the same features that the common print management solutions offer, like Follow Print, print rules and accounting. So one might say that Cirrato is the better solution for MPS as it has additional benefits over the traditional solutions.
Yes. Cirrato driver archives are normally downloaded from the server when needed to perform a printer queue installation on a client PC. These driver packages are then kept on the client PCs in case they should be needed again to avoid unnecessary downloads. Any method that simply copies these driver archives to the client PCs in the directory where the Cirrato client expects to find them will work. It is also possible to use the drivers that are included with Windows.
Yes, you can do this in many ways. Some examples: A) Use Rules functionality to enforce restrictions for certain user groups. (Please note: Cirrato uses information provided by the printer driver to decide if the printout is color or B&W. Printer drivers may report color even for B&W printouts. It is therefore important to verify the correctness of the driver before deciding to implement color restriction rules). B) Set up dedicated color queues which are only pushed out to certain user groups while hidden from others. C) Set defaults to B&W and Duplex, but allow users to configure printer settings on a job-by-job basis, then use reports to see who printed in color. We typically recommend option C because it achieves the required savings while being the least restrictive.
Yes. If the application runs on Windows, the Cirrato client can simply be installed to facilitate that. If not, one option is to set up a Windows server with the Cirrato client and associated Cirrato printer queue and share the queues using "Print services for UNIX". Another option is to use the Cirrato EUT_API to submit jobs using our submit_job.dll interface. This API requires that the Cirrato client software is installed. Spooled print job files from any source can be submitted as any user using this interface.
Yes, it is possible to use a PIN with Follow Print. There are several options. The PIN may be used as a primary means of identification. This is what we call a 'Short ID'. The Short ID does not have to be a number. The PIN may also be used in combination with another means of identification like a contactless card, username/password or Short ID. Another option is to only require a PIN for printouts in one or more secure print queues. End-users may set their own PIN on the self-service web page. Which options are available depend on the embedded software used on your printer models. Talk to your sales representative to find out which of the above functions are supported on your printer models.
Yes, the Cirrato database can be run on the Express versions of Microsoft SQL Server but it is very important to be aware of the limitations of the Express version. The Express versions of SQL Server 2005 and 2008 are limited to one CPU, 1 GB of memory and 4 GB and 10 GB databases respectively. No profiling tools are included and data import/export capabilities are limited. Log shipping is not supported. SQL Server 2008 R2 Express with Advanced Services does include Reporting capabilities but earlier Express versions do not. Hence, performance, features, redundancy and supportability of Cirrato will be limited.
Yes, The client supports Mac OS X Mavericks (10.9), Mac OS X Yosemite (10.10), Mac OS X El Capitan (10.11), Mac OS X Sierra (10.12)
Note: If the Cirrato server is older than release 15R1 v. 20.2.2, OS X El Capitan compatibility requires that the script Add_Deployment_OSX_10_10 & 10_11.sql (included in the client package) has been run on the installed Cirrato database. If the server is older than release 15R1 (any version), the script is also required for compatibility with OS X Yosemite.
Yes. If it is desired to assign printer queues per user, the Cirrato client can be installed on a server and the Cirrato printer queues shared from there. If follow-print is used, only a single printer queue needs to be used, this printer queue can be installed on the terminal server (we do not recommend installing more than one printer driver directly on a terminal server). Another option is available when the thin clients connect to virtualized PCs, if the state is saved between logons, it is no different than a regular PC, but if the image is cleared on logout, login scripts are needed to reinstall the Cirrato printer queues. (Cirrato printer queues are installed as per computer, not per user printer objects.)
For employees that move a lot to different offices, Cirrato One's Printer Search application (available from the tray icon or through a web page integrated in your intranet) allows you to find and install nearby printers. Cirrato automatically installs the printer and driver, allowing users to print immediately.
The IIS should be the one included in Windows Server 2008 (standard / R2). Make sure IIS Application server is installed at same time. IIS 6 metabase compatibility layer must be installed to provide support for the automatic installer. Some SMO related .msi packages might have to be downloaded / installed from microsoft.com to the IIS server prior to deployment of the application if the SQL client software is not installed. The affected packages are mentioned in the documentation.
It depends on the brand and model of printer or MFD. Please contact Cirrato for a list of supported card readers. Magstripe or contactless Card readers are available for most platforms where Cirrato followprint is available.
The server IP and license key must be defined so that client can communicate with the Cirrato server. You can also choose to enable the "selfservice" feature, which enables users to manage their print jobs and, if they are using Follow Print with manual authentication, their authentication codes. Configuration is done using any third-party msi-package editor (for example the Microsoft Orca tool).
It depends on how the Cirrato environment has been configured. Direct printing: The Cirrato client recognizes that the server is down and preforms ordinary printout without the server having to confirm. End users won't notice any difference. Follow print: The Cirrato client presents the user with a list of previously used follow print queues. When you select one of the queues the print job will then be printed out as if that follow print queue were a direct printer. In both cases, statistics will be stored by the client and uploaded to the server once the server is back online. Payment solution (users pay for each print job): Cirrato can be configured to deny printing while the server is offline.
Phased Driver Rollout is a feature that was introduced in March 2016. It allows IT administrators to test print drivers prior to deploying them. Testing can be done based on version (32 or 64 bit) or operating system. Testing can be done per print queue or region. It avoids a new driver from causing disruptions. If a driver is not performing as it should, it can be deleted and the region or print queue that it was tested in, automatically goes back to using the previous version.
The Cirrato client listens for incoming TCP connections from the server on port 5001. The Cirrato server listens for incoming TCP connections from the workstations and laptops on port 5000. The Cirrato server also listens for incoming TCP connections from administrators on port 5005. The Cirrato monitoring service needs to be able to query all printers using SNMP (usually port 161). Since Cirrato is a direct printing solution, all end-user workstations and laptops need to be able to connect to all printers on TCP port 9100 or 515 depeding on if LPR is used or not. All port numbers are possible to change if needed.
Besides using our patented Cirrato protocol (which is the core functionality of Cirrato itself, ticket based printing using single server, driver deployment and so on) we use the standard TCP/IP layer.
"The Cirrato server hardware must fulfill the following requirements or, if a virtualized server, the equivalent of these requirements: Intel Pentium 4 - 1.5 GHz or greater, 2048 MB RAM, or greater. Note: If the minimum requirements for running the server´s operating system with SQL Server exceed the values listed here, they take precedence as requirements for the installation. This is the hardware of one major customer with thousands of users and hundreds of printers/MFDs: Cirrato Server Brand/model: Dell PowerEdge R515 Amount: 2 Processor: AMD Opteron 4184 (2.8GHz, 6 cores) Memory: 8 GB DDR3 Harddisk: 5x 250GB 3.5” SATA Hotplug (RAID 5) Power: 2x 750 watt Operating System: Microsoft Windows Server 2008 R2 x64 Cirrato Handover Point Processor: Intel DualCore 3GHz Memory: 4 GB Harddisk: 500 GB Power: 2x 750 watt Database Server Brand/model: Dell PowerEdge R515 Amount: 1 Processor: AMD Opteron 4184 (2.8GHz, 6 cores) Memory: 8 GB DDR3 Harddisk: 5x 1TB 3.5” SATA Hotplug (RAID 5) Power: 2x 750 watt Operating System: Microsoft Windows Server 2008 R2 x64 Database: Microsoft SQL Server 2008 R2 Enterprise"
Printer queues can be installed using login scripts by calling the command line program cirrato.exe, the graphical user interface program Cirrato Printer Search, helpdesk personnel can push printer queues to PCs using the Cirrato webGUI and end users can install printer queues using a web based tree view. None of these methods require the users to be local administrators.
As a general rule, all forms where the user has to enter their credentials are encrypted. Examples are: The Cirrato Web GUI (if HTTPS has been enabled), almost every machine terminal has the option to encrypt credentials (HTTPS), Cirrato MMC Snap-in, Cirrato Client (if user confirmation has been enabled), Self Service (if HTTPS has been enabled).
Cirrato does not process the print job on the server. Each job gets a ticket and that ticket contains all the information needed to check user permissions and device availability. The server also applies rules and checks if the correct driver is installed. It can do that for thousands of tickets per minute. For all of the printers in the organization. Because the job stays on the user workstation, a print server for each location is no longer required. Printing is fast and reliable while fully managed by Cirrato.