summaryrefslogtreecommitdiff
path: root/docs/textdocs
diff options
context:
space:
mode:
authorSamba Release Account <samba-bugs@samba.org>1997-03-09 18:21:46 +0000
committerSamba Release Account <samba-bugs@samba.org>1997-03-09 18:21:46 +0000
commit35de5ef34343d546ce7269308871d7da55991861 (patch)
tree0cd6f1fc3d1359290fc2bff9f812ab8d26d1bece /docs/textdocs
parent9c209aba82c76e203f87ae218ae6a6eb2a05544a (diff)
downloadsamba-35de5ef34343d546ce7269308871d7da55991861.tar.gz
samba-35de5ef34343d546ce7269308871d7da55991861.tar.bz2
samba-35de5ef34343d546ce7269308871d7da55991861.zip
missed some bits. added some more on profiles - e.g windows 95 description
of what needs to be done. lkcl (This used to be commit d998795503ce7872073a79a710a41ffdbc535e75)
Diffstat (limited to 'docs/textdocs')
-rw-r--r--docs/textdocs/DOMAIN.txt68
1 files changed, 68 insertions, 0 deletions
diff --git a/docs/textdocs/DOMAIN.txt b/docs/textdocs/DOMAIN.txt
index 9bdff5dc88..ba420e6111 100644
--- a/docs/textdocs/DOMAIN.txt
+++ b/docs/textdocs/DOMAIN.txt
@@ -99,4 +99,72 @@ The user.dat file contains all the user's preferences. If you wish to
enforce a set of preferences, rename their user.dat file to user.man,
and deny them write access to the file.
+2) On the Windows 95 machine, go to Control Panel | Passwords and
+ select the User Profiles tab. Select the required level of
+ roaming preferences. Press OK, but do _not_ allow the computer
+ to reboot.
+
+3) On the Windows 95 machine, go to Control Panel | Network |
+ Client for Microsoft Networks | Preferences. Select 'Log on to
+ NT Domain'. Press OK, and this time allow the computer to reboot.
+
+You will now find that the Microsoft Networks Login box contains
+[user, password, domain] instead of just [user, password]. Type in
+the samba server's domain name (or any other domain known to exist),
+user name and user's password.
+
+Once the user has been successfully validated, the Windows 95 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'.
+
+Once the Windows 95 client comes up with the desktop, you should be able
+to examine the contents of the directory specified in the "logon path"
+(the default is \\samba_server\username) and verify that the "desktop",
+"start menu", "programs" and "nethood" folders have been created.
+
+These folders will be cached locally on the client, and updated when
+the user logs off (if you haven't made them read-only by then :-).
+
+
+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".
+
+
+1) instead of logging in under the [user, password, domain] dialog],
+ press escape.
+
+2) run the regedit.exe program, and look in:
+
+ HKEY_LOCAL_MACHINE\Windows\CurrentVersion\ProfileList
+
+ you will find an entry, for each user, of ProfilePath. Note the
+ contents of this key (likely to be c:\windows\profiles\username),
+ then delete the key ProfilePath for the required user.
+
+ [Exit the registry editor].
+
+3) 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 have any important files stored on their desktop
+ or in their start menu. delete the contents of the directory
+ ProfilePath (making a backup if any of the files are needed).
+
+ 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.
+
+4) search for the user's .PWL password-cacheing file in the c:\windows
+ directory, and delete it.
+
+5) log off the windows 95 client.
+
+6) 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.
+
+
+If all else fails, increase samba's debug log levels to between 3 and 10,
+and / or run a packet trace program such as tcpdump or netmon.exe, and
+look for any error reports.