On the premises, in the cloud, or a hybrid of both; one device, one hundred, or one thousand… We’ll slot in beautifully no matter how you choose to set up your network.

Join me as I look at how PaperCut goes above and beyond in giving customers unbeatable flexibility, and future-proofing choice.

We’ve been using Apache Beam Java SDK to build streaming and batch pipelines running on Google Cloud Dataflow. It’s solid, but we felt the code could be a bit more streamlined.

That’s why we took Kotlin for a spin! Find out how we leverage it to reduce the boilerplate code.

Picture this: a customer has a PaperCut App Server in their data center; each computer has Direct Print Monitor installed; and the local water company has a date first thing Monday to drill clean through the data center link.

… That hurt to type out. Surely no link means no printing, right? Well, not with failure mode doing its thing. Find out how!

High Availability is incredibly important for maximizing uptime in any print infrastructure using Microsoft SQL Server.

But if a customer wants to go beyond mere implementation, and figure out which High Availability method is truly the best for their business, the process can be a doozy.

So let’s clear things up a bit!

Like most geeks on the planet, many of us here at PaperCut have been getting up to speed on Docker (the Open Source containerization platform) over the last few months and years.

Remembering the difficulties and the questions I had back then, I’ve created a short one hour talk to get people bootstrapped into Docker.

99.99%.

It’s a compelling figure. The uptime guarantee trumpeted in SLAs the world over.

Of course, 100% is simply unattainable. Those SLAs must provide wiggle room for the .01% of unplanned, unavoidable, ‘well I didn’t expect THAT to happen, ‘what do you mean there’s been a power spike to the UPS’, ‘so THAT’S what that switch does’ events.

We started using Google Pub/Sub to synchronize between a legacy operations application and newer tech such as Salesforce. Along the way, we encountered quite a few challenges and not everything went according to plan.

In this post, I want to take a look back and share what we’ve learnt so far.

I recently installed and tested out PaperCut NG on the easy-to-use Univention Corporate Server (UCS).

Tl;dr? It was a breeze. But what about getting the server itself up and running?

Join me as I walk through creating a PaperCut-ready UCS test environment on a virtual machine.

Take it from a support manager who’s seen some grisly stuff: when it comes to protecting your print infrastructure, implementing health monitoring should be your top priority.

Sceptical? These chilling tales should scare some sense into you.

*wolves howl, printers jam in the distance*

I love making life easier. And let’s face it – some repetitive administrator tasks are prime targets for streamlining. Take the case of a boatload of inactive PaperCut users. Removing them’s too much trouble, but letting them take up valuable licenses is a big no-no. Here’s where scripting can really help.

Another successful PaperCut Constructival hackathon has come and gone. Around 120 PaperCutters huddled together in busy little groups for 30-odd hours and hacked to their collective heart’s’ content.

Why have a hackathon? What’s the value? How do I run a hackathon with my own team? These are the questions we’ll solve today.

When you’re responsible for software updates and upgrades, it’s best not to jump in without checking what the repercussions will be.

Systems architect Matt Lee shares his personal formula for ensuring a safe software update. As a bonus, Matt shares the horror story that led to his formula.