Be cautious if you use the Explorer interface to make these changes. If you have the “Hide file extensions for known file types”option enabled (this is the default), be sure to check the properties to be sure that there are not two extensions. For example, say you want to make a profile man- datory and you use Explorer to rename the NTuser.dat file name to NTuser.man. Because of the Hide extensions default, Explorer saves the file as type .man, but does not display the .man extension. Later, you de- cide to allow the user to make changes again, and through Explorer, you rename the file back to NTuser.dat. However, because Explorer was hid- ing that part of the file name that determines its type, the only thing you rename is the prefix. The file name is now NTuser.dat.man. To avoid this situation, you can either rename files from the command line or change the behavior of Explorer.

Enforcing the Use of the Server-based Profile

In addition to enforcing the read-only property of a profile, the administrator can duplicate the functionality that was available in Windows NT 3.5x of not allowing the user to log on unless the server profile is available.

To enforce the use of the server-based profile for a given user:

1.Append the .man extension to the User Profile path in User Manager as explained in the previous section. (Skip this step for users who have ex- isting Windows NT 3.5x profiles and who already have the .man extension appended to their profile paths.)

2.If the user already has a Windows NT 3.5x mandatory profile on the server, change the name of the folder where the Windows NT 4.0 roaming profile currently exists to foldername.pdm. If the user logs on to a Windows NT 4.0-based workstation and the User Profile path contains the .man extension, Windows NT will determine that a mandatory Windows NT 3.5x profile exists and will automatically replace the .man extension with .pdm and will look for the directory path configured in the User Profile path. For example, at logon if the User Profile path is config- ured to use \\server\share\username.man, Windows NT will look for \\server\share\username.pdm for the correct profile to load.

If only the Windows NT 4.0 user profile exists, change the name of the folder where the Windows NT 4.0 roaming profile exists to folder- name.man. If the user logs on to a Windows NT 4.0-based workstation and the User Profile path contains the extension .man, Windows NT will look for the directory path configured in the User Profile path. If Win- dows NT does not find the directory, it will replace the .man extension with

.pdm, and will check again.

3.If you haven't already done so, change the name of the NTuser.xxx file to NTuser.dat. (Refer to the section, “Changing the User’s Ability to Modify a Profile, ”in this document.)

18 Microsoft Windows NT Server White Paper

Page 26
Image 26
Microsoft Windows NT 4.0 manual Enforcing the Use of the Server-based Profile

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.