krev

Having the same issue here with a lot of devices, we have a super node configured. For end users, when printing it shows that either the handle is invalid, and crashes the app they are printing from, or the print queue shows as offline. There is some success with manually starting the pc-print-client executable and restarting the device.