I am trying to support OS X 10.5 clients using Windows Server 2003 R2 shares as the users home directory, but run in to an issue with the creation of the default folders OS X needs to run. If the OS X computer is pointed to an AFP share on an Apple server the folders are created, but when using an samba share only two of the eight folders are created.
The Apple systems engineer responded to with the following in regards to this issue:
I have been digging a little deeper into your question about why,
when a new user signs on for the first time, it only creates a Library
and Desktop folder for your network users with a SMB/Windows share.
If you could support modern AFP (via something like Extreme-Z IP), all
of the folders will be created automatically. Because of the
limitations of SMB, and how Samba is written to behave, it assumes the
folders are already there, and only does those two.
The typical solutions that I see are to script the folders creation
based on all the users in the system with homes in the directory, move
to a modern AFP, or move the shares to an xserve/Apple. I vaguely
remember Chas looking into the Extreme-Z IP solution to allow all of
the advantages of AFP, but I don’t remember the results of his
research. If that wasn’t possible the folders should be scriptable/
create-able on the Windows side, but I would still rather see a modern
AFP solution, if at all possible.
I hope this helps… I expect some of the SAMBA open-source project
notes would help clarify, from a programming perspective, why those
choices were made. I think they are going to be around the
limitations of SMB, but I don’t have enough coding experience to know
I do not follow how a samba share would limit this from the server side, but perhaps it is the Apple samba client that is the issue. If anyone can point me to any information that would help shed light on this I would be most appreciative.