AD Network Home not appearing in Dock

[dom9inic]

Hi all,

I’m currently testing Tiger client AD binding and while I have no trouble logging in as an AD user in Tiger and accessing SMB shares via Kerberos single-sign-on, my SMB AD Network Home Directory does not automount into the Dock.

All I have done is configure the AD Plugin thus:

localhome -disable
use UNC SMB paths
left mappings untouched
used a preferred domain server
no mobile account stuff

Also, when I use dscl userWithName: myAccountHere

it shows
home: /Users/myAccountHere

which suggests the plugin is definitely not seeing the AD Network Home.

Any help would be greatly appreciated.

This testing in lieu of using Tiger server (on Xserve) to bind to the AD server so Mac clients can logon using the AD accounts but be managed by MCX under Tiger server.

As this is education I’m wondering how I will get all the shares I want them to access on the Windows side to automount?

Cheers in advance

[dom9inic]

That I would need to find out. I’ll be getting all the Windows side info on Monday from the Wintel Admins. Bit of an odd situation, they are not too forward coming in aiding my “research”.

Don’t want to post that info on the web anyway, no offence.

Once I find out all the AD info, how do I use it to troubleshoot the problem? Via dscl, lookupd etc?

When monitoring through DirectoryService.debug.log the bind shows no errors.

Thanks for the input, I’ll let you know.

[dom9inic]

Hi there,

the home path as seen on the A server is:

\\machineName\Group\myUserName

Regards,

[dom9inic]

Just run a lookupd -d userWithName and it turns out I’m not pulling the AD account at all, it shows the home as /Users/myUserName

(Ponders a coffee break.)

[dom9inic]

Hi macshome,

I have disabled use local home (if that was what you were referring to)

I can also manually mount the home folder or put it as a startup item. Of course this is no good as I’m trying to setup in a college environment with dynamic logins.

Can someone please confirm that what I’m attempting is actually possible:

Bind clients to AD in straightforward manner so when they login they receive their windows home directory automounted.

Then manage them using Mac OS X Server as an OD master and further adding afp automounts.

Cheers

[dom9inic]

A little update,

using an LDAP browser, I have looked at my account plus other staff members whom I know have a home folder in a windows share.

Interestingly, I seem to be the only one with the AD attribute “home Direcotry: \\\\” and the other staff members do not have that attribute.

Yet, when I manually mount that share I see all the staff members home folders, and they are home folders because mine contains the .normal Word file and usual rubbish.

This puzzles me because at first glance it means I shouldn’t see a home drive mount when binded to the AD plugin on the Mac, but then again, I’m using my login and I do have the home Directory attribute specified.

I’m trying to set a meeting with my Wintel admins to sort this out.

[Author]

Posts