Hi! I have an Windows 2003 with Active Directory providing authentication to the network, and a SUSE box providing file services (currently hosting the users' homes). Now I want to migrate the roaming profiles from the Windows 2003 box to the SUSE box, but it is proving difficult. I copied a profile folder for a test user to the SUSE box and changed its permissions to give ownership back to the user, but after changing the users' profile path in AD, Windows clients say they can't use the profile (the share is accessible to the user though). My samba configuration isn't using winbind, its using kerberos + local ldap authentication. Can this be a permissions problem? Do I need to run winbind to be able to do this? I thought roaming profiles were little more that normal shares... Carlos Rodrigues
Carlos Rodrigues schrieb:> Hi! > > I have an Windows 2003 with Active Directory providing authentication to > the network, and a SUSE box providing file services (currently hosting > the users' homes). > > Now I want to migrate the roaming profiles from the Windows 2003 box to > the SUSE box, but it is proving difficult. > > I copied a profile folder for a test user to the SUSE box and changed > its permissions to give ownership back to the user, but after changing > the users' profile path in AD, Windows clients say they can't use the > profile (the share is accessible to the user though). > > My samba configuration isn't using winbind, its using kerberos + local > ldap authentication. > > Can this be a permissions problem? Do I need to run winbind to be able > to do this? I thought roaming profiles were little more that normal > shares... > > Carlos Rodrigues >i think you have to use robocopy cause only this will let the acl stay, as far i remember there is something written about it in the samba profiles faqs -- Mit freundlichen Gruessen Best Regards Robert Schetterer robert_at_schetterer.org Munich / Bavaria / Germany https://www.schetterer.org \********************************** \* gnupgp \* public key: \* https://www.schetterer.org/public.key \**********************************
Mr. Boy wrote:>you will have to change some settings in windows clients, open >gpedit.msc. > >Then find these setting (i dont remember where they are and i dont have >a windows near ): > >enable this: >under Computer Configuration -> Administrative Templates -> System -> >Logon > > 1. Do not check for ownership of roaming profiles folders > 2. Add the administrators security group to roaming users profiles > 3. Wait for remote user profile > >this should fix your problem... > >It did. Thanks! Carlos Rodrigues