Microsoft Windows NT 4.0 manual System Policy Editor

Page 47

THE SYSTEM POLICY EDITOR

The System Policy Editor is a graphical tool that allows you to easily update the registry settings to implement a System Policy. The System Policy Editor is included with Windows NT Server 4.0, but you can install it on Windows NT Workstation-based machines and on Windows 95-based machines as well.

Note that a policy file is valid only for the platform on which it was created. For example, if you run Poledit.exe on a Windows 95-based machine, and you save the policy file, the file will be written in a format that can be interpreted by Windows 95-based machines only. The same is true when you create policy files on Windows NT-based machines. As a result, Windows 95 and Windows NT policy files are not interchangeable.

After you complete the installation, the administrative tools group includes the System Policy Editor.

Installing the System Policy Editor on a Windows NT Workstation

You have two options when installing the System Policy Editor on a Windows NT Workstation-based computer. You can

∙Run the Setup.bat file from the Windows NT 4.0 CD-ROM \Clients\Svrtools\Winnt directory, or

∙Copy the System Policy Editor executable, Poledit.exe, and template files to the workstation. The template files have an .adm extension, and are lo- cated in the %systemroot%\INF directory, which is hidden by default.

Installing the System Policy Editor on a Windows 95 Computer

When you install the System Policy Editor on a Windows 95-based computer, the installation process modifies the Windows 95 registry to allow system poli- cies to function correctly. You can install the policy editor from the Windows 95 Upgrade or Retail compact disc, or you can install the editor that ships with Windows NT Server 4.0.

To install the System Policy Editor from the Windows 95 compact disc:

1.Insert the Windows 95 Upgrade compact disc in your CD-ROM drive.

2.Open Control Panel, and click Add/Remove Programs.

3.Click the Windows Setup tab, and select Have Disk.

Microsoft Windows NT Server White Paper

39

Page 46 Page 48
Image 47
Page 46 Page 48
Contents Server Operating System Page Windows NT 4.0 documentation and Resource Kits AbstractUser environment than they have ever had before Page Contents System Policy Editor System Policy An IntroductionPage Appendix C Usage Notes For More Information Appendix a -FlowchartsUser Profile Flowcharts System Policy Flowchart Autorun Start BannerTCO and the User Profiles, Policies, and the Zero Administration KitIntroduction Before You Begin What are User Profiles and System Policies?Key Terminology 32-bit version of the Registry EditorComputer Technical NotesUser Profile Structure Creating and Administering User ProfilesEstablishing User Profiles AN Overview Configuration Preferences Stored in Profile Directories Configuration Preferences Stored in the Registry HiveEquivalent Windows 95 file Windows NT 4.0 and Windows User Profile DifferencesWindows NT 4.0 file List, is checked for an existing entry for that userUser Profile Planning and Implementation Setting Permissions for User ProfilesSelecting a Location to Save User Profiles Encoding Permissions in the User ProfileSetting Persistent Connections Working Around Slow Network Links Delete the network connection and reconnectTo create a new roaming user profile Creating and Maintaining User ProfilesCreating a New Roaming User Profile for Windows NT Microsoft Windows NT Server White Paper ∙ To copy a template profile manually to a number of users Copy the profile appropriate to your implementation∙ To copy an existing user’s profile to another user To create a new mandatory User Profile Creating a New Mandatory User Profile for Windows NTCalled TemplateUser Changing the User’s Ability to Modify a Profile Making a Roaming Profile Mandatory Windows NTEnforcing the Use of the Server-based Profile To create a roaming user profile for a Windows 95 user Creating a New Roaming User Profile for a Windows 95 UserTo create a mandatory user profile for a Windows 95 user Creating a New Mandatory User Profile for WindowsDeleting Profiles Ddays \\computernameDetermining Which Profile Is Displayed Copying Profiles Microsoft Windows NT Server White Paper All Users Shared Profile Log Files Used by ProfilesProfile Names and Storage in the Registry Default User Template ProfilesTo manually customize a User Profile Manually Administering a User Profile through the RegistryModifying the Default User Profile Microsoft Windows NT Server White Paper To create the profile from an existing template profile To create a mandatory profile from the old profileTo change the profile Creating Profiles Without User-Specific ConnectionsStart REGEDT32 and locate the following path Troubleshooting User Profiles with the UserEnv.log FileTo enable logging ========================================================= Sample LogSystem Policy Files System Policy AN IntroductionThis change must be made individually to each workstation Policy ReplicationHow Policies Are Applied Additional Implementation Considerations Microsoft Windows NT Server White Paper System Policy Editor Installing the System Policy Editor on a Windows 95 ComputerSystem Policy Editor Template .Adm Files Updating the Registry with the System Policy EditorYour Own Custom .Adm File,later in this document Configuring Policy SettingsTo create a new System Policy Setting Folder Paths Back to DefaultsTo restore the defaults Creating a System PolicyTem Policy Editor To resolve links correctly Setting Up Shortcuts for Server-based ProfilesCreating Alternate Folder Paths To create shared folders and alternate folder pathsTo retrieve the policy file from a specific location Deploying Policies for Windows NT 4.0 MachinesTo deploy policies for a Windows 95-based computer Update mode box, select Manual use specific pathDeploying Policies for Windows 95 Machines To create a policy file for stand-alone workstations Modifying Policy Settings on Stand-Alone WorkstationsTo change policy settings remotely To create a custom .adm file To change policy settings locallyCreating a Custom .Adm File Remember that the Valuename needs to be within a Part if Would useThese can be nested to create sub-categories as follows END Part Save and test your file Type REGEXPANDSZ, for example∙ MAXLEN- Specifies the maximum length of text, for example Each time the System Policy Editor starts Configuring System Policies Based on Geographic LocationBuilding Fault Tolerance for Custom Shared Folders Clearing the Documents Available ListMicrosoft Windows NT Server White Paper Default User Settings Selection Color scheme Key Selection Remove Run command from Start menu DescriptionSelection Remove Find command from Start menu Description Selection No Entire Network in Network Neighborhood Key Selection Hide drives in My Computer DescriptionSelection Hide Network Neighborhood Description Selection Hide all items on desktop Description Selection No workgroup contents in Network Neighborhood KeyCategory System Selection Disable Shut Down command DescriptionSelection Dont save settings at Exit Description SelectionDisable registry editing toolsSelection Run only allowed Windows applications Description Selection Custom desktop icons Description Selection Custom Program folder DescriptionSelection Custom Network Neighborhood Description Selection Hide Start menu subfolders DescriptionSelection Custom Startup folder Description Selection Only use approved shell extensions Key \CurrentVersion \Explorer \User Shell FoldersSelection Custom Start menu Description As part of the Start menuSelection Selection Disable context menus for the Taskbar DescriptionSelection Remove File menu from Explorer Description Work Drive options Selection Run logon scripts synchronously Description Selection Disable link file tracking DescriptionSelection Show welcome tips at logon Description Selection Disable Task Manager Description\Tips Default Computer SettingsSelection Remote update Description \ExplorerSelection Permitted managers Key Selection Run Description Selection Scheduler priority Key Selection Create hidden drive shares server DescriptionSelectionMax number of unsuccessful authentication retries Selection Beep for error enabled DescriptionError occurs on a print server CategoryWindows NT Remote AccessRAS Auto-disconnect SelectionWait interval for callbackSelectionAuto disconnect RAS Call-back IntervalSelection Custom shared desktop icons Description Custom shared foldersSelection Custom shared Programs folder Description Start menuSelection Logon banner Selection Custom shared Start menu DescriptionSelection Custom shared Startup folder Description Logon dialog is displayed Enables or disables display of the last logged on userWith text Dialog windowSelection Allow extended characters in 8.3 file names Tion, this value takes precedenceFile system \System \CurrentControlSet \Control \FileSystemSelectionDelete cached copies of roaming profiles Last access time. This increases the file system’sPerformance CategoryWindows NT User ProfilesSelectionAutomatically detect slow network connections SelectionSlow network connection timeoutSelectionTimeout for dialog boxes Registry Value Registry Data Description Registry Entries not Included in the System Policy Editor Registry Value Registry Data Description NoStartBanner For More Information User Profile Flowcharts Appendix a 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 Do Group Policies System Policy FlowchartExisting Windows NT 3.5x Roaming Profile Appendix B Implementing User ProfilesCreating a New Windows NT 4.0 Mandatory Profile Creating a New Windows NT 4.0 Roaming ProfileChanging a Roaming Profile to a Mandatory Profile Appendix C Usage Notes Recent Updates to Profiles Since Retail ReleaseRecent Updates to Policies Since Retail Release Policies Appendix D Related Knowledge Base ArticlesProfiles 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