user for whom the changes will apply. If the user is not currently logged on, click Cancel. (The user must be logged on for the changes to take effect.)

3.If the user is logged on, click OK.

4.The icons Local Computer and Local User will be displayed.

5.Modify these just as you would modify a normal policy file. Save your changes. The next time the user logs on, the changes made to the com- puter and the user settings will be in effect on the remote machine.

To change policy settings locally:

1.Log on as an administrator, and copy the Poledit.exe, Common.adm, and Winnt.adm files to the Windows NT-based workstation where the changes for the computer or user need to be made.

2.Log on with administrative permissions as the user for whom the modifica- tions will apply.

3.Open Poledit.exe and load the templates that were copied to the local computer.

4.From the File menu, select Open Registry.

5.The icons Local Computer and Local User will be displayed.

6.Modify these just as you would modify a normal policy file. Save your changes. The next time the user logs on, these changes will be in effect.

6.Close the System Policy Editor and remove this tool from the workstation by deleting the Poledit.exe file and any .adm files used.

These changes modify the registry entries that control the behavior of Windows NT on the target computer. A policy file is not created when this pro- cedure is used. This procedure is the same for Windows NT Workstation 4.0 and Windows NT Server 4.0.

Creating a Custom .Adm File

The content of this section is also documented in the Windows 95 Resource Kit and the Windows 32-bit Software Developer’s Kit, which are available on the Microsoft Developer’s Network or through Microsoft Sales.

This section refers extensively to the following .adm files:

∙Common.adm— This contains registry settings common to both Windows NT 4.0 and Windows 95.

∙Winnt.adm— This contains registry settings specific to Windows NT 4.0.

∙Windows.adm— This contains registry settings specific to Win- dows 95.

To create a custom .adm file:

1.Create a backup copy of the Winnt.adm file in the %systemroot%\ inf directory.

2.Use a text editor to open the Winnt.adm file. The first entry of this file is CLASS xxxx, where xxxx could be either:

∙MACHINE = This section includes all entries available in the Local Computer/DefaultComputer icon.

∙USER = This section includes all entries available to modify user- specific settings.

48 Microsoft Windows NT Server White Paper

Page 55 Page 57
Page 56
Image 56
Microsoft Windows NT 4.0 Creating a Custom .Adm File, To change policy settings locally, To create a custom .adm file
Page 55 Page 57

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