From 5c572b216eb9e9e40e85625ddf71e98f64a57039 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Thu, 24 Apr 2003 22:52:07 +0000 Subject: Update: ADS: Type, ProfileMgmt: Docs on how to disable roaming profiles (This used to be commit a154203e338d905dfa9427678dfdb0141dd2f735) --- docs/docbook/projdoc/ADS-HOWTO.sgml | 10 +++--- docs/docbook/projdoc/ProfileMgmt.sgml | 59 ++++++++++++++++++++++++++++++++++- 2 files changed, 63 insertions(+), 6 deletions(-) (limited to 'docs') diff --git a/docs/docbook/projdoc/ADS-HOWTO.sgml b/docs/docbook/projdoc/ADS-HOWTO.sgml index c7def652fc..c36f150112 100644 --- a/docs/docbook/projdoc/ADS-HOWTO.sgml +++ b/docs/docbook/projdoc/ADS-HOWTO.sgml @@ -56,15 +56,16 @@ In case samba can't figure out your ads server using your realm name, use the Test your config by doing a kinit -USERNAME@REALM and making sure that - your password is accepted by the Win2000 KDC. +USERNAME@REALM and +making sure that your password is accepted by the Win2000 KDC. + The realm must be uppercase or you will get "Cannot find KDC for requested realm while getting initial credentials" error Time between the two servers must be synchronized. You will get a "kinit(v5): Clock skew too great while getting initial credentials" if the time -difference is more than five minutes. +difference is more than five minutes. You also must ensure that you can do a reverse DNS lookup on the IP @@ -86,8 +87,7 @@ If all you want is kerberos support in &smbclient; then you can skip straight to Test with &smbclient; now. Creating a computer account and testing your servers -is only needed if you want kerberos -support for &smbd; and &winbindd;. +is only needed if you want kerberos support for &smbd; and &winbindd;. diff --git a/docs/docbook/projdoc/ProfileMgmt.sgml b/docs/docbook/projdoc/ProfileMgmt.sgml index bc0113baeb..ac61391306 100644 --- a/docs/docbook/projdoc/ProfileMgmt.sgml +++ b/docs/docbook/projdoc/ProfileMgmt.sgml @@ -122,6 +122,63 @@ You can support profiles for both Win9X and WinNT clients by setting both the logon path = \\%L\profiles\%u + + +Disabling Roaming Profile Support + + +A question often asked is "How may I enforce use of local profiles?" or +"How do I disable Roaming Profiles?" + + + +There are three ways of doing this: + + + + + In smb.conf: affect the following settings and ALL clients + will be forced to use a local profile: + + logon home = + logon path = + + + + MS Windows Registry: by using the Microsoft Management Console + gpedit.msc to instruct your MS Windows XP machine to use only a local profile. This + of course modifies registry settings. The full path to the option is: + + Local Computer Policy\ + Computer Configuration\ + Administrative Templates\ + System\ + User Profiles\ + + Disable: Only Allow Local User Profiles + Disable: Prevent Roaming Profile Change from Propogating to the Server + + + + + Change of Profile Type: From the start menu right click on the + MY Computer icon, select Properties, click on the "User Profiles + tab, select the profile you wish to change from Roaming type to Local, click Change Type. + + + + +Consult the MS Windows registry guide for your particular MS Windows version for more +information about which registry keys to change to enforce use of only local user +profiles. + + + +The specifics of how to convert a local profile to a roaming profile, or a roaming profile +to a local one vary according to the version of MS Windows you are running. Consult the +Microsoft MS Windows Resource Kit for your version of Windows for specific information. + + @@ -885,7 +942,7 @@ The default entries are: Common Desktop %SystemRoot%\Profiles\All Users\Desktop Common Programs %SystemRoot%\Profiles\All Users\Programs Common Start Menu %SystemRoot%\Profiles\All Users\Start Menu - Common Startu p %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup + Common Startup %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup -- cgit