Network homes share appearing in dock

[Sinergi]

Hi everyone,

Basically long story short, we have a couple of hundred machines on our network running 10.6.8 all happily working away on a server. We created a couple of new 10.7 images earlier in 2011 which was unusable due to the AD binding and connecting to samba shares. However, now this is all working pretty good I managed to login using my AD account, but for some reason my network homes share now sits in my dock (next to applications), a standard Managed account is created locally and im really not sure why?

I'm just very confused as to why this has happened and hoping someone can shed some light onto this for me? If I log into 10.6.8 OS, I have my network share homes automatically loadup on startup for example, the storage/network file structure replicates the desktop but if I login to 10.7.3 with my AD account, it creates a brand new local managed account and mounts the network home share in the dock.

The only difference I can think of (the guy who set this up has left!) is that we are not using AD with 10.6.8.

If anyone can give any indication what settings I should be looking for I would be grateful!

Thanks.

 

[rwwest7]

Hi everyone,

Basically long story short, we have a couple of hundred machines on our network running 10.6.8 all happily working away on a server. We created a couple of new 10.7 images earlier in 2011 which was unusable due to the AD binding and connecting to samba shares. However, now this is all working pretty good I managed to login using my AD account, but for some reason my network homes share now sits in my dock (next to applications), a standard Managed account is created locally and im really not sure why?

I'm just very confused as to why this has happened and hoping someone can shed some light onto this for me? If I log into 10.6.8 OS, I have my network share homes automatically loadup on startup for example, the storage/network file structure replicates the desktop but if I login to 10.7.3 with my AD account, it creates a brand new local managed account and mounts the network home share in the dock.

The only difference I can think of (the guy who set this up has left!) is that we are not using AD with 10.6.8.

If anyone can give any indication what settings I should be looking for I would be grateful!

Thanks.

Bingo! A 10.7 Mac bound to AD will put the home share in the dock and create a "mobile" account if that is what is checked in the directory utility.

 

[Sinergi]

Bingo! A 10.7 Mac bound to AD will put the home share in the dock and create a "mobile" account if that is what is checked in the directory utility.

Cheers for reply rwwest7! Unfortunately "create mobile account at login" has been unchecked although I noticed "Force local home directory on startup disk" remains check.

I just tried unchecking force local home directory on startup disk but nothing seemed to have changed, same issue as before... created managed account and home directory appeared in dock.

Any other solutions?

Thanks.

 

[Sinergi]

I happened to fix this issue quite bizarrely!

Everytime I binded to AD, I was then configuring the User & Experience settings so that a mobile account and force local homes... was unchecked. Whenever I restarted the machine it some how cached the settings and force local home directory on startup disk was re-enabled!

What I did differently, before binding to an AD address, I configured the User & Experience settings first and then added the AD address.

This now logs straight into the network share homes compared to creating a local account everytime.

 

[rwwest7]

I think I misunderstood your question. I thought the homeshare showing up in the dock was a good thing, does doing it your way work similar to "roaming profiles" ?

 

[Sinergi]

It is a good thing but not what we wanted. It works more like folder-redirection so when the user logs in they see there network Desktop on any machine they access.

Disabling "Force local home directory on startup disk" did the trick but for some apparent reason I had to configure the settings first before adding the AD server.