Microsoft Windows NT 4.0 manual Would use, These can be nested to create sub-categories as follows

Page 57

These are the only two classes that are valid within the System Policy Editor. The System Policy Editor checks the syntax of each .adm file when the files are loaded, and displays a message if any errors are found.

3.Choose the CLASS in which you want your custom entries to appear.

4.Create categories by using the keyword CATEGORY followed by a space and !!variable. The System Policy Editor requires that anything preceded by !! must have a string defined in the [strings] section of the .adm file.

This allows the editor to use variables to define long strings of text that will appear in the user interface a single time, even if these strings are used in multiple locations in the .adm file. For example, to open a category you

would use:

CATEGORY !!MyNewCategory

To close the category after filling in the options, you would use:

END CATEGORY

; MyNewCategory

These can be nested to create sub-categories as follows:

CATEGORY !!FirstCategory

CATEGORY !!SecondCategory

CATEGORY !!ThirdCategory

...

...

END CATEGORY ; ThirdCategory

END CATEGORY

;

SecondCategory

END CATEGORY

;

FirstCategory

Be sure to specify the text for the variables you used above. In this case, in the [strings] section of the .adm file, you would need to include:

FirstCategory=”My First Category”

SecondCategory=”My Second Category”

ThirdCategory=”My Third Category”

5.Within each category, define the registry key that will be modified. To do this, use the keyword KEYNAME followed by the registry path to the key that contains the value you want to change. Note that due to the CLASS you are in, you do not need to specify HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER. For example, you can use:

KEYNAME System\CurrentControlSet\Services\ LanManServer\Parameters

6.Identify the policy that specifies which options the user can modify. Use the keyword POLICY for this, followed by !!variable. For example:

POLICY !!MyFirstPolicy

Be sure to define MyFirstPolicy in the [strings] section of the .adm file. Complete the policy specifics, and finish with an END POLICY statement.

7.Define the options available within the policy.

∙Use the keyword VALUENAME to identify the registry value that an administrator can modify. For example:

VALUENAME MyFirstValue

Remember that the VALUENAME needs to be within a PART if the

Microsoft Windows NT Server White Paper

49

Page 56 Page 58
Image 57
Page 56 Page 58
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 Editor System Policy An IntroductionPage User Profile Flowcharts System Policy Flowchart For More Information Appendix a -FlowchartsAutorun Start Banner Appendix C Usage NotesProfiles, Policies, and the Zero Administration Kit IntroductionTCO and the User Before You Begin What are User Profiles and System Policies?Key Terminology 32-bit version of the Registry EditorComputer Technical NotesCreating and Administering User Profiles Establishing User Profiles AN OverviewUser Profile Structure Configuration Preferences Stored in Profile Directories Configuration Preferences Stored in the Registry HiveWindows NT 4.0 file Windows NT 4.0 and Windows User Profile DifferencesList, is checked for an existing entry for that user Equivalent Windows 95 fileUser 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 reconnectCreating 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 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 ConnectionsTroubleshooting User Profiles with the UserEnv.log File To enable loggingStart REGEDT32 and locate the following path ========================================================= Sample LogSystem Policy Files System Policy AN IntroductionPolicy Replication How Policies Are AppliedThis change must be made individually to each workstation 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 restore the defaults Setting Folder Paths Back to DefaultsCreating a System Policy To create a new System PolicyTem Policy Editor Creating Alternate Folder Paths Setting Up Shortcuts for Server-based ProfilesTo create shared folders and alternate folder paths To resolve links correctlyTo retrieve the policy file from a specific location Deploying Policies for Windows NT 4.0 MachinesUpdate 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 Building Fault Tolerance for Custom Shared Folders Configuring System Policies Based on Geographic LocationClearing the Documents Available List Each time the System Policy Editor startsMicrosoft 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 Hide drives in My Computer Description Selection Hide Network Neighborhood DescriptionSelection No Entire Network in Network Neighborhood Key Selection Hide all items on desktop Description Selection No workgroup contents in Network Neighborhood KeySelection Dont save settings at Exit Description Selection Disable Shut Down command DescriptionSelectionDisable registry editing tools Category SystemSelection Run only allowed Windows applications Description Selection Custom desktop icons Description Selection Custom Program folder DescriptionSelection Hide Start menu subfolders Description Selection Custom Startup folder DescriptionSelection Custom Network Neighborhood Description Selection Custom Start menu Description \CurrentVersion \Explorer \User Shell FoldersAs part of the Start menu 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 Run logon scripts synchronously Description Selection Disable link file tracking DescriptionSelection Show welcome tips at logon Description Selection Disable Task Manager DescriptionSelection Remote update Description Default Computer Settings\Explorer \TipsSelection Permitted managers Key Selection Run Description Selection Scheduler priority Key Selection Create hidden drive shares server DescriptionError occurs on a print server Selection Beep for error enabled DescriptionCategoryWindows NT Remote Access SelectionMax number of unsuccessful authentication retriesSelectionAuto disconnect SelectionWait interval for callbackRAS Call-back Interval RAS Auto-disconnectSelection Custom shared Programs folder Description Custom shared foldersStart menu Selection Custom shared desktop icons DescriptionSelection Custom shared Start menu Description Selection Custom shared Startup folder DescriptionSelection Logon banner With text Enables or disables display of the last logged on userDialog window Logon dialog is displayedFile system Tion, this value takes precedence\System \CurrentControlSet \Control \FileSystem Selection Allow extended characters in 8.3 file namesPerformance Last access time. This increases the file system’sCategoryWindows NT User Profiles 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 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 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