Skip to main content

Hi all,



Simple issue turned nasty. I'm running JSS 8.71 on 10.8+ clients. The shares i'm working with are just standard Windows server based smb shares and we have AD logons in mandatory use. I've checked and we seem to have proper Kerberos tickets generated on the computer. The Apple AD plugin is mounting the user's home drive correctly.



What I want to do is just mount a network share on logon. Here's what i've tried so far:



Config Profiles. These work intermittently. They fail for some of the users on our test machines and work for other users on the same machines. They've been deployed to the two computers I have on my desk and have failed to install on either despite our JSS telling me that they're present.



MCX Settings: Based on mcx settings i've found posted on jamfnation elsewhere, (actual link escapes me right now) I can get the shares to mount on login with the current user's AD credentials. Trouble is this then breaks the automatic home drive mount through the AD plugin.



On to ..



Resource Kit Script: I've been fooling with this ... thing all day. I've finally managed to get it to create the user LaunchAgent correctly as it was applying permissions to the folder and files that OS X refused to like. I've substantially modified the code to fix a whole bunch of things I found that didn't work and now it creates the LaunchAgent correctly.



Sadly that's where it falls over. It does actually mount the drive but no share icon appears on any user's Desktop! I've a theory that it may be due to whatever user is executing the mount command but i'll work on that tomorrow.



I did get it to work momentarily without any modifications but it didn't pass the AD credentials through so each share immediately asked for a username and password on mount. Not good when I've multiple shares to deal with. (We're struggling to consolidate in the background but that's not my department so i've no control over that.)



Any suggestions as to what I should try next? Nothing I've tried so far has either been reliable or issue free.

@bentoms we took the script put in our fqdn of the server and put it in a policy that runs at login and set as ongoing. We also have a delay in the script of 60 seconds to allow wireless to connect on the laptop.



As a test we also have it in self service, but running that on a laptop on wireless does not work either. As soon as i plug in the laptop to wired connection itll work no problem.



Yes on the laptop over wireless i can go to connect to server and manually map the drive.


I'll start my own thread guys. :)