It took a few days of beating my head against a wall, but my roaming
profiles now roam.  Turns out to be more a legacy MS Windows than Samba
issue.

Situation:

  - Samba 3.0.x (current Debian testing/unstable).

  - 10 WinXP Pro clients.

  - A working Samba server which offers share, domain login (aka PDC),
    and centralized print services.

However, user profiles weren't roaming properly.  The profile from the
network share wouldn't be fetched at logon (the local Default User
profile was used instead), and wasn't saved to the [profiles] share at
logout.

Configuration was taken pretty much straight from the Samba 3 HOWTO
Collection docs, and I ruled out issues such as file permissions or
misspecified 'logon path' values.

The problem turned out to be a legacy MS Windows Registry key:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System] 
"LocalProfile"=dword:00000001

Changing that to:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System] 
"LocalProfile"=dword:00000000

...allows profiles to roam.


I don't have this as a .REG file, but setting and saving this value will
allow you to apply the value simply by double-clicking the registry
file (among other tools).  Samba distributes several such registry files
for sorting other issues.


My only question is this:  is this key documented somewhere, and how
would one ordinarially go about getting documentation on a registry key?


Peace.

-- 
Karsten M. Self <[EMAIL PROTECTED]>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
     And can you imagine fifty people a day? I said FIFTY people a day...
     walkin' in, singin' a bar of "Alice's Restaurant" and walkin' out?
     Friends, they may think it's a MOVEMENT!
    - A. Guthrie

Attachment: signature.asc
Description: Digital signature

Reply via email to