samba - Mar 2013 - ADUC tool cannot creates users home directory

Hello everybody,

if I use Microsoft's Active Directory & Users tool to add a home drive
mapping to a users profile, I encounter the problem that ADUC tool cannot create
automatically the home directory for the desired user. ADUC tool fails with the
message, that the share cannot be accessed.

My smb.conf contains:

[global]
   template homedir = /data1/homes/%ACCOUNTNAME

[homes]
         browseable = no
   read only = no

When user "johndoe" browse the share \\s4srv he will see a share with
the name "johndoe". If he doubleclicks this share, he see's the
content of his home directory. Until here everything work's fine and is
reasonable. As "man smb.conf" explains the [homes] share is a special
share and the behavior is explained in details.

My problem is, that I am logged-in with MYDOMNAME\Administrator at a Windows
client, and running the ADUC tool. In users profile I enter for home drive
mapping following information:

U: --map---to--->    \\s4srv\%username%

The syntax is correct, but ADUC cannot access this share, because it would
resolve to \\s4srv\administrator at this step. I think that's why ADUC
cannot create this share, because of the special mapping of the [home] share.
The [home] share is cloned and the username of the accessing user is used. (see
'man smb.con' under section [homes] special share).

How can I achieve to have ADUC tool create also the home dir when I create a new
user? Any help appreciated.

Thanks in advance,
Lucas.

On Mar 27, 2013 8:08 PM, "?icro MEGAS" <micromegas at
mail333.com> wrote:
>
>
> My smb.conf contains:
>
> [global]
>    template homedir = /data1/homes/%ACCOUNTNAME
>
> [homes]
>          browseable = no
>    read only = no
Remove template homedir from global and add following to your homes section:

path = /data1/homes

And while defining home directory for users in dsa.msc give following path:

\\SRV4\homes\%USERAME%

And it should work fine.

Regards,
Nishant

Well,

In that case you could choose to hide the homes share by naming it homes$
and assigning a network drive say H: to users as their home drive.

This is the way I have implemented it, may be there is some oversight from
my side, but it works for me. And directories are created automagically by
the windows tool.

Regards,
Nishant
On Mar 27, 2013 8:41 PM, "?icro MEGAS" <micromegas at
mail333.com> wrote:
> Hello Nishant,
>
> thanks for your feedback. Well, of course your proposed configuration
> would work, but have a caveats in my eyes:
>
> - a user accessing the share \\s4srv\homes would see all other users home
> directories. Although he cannot enter/access them, I don't like this
> behavior.
> - you would have two shares shown, one is \\s4srv\homes and the other
> cloned one (because of the homes special share) \\s4srv\johndoe. That's
> annoying, too. If I would use "browseable = no" at the [homes]
section,
> than only the share \\s4srv\johndoe would be visible and when you open this
> share, you see again all other users home directories (which is not wanted
> at all).
>
> I would really appreciate to use the special share [homes] as it is
> intended to be used (as described in the manual of smb.conf). But I cannot
> find another option to have ADUC tool use somehow this syntax form of this
> special share which will clone [homes]-->[username]. As I think exactly
> that is the problem, that's why ADUC cannot access this share to create
a
> subdir there.
>
> Of course there would be an option to use logon scripts to create a
> non-existing home dir on-the-fly after the user logs in. I just wanted to
> ask here on the community, if I miss something and maybe there's a
> workaround to use [homes] as described initially on my post here *AND* to
> have ADUC tool creates a homedir for a user.
>
> However, thanks for your feedback.
>
> Cheers,
> Lucas.
>
> ??? 27 ??? 2013 18:50:02 +0400, Nishant Sharma <codemarauder at
gmail.com>
> ???????:
>
>
> On Mar 27, 2013 8:08 PM, "?icro MEGAS" <micromegas at
mail333.com<http://compose/?adb_to=micromegas at mail333.com>>
> wrote:
> >
>
> >
> > My smb.conf contains:
> >
> > [global]
> >    template homedir = /data1/homes/%ACCOUNTNAME
> >
> > [homes]
> >          browseable = no
> >    read onlyXSSCleaned= no
>
> Remove template homedir from global and add following to your homes
> section:
>
> path = /data1/homes
>
> And while defining home directory for users in dsa.msc give following path:
>
> \\SRV4\homes\%USERAME%
>
> And it should work fine.
>
> Regards,
> Nishant
>
>