10.Copy the profile appropriate to your implementation.

∙To copy an existing user’s profile to another user:

a)From the Windows NT-based machine hosting the profile to be used, log on as an administrator.

b)From the Control Panel, click System. On the User Profiles page, select the profile to be copied and use the Copy To option to en- ter the path of the directory you created in Step 9.

c)Modify the permissions to reflect the proper account. To do this, click the Change button, select the account, and click OK. Click OK again to copy the profile.

∙To copy the template profile to the Default User folder on validating domain controllers:

a)From the Windows NT-based machine hosting the profile to be used, log on as an administrator.

b)From the Control Panel, click System. On the User Profiles page, select the profile to be copied and use the Copy To option to en- ter the path of the Default User directory on the validating domain controller.

c)Modify the permissions to reflect the Everyone group. To do this, click the Change button, select the account, and click OK. Click OK again to copy the profile.

∙To copy a template profile manually to a number of users:

a)Copy the entire contents (files and subdirectories) from the direc- tory containing the template user profile created in Step 8 to the directory created in Step 9.

b)Repeat this for each of the user profile directories that will receive the template user profile.

NOTES:

∙When entering the path to the target directory, you can use Uniform Naming Convention (UNC) names. However, if you are going to use the Browse function to locate the target directory for the profile, it is important that you first map a drive to the \\server\share where the profile will be stored.

∙The mydomainuser name shown in Step 2 does not have to be the user’s name. Many user accounts or groups can be configured to point to the same profile. Of course, if the profile is shared by a group of users and is not mandatory, as each user logs off, the user’s changes are written back to the shared profile.

∙The profile does not need to be stored one directory below the server\share. The profile can be nested several directories below, or the profile path can be local.

∙If the profile path points to a directory on the local machine, a share is not needed.

∙The variable %USERNAME% is replaced by the user name only once in the User Profile path in User Manager, and it must be the last subdirectory in the path. However, extensions can still be added, such as .usr or .man.

∙You can select any group or a specific user when setting the permissions. However, only the user or group specified will be able to use the profile. For this reason, it is recommended that the Everyone group be given permission to use template profiles.

14 Microsoft Windows NT Server White Paper

Page 21 Page 23
Page 22
Image 22
Microsoft Windows NT 4.0 manual Copy the profile appropriate to your implementation
Page 21 Page 23

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