AD Authenticated printing - ksmbprintd

Not applicable

Hey guys

Is anyone successfully using ksmbprintd on 10.6? We have tried using it
previously on 10.5 without success and we're re-evaluating it for 10.6. Has
anyone seen any updated documentation for it from the DS guys? The disk
image just has the installer and the documentation I've seen was from 2007.

Regards

Sven Schott

P.S. Any hints, if you have got it working, would be appreciated. :)

6 REPLIES 6

Bukira
Contributor

Hi

Yes i use it and it works great, i use version 1.1 fine.

How can i help? this is what i do, we use pcounter queues

  1. install ksmprintd via Casper from the pkg
  2. add a printer in system prefs as an LPD print queue, with server, queue name and driver (make usre drivers are installed
  3. go to localhost:631 CUPS server and modify the printer to a kmsb;// queue, "windows printing via SAMBA with kerberos support v1.0"
  4. add the printer to Casper Admin and not that it is ksmb://servername/queuename

then dpeloy as normal, ksmbrintd , print drivers and print queue via casper policys

Criss

Criss Myers
Senior IT Analyst (Mac Services)
iPhone / iPad Developer
Apple Certified Technical Coordinator v10.5
LIS Development
Software Management Team
Adelphi Building AB28
University of Central Lancashire
Preston PR1 2HE
Ex 5050
01772 895050

ImAMacGuy
Valued Contributor II

We looked at ksmbprint but found it screwed up something... though for
the life of me I couldn't remember what specifically... I think it had
something to do with the reporting wasn't showing up properly. Maybe
not passing userids to the log, only the ksmbprint....(everything showed
up as ksmbprint instead of the user that actually printed?). Sorry it
was a while ago...

We got around it by running a script that changes the user's full name
to their short name... then they just have to type in the password the
first time and save to keychain.

Well, it's a bit more complicated than that - for some reason whenever
they try to print the first time the job goes to "on hold" and we have
to click resume, then put in their password.... But if we save to
keychain, then we don't have to worry about it again until we change
passwords.

John Wojda

Lead System Engineer, DEI

3333 Beverly Rd. B2-338B

Hoffman Estates, IL 60179

Phone: (847)286-7855

Page: (224)532.3447

Team Lead: Matt Beiriger
<mailto:mbeirig at searshc.com;jwojda at searshc.com?subject=John%20Wojda%20Fe
edback&body=I%20am%20contacting%20you%20regarding%20John%20Wojda.>

Mac Tip/Tricks/Self Service & Support <http://bit.ly/gMa7TB>

ernstcs
Contributor III

Are users being prompted to reauthenticate when they print, or not?

What version of Windows is your Windows print server?

Craig E

jarednichols
Honored Contributor

2008 R2 allows non-authenticated printing for non-Windows machines. We've got it setup as our print server and it works well. Not sure what kind of wizardry Microsoft whipped up to make the determination of what kind of client is inbound with a print job, but it works :)

Best of both worlds: Users don't have to worry about a bad stored password after they've changed it, support doesn't have a ticket when that happens, you still get your jobs sent through the print server.

j
--
Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

ernstcs
Contributor III

Why does that just sound wrong to me? Do I take that for face value and translate it to anonymous printing? Can just anyone print to your printers? Are you restricting it somehow?

Craig E

michaelhusar
Contributor II

Since it is an old post I hope there is a solution.
We have Windows 2012 R2 print servers and used a script to connect the printers via ksmb.
Yosemite broke it since ksmbprintd cannot be installed...
Thank you!

Ok , my bad - its old because this is the solution: https://jamfnation.jamfsoftware.com/discussion.html?id=4075