[Samba] Moving from SAMBA to 2003 domain with XP SP# client machines roaming profiles stopped working
phillipd at oem.doe.gov
Wed Feb 9 12:47:18 MST 2011
We have been directed to move off a SAMBA domain to a server 2003R2
domain. We run roaming profiles with samba and would like to continue
this on 2003R2. After bringing all the XPSP3 desktops into the 2003R2
domain, roaming profiles wont work. I'm not even trying to use the
SAMBA generated profiles. The error I get when logging on is:
*Windows cannot locate the server copy of your roaming profile and is
attempting to log you on with your local profile. Changes to the
profile will not be copied to the server when you logoff.
Errors in the event viewer are:
DETAIL - Configuration information could not be read from the domain
controller, either because the machine is unavailable, or access has
This only happens on machines we switched from SAMBA. Any other machine
we add to the AD Domain that wasn't in the SAMBA domain handles roaming
profiles just fine. Has anyone ever seen this behavior? I've checked
the permissions on "Documents and Settings" and they are the same as on
other machines that work so I don't think it's a permissions problem
loading a profile into the Documents and Settings Dir. I've tried
flushing old local group policies with gpedit, loading the policy
templates. I just don't know where to go from here and what else to
try, short of re-imaging the machines. They come into the AD Domain
just fine and authenticate users, but roaming profiles won't load. This
even occurs if the roaming profile account used is a "Domain Admin".
We are using SAMBA version 3.0.33...
Thank you very much in advance for your time...
Doug P (Sadly moving off Linux)
More information about the samba