failure copying profiles, using temp profile

[Kohei Yoshida]

On Wed, 2002-01-02 at 21:57, Paul Miller wrote:
> Would it help to put the profile directory inside each user's home?

No it wouldn't.  It's best that you have a separate profile share, and I
understand you've already done that.

I also need to say that I had no idea that you were using 3.0 alpha
version of Samba.  That's a whole new different code (not to mention
it's still alpha), and I'm just not sure how much of my suggestions can
apply to 3.0.  I use Samba 2.2.2, and the following works perfectly for
me.

[global]

    logon path = \\Server1\profiles\%u

[profiles]
    comment = Profile Directory for NT/2k Machines
    path = /path/to/profile
    writeable = yes
    create mask = 0600
    directory mask = 0700
    nt acl support = no  #<- This shouldn't be necessary but won't hurt
anyway.


Inside the profiles share, there is one directory for each user where
the name of the directory is identical to the associated user name.  For
example, let's say you have users named albert, bob, charlie, david,
edward, then you need to manually create under the profile directory:

mode        user       group          directory
------------------------------------------------
drwx------  albert     albert         albert/
drwx------  bob        bob            bob/
drwx------  charlie    charlie        charlie/
drwx------  david      david          david/
drwx------  edward     edward         edward/

The gist of it is that each user must have a directory with his/her
name, and have write permission to his/her own profile share (but of
course other users shouldn't be able to even browse other users
profiles).  If, for example, there is a user named frank, and there is
no directory named frank under the profiles share, then frank will
receive a "profile not found on server" (or something similar) error
message when he logs in.

As long as you follow this, the roaming profiles should work.  You may
well have already covered all of this, but I just need to make sure that
I understand your situation correctly.  I also suggest you try this on
samba 2.2.2 if this doesn't work on 3.0-alpha.

Kohei

> delete profiles share
> set logon home = \\penguin\%u
> set logon path = \\penguin\%u\profile
> 
> -Paul
> 
> On Wed, 2 Jan 2002, Paul Miller wrote:
> 
> > My Samba (3.0 cvs) server is running as a PDC and I also have "nt acl
> > support = no" in the global section and the profiles share.  The profiles
> > share is located outside of the home directory.  Any other ideas?
> > 
> > Thanks
> > -Paul
> > 
> > On 2 Jan 2002, Kohei Yoshida wrote:
> > 
> > > On Wed, 2002-01-02 at 16:18, Paul Miller wrote:
> > > > yes, I run net to synchronize the client's time in the logon script.  This
> > > > error occurs before the client runs the logon script...?  I double checked
> > > > if the logon script is working, and it is -- the time is corrected on a
> > > > successful logon.  Should I synchronize the time? 
> > > 
> > > No.  You've already covered that.
> > > 
> > > > But still, why would windows complain about a file not being found?
> > > 
> > > Hmm...  I'll give you two other things that I know of related to serving
> > > profiles on Samba.  
> > > 
> > > 1) If you use a Samba server (not as a PDC) to serve profiles for Win2k
> > > SP2, you must add "nt acl support = no" to the profile share, or you'll
> > > get "Access Denied" message (per docs/README.Win2kSP2 included in the
> > > source package of samba 2.2.2).
> > > 
> > > 2) If the profile share is inside the home share, sometimes a Windows
> > > client can't find the profile share, because it is not a guarantee that
> > > the client connects to the home share before it does the profile share. 
> > > 
> > > 
> > > Unfortunately these are all I know regarding profiles.  If these don't
> > > help, maybe others can help?  :)
> > > 
> > > Kohei
> > > 
> > > > -Paul
> > > > On 2 Jan 2002, Kohei Yoshida wrote:
> > > > 
> > > > > On Wed, 2002-01-02 at 14:56, Paul Miller wrote:
> > > > > > (C) Everything works if I delete the user profile and he/she logs in/out
> > > > > > again... but soon screws up when logging in on multiple computers with
> > > > > > different versions of windows, etc.
> > > > > 
> > > > > This is just a quick guess, but do you have your client machines
> > > > > synchronize their time with the Samba server (or whatever time server
> > > > > that you may have available)?  I've never had this type of problem so I
> > > > > may be totally wrong, but I saw someone mention on this list (a fairly
> > > > > long time ago) that if the time is not properly synchronized, it may
> > > > > cause a problem when downloading/uploading profiles. This is because
> > > > > Windows relies on this to determine whether or not to update the local
> > > > > profile data.
> > > > > 
> > > > > Just a thought.
> > > > > 
> > > > > Kohei
> > > > > 
> > > > > 
> > > > 
> > > > 
> > > > -- 
> > > > To unsubscribe from this list go to the following URL and read the
> > > > instructions:  http://lists.samba.org/mailman/listinfo/samba
> > > > 
> > > 
> > > 
> > > 
> > > -- 
> > > To unsubscribe from this list go to the following URL and read the
> > > instructions:  http://lists.samba.org/mailman/listinfo/samba
> > > 
> > 
> > 
> > 
> > -- 
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  http://lists.samba.org/mailman/listinfo/samba
> > 
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
>