[Samba] roaming profile not uploaded correctly when logging out for the first time

[Jason Baker]

I experienced this same issue and it turned out to be a permissions 
problem in the windows client. I had copied some files from the users 
old machine profile to their new domain profile and then logged out. It 
complained that it could not write to the roaming profile. I went back 
into the account, in your case it would be C:\Documents and 
Settingsd\user\SendTo\31/2Floppy(A).lnk and right click the file and go 
to Sharing and Security. You need to make sure the domain user has read 
write access to that file. After I changed the permissions, logout was 
successful.

*Jason Baker
*/IT Coordinator/


*Glastender Inc.*
5400 North Michigan Road
Saginaw, Michigan 48604 USA
800.748.0423
Phone: 989.752.4275 ext. 228
Fax: 989.752.4444
www.glastender.com <http://www.glastender.com>

-----BEGIN GEEK CODE BLOCK----- 
Version: 3.1
GIT$ d- s: a C++$ LU+++$ P+ L++>L++++ !E--- W+++ N o? K?
w !O M !V PS PE- Y? PGP- t 5? X+ R+ tv+ b- DI-- D++ G e+ h--- 
r+++ y+++
------END GEEK CODE BLOCK------



On 3/14/2007 7:33 AM, Tomasz Chmielewski wrote:
> I have a strange issue with roaming profiles.
>
> It only happens for users which has no roaming profile on a Samba 
> server yet.
>
> When a user logs out for the first time, some files can't be copied from:
>
> C:\Documents and Settings\username\SendTo\
>
> to a profiles directory on the server.
>
> (Files like 31/2Floppy(A).lnk, some *.tmp files etc.).
>
>
> Only very rarely, a first-time logout process happens without any 
> problems.
> Second and any later logouts are without problems.
>
>
> I found another reference on the list:
>
> lists.samba.org/archive/samba/2002-December/057885.html
>
>
> "When user logoff it appear
>
> Windows cannot copy file C:\Documents and 
> Settingsd\user\SendTo\31/2Floppy(A).lnk to location 
> \\192.168.0.1\domain\profiles\user\SendTo\3 1/2 Floppy(A).lnk. Contact 
> your network administrator
>
> Are there someone found like me?"
>
>
> Is it a Windows problem, or Samba problem?
>
> I'm using Samba 3.0.24.
>
>