3.In the Update mode box, select Manual (use specific path).

4.In the Path for manual update box, type the UNC path and file name for the policy file.

5.Click OK to save your changes.

The first time the workstation is modified locally via the System Policy Editor or receives a default System Policy file from the NETLOGON share of a do- main controller, this location is written to the registry. Thereafter, all future policy updates use the location you specified manually. This is a permanent change until the policy file resets the option to Automatic. The Windows NT

4.0-based computer will never again look at a domain controller to find a policy file until you either change the instruction in the local registry or modify the policy file in the location specified by the manual path to set the mode back to Automatic.

Deploying Policies for Windows 95 Machines

When creating a system policy file for a Windows 95-based client, you must first install the System Policy Editor on a Windows 95-based computer so that you can create the policy (.pol) file. You cannot run the System Policy Editor on a Windows NT 4.0-based server to generate a .pol file for Windows 95- based clients because a policy file is valid only for the platform on which it was created. For procedures when installing the System Policy Editor on a Win- dows 95-based computer, refer to the section “Installing the System Policy Editor on a Windows 95 Computer”earlier in this document.

After you have created the .pol file, you can enable a Windows 95-based computer to look for and accept system policies as is described below.

To deploy policies for a Windows 95-based computer:

1.Open the Control Panel, and click Passwords and then User Profiles.

2.To enable User Profiles, select Users can customize and then click OK.

3.Check the UpdateMode value in the following registry location:

HKEY_LOCAL_MACHINE \System \CurrentControlSet

\Control

\Update

If this value is 0, policies will not be applied. If this value is 1, the Auto- matic Policy mode is in effect and when the user is validated on the domain, the validating domain controller’s NETLOGON share will be checked for the existence of the Config.pol file. If this value is 2, the Man- ual Policy mode is in effect, and when the user is validated on the domain, the Windows 95-based machine will check the path specified in the value NetworkPath for the existence of the Config.pol file. Note that the default mode for a Windows 95-based machine is Automatic.

4.Restart the computer and have the user log on. The policy file will be downloaded from the configured location and applied.

46 Microsoft Windows NT Server White Paper

Page 53 Page 55
Page 54
Image 54
Microsoft Windows NT 4.0 Deploying Policies for Windows 95 Machines, Update mode box, select Manual use specific path
Page 53 Page 55

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