Posted on 01-10-2014 06:27 AM
For years, we have been having our end-users add printers via Self Service and it's worked flawlessly. Recently, we're seeing the following behavior:
1) End-user adds a printer(s)
2) CUPS is supposed to stop itself and then restart, but this doesn't seem to be happening.
3) The end-result is that no printers are listed in the "Print & Scan" system prefs pane.
A few notes;
- on a machine where this has occurred, when I try to restart CUPS at the command line using sudo launchctl start org.cups.cupsd but it does not actually start CUPS again. I know this because browsing to http://localhost:631 on the machine returns errors like "Cannot connect to server"
- a restart of the system actually gets CUPS running again and the just-added printers show up, but we don't feel it's acceptable to ask our end-users to have to restart their system just for adding a printer.
This *used* to work just fine all the way through Casper 7.x to Casper 9.2.1. The only thing's that has changed recently is an update to JSS 9.22. I don't know if this is what has introduced this problem.
Any ideas? I've kind of run out of things to try at this point.
Solved! Go to Solution.
Posted on 01-10-2014 06:49 AM
Hey All! Happy Friday! It looks like we are running into a known issue with 9.22. The good news is there is a really simple workaround. Check out this thread for more info:
https://jamfnation.jamfsoftware.com/discussion.html?id=9373#responseChild51511
Posted on 01-10-2014 06:37 AM
I have also noticed this since updating to JSS 9.22. No solution on our end yet.
Posted on 01-10-2014 06:49 AM
Hey All! Happy Friday! It looks like we are running into a known issue with 9.22. The good news is there is a really simple workaround. Check out this thread for more info:
https://jamfnation.jamfsoftware.com/discussion.html?id=9373#responseChild51511
Posted on 01-10-2014 07:11 AM
Ah ha! I totally missed this post on the boards. Weird that it didn't show up in my searches...
I've written a simple script to bounce CUPS and have attached it to my printer policies and this is a sufficient workaround for now. Thanks!