>> We were striving for live network stored access - no replication - have I
>> missed something else?
>I think so, this sounds exactly like how *roaming* profiles behave.
>Use a policy to redirect "My Documents" out of the profile an to a
>'real' share somewhere like \\{servername}\homedir. The
We were striving for live network stored access - no replication - have I
missed something else?
Oh, I guess I misunderstood. That's not the way Windows works by
default. Windows copies all of the profile locally then does all file
access on the client. At logoff that is copied back to the
> [Mitch says:] D'oh! Ok- I've set that, still seeing the problem though -
> without the error message (yes I was smart enough to restart smbd ;-)
Actually, changes to the smb.conf become live withing a few minutes,
you don't need to restart.
> When the user logs on, the profile folder is created
[Paul says:] Perhaps you should try messing with this setting in the share
you're having problems with. From the man page:
[Mitch says:] D'oh! Ok- I've set that, still seeing the problem though -
without the error message (yes I was smart enough to restart smbd ;-)
When the user logs on, the prof
The error is apparently that as Samba doesn't support telling 2003 NOT to
cache network data offline, 2003 DOES THIS by default, which means I'm not
Perhaps you should try messing with this setting in the share you're
having problems with. From the man page:
csc policy (S)
This stands for
Sorry - sent before completed.- my apologies for the dup.
I've got Samba set up with the homes share configured.
I've added the settings under the Terminal Services Profile tab of a test
user.
When I log in, the folder specified is created, but it doesn't receive any
data files until th
I've got Samba set up with the homes share configured.
I've added the settings under the Terminal Services Profile tab of a test
user.
When I log in, the folder specified is created, but it doesn't receive any
data files until the user logs off.
In the NT event viewer, I see :
Event Ty