4.Browse to locate the directory x:\Admin\Apptools\Poledit\ (where x is drive A through Z) on the Windows 95 compact disc.

5.Select both Group Policies and the System Policy Editor, and then click OK to Install.

It is important that you run the setup program as described above. Undesir- able results will occur if you merely copy the Policy Editor and related files to the Windows 95-based computer.

To install the System Policy Editor from a Windows NT 4.0 Server:

1.Copy the Poledit.exe file from the Windows NT Server 4.0 to the \windows directory of the Windows 95-based machine.

2.Copy the Common.adm and Windows.adm files from the Windows NT 4.0- based server to the \windows directory of the Windows 95-based machine.

3.Create a shortcut to the System Policy Editor executable (Poledit.exe, located in the \windows directory of the Windows 95-based computer).

Updating the Registry with the System Policy Editor

The System Policy Editor allows you to easily update the registry settings to generate the correct environment for a particular user or group of users. You can use the System Policy Editor in two ways:

∙You can open the local registry through the System Policy Editor, and change the settings for the local user and computer.

∙You can modify an existing policy file or create a new one to contain the

settings that you want to enforce on a per user, per computer, or com- bined user/computer basis.

When you open the System Policy Editor in registry mode, you can modify the registry of the local computer without having to use Regedt32.exe or Re- gedit.exe. However, you can modify only those values exposed by the templates; the System Policy Editor does not give you access to the entire registry.

System Policy Editor Template (.Adm) Files

The System Policy Editor uses administrative (.adm) files to determine which registry settings can be modified. An .adm file is a hierarchical template, and consists of categories and subcategories that dictate which settings are avail- able through the user interface. An .adm file contains the registry locations where changes should be made for a particular selection, additional options for a particular selection, restrictions, and in some cases, the default value for a selection.

When you run the System Policy Editor and select Policy Template from the Options menu, a window similar to the one shown below appears. This window displays the names of the .adm files that are currently being used. If you need to make changes to custom applications, for example, you can add a template to this list. To ensure that the system uses the latest administrative information, the System Policy Editor reads the custom .adm files each time it starts.

For detailed instructions when creating .adm files, see the section “Creating

40 Microsoft Windows NT Server White Paper

Page 47 Page 49
Page 48
Image 48
Microsoft Windows NT 4.0 Updating the Registry with the System Policy Editor, System Policy Editor Template .Adm Files
Page 47 Page 49

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