If the box is cleared, the policy is not implemented, and if the settings were previously implemented, they are removed from the registry.

If the box is grayed, the setting is ignored and unchanged from the last time the user logged on. Windows NT does not modify this setting. The grayed state ensures that Windows NT provides quick processing at sys- tem startup because it does not need to process each entry every time a user logs on.

NOTE: When you decide whether the value should be checked or cleared, be careful of the terminology of the setting or unexpected results may occur. For example, the Don’t save settings at exit option, when checked, does not allow settings to be saved. If you clear the checkbox, the settings can be saved.

When you select an option, the pane below it contains other configurable items that relate to the setting you modified, as well as information about the option you selected.

When administering System Policies, if you specify paths for particular op- tions such as wallpaper, ensure that the paths are consistent across all workstations that will receive the policy file.

Setting Folder Paths Back to Defaults

If you create a policy file and then change the path to any of the custom shared folders or custom user-specific folders, the change overrides the de- fault setting established in the .adm file. For example, by default a user’s program folder path is %USERPROFILE%\Start Menu\Programs.

If the policy file is not modified from the default, this value is not changed for the client computer. However, you can modify this value to point to a server location that contains different shortcuts. To do this, click the option in the System Policy Editor, and specify the path to the folder containing the short- cuts. Once this change is applied, the user will receive the new shortcuts.

Suppose, however, that you want to restore the user’s environment to the state it was in before the change was made. To do this, follow the procedure described next.

To restore the defaults:

1.Open the policy file, and click the option to clear the check box.

2.Save and close the policy file.

3.Reopen the policy file, and click the option to re-enable it. The original setting should be displayed, pointing to the user’s local machine.

NOTE: Be sure to complete all steps; completing Steps 1 and 2 only results in an empty Programs folder on the client machine.

Creating a System Policy

Before you create a System Policy, decide which settings will be enforced and how the settings will be grouped.

To create a new System Policy:

1.On a Windows NT Server-based machine in the domain where the policy file will apply, open the System Policy Editor. From the Start menu, click Programs, then click Administrative Tools (Common), then click Sys-

42 Microsoft Windows NT Server White Paper

Page 50
Image 50
Microsoft Windows NT 4.0 manual Creating a System Policy, Setting Folder Paths Back to Defaults, To restore the defaults

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.