Microsoft Windows NT 4.0 manual Microsoft Windows NT Server White Paper

Page 38

Upgrading Windows NT 3.5x Server-based Profiles to Windows NT 4.0 Roaming Profiles

When you upgrade Windows NT 3.5x roaming profiles (.usr profiles), you do not need to change anything in the profile path configured in the user account. When the user logs on to a Windows NT 4.0-based machine and the profile is found to be a Windows NT 3.5x profile, a process automatically looks for the equivalent Windows NT 4.0 profile. If the profile isn’t found, a conversion proc- ess creates a new Windows NT 4.0 profile using the settings established in the Windows NT 3.5x profile.

During the conversion process, Windows NT 4.0 creates a directory for the new profile in the same location as the existing Windows NT 3.5x profile. The resulting directory has a .pds extension, which stands for Profile Directory Structure, rather than the previous Windows NT 3.5x .usr extension. For ex- ample, if the User Profile path for the Windows NT 3.5x user mydomainuser is \\myserver\myshare\mydomainuser.usr, and the user logs on to a Windows NT 4.0-based machine, the profile directory mydomainuser.pds would be created within \\myserver\myshare.

This approach allows the user to log on to the network from either a Windows NT 3.5x or 4.0-based workstation. If the user were to log on from a Windows NT 3.5x-based computer, the profile path would direct the Windows NT 3.5x-based machine to the User Profile used prior to the Windows NT 4.0 upgrade. If the user then moved to a Windows NT 4.0-based computer, the user’s Windows NT-based workstation would recognize that the profile contained Windows NT 3.5x syntax, would replace the .usr with .pds, and would then use that string to locate the Windows NT 4.0 profile. The re- sulting Windows NT 4.0 structure will be the Windows NT 3.51 profile (now NTuser.xxx) and the Default User Profile folders.

It is important to emphasize that the Windows NT 3.5x profile is not de- leted— it is still available to the user should they ever log on from a Windows NT 3.5x-based computer. It is also important to note that the settings for these two profiles are completely independent; changes made to the Windows NT 3.5x profile will not be reflected in the Windows NT 4.0 profile, and vice versa.

NOTE: As an administrator, if you review the directory structures in the share where users’roaming pro- files are stored, and no .pds or .pdm extensions are appended, this is normal. No extension is appended to roaming profile directories that are new to Windows NT 4.0. These extensions are only added when profiles are migrated from Windows NT 3.5x to 4.0, or when the administrator creates a new Windows NT 4.0 mandatory profile that requires a successful logon.

Upgrading Windows NT 3.5x Mandatory Profiles to Windows NT 4.0 Mandatory Profiles

Upgrades of Windows NT 3.5x mandatory profiles to Windows NT 4.0 cannot be done automatically. This is because the same restrictions that prevent a user from saving any changes to his or her profile also restricts the system’s ability to generate a new Windows NT 4.0 mandatory profile from an existing profile.

30 Microsoft Windows NT Server White Paper

Page 37 Page 39
Image 38
Page 37 Page 39
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 An Introduction System Policy EditorPage Autorun Start Banner For More Information Appendix a -FlowchartsUser Profile Flowcharts System Policy Flowchart Appendix C Usage NotesTCO and the User Profiles, Policies, and the Zero Administration KitIntroduction What are User Profiles and System Policies? Before You Begin32-bit version of the Registry Editor Key TerminologyTechnical Notes ComputerUser Profile Structure Creating and Administering User ProfilesEstablishing User Profiles AN Overview 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 LinksTo 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 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 profileStart REGEDT32 and locate the following path Troubleshooting User Profiles with the UserEnv.log FileTo enable logging Sample Log =========================================================System Policy AN Introduction System Policy FilesThis change must be made individually to each workstation Policy ReplicationHow Policies Are Applied 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 locationTo 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 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 No Entire Network in Network Neighborhood Key Selection Hide drives in My Computer DescriptionSelection Hide Network Neighborhood Description 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 Custom Network Neighborhood Description Selection Hide Start menu subfolders DescriptionSelection Custom Startup folder Description As part of the Start menu \CurrentVersion \Explorer \User Shell FoldersSelection Custom Start menu Description Selection Only use approved shell extensions KeySelection Selection Disable context menus for the Taskbar DescriptionSelection Remove File menu from Explorer Description 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 Logon banner Selection Custom shared Start menu DescriptionSelection Custom shared Startup folder Description 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 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 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 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