Filter
Top Products
Microsoft Windows NT Server White Paper 15
Once the above steps are completed, the user receives the appropriate
profile as follows:
• If the user is to receive the Default User profile from a Windows NT 4.0-
based workstation, the workstation’s default profile is used when the user
first logs on. When the user logs off, the profile is automatically written to
the local cache and to the server-based profile.
• If the user is to receive the Default User profile from the validating domain
controller, the default profile from the server is used when the user first
logs on. When the user logs off, this profile is automatically written to the
local cache and to the server-based profile.
• In all other cases, the profile—including the folder trees and the
NTuser.xxx file originally included with the profile—is written to the user’s
profile directory. The permissions are also encoded into the binary
NTuser.xxx file.
Creating a New Mandatory User Profile for
Windows NT 4.0
To create a new mandatory User Profile:
1. If a location has not already been prepared, create a directory on the
server and establish a network share. Users who will have mandatory pro-
files need only Read permissions to the shared directory. (For more
information on planning for this type of user, read the sections “Selecting a
Location to Save User Profiles” and “Setting Permissions for User Profiles”
earlier in this document.) If your implementation stores user profiles within
users’ home directories, make the profile directory a subdirectory of the
user’s home directory. (Note that this approach precludes the use of the
%USERNAME% variable.) To prevent the share from being browsable,
append “$” to the share name.
2. If this will be a domain user or if this will be a local account for a
Windows NT Server, use User Manager for Domains to create the ac-
count. If this will be a Windows NT 4.0 Workstation account, use the
version of User Manager included in the Administrative Tools program
group. Refer to your operating system documentation and online Help for
procedures when using these tools. (Note that for this example, the user
account is mydomainuser.)
3. Enter the User Profile path. This is the location where the User Profile will
be stored, for example: \\myserver\myshare\mydomainuser.
Or, if the profile is being stored within the user’s home directory, use:
\\myserver\myshare\MyUsersHomeDir\profile.
4. Determine if an extension needs to be appended to the User Profile path.
If it will be mandatory that the user reads the profile from the server, and if
logon will be denied unless this is the case, add the extension .man to the
User Profile path; for example: \\myserver\myshare\mydomainuser.man.
5. Use User Manager to create an account for establishing the template pro-
file. So that you can easily identify this account, we recommend that it be