Forcing Local Profiles with a Samba PDC Is there any way for Samba to force all NT and Win2k clients of a Samba 2.2.7 PDC to use LOCAL profiles instead of ROAMING profiles? In my area each M$ box is attached to test equipment. The differences in test equipment between M$ boxes is significant. Roaming profiles are causing boxes to complain about hardware that exists only on another box. Forcing local profiles seems to be the logical fix for this problem, however I don't see a way to do this in smb.conf. Currently I have made the "profile" directory in each user's home directory (Samba's Z: drive) owned by root and chmod 500. This seems to work but causes an error on login about their "roaming profile is not available". Is there a way to force local profiles without causing this error on login? Thanks for any insight you might provide. Regards, Randy Parker Dallas, Texas
Just change the logon path option in your smb.conf to "logon path = ". When there is no path set this will make the windows clients store the profiles locally. Patrick Gunerud Randy Parker wrote:>Forcing Local Profiles with a Samba PDC > >Is there any way for Samba to force all NT and Win2k >clients of a Samba 2.2.7 PDC to use LOCAL profiles >instead of ROAMING profiles? > >In my area each M$ box is attached to test equipment. >The differences in test equipment between M$ boxes >is significant. Roaming profiles are causing boxes >to complain about hardware that exists only on another >box. Forcing local profiles seems to be the logical >fix for this problem, however I don't see a way to >do this in smb.conf. > >Currently I have made the "profile" directory in each >user's home directory (Samba's Z: drive) owned by root >and chmod 500. This seems to work but causes an error >on login about their "roaming profile is not available". > >Is there a way to force local profiles without causing >this error on login? Thanks for any insight you might >provide. > >Regards, >Randy Parker >Dallas, Texas > >
>Is there a way to force local profiles >without causing this error on login?Making profiles mandatory. But it's probably better to configure a policy that all profiles should be local automatically. You would have the same problem with a Windows server too. This is not a samba-specific problem imho.