samba - Dec 2010 - samba 3.5.x, pdbedit smb.conf and profiles

Who wins the fight for the roaming profile path, "logon path" in
smb.conf or "profile path" set by pdbedit?

How do you force the "profile path" in pdbedit to get its value from
"logon path" in smb.conf?

Is it possible to disable roaming profiles by user with pdbedit and leave
"logon path" set in smb.conf?

Thanks.

I would guess that the per-user settings should override the general 
smb.conf settings.

I had problems with roaming profiles-  I didn't want to use them but 
sometimes on client logins/logouts the XP client would try to load or 
create one.  I have an ldap backend and eventually just deleted the 
profile parameter in ldap for problem users altogether.




On 12/05/2010 12:08 PM, Andy wrote:
> Who wins the fight for the roaming profile path, "logon path" in 
> smb.conf or "profile path" set by pdbedit?
>
> How do you force the "profile path" in pdbedit to get its value
from
> "logon path" in smb.conf?
>
> Is it possible to disable roaming profiles by user with pdbedit and 
> leave "logon path" set in smb.conf?
>
> Thanks.
>
>

Yes, that is it exactly.


On 12/8/2010 5:14 PM, Chris Smith wrote:
> On Tue, Dec 7, 2010 at 1:29 PM, Andy<ange3791 at area5101.com> 
wrote:
>> How do you remove the per-user value with pdbedit and have the value
read
>> from smb.conf? I have tried setting the per-user value both to
"" and NULL.
> I reported a similar problem on May 26, 2010, the post was titled "how
> to reset logon script inheritance?"
>
> It seems there are certain values that are inherited from smb.conf but
> once you set them individually with pdbedit the tdbsam is effectively
> "tattooed" - that is there is seemingly no way to get that
setting
> back to automatic inheritance.
>
> Is this a bug? Or have we just missed the proper documentation?
>
> Chris

Hello,

2010/12/9 Andy <ange3791 at area5101.com>:
> Yes, that is it exactly.
On 12/8/2010 5:14 PM, Chris Smith wrote:
>>
>> I reported a similar problem on May 26, 2010, the post was titled
"how
>> to reset logon script inheritance?"
>>
>> It seems there are certain values that are inherited from smb.conf but
>> once you set them individually with pdbedit the tdbsam is effectively
>> "tattooed" - that is there is seemingly no way to get that
setting
>> back to automatic inheritance.
>>
>> Is this a bug? Or have we just missed the proper documentation?
I think this behavior is by design. In smb.conf(5), there is a warning
notice at the description of "logon path":

-----
Where the tdbsam or ldapsam passdb
backend is used, at the time the user account is created the
value configured for this parameter is written to the passdb
backend and that value will over-ride the parameter value
present in the smb.conf file.
-----

This warning should be applied not only at "logon path" but also at
"logon home", "logon script" and  "logon drive".

---
TAKAHASHI Motonobu <monyo at samba.gr.jp>

On Wed, Dec 8, 2010 at 6:36 PM, TAKAHASHI Motonobu <monyo at monyo.com>
wrote:
> I think this behavior is by design.
The override is clearly by design, but the inability to get back to
the inherited state seems more like an unintended consequence (I just
tend to doubt someone would purposely design it this way) that nobody
was interested in solving. Would be extremely helpful to be able to
reset inheritance in such cases.

Chris