From cc841dde2f26843c2b6ec788337b779ed1abf8ea Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 27 May 2003 16:46:06 +0000 Subject: A lot of syntax updates, consistency when using certain tags and converting ASCII -> XML (This used to be commit 85434d3144656e6fe587637276d6a2667df1857f) --- docs/docbook/projdoc/ProfileMgmt.xml | 582 +++++++++++++++++++---------------- 1 file changed, 313 insertions(+), 269 deletions(-) (limited to 'docs/docbook/projdoc/ProfileMgmt.xml') diff --git a/docs/docbook/projdoc/ProfileMgmt.xml b/docs/docbook/projdoc/ProfileMgmt.xml index 680555cd6a..fc51b1826c 100644 --- a/docs/docbook/projdoc/ProfileMgmt.xml +++ b/docs/docbook/projdoc/ProfileMgmt.xml @@ -320,7 +320,7 @@ they will be told that they are logging in "for the first time". instead of logging in under the [user, password, domain] dialog, - press escape. + press escape. @@ -342,9 +342,9 @@ they will be told that they are logging in "for the first time". [Exit the registry editor]. - - - WARNING - before deleting the contents of the + + + Before deleting the contents of the directory listed in the ProfilePath (this is likely to be c:\windows\profiles\username), ask them if they have any important files stored on their desktop or in their start menu. @@ -357,11 +357,11 @@ they will be told that they are logging in "for the first time". system file) user.DAT in their profile directory, as well as the local "desktop", "nethood", "start menu" and "programs" folders. - + - search for the user's .PWL password-caching file in the c:\windows + search for the user's .PWL password-caching file in the c:\windows directory, and delete it. @@ -374,8 +374,8 @@ they will be told that they are logging in "for the first time". - check the contents of the profile path (see "logon path" described - above), and delete the user.DAT or user.MAN file for the user, + check the contents of the profile path (see logon path described + above), and delete the user.DAT or user.MAN file for the user, making a backup if required. @@ -384,7 +384,7 @@ they will be told that they are logging in "for the first time". If all else fails, increase samba's debug log levels to between 3 and 10, -and / or run a packet trace program such as ethereal or netmon.exe, and +and / or run a packet trace program such as ethereal or netmon.exe, and look for error messages. @@ -403,12 +403,12 @@ differences are with the equivalent samba trace. When a user first logs in to a Windows NT Workstation, the profile NTuser.DAT is created. The profile location can be now specified -through the "logon path" parameter. +through the logon path parameter. There is a parameter that is now available for use with NT Profiles: -"logon drive". This should be set to H: or any other drive, and +logon drive. This should be set to H: or any other drive, and should be used in conjunction with the new "logon home" parameter. @@ -422,23 +422,23 @@ for those situations where it might be created.) In the profile directory, Windows NT4 creates more folders than Windows 9x / Me. -It creates "Application Data" and others, as well as "Desktop", "Nethood", -"Start Menu" and "Programs". The profile itself is stored in a file -NTuser.DAT. Nothing appears to be stored in the .PDS directory, and +It creates Application Data and others, as well as Desktop, Nethood, +Start Menu and Programs. The profile itself is stored in a file +NTuser.DAT. Nothing appears to be stored in the .PDS directory, and its purpose is currently unknown. -You can use the System Control Panel to copy a local profile onto +You can use the System Control Panel to copy a local profile onto a samba server (see NT Help on profiles: it is also capable of firing -up the correct location in the System Control Panel for you). The -NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN +up the correct location in the System Control Panel for you). The +NT Help file also mentions that renaming NTuser.DAT to NTuser.MAN turns a profile into a mandatory one. The case of the profile is significant. The file must be called -NTuser.DAT or, for a mandatory profile, NTuser.MAN. +NTuser.DAT or, for a mandatory profile, NTuser.MAN. @@ -450,58 +450,58 @@ You must first convert the profile from a local profile to a domain profile on the MS Windows workstation as follows: - - - Log on as the LOCAL workstation administrator. - + + + Log on as the LOCAL workstation administrator. + - - Right click on the 'My Computer' Icon, select 'Properties' - + + Right click on the My Computer Icon, select Properties + - - Click on the 'User Profiles' tab - + + Click on the User Profiles tab + - + Select the profile you wish to convert (click on it once) - + - - Click on the button 'Copy To' - + + Click on the button Copy To + - - In the "Permitted to use" box, click on the 'Change' button. - + + In the Permitted to use box, click on the Change button. + - + Click on the 'Look in" area that lists the machine name, when you click here it will open up a selection box. Click on the domain to which the profile must be accessible. You will need to log on if a logon box opens up. Eg: In the connect - as: MIDEARTH\root, password: mypassword. - + as: MIDEARTH\root, password: mypassword. + - + To make the profile capable of being used by anyone select 'Everyone' - + - - Click OK. The Selection box will close. - + + Click OK. The Selection box will close. + - - Now click on the 'Ok' button to create the profile in the path you + + Now click on the Ok button to create the profile in the path you nominated. - - + + Done. You now have a profile that can be editted using the samba-3.0.0 -profiles tool. +profiles tool. @@ -512,16 +512,16 @@ storage of mail data. That keeps desktop profiles usable. - - + + This is a security check new to Windows XP (or maybe only Windows XP service pack 1). It can be disabled via a group policy in Active Directory. The policy is: -"Computer Configuration\Administrative Templates\System\User -Profiles\Do not check for user ownership of Roaming Profile Folders" +Computer Configuration\Administrative Templates\System\User +Profiles\Do not check for user ownership of Roaming Profile Folders -...and it should be set to "Enabled". +...and it should be set to Enabled. Does the new version of samba have an Active Directory analogue? If so, then you may be able to set the policy through this. @@ -533,36 +533,35 @@ the following (N.B. I don't know for sure that this will work in the same way as a domain group policy): - + - + On the XP workstation log in with an Administrator account. - - - Click: "Start", "Run" - Type: "mmc" - Click: "OK" - - A Microsoft Management Console should appear. - Click: File, "Add/Remove Snap-in...", "Add" - Double-Click: "Group Policy" - Click: "Finish", "Close" - Click: "OK" - - In the "Console Root" window: - Expand: "Local Computer Policy", "Computer Configuration", - "Administrative Templates", "System", "User Profiles" - Double-Click: "Do not check for user ownership of Roaming Profile - Folders" - Select: "Enabled" - Click: OK" - - Close the whole console. You do not need to save the settings (this + + + Click: Start, Run + Type: mmc + Click: OK + + A Microsoft Management Console should appear. + Click: File, Add/Remove Snap-in..., Add + Double-Click: Group Policy + Click: Finish, Close + Click: OK + + In the "Console Root" window: + Expand: Local Computer Policy, Computer Configuration, + Administrative Templates, System, User Profiles + Double-Click: Do not check for user ownership of Roaming Profile Folders + Select: Enabled + Click: OK + + Close the whole console. You do not need to save the settings (this refers to the console settings rather than the policies you have - changed). + changed). - Reboot - + Reboot + @@ -584,13 +583,13 @@ on again with the newer version of MS Windows. If you then want to share the same Start Menu / Desktop with W9x/Me, you will need to specify a common location for the profiles. The smb.conf parameters -that need to be common are logon path and -logon home. +that need to be common are logon path and +logon home. -If you have this set up correctly, you will find separate user.DAT and -NTuser.DAT files in the same profile directory. +If you have this set up correctly, you will find separate user.DAT and +NTuser.DAT files in the same profile directory. @@ -617,14 +616,14 @@ NT4/200x. The correct resource kit is required for each platform. Here is a quick guide: - + - -On your NT4 Domain Controller, right click on 'My Computer', then -select the tab labelled 'User Profiles'. - + +On your NT4 Domain Controller, right click on My Computer, then +select the tab labelled User Profiles. + - + Select a user profile you want to migrate and click on it. @@ -632,20 +631,20 @@ Select a user profile you want to migrate and click on it. create a group profile. You can give the user 'Everyone' rights to the profile you copy this to. That is what you need to do, since your samba domain is not a member of a trust relationship with your NT4 PDC. - + - Click the 'Copy To' button. +Click the Copy To button. - In the box labelled 'Copy Profile to' add your new path, eg: - c:\temp\foobar + In the box labelled Copy Profile to add your new path, eg: + c:\temp\foobar - Click on the button labelled 'Change' in the "Permitted to use" box. + Click on the button Change in the Permitted to use box. - Click on the group 'Everyone' and then click OK. This closes the - 'chose user' box. + Click on the group 'Everyone' and then click OK. This closes the + 'choose user' box. - Now click OK. - + Now click OK. + Follow the above for every profile you need to migrate. @@ -690,7 +689,7 @@ Resource Kit. Windows NT 4.0 stores the local profile information in the registry under the following key: -HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList +HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList @@ -730,7 +729,7 @@ file in the copied profile and rename it to NTUser.MAN. -For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to +For MS Windows 9x / Me it is the User.DAT file that must be renamed to User.MAN to affect a mandatory profile. @@ -750,7 +749,7 @@ to the group profile. -The next step is rather important. PLEASE NOTE: Instead of assigning a group profile +The next step is rather important. Please note: Instead of assigning a group profile to users (ie: Using User Manager) on a "per user" basis, the group itself is assigned the now modified profile. @@ -780,18 +779,19 @@ advantages. MS Windows 9x/Me -To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System -Policy Editor or change the registry directly. +To enable default per use profiles in Windows 9x / Me you can either use the Windows 98 System +Policy Editor or change the registry directly. -To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then -select File -> Open Registry, then click on the Local Computer icon, click on Windows 98 System, -select User Profiles, click on the enable box. Do not forget to save the registry changes. +To enable default per user profiles in Windows 9x / Me, launch the System Policy Editor, then +select File -> Open Registry, then click on the +Local Computer icon, click on Windows 98 System, +select User Profiles, click on the enable box. Do not forget to save the registry changes. -To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive +To modify the registry directly, launch the Registry Editor (regedit.exe), select the hive HKEY_LOCAL_MACHINE\Network\Logon. Now add a DWORD type key with the name "User Profiles", to enable user profiles set the value to 1, to disable user profiles set it to 0. @@ -831,7 +831,7 @@ profile, the changes are written to the user's profile on the server. On MS Windows NT4 the default user profile is obtained from the location %SystemRoot%\Profiles which in a default installation will translate to C:\WinNT\Profiles. Under this directory on a clean install there will be -three (3) directories: Administrator, All Users, Default User. +three (3) directories: Administrator, All Users, Default User. @@ -854,8 +854,8 @@ When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft the following steps are followed in respect of profile handling: - - + + The users' account information which is obtained during the logon process contains the location of the users' desktop profile. The profile path may be local to the @@ -865,25 +865,25 @@ the following steps are followed in respect of profile handling: settings in the All Users profile in the %SystemRoot%\Profiles location. - + - + If the user account has a profile path, but at it's location a profile does not exist, then a new profile is created in the %SystemRoot%\Profiles\%USERNAME% directory from reading the Default User profile. - + - + If the NETLOGON share on the authenticating server (logon server) contains a policy file (NTConfig.POL) then it's contents are applied to the NTUser.DAT which is applied to the HKEY_CURRENT_USER part of the registry. - + - + When the user logs out, if the profile is set to be a roaming profile it will be written out to the location of the profile. The NTuser.DAT file is then @@ -892,8 +892,8 @@ the following steps are followed in respect of profile handling: next logon, the effect of the provious NTConfig.POL will still be held in the profile. The effect of this is known as tatooing. - - + + MS Windows NT4 profiles may be Local or Roaming. A Local profile @@ -925,59 +925,58 @@ are controlled by entries on Windows NT4 is: - - HKEY_CURRENT_USER - \Software - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders\ - +HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\ The above hive key contains a list of automatically managed folders. The default entries are: - - - Name Default Value - -------------- ----------------------------------------- - AppData %USERPROFILE%\Application Data - Desktop %USERPROFILE%\Desktop - Favorites %USERPROFILE%\Favorites - NetHood %USERPROFILE%\NetHood - PrintHood %USERPROFILE%\PrintHood - Programs %USERPROFILE%\Start Menu\Programs - Recent %USERPROFILE%\Recent - SendTo %USERPROFILE%\SendTo - Start Menu %USERPROFILE%\Start Menu - Startup %USERPROFILE%\Start Menu\Programs\Startup - - + + + User Shell Folder registry keys default values + + + NameDefault Value + + + AppData%USERPROFILE%\Application Data + Desktop%USERPROFILE%\Desktop + Favorites%USERPROFILE%\Favorites + NetHood%USERPROFILE%\NetHood + PrintHood%USERPROFILE%\PrintHood + Programs%USERPROFILE%\Start Menu\Programs + Recent%USERPROFILE%\Recent + SendTo%USERPROFILE%\SendTo + Start Menu %USERPROFILE%\Start Menu + Startup%USERPROFILE%\Start Menu\Programs\Startup + + +
+ The registry key that contains the location of the default profile settings is: + - - HKEY_LOCAL_MACHINE - \SOFTWARE - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders - + +HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders + + 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 Startup %SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup - + + Defaults of profile settings registry keys + + + Common Desktop%SystemRoot%\Profiles\All Users\Desktop + Common Programs%SystemRoot%\Profiles\All Users\Programs + Common Start Menu%SystemRoot%\Profiles\All Users\Start Menu + Common Startup%SystemRoot%\Profiles\All Users\Start Menu\Progams\Startup + + +
 @@ -1014,7 +1013,7 @@ login name of the user. - This path translates, in Samba parlance, to the smb.conf [NETLOGON] share. The directory + This path translates, in Samba parlance, to the &smb.conf; [NETLOGON] share. The directory should be created at the root of this share and must be called Default Profile. @@ -1064,49 +1063,43 @@ are controlled by entries on Windows 200x/XP is: - - HKEY_CURRENT_USER - \Software - \Microsoft - \Windows - \CurrentVersion - \Explorer - \User Shell Folders\ - +HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\ The above hive key contains a list of automatically managed folders. The default entries are: - - - Name Default Value - -------------- ----------------------------------------- - AppData %USERPROFILE%\Application Data - Cache %USERPROFILE%\Local Settings\Temporary Internet Files - Cookies %USERPROFILE%\Cookies - Desktop %USERPROFILE%\Desktop - Favorites %USERPROFILE%\Favorites - History %USERPROFILE%\Local Settings\History - Local AppData %USERPROFILE%\Local Settings\Application Data - Local Settings %USERPROFILE%\Local Settings - My Pictures %USERPROFILE%\My Documents\My Pictures - NetHood %USERPROFILE%\NetHood - Personal %USERPROFILE%\My Documents - PrintHood %USERPROFILE%\PrintHood - Programs %USERPROFILE%\Start Menu\Programs - Recent %USERPROFILE%\Recent - SendTo %USERPROFILE%\SendTo - Start Menu %USERPROFILE%\Start Menu - Startup %USERPROFILE%\Start Menu\Programs\Startup - Templates %USERPROFILE%\Templates - - + + + Defaults of default user profile paths registry keys + + NameDefault Value + + AppData%USERPROFILE%\Application Data + Cache%USERPROFILE%\Local Settings\Temporary Internet Files + Cookies%USERPROFILE%\Cookies + Desktop%USERPROFILE%\Desktop + Favorites%USERPROFILE%\Favorites + History%USERPROFILE%\Local Settings\History + Local AppData%USERPROFILE%\Local Settings\Application Data + Local Settings%USERPROFILE%\Local Settings + My Pictures%USERPROFILE%\My Documents\My Pictures + NetHood%USERPROFILE%\NetHood + Personal%USERPROFILE%\My Documents + PrintHood%USERPROFILE%\PrintHood + Programs%USERPROFILE%\Start Menu\Programs + Recent%USERPROFILE%\Recent + SendTo%USERPROFILE%\SendTo + Start Menu%USERPROFILE%\Start Menu + Startup%USERPROFILE%\Start Menu\Programs\Startup + Templates%USERPROFILE%\Templates +
+ -There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all -the others are of type REG_EXPAND_SZ. +There is also an entry called "Default" that has no value set. The default entry is of type REG_SZ, all +the others are of type REG_EXPAND_SZ. @@ -1117,21 +1110,20 @@ write the Outlook PST file over the network for every login and logout. To set this to a network location you could use the following examples: + - - %LOGONSERVER%\%USERNAME%\Default Folders - - -This would store the folders in the user's home directory under a directory called "Default Folders" +%LOGONSERVER%\%USERNAME%\Default Folders + +This would store the folders in the user's home directory under a directory called Default Folders You could also use: + - - \\SambaServer\FolderShare\%USERNAME% - +\\SambaServer\FolderShare\%USERNAME% -in which case the default folders will be stored in the server named SambaServer -in the share called FolderShare under a directory that has the name of the MS Windows + + in which case the default folders will be stored in the server named SambaServer +in the share called FolderShare under a directory that has the name of the MS Windows user as seen by the Linux/Unix file system. @@ -1145,12 +1137,9 @@ MS Windows 200x/XP profiles may be Local or Roami A roaming profile will be cached locally unless the following registry key is created: - - - HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\ - "DeleteRoamingCache"=dword:00000001 - +HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft\Windows NT\CurrentVersion\winlogon\"DeleteRoamingCache"=dword:00000001 + In which case, the local cache copy will be deleted on logout. @@ -1192,17 +1181,11 @@ In any case, you can configure only one profile per user. That profile can be either: - - - A profile unique to that user - - - A mandatory profile (one the user can not change) - - - A group profile (really should be mandatory ie:unchangable) - - + + A profile unique to that user + A mandatory profile (one the user can not change) + A group profile (really should be mandatory ie:unchangable) + @@ -1210,33 +1193,67 @@ be either: Can NOT use Roaming Profiles - -> I dont want Roaming profile to be implemented, I just want to give users -> local profiles only. + + I dont want Roaming profile to be implemented, I just want to give users + local profiles only. ... -> Please help me I am totally lost with this error from past two days I tried -> everything and googled around quite a bit but of no help. Please help me. - + Please help me I am totally lost with this error from past two days I tried + everything and googled around quite a bit but of no help. Please help me. + + Your choices are: - 1. Local profiles - - I know of no registry keys that will allow auto-deletion - of LOCAL profiles on log out - 2. Roaming profiles - - your options here are: - - can use auto-delete on logout option - - requires a registry key change on workstation - a) Personal Roaming profiles - - should be preserved on a central server - - workstations 'cache' (store) a local copy + + + + + Local profiles + + I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out + + + + + Roaming profiles + + + can use auto-delete on logout option + requires a registry key change on workstation + + + Your choices are: + + + + Personal Roaming profiles + + - should be preserved on a central server + - workstations 'cache' (store) a local copy - used in case the profile can not be downloaded at next logon - b) Group profiles - - loaded from a cetral place - c) Mandatory profiles - - can be personal or group - - can NOT be changed (except by an administrator + + + + + Group profiles + - loaded from a cetral place + + + + Mandatory profiles + + - can be personal or group + - can NOT be changed (except by an administrator + + + + + + + + + A WinNT4/2K/XP profile can vary in size from 130KB to off the scale. Outlook PST files are most often part of the profile and can be many GB in size. On average (in a well controlled environment) roaming profie size of @@ -1244,64 +1261,91 @@ size. On average (in a well controlled environment) roaming profie size of undisciplined environment I have seen up to 2GB profiles. Users tend to complain when it take an hour to log onto a workstation but they harvest the fuits of folly (and ignorance). + + The point of all the above is to show that roaming profiles and good controls of how they can be changed as well as good discipline make up for a problem free site. + -PS: Microsoft's answer to the PST problem is to store all email in an MS + +Microsoft's answer to the PST problem is to store all email in an MS Exchange Server back-end. But this is another story ...! + + So, having LOCAL profiles means: - a) If lots of users user each machine - - lot's of local disk storage needed for local profiles - b) Every workstation the user logs into has it's own profile - - can be very different from machine to machine + + + If lots of users user each machine - lot's of local disk storage needed for local profiles + Every workstation the user logs into has it's own profile - can be very different from machine to machine + On the other hand, having roaming profiles means: - a) The network administrator can control EVERY aspect of user - profiles - b) With the use of mandatory profiles - a drastic reduction - in network management overheads - c) User unhappiness about not being able to change their profiles - soon fades as they get used to being able to work reliably + + The network administrator can control EVERY aspect of user profiles + With the use of mandatory profiles - a drastic reduction in network management overheads + User unhappiness about not being able to change their profiles soon fades as they get used to being able to work reliably + -But note: + + I have managed and installed MANY NT/2K networks and have NEVER found one where users who move from machine to machine are happy with local profiles. In the long run local profiles bite them. + -> When the client tries to logon to the PDC it looks for a profile to download -> where do I put this default profile. + + + + + Changing the default profile + + +When the client tries to logon to the PDC it looks for a profile to download +where do I put this default profile. + + + Firstly, your samba server need to be configured as a domain controller. - server = user - os level = 32 (or more) - domain logons = Yes + - Plus you need to have a NETLOGON share that is world readable. - It is a good idea to add a logon script to pre-set printer and - drive connections. There is also a facility for automatically - synchronizing the workstation time clock with that of the logon - server (another good thing to do). + + server = user + os level = 32 (or more) + domain logons = Yes + -Note: To invoke auto-deletion of roaming profile from the local -workstation cache (disk storage) you need to use the Group Policy Editor -to create a file called NTConfig.POL with the appropriate entries. This -file needs to be located in the NETLOGON share root directory. + +Plus you need to have a [netlogon] share that is world readable. +It is a good idea to add a logon script to pre-set printer and +drive connections. There is also a facility for automatically +synchronizing the workstation time clock with that of the logon +server (another good thing to do). + + + +To invoke auto-deletion of roaming profile from the local +workstation cache (disk storage) you need to use the Group Policy Editor +to create a file called NTConfig.POL with the appropriate entries. This +file needs to be located in the netlogon share root directory. + Oh, of course the windows clients need to be members of the domain. Workgroup machines do NOT do network logons - so they never see domain profiles. + + Secondly, for roaming profiles you need: logon path = \\%N\profiles\%U (with some such path) logon drive = H: (Z: is the default) Plus you need a PROFILES share that is world writable. - -- cgit