Home › Forums › Software › InstaDMG › Another qustion (Not really instaDMG related though) – KSMB Print
- This topic has 2 replies, 3 voices, and was last updated 14 years, 6 months ago by
Rusty Myers.
-
AuthorPosts
-
October 11, 2010 at 5:10 pm #379642
nobrainer
ParticipantI’ve been bashing my head against a wall trying to figure out KSMB Print. Has anybody worked with it? I’ve tried the Casper Forums, Deploy Studio forums (it’s part of their software package, but it’s a separate download), and Google… can’t find much of anybody that’s got any knowledge of it or how to troubleshoot it.
Basically it’s an app that allows OSX to print to windows print queues and translates the Mac kerberos and translates it to windows kerberos. I can make it work if I install the package file manually, but if I take that same pkg and push it through casper it doesn’t work unless I create a login hook to install it every time a user logs in which to me is just sloppy.
I can’t “Show pkg contents” on the installer either, so i can’t tell if there’s a postflight or anything that may not be running when I deploy it.
I’m open to troubleshooting this one or trying a different solution – but I haven’t found any alternatives.
October 11, 2010 at 9:24 pm #379643Allister Banks
ParticipantHey nobrainer,
I’d assume there’s helpful folks in either IRC or DeployStudio’s forums, but if I could just give you my experiences:
I thought I needed ksmb print, because I saw an apple news blog showing its setup in response to the ‘authenticate every time you print’ symptom I was getting.
http://theappleblog.com/2010/04/22/how-to-print-using-active-directory-credentials/
I successfully pushed out the installer over ARD without incident, sent the printer setup via lpadmin at the command line after testing, but when I sent prints to an efi-rip hosted xerox workcentre, the username would be unknown and the job name would be a generic name when windows has an issue understanding the job being sent to it.
I ended up having the wrong driver – once I used the EFI subsystem and ‘cured’ the install by setting permissions correctly with a hack package by Xerox I was able to consistently have the print job and user identified. The users could store their password in the keychain and it didn’t bother them from that point on. Hope that helps,Allister
October 12, 2010 at 12:19 am #379644Rusty Myers
Participantnobrainer, there is a postflight: http://pastie.org/1214255
Installers like this annoy me. The installer drops all the files into some directory, probably tmp, I didn’t check. Then the postflight script checks for any existence of previous files, and deletes them if they are there. Then it moves the rest of the files, sets the correct permissions and links one of the files into /usr/libexec.
What does Composer find when you run it? It should find 5 files:
Permissions Owner:Group Path
drwxr-xr-x _lp:wheel /var/spool/ksmbprintd
-rwxr–r– root:admin /Library/LaunchAgents/com.deploystudio.ksmbprintd.plist
drwxr-xr-x root:wheel /usr/local/bin/ksmbprintd
drwxr-xr-x root:wheel /usr/local/bin/ksmbprintspool
drwxr-xr-x root:wheel /usr/local/bin/smbclient
lrwxr-xr-x root:wheel /usr/libexec/cups/backend/ksmbIf Composer doesn’t find them, try dragging them into the Composer window and it should create a new project with those as the installer files.
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed