Posted on 03-21-2024 05:08 AM
We're testing Jamf connect for our Macs. I haven't bound our Macs to AD. I know people say that is usually a bad idea. However, I've ran into issues with our network printers. The Macs can't see the printers. I can try to install the printers, but I end up with the print job hanging with a message stating that the printer is busy. Any ideas on how to map these printers without binding to AD?
Posted on 03-21-2024 05:11 AM
Does binding to AD actually change the behavior?
Generally speaking, if the printers require authentication the user should receive a prompt to authenticate. If you are using LDAP authentication, I would assume you have a print management system, and the users would actually be authenticating against the print server. Depending on the print server and its requirements, it may be possible to have Jamf Connect generate the Kerberos ticket needed to authenticate the print server without the users needing to authenticate manually.
Posted on 03-21-2024 11:31 PM