Microsoft Windows NT 4.0 manual Deploying Policies for Windows 95 Machines

Page 54

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
Image 54
Page 53 Page 55
Contents Server Operating System Page Abstract User environment than they have ever had beforeWindows NT 4.0 documentation and Resource Kits Page Contents System Policy An Introduction System Policy EditorPage Autorun Start Banner For More Information Appendix a -FlowchartsUser Profile Flowcharts System Policy Flowchart Appendix C Usage NotesProfiles, Policies, and the Zero Administration Kit IntroductionTCO and the User What are User Profiles and System Policies? Before You Begin32-bit version of the Registry Editor Key TerminologyTechnical Notes ComputerCreating and Administering User Profiles Establishing User Profiles AN OverviewUser Profile Structure Configuration Preferences Stored in the Registry Hive Configuration Preferences Stored in Profile DirectoriesList, is checked for an existing entry for that user Windows NT 4.0 and Windows User Profile DifferencesWindows NT 4.0 file Equivalent Windows 95 fileSetting Permissions for User Profiles User Profile Planning and ImplementationEncoding Permissions in the User Profile Selecting a Location to Save User ProfilesSetting Persistent Connections Delete the network connection and reconnect Working Around Slow Network LinksCreating and Maintaining User Profiles Creating a New Roaming User Profile for Windows NTTo create a new roaming user profile Microsoft Windows NT Server White Paper Copy the profile appropriate to your implementation ∙ To copy an existing user’s profile to another user∙ To copy a template profile manually to a number of users Creating a New Mandatory User Profile for Windows NT To create a new mandatory User ProfileCalled TemplateUser Making a Roaming Profile Mandatory Windows NT Changing the User’s Ability to Modify a ProfileEnforcing the Use of the Server-based Profile Creating a New Roaming User Profile for a Windows 95 User To create a roaming user profile for a Windows 95 userCreating a New Mandatory User Profile for Windows To create a mandatory user profile for a Windows 95 userDeleting Profiles \\computername DdaysDetermining Which Profile Is Displayed Copying Profiles Microsoft Windows NT Server White Paper Log Files Used by Profiles All Users Shared ProfileDefault User Template Profiles Profile Names and Storage in the RegistryManually Administering a User Profile through the Registry To manually customize a User ProfileModifying the Default User Profile Microsoft Windows NT Server White Paper To create a mandatory profile from the old profile To create the profile from an existing template profileCreating Profiles Without User-Specific Connections To change the profileTroubleshooting User Profiles with the UserEnv.log File To enable loggingStart REGEDT32 and locate the following path Sample Log =========================================================System Policy AN Introduction System Policy FilesPolicy Replication How Policies Are AppliedThis change must be made individually to each workstation Additional Implementation Considerations Microsoft Windows NT Server White Paper Installing the System Policy Editor on a Windows 95 Computer System Policy EditorUpdating the Registry with the System Policy Editor System Policy Editor Template .Adm FilesConfiguring Policy Settings Your Own Custom .Adm File,later in this documentCreating a System Policy Setting Folder Paths Back to DefaultsTo restore the defaults To create a new System PolicyTem Policy Editor To create shared folders and alternate folder paths Setting Up Shortcuts for Server-based ProfilesCreating Alternate Folder Paths To resolve links correctlyDeploying Policies for Windows NT 4.0 Machines To retrieve the policy file from a specific locationUpdate mode box, select Manual use specific path Deploying Policies for Windows 95 MachinesTo deploy policies for a Windows 95-based computer Modifying Policy Settings on Stand-Alone Workstations To change policy settings remotelyTo create a policy file for stand-alone workstations To change policy settings locally Creating a Custom .Adm FileTo create a custom .adm file Would use These can be nested to create sub-categories as followsRemember that the Valuename needs to be within a Part if END Part Type REGEXPANDSZ, for example ∙ MAXLEN- Specifies the maximum length of text, for exampleSave and test your file Clearing the Documents Available List Configuring System Policies Based on Geographic LocationBuilding Fault Tolerance for Custom Shared Folders Each time the System Policy Editor startsMicrosoft Windows NT Server White Paper Default User Settings Selection Remove Run command from Start menu Description Selection Color scheme KeySelection Remove Find command from Start menu Description Selection Hide drives in My Computer Description Selection Hide Network Neighborhood DescriptionSelection No Entire Network in Network Neighborhood Key Selection No workgroup contents in Network Neighborhood Key Selection Hide all items on desktop DescriptionSelectionDisable registry editing tools Selection Disable Shut Down command DescriptionSelection Dont save settings at Exit Description Category SystemSelection Run only allowed Windows applications Description Selection Custom Program folder Description Selection Custom desktop icons DescriptionSelection Hide Start menu subfolders Description Selection Custom Startup folder DescriptionSelection Custom Network Neighborhood Description As part of the Start menu \CurrentVersion \Explorer \User Shell FoldersSelection Custom Start menu Description Selection Only use approved shell extensions KeySelection Disable context menus for the Taskbar Description Selection Remove File menu from Explorer DescriptionSelection Work Drive options Selection Disable link file tracking Description Selection Run logon scripts synchronously DescriptionSelection Disable Task Manager Description Selection Show welcome tips at logon Description\Explorer Default Computer SettingsSelection Remote update Description \TipsSelection Permitted managers Key Selection Run Description Selection Create hidden drive shares server Description Selection Scheduler priority KeyCategoryWindows NT Remote Access Selection Beep for error enabled DescriptionError occurs on a print server SelectionMax number of unsuccessful authentication retriesRAS Call-back Interval SelectionWait interval for callbackSelectionAuto disconnect RAS Auto-disconnectStart menu Custom shared foldersSelection Custom shared Programs folder Description Selection Custom shared desktop icons DescriptionSelection Custom shared Start menu Description Selection Custom shared Startup folder DescriptionSelection Logon banner Dialog window Enables or disables display of the last logged on userWith text Logon dialog is displayed\System \CurrentControlSet \Control \FileSystem Tion, this value takes precedenceFile system Selection Allow extended characters in 8.3 file namesCategoryWindows NT User Profiles Last access time. This increases the file system’sPerformance SelectionDelete cached copies of roaming profilesSelectionSlow network connection timeout SelectionTimeout for dialog boxesSelectionAutomatically detect slow network connections Registry Value Registry Data Description Registry Entries not Included in the System Policy Editor Registry Value Registry Data Description NoStartBanner For More Information Appendix a Flowcharts User Profile FlowchartsWill the user be mandated to receive the profile for logon? Available? See Apply System Policy Save settings to Registry Call made to check Check for .man extension Server profile System Policy Flowchart Do Group PoliciesAppendix B Implementing User Profiles Existing Windows NT 3.5x Roaming ProfileCreating a New Windows NT 4.0 Roaming Profile Creating a New Windows NT 4.0 Mandatory ProfileChanging a Roaming Profile to a Mandatory Profile Recent Updates to Profiles Since Retail Release Appendix C Usage NotesRecent Updates to Policies Since Retail Release Appendix D Related Knowledge Base Articles ProfilesPolicies Q156432

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