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

Microsoft Windows NT Server White Paper

15

Page 22 Page 24
Page 23
Image 23
Microsoft Windows NT 4.0 Creating a New Mandatory User Profile for Windows NT, To create a new mandatory User Profile
Page 22 Page 24

Windows NT 4.0 specifications

Microsoft Windows NT 4.0, released on July 29, 1996, marked a significant milestone in the evolution of Microsoft's operating systems. As the successor to Windows NT 3.51, this version brought a range of enhancements and features that appealed to both enterprise users and consumers.

One of the standout characteristics of Windows NT 4.0 was its introduction of the Windows 95 user interface, which significantly improved user experience and accessibility. This graphical interface made it easier for users to navigate the operating system, transitioning from the more complex interfaces of previous NT versions. The integration of familiar elements such as the Start menu and taskbar helped bridge the gap between professional and personal computing environments.

Windows NT 4.0 was built on a robust and secure architecture. It utilized the NT kernel, which provided improved multitasking and stability compared to its predecessors. This operating system was designed to handle multiple user sessions simultaneously, making it suitable for servers as well as workstations. The inherent stability of NT 4.0 made it a favorite in enterprise environments, particularly for critical applications and systems.

Another defining feature of NT 4.0 was its support for a wide range of hardware, making it versatile across various machine configurations. It included compatibility with numerous devices and peripherals, which facilitated its adoption in diverse settings.

In addition to user interface enhancements and hardware compatibility, Windows NT 4.0 introduced powerful networking capabilities. The operating system supported TCP/IP natively, alongside NetBEUI and IPX/SPX protocols. This meant that it could seamlessly integrate into existing network environments, providing essential services for file and printer sharing, domain management, and remote access through features like Remote Access Service (RAS).

Security was another key focus area for Windows NT 4.0. Built around security principles, it employed a discretionary access control system, allowing administrators to define user permissions and manage access to resources effectively. This was particularly appealing to businesses that needed to enforce strict security policies.

Windows NT 4.0 also included improved support for backup and recovery, through the inclusion of the NT Backup utility. The operating system allowed for the creation of scheduled backups and simplified data recovery processes, enhancing data integrity and reliability.

As NT 4.0 entered its later years, it laid the groundwork for future Windows operating systems, influencing the design of later versions, particularly Windows 2000. It combined user-friendly features with enterprise-level robustness, ultimately shaping expectations for modern operating systems across various industries.
Top Page Image Contents