Closed slmclane closed 4 months ago
Default options on Risk-RioPro:
Logs from successful print jobs on Risk-RioPro (top) and Magicard Pronto (bottom):
Cloned Admweb4 to a VM. Upgraded Admweb4 from Debian 10 to Debian 11. This allowed CUPS to update to 2.3.3op2 from 2.2.10 (the max supported on Debian 10). Opened admweb4 clone (ip 10.0.3.125) in browser and was able to log into Badger, and print a card.
Now I need to make sure that the other services on admweb4 do not break from upgrading from debian 10 to 11, backup admweb4, upgrade, and ensure that printing works.
Services on admweb4 include *badger - Working after update hdtg.conf -helpdeskt ticketing budgy - budget revision TARS - travel authorization
EDIT Did the upgrade by following instructions on youtoube https://www.youtube.com/watch?v=-J8y6LeZVjI but from Debian 10 to 11. The server is now on Debian 11, CUPS is now 2.3.3, the printer works, and nothing else broke.
The printer now works after the upgrade from Debian 10 to 11. Debian 12 is out, so we might want to consider re-testing and updating to it to get ahead of the game, I changed the .config file over to Magicard-Pronto, moved the printer to HR and it still works.
HR has obtained a new badge printer Magicard Pronto. This printer has been added to admweb4 via the CUPS driver, but print jobs sent from badger (or anything else from the server) do not print. The printer is connected and reachable on the network, print jobs show complete on the CUPS interface, and logs seem to indicate a successful print, but the printer shows no activity.