Mulhern

Apologies for bringing this post back up, but we’re currently midway through deploying PaperCut Hive as a replacement for MF. We have five Sharp copiers, and the OSD works well with Hive, including the fob readers on each device. We’ve followed Hive’s documentation and deployed the PaperCut Hive Edge Node and Print Client to all computers. So far, so good. But after that… it becomes a nightmare. Staff are sent an email invite they need to accept, which includes a unique code. Realistically, we all know they won’t be able to find that email next week when they’re back at work. There’s no bulk export of these codes to support staff proactively, and no option to import our own codes either. Even worse, there’s no way to import existing RFID fob codes from MF—so now staff have to go through yet another process. It's not like we’re switching brands here; surely PaperCut knows this is a basic migration requirement. Export from MF, import into Hive—done. Come on! Then we move onto laptops and desktops. Hive is clearly built with 1:1 device environments in mind, which, let’s be honest, most schools just don’t have. Here’s the process: A staff member logs into a PC. They wait for the user-based Print Client to install (because it’s not system-wide). Intune does its bit, the printer appears. They print something… then a browser window opens to say an admin has allowed them to print—but they must first accept/confirm. After doing that, another page pops up telling them they can now reprint the document they originally sent. Fine. Next time they log into that same machine, printing works smoothly. But if they log into a different machine? They have to go through all that again. And if profiles ever get cleared? Yep—start from scratch again. Surely this can’t be the expected process? I would have thought the app would install to the machine for all users, and when a user logs in, SSO would connect Hive with Azure AD and just let them print.