Microsoft Windows NT 4.0 - Manual (Page 101)

Microsoft Windows NT Server White Paper 93
Important Information for Administrators
Regarding User Logons and User Logoffs
•
Changes that you make to server-based profiles can be lost if you do not
modify the last modification date/time stamp. When a locally cached ver-
sion of a profile is compared with the server-based profile, only the
time/date stamp of the NTuser.xxx file is compared. If the stamps are the
same, the local copy is used. If you have made modifications to other fold-
ers within the profile, these changes can be lost. Utilities are available to
update the last modified date.
•
If the Default User profile directory (including the NTuser.xxx file) is not
available at log on, a new user who does not have a server-based Default
User Profile will be unable to log on. When troubleshooting logon prob-
lems or if a user receives a message stating that the profile could not be
loaded, always check for the existence of the Default User profile.
•
If the locally cached copy of the User Profile is more current than the
server-based profile, and if it is not mandatory, the user will be prompted
to select which profile to use.
•
If the user does not successfully receive a profile when he or she logs on,
the user should check to see if the profile path can be reached by con-
necting to that resource with Explorer, File Manager, or Start\Run.
•
Users who are members of both the Domain Users and Guests group or
who are members of just the Guests group will have their local profiles
deleted automatically at logoff.
Recent Updates to Profiles Since Retail Release
•
In the original retail release of Windows NT Server 4.0, if the administrator
creates a mandatory profile that ends with .man and the user is denied ac-
cess to the profile, the user is still able to log on locally, rather than being
denied access. This problem was resolved in Service Pack 3.
•
Under certain conditions, sharing violations when accessing roaming or
mandatory profiles could occur. Before this problem was resolved, if multi-
ple users tried to log on at the exact same time, a sharing violation could
result on the files making up the User Profile because Windows NT was
attempting to get exclusive access to the profile. This was resolved in
Service Pack 2.
•
Administrators creating shortcuts on one machine for use on a central
server have run into problems on user’s workstations where a password
prompt is displayed asking for credentials to the machine that originally
created the shortcut. This is due to the default behavior of Windows NT
using the “absolute path” (the path to the original location where the short-
cut was created), to start an application even if the application is available
in the specified path of the shortcut properties. In Service Pack 2, support
was added to give the administrator the ability to disable this behavior and
use the path specified in the shortcut properties. For more information,
reference Microsoft Knowledge Base article Q158682.
APPENDIX C –
USAGE NOTES