User Profile Planning and Implementation

home directory (or other specified directory if the location has been modified) on the server for the User Profile. If a profile exists in both locations, the newer of the two is used. If the User Profile exists on the server, but does not exist on the local machine, the profile on the server is downloaded and used. If the User Profile only exists on the local machine, that copy is used.

If a User Profile is not found in either location, the Default User Profile from the Windows 95 machine is used and is copied to a newly created folder for the logged on user. At log off, any changes that the user made are written to the user’s local profile. If the user has a roaming profile, the changes are writ- ten to the user’s profile on the server.

A successful implementation of User Profiles requires planning and prepara- tion. Before creating User Profiles, consider the following:

∙How much of the user environment do you wish to control? Would System Policies— either in conjunction with User Profiles, or by themselves— be a better solution?

∙Will users be required to use a specific set of desktop folders and envi- ronment settings?

∙Will users be able to make modifications to their profiles?

∙What features will you be implementing in User Profiles? Optional features include persistent network connections, custom icons, backgrounds, and so on.

∙For roaming profiles, will users be allowed to use the default profile from the client workstation or will a standardized server-based default profile be used instead?

∙Where will the profiles be stored, and is there enough drive space to store them?

∙Where do existing user home directories reside?

∙How will shortcuts and links be displayed for the user?

∙What are the speeds of the links between the clients and the server stor-

ing the profiles?

These issues are examined more fully in the following paragraphs. For more information, refer to the Windows NT Server Concepts and Planning Guide.

Setting Permissions for User Profiles

When troubleshooting or preparing for a rollout of User Profiles, you should pay careful attention to permissions at the Windows NT File System (NTFS) and share levels. If the profile is mandatory, the user account should have at least Read permissions on the network share where that user’s User Profile is stored. If the user’s profile is roaming, the user must have Change permissions (or better) because the client will need to write the changes back to the central profile on the shared network drive when the user logs off. If roaming profiles are stored on an NTFS partition, you can choose to remove the Delete permis- sion from the default Change permissions at the NTFS level.

8 Microsoft Windows NT Server White Paper

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.

Microsoft Windows NT 4.0 manual User Profile Planning and Implementation

Models: Windows NT 4.0