Universal Print is the new way to cloud print from your devices. It replaces Hybrid Cloud Print and is a lot easier to set up and manage. You’ll need your devices to be connected to Azure AD (either domain joined or hybrid joined, or registered).
It’s included in the following subscriptions:
Microsoft 365 Business Premium
Microsoft 365 Enterprise F3/E3/E5
Windows 10 Enterprise E3/E5
Microsoft 365 Education A3/A5
Windows 10 Education A3/A5
There’s also a stand-alone licence but this requires (but does not include) Azure AD.
Hybrid Cloud Print is a solution to allow users to print to on-premise printers from their devices without needing to be on site or even have VPN connectivity – they just need Internet access. It is however fairly complicated to set up and requires multiple app registrations in Azure, and an Application Proxy server setting up. In this post I go through the steps on how to set it up and print from an Intune managed device.
Hybrid Cloud Print is being replaced with Universal Print, which is a lot easier to set up and manage – no messing with SQLite and it has a portal in Azure, however it’s only currently available in preview to people with specific existing subscriptions. I’ve also gone through setting up Universal Print.
Over the last 15 years I’ve tried pretty much every method of adding printers at logon there is – KIXTART script, VBS, Group Policy Preferences and Powershell. As part of speeding up logon, and investigating a weird issue with Windows 10 printers, I moved away from GPP and to Powershell shortly after we upgraded from Windows 8.1 to Windows 10.
The issue being – roughly 5% of the time, on random user/computer combinations, printers would take a long time adding and then fail to add, with a non-specific error message. My first go at this was a basic powershell script which had a hard coded list of location/printer mapping, and it would run the “add printer” command repeatedly until the error went away. (It always added fine on the 2nd go). The problem with this is that it’s a complicated script for technicians to update, and being a single threaded script the nice form it displays showing people what’s happening would freeze while it was working in the background.
My new script does the bulk of the work in background jobs – so printers add quicker (as it can do more than one at once), and the UI doesn’t lock up and freeze. More importantly, it uses Group Policy Preferences by reading the XML file generated and applies that – so technicians have the familiar interface for adding/removing printers from the script. Continue reading “Powershell Printer Script”
We’ve recently switched from Ringdale FollowMe to PaperCut MF and I wanted to bring over our classroom queues. Unfortunately the supplier said this couldn’t be done, so I did some experimenting and worked out how myself.
The idea behind the classroom queue is that a second printer is listed on each PC in the room, so for room 10 the PCs would all show the “PaperCut” printer and also “Room 10”. Print to PaperCut and you use your personal code to release, print to Room 10 and you use the room code. This way a class of 24 pupils can all print their work to the Room 10 queue, then the teacher (or a single pupil) can go and release all 24 documents in one go. Loads quicker than a queue forming at the device. Continue reading “Classroom Queue in Papercut MF”
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.