8.Place the template profile in the appropriate location for the type of profile distribution that will be used. (The template profile, including customiza- tions, is stored initially in %systemroot%\Profiles\TemplateUser.)

∙If the template profile will be distributed manually to multiple users:

a)Create a directory where the template profile will be stored for distribution to each user account created.

b)From the Windows NT-based machine hosting the template pro- file to be used, log on as an administrator.

c)From the Control Panel, click System. From the User Profiles page, use the Copy To option to enter the path of the directory you just created.

d)Modify the permissions to allow the Everyone group to use the profile. To do this, click the Change button, select the group, and click OK.

e)Continue to Step 9.

∙If the template profile will be distributed via the Default User folder on validating servers:

a)Create a Default User directory in the NETLOGON share (which is %systemroot%\Repl\Import\Scripts by default) of validating do- main controllers. This folder name must be named Default User or the profile will not be downloaded from the server. To keep the Default User profile consistent across domain controllers and to ease administrative overhead, you can create this folder on one computer and then use the directory replication service to export it to all validating domain controllers.

b)If a user logs on and does not have an existing local or server- based profile and your implementation uses the Default User folder on validating domain controllers, Windows NT will check the NETLOGON share for the Default User profile before it uses the local default profile. (Workstations save the server Default User profile on a local cache.) Windows NT will check the time/date/size of the server copy against the locally cached copy before downloading the server copy. And, if the files are identical, Windows NT will use the local copy of the server Default User profile.

c)Continue to Step 10.

9.In the \\server\share from Step 1, create the directory structure you speci- fied as the path in Step 3. For example, create the directory mydomainuser under \\myserver\myshare. If the profile is to be stored within the user's home directory, use the directory structure \mydomainuser\profile under \\myserver\myshare.

Microsoft Windows NT Server White Paper

13

Page 20 Page 22
Page 21
Image 21
Microsoft Windows NT 4.0 manual Microsoft Windows NT Server White Paper
Page 20 Page 22

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