Chapter 24. Desktop Profile Management

@@ -11,7 +11,7 @@ problem to others. In particular, users of mobile computing tools, where often t be a sustained network connection, are often better served by purely Local Profiles. This chapter provides information to help the Samba administrator to deal with those situations also. -

Roaming Profiles

Warning

Roaming Profiles

Warning

Roaming profiles support is different for Win9x / Me and Windows NT4/200x.

Before discussing how to configure roaming profiles, it is useful to see how @@ -24,21 +24,17 @@ profiles are restricted to being stored in the user's home directory.

Windows NT4/200x clients send a NetSAMLogon RPC request, which contains many fields, including a separate field for the location of the user's profiles. -

Samba Configuration for Profile Handling

This section documents how to configure Samba for MS Windows client profile support. -

NT4/200x User Profiles

To support Windows NT4/200x clients, in the [global] section of smb.conf set the following (for example):

-	logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath
-

logon path = \\profileserver\profileshare\profilepath\%U\moreprofilepath

This is typically implemented like: -

-		logon path = \\%L\Profiles\%u
-

logon path = \\%L\Profiles\%u

where %L translates to the name of the Samba server and %u translates to the user name

The default for this option is \\%N\%U\profile, @@ -51,31 +47,26 @@ semantics of %L and %N, as well as %U and %u. MS Windows NT/2K clients at times do not disconnect a connection to a server between logons. It is recommended to NOT use the homes meta-service name as part of the profile share path. -

Windows 9x / Me User Profiles

- To support Windows 9x / Me clients, you must use the logon home parameter. Samba has +

Windows 9x / Me User Profiles

+ To support Windows 9x / Me clients, you must use the logon home parameter. Samba has now been fixed so that net use /home now works as well, and it, too, relies on the logon home parameter.

By using the logon home parameter, you are restricted to putting Win9x / Me profiles in the user's home directory. But wait! There is a trick you can use. If you set the following in the [global] section of your smb.conf file: -

-	logon home = \\%L\%U\.profiles
-

logon home = \\%L\%U\.profiles

then your Windows 9x / Me clients will dutifully put their clients in a subdirectory of your home directory called .profiles (thus making them hidden).

Not only that, but net use /home will also work, because of a feature in Windows 9x / Me. It removes any directory stuff off the end of the home directory area and only uses the server and share portion. That is, it looks like you -specified \\%L\%U for logon home. -

Mixed Windows 9x / Me and Windows NT4/200x User Profiles

+specified \\%L\%U for logon home. +

Mixed Windows 9x / Me and Windows NT4/200x User Profiles

You can support profiles for both Win9X and WinNT clients by setting both the -logon home and logon path parameters. For example: -

-	logon home = \\%L\%u\.profiles
-	logon path = \\%L\profiles\%u
-

Disabling Roaming Profile Support

+logon home and logon path parameters. For example: +

logon home = \\%L\%u\.profiles

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?”

@@ -83,13 +74,11 @@ 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 =
-

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\
@@ -112,15 +101,15 @@ 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.
-

Windows Client Profile Configuration Information

Windows 9x / Me Profile Setup

Windows Client Profile Configuration Information

Windows 9x / Me Profile Setup

When a user first logs in on Windows 9X, the file user.DAT is created, as are folders Start Menu, Desktop, Programs and Nethood. These directories and their contents will be merged with the local versions stored in c:\windows\profiles\username on subsequent logins, taking the most recent from each. You will need to use the [global] -options preserve case = yes, short preserve case = yes and -case sensitive = no in order to maintain capital letters in shortcuts +options preserve case = yes, short preserve case = yes and +case sensitive = no in order to maintain capital letters in shortcuts in any of the profile folders.

The user.DAT file contains all the user's preferences. If you wish to @@ -153,11 +142,11 @@ domain and profiles downloaded from it, if that domain logon server supports it), user name and user's password.

Once the user has been successfully validated, the Windows 9x / Me machine -will inform you that The user has not logged on before' and asks you - if you wish to save the user's preferences? Select yes. +will inform you that The user has not logged on before and asks you +Do you wish to save the user's preferences?. Select yes.

Once the Windows 9x / Me client comes up with the desktop, you should be able -to examine the contents of the directory specified in the logon path +to examine the contents of the directory specified in the logon path on the samba server and verify that the Desktop, Start Menu, Programs and Nethood folders have been created.

@@ -171,14 +160,14 @@ the newest folders and short-cuts from each set. If you have made the folders / files read-only on the samba server, then you will get errors from the Windows 9x / Me machine on logon and logout, as it attempts to merge the local and the remote profile. Basically, if -you have any errors reported by the Windows 9x / Me machine, check the Unix file +you have any errors reported by the Windows 9x / Me machine, check the UNIX file permissions and ownership rights on the profile directory contents, on the samba server.

If you have problems creating user profiles, you can reset the user's local desktop cache, as shown below. When this user then next logs in, they will be told that they are logging in "for the first time". -

Warning

Before deleting the contents of the directory listed in the ProfilePath (this is likely to be c:\windows\profiles\username), ask them if they @@ -189,7 +178,7 @@ they will be told that they are logging in "for the first time". This will have the effect of removing the local (read-only hidden system file) user.DAT in their profile directory, as well as the local "desktop", "nethood", "start menu" and "programs" folders. -

instead of logging in under the [user, password, domain] dialog, press escape.
@@ -206,7 +195,7 @@ they will be told that they are logging in "for the first time".
log off the windows 9x / Me client.
- check the contents of the profile path (see logon path described + 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.

@@ -218,14 +207,14 @@ If you have access to an Windows NT4/200x server, then first set up roaming prof and / or netlogons on the Windows NT4/200x server. Make a packet trace, or examine the example packet traces provided with Windows NT4/200x server, and see what the differences are with the equivalent samba trace. -

Windows NT4 Workstation

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 -should be used in conjunction with the new "logon home" parameter. +logon drive. This should be set to H: or any other drive, and +should be used in conjunction with the new logon home parameter.

The entry for the NT4 profile is a _directory_ not a file. The NT help on profiles mentions that a directory is also created with a .PDS @@ -247,7 +236,7 @@ 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. -

Windows 2000/XP Professional

You must first convert the profile from a local profile to a domain profile on the MS Windows workstation as follows:

@@ -266,8 +255,7 @@ profile on the MS Windows workstation as follows: 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. -
Note
You will need to log on if a logon box opens up. Eg: In the connect - as: MIDEARTH\root, password: mypassword.
+
Note
You will need to log on if a logon box opens up. Eg: In the connect as: DOMAIN\root, password: mypassword.
To make the profile capable of being used by anyone select 'Everyone'
Click OK. The Selection box will close. @@ -275,12 +263,12 @@ profile on the MS Windows workstation as follows: Now click on the Ok button to create the profile in the path you nominated.

-Done. You now have a profile that can be edited using the samba-3.0.0 +Done. You now have a profile that can be edited using the samba profiles tool.

Note

Under NT/2K the use of mandatory profiles forces the use of MS Exchange storage of mail data. That keeps desktop profiles usable. -

Note

Procedure 24.2. Windows XP Service Pack 1

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 @@ -297,7 +285,7 @@ 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 refers to the console settings rather than the policies you have - changed).
Reboot

`Sharing Profiles between W9x/Me and NT4/200x/XP workstations`

+ changed).

Reboot

`Sharing Profiles between W9x/Me and NT4/200x/XP workstations`

Sharing of desktop profiles between Windows versions is NOT recommended. Desktop profiles are an evolving phenomenon and profiles for later versions of MS Windows clients add features that may interfere with earlier versions @@ -308,18 +296,18 @@ version resulting in loss of profile information content when that user logs 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. +need to specify a common location for the profiles. The smb.conf parameters +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. -

`Profile Migration from Windows NT4/200x Server to Samba`

+

`Profile Migration from Windows NT4/200x Server to Samba`

There is nothing to stop you specifying any path that you like for the location of users' profiles. Therefore, you could specify that the profile be stored on a samba server, or any other SMB server, as long as that SMB server supports encrypted passwords. -

`Windows NT4 Profile Management Tools`

+

`Windows NT4 Profile Management Tools`

Unfortunately, the Resource Kit information is specific to the version of MS Windows NT4/200x. The correct resource kit is required for each platform.

@@ -336,17 +324,13 @@ domain is not a member of a trust relationship with your NT4 PDC.

c:\temp\foobar Click on the button Change in the Permitted to use box. Click on the group 'Everyone' and then click OK. This closes the 'choose user' box. Now click OK.

Follow the above for every profile you need to migrate. -

`Side bar Notes`

+

`Side bar Notes`

You should obtain the SID of your NT4 domain. You can use smbpasswd to do -this. Read the man page.

-With Samba-3.0.0 alpha code you can import all you NT4 domain accounts -using the net samsync method. This way you can retain your profile -settings as well as all your users. -

`moveuser.exe`

+this. Read the man page.

`moveuser.exe`

The W2K professional resource kit has moveuser.exe. moveuser.exe changes the security of a profile from one user to another. This allows the account domain to change, and/or the user name to change. -

`Get SID`

+

`Get SID`

You can identify the SID by using GetSID.exe from the Windows NT Server 4.0 Resource Kit.

@@ -359,7 +343,7 @@ users who have logged on to this computer. (To find the profile information for the user whose locally cached profile you want to move, find the SID for the user with the GetSID.exe utility.) Inside of the appropriate user's subkey, you will see a string value named ProfileImagePath. -

`Mandatory profiles`

+

`Default Profile for Windows Users`

MS Windows 9x / Me and NT4/200x/XP will use a default profile for any user for whom a profile does not already exist. Armed with a knowledge of where the default profile is located on the Windows workstation, and knowing which registry keys affect the path from which the default profile is created, it is possible to modify the default profile to one that has been optimised for the site. This has significant administrative advantages. -

`MS Windows 9x/Me`

+

`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.

@@ -409,7 +393,7 @@ select User Profiles, click on the enable box. Do 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. -

`How User Profiles Are Handled in Windows 9x / Me?`

+

`How User Profiles Are Handled in Windows 9x / Me?`

When a user logs on to a Windows 9x / Me machine, the local profile path, HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ProfileList, is checked for an existing entry for that user: @@ -425,7 +409,7 @@ If a User Profile is not found in either location, the Default User Profile from machine is used and is copied to a newly created folder for the logged on user. At log off, any changes that the user made are written to the user's local profile. If the user has a roaming profile, the changes are written to the user's profile on the server. -

`MS Windows NT4 Workstation`

+

`MS Windows NT4 Workstation`

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 @@ -436,7 +420,7 @@ system users. The Default User directory contains menu customisable per user depending on the profile settings chosen/created.

When a new user first logs onto an MS Windows NT4 machine a new profile is created from: -

All Users settings

Default User settings (contains the default NTUser.DAT file)

+

All Users settings
Default User settings (contains the default NTUser.DAT file)

When a user logs onto an MS Windows NT4 machine that is a member of a Microsoft security domain the following steps are followed in respect of profile handling:

@@ -468,8 +452,8 @@ will stored in the %SystemRoot%\Profiles\%USERNAME% lo also remain stored in the same way, 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 copy (in %SystemRoot%\Profiles\%USERNAME%) will be @@ -488,7 +472,7 @@ are controlled by entries on Windows NT4 is:

The above hive key contains a list of automatically managed folders. The default entries are:

-

Table 24.1. User Shell Folder registry keys default values 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

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

+

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

The registry key that contains the location of the default profile settings is:

@@ -496,8 +480,8 @@ The registry key that contains the location of the default profile settings is:

The default entries are: -

Table 24.2. 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\Programs\Startup

-

`MS Windows 200x/XP`

`Note`

+

`MS Windows 200x/XP`

`Note`

MS Windows XP Home Edition does use default per user profiles, but can not participate in domain security, can not log onto an NT/ADS style domain, and thus can obtain the profile only from itself. While there are benefits in doing this the beauty of those MS Windows @@ -546,7 +530,7 @@ are controlled by entries on Windows 200x/XP is:

The above hive key contains a list of automatically managed folders. The default entries are:

-

Table 24.3. Defaults of default user profile paths registry keys 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

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

+

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

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. @@ -562,18 +546,21 @@ You could also use:

\\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 -user as seen by the Linux/Unix file system. +user as seen by the Linux/UNIX file system.

Please note that once you have created a default profile share, you MUST migrate a user's profile (default or custom) to it.

MS Windows 200x/XP profiles may be Local or Roaming. 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. -

`Common Errors`

+

`Common Errors`

The following are some typical errors/problems/questions that have been asked. -

`How does one set up roaming profiles for just one (or a few) user/s or group/s?`

+

`Setting up roaming profiles for just a few user's or group's?`

With samba-2.2.x the choice you have is to enable or disable roaming profiles support. It is a global only setting. The default is to have roaming profiles and the default path will locate them in the user's home @@ -585,42 +572,40 @@ those machines on which roaming profile support is NOT wanted it is then necessary to disable roaming profile handling in the registry of each such machine.

-With samba-3.0.0 (soon to be released) you can have a global profile -setting in smb.conf _AND_ you can over-ride this by per-user settings +With samba-3 you can have a global profile +setting in smb.conf _AND_ you can over-ride this by per-user settings using the Domain User Manager (as with MS Windows NT4/ Win 2Kx).

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)

`Can NOT use Roaming Profiles`

+

A profile unique to that user
A mandatory profile (one the user can not change)
A group profile (really should be mandatory ie:unchangable)

`Can NOT use Roaming Profiles`

+A user requested the following: “ - 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. +I do not want Roaming profiles to be implemented. I want to give users a local profile alone. ... +Please help me I am totally lost with this error. For the past two days I tried everything, I googled +around but found no useful pointers. Please help me. ”

-Your choices are: - - -

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 -
Group profiles: - loaded from a central place
Mandatory profiles: - - can be personal or group - - can NOT be changed (except by an administrator -

+The choices are: +

Local profiles:: + I know of no registry keys that will allow auto-deletion of LOCAL profiles on log out +
Roaming profiles:: + As a user logs onto the network a centrally stored profile is copied to the workstation + to form a local profile. This local profile will persist (remain on the workstation disk) + unless a registry key is changed that will cause this profile to be automatically deleted + on logout. +

+The Roaming Profile choices are: +

Personal Roaming profiles

+ These are typically stored in a profile share on a central (or conveniently located + local) server. +

+ Workstations 'cache' (store) a local copy of the profile. This cached copy is used when + the profile can not be downloaded at next logon. +

Group profiles

These are loaded from a central profile server

Mandatory profiles

+ Mandatory profiles can be created for a user as well as for any group that a user + is a member of. Mandatory profiles can NOT be changed by ordinary users. Only the administrator + can change or reconfigure a mandatory profile.

- -

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 profile size of @@ -634,47 +619,34 @@ controls of how they can be changed as well as good discipline make up for a problem free site.

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: - -

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: -

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

- +Exchange Server back-end. This removes the need for a PST file.

-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. -

`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. +LOCAL profiles mean: +

If each machine is used my many users then much local disk storage is needed for local profiles
Every workstation the user logs into has it's own profile, these can be very different from machine to machine

+On the other hand, use of roaming profiles means: +

The network administrator can control the desktop environment of all users.
Use of mandatory profiles drasitcally reduces network management overheads.
In the long run users will be experience fewer problems.

`Changing the default profile`

+Question: +“ +When the client logs onto the domain controller it searches 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. +Firstly, the samba server needs to be configured as a domain controller. +This can be done by setting in smb.conf: +

security = user

os level = 32 (or more)

domain logons = Yes

+There must be an [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).

`Note`

To invoke auto-deletion of roaming profile from the local -workstation cache (disk storage) you need to use the Group Policy Editor +workstation cache (disk storage) 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. +Windows clients need to be members of the domain. Workgroup machines do NOT use network logons so +they do not interoperate with 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. -

Prev	Up	Next
Chapter 23. System and Account Policies	Home	Chapter 25. PAM based Distributed Authentication

+For roaming profiles add to smb.conf: + + logon path = \\%N\profiles\%U # Default logon drive is Z: logon drive = H: # This requires a PROFILES share that is world writable. +

Prev	Up	Next
Chapter 23. System and Account Policies	Home	Chapter 25. PAM based Distributed Authentication

-- cgit

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\Programs\Startup