Recent Updates to Policies Since Retail Release

The following changes have been made to System Policies support since the initial retail release of Windows NT 4.0.

∙When a policy file was to be downloaded, if the validating domain control- ler name was 13 characters or longer, the policy would not be applied. This has been resolved in Service Pack 3.

∙NoNetConnectDisconnect, NoTrayContextMenu, NoViewCon- textMenu, NoFileMenu, and DisableTaskMgr were added in Service Pack 2. For more information on these, see the section, “Registry Keys Modified by the System Policy Editor Default Templates.”

∙In Service Pack 2 and later, the policy file is no longer cached. This change was made to increase security. Instead of being cached, the policy file is downloaded at each logon, written to a temporary file, and applied.

∙When the NoViewContextMenu policy was introduced, it did not support the tree view on the left-hand side of Explorer. This was corrected in Service Pack 3. If this option is turned on, context menus for both the list view and the tree view are disabled.

∙Manual mode policy path expansion support was added in Service Pack 3. If you specify a policy path in the registry (rather than using Automatic mode), Windows NT now supports paths in the form of \\someserver\share\ntconfig.pol.

∙If the administrator created a new policy file and turned on synchronous logon scripts, saved it to disk, and reloaded the policy file, the policy set- ting would be lost because the .adm file needed modification in three different places. This was corrected in Service Pack 3.

∙Changing the location of a user’s Start menu caused duplicate Programs items. If you used the System Policy Editor to change the Custom Start Menu to point to a different directory (even an empty one), the user would receive the normal Programs menu item and a Programs menu item above it that pointed to the All Users programs directory. This has been corrected in Service Pack 3.

∙The Microsoft Office 97 Resource Kit contains .adm files that administra- tors can use when configuring the Office environment for their users. This is available now from Microsoft.

94 Microsoft Windows NT Server White Paper

Page 101 Page 103
Page 102
Image 102
Microsoft Windows NT 4.0 manual Recent Updates to Policies Since Retail Release
Page 101 Page 103

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