Microsoft Windows NT 4.0 Guide Manual
  1. Manuals
  2. Brands
  3. Microsoft Manuals
  4. Software
  5. Windows NT 4.0 Guide
  6. Manual
Microsoft Windows NT 4.0 Guide Manual

Microsoft Windows NT 4.0 Guide Manual

Server operating system
Hide thumbs
Table of Contents

Advertisement

Quick Links

Server Operating System
®
White Paper
Guide to Microsoft
Windows NT
4.0 Profiles and Policies
®
®

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Windows NT 4.0 Guide and is the answer not in the manual?

Questions and answers

igor
March 11, 2025

как активировать порт irda

-1

Related Manuals for Microsoft Windows NT 4.0 Guide

Summary of Contents for Microsoft Windows NT 4.0 Guide

  • Page 1 Server Operating System ® White Paper Guide to Microsoft Windows NT 4.0 Profiles and Policies ® ®...
  • Page 2 Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
  • Page 3 4.0 Profiles and Policies on client workstations and servers. A ® Microsoft Windows NT 4.0 User Profile describes the Windows NT configuration for a specific user, including the user’ s environment and preference settings. A System Policy is a set of registry settings that together define the computer resources available to a group of users or an individual.
  • Page 5 Introduction ..................CONTENTS TCO and the User Profiles, Policies, and the Zero Administration Kit What are User Profiles and System Policies? Before You Begin Key Terminology Technical Notes Establishing User Profiles – An Overview .......... Creating and Administering User Profiles User Profile Structure Configuration Preferences Stored in the Registry Hive Configuration Preferences Stored in Profile Directories...

  • Page 6: Table Of Contents

    Upgrading Windows NT 3.5x Mandatory Profiles to Windows NT 4.0 Mandatory Profiles Extracting a User Profile for Use on Another Domain or Machine Creating Profiles Without User-Specific Connections Troubleshooting User Profiles with the UserEnv.log File System Policy – An Introduction............35 System Policy Files Policy Replication How Policies Are Applied...
  • Page 7 Start Menu Shut Down Command Saved Settings Registry Editing Tools Windows Applications Restrictions Custom Programs Custom Desktop Icons Start Menu Subfolders Custom Startup Folder Custom Network Neighborhood Custom Start Menu Shell Extensions Explorer File Menu Start Menu Common Program Groups Taskbar Context Menus Explorer Context Menu Network Connections...
  • Page 8 Extended Characters in 8.3 File Names Read Only Files – Last Access Time Cached Roaming Profiles Slow Network Detection Slow Network Timeout Dialog Box Timeout Registry Entries Not Included in the System Policy Editor.... 81 Autorun Start Banner For More Information................. 83 Appendix A –Flowcharts..............
  • Page 9 With these escalating costs in mind, Microsoft and others are working together on several initiatives to lower the total cost of ownership of personal computers.

  • Page 10: Before You Begin

    What are User Profiles and System Policies? A Microsoft Windows NT 4.0 User Profile describes the Windows NT configu- ration for a specific user, including the user’ s environment and preference settings. For example, those settings and configuration options specific to the user—...
  • Page 11 (named for their resemblance to the cel- lular structure of a beehive). A hive is a discrete body of keys, subkeys, and values. Roaming Profile A roaming profile is stored on a network share and can be accessed Microsoft Windows NT Server White Paper...

  • Page 12: Technical Notes

    Caution: Using Registry Editor incorrectly can cause system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be resolved. In addition, portions of this guide refer to a registry hive called NTuser.xxx. In instances where this is used, .xxx can be replaced with either .dat or .man.
  • Page 13 ESTABLISHING USER A Microsoft Windows NT 4.0 User Profile describes the Windows NT configu- PROFILES – AN ration for a specific user, including the user’ s environment and preference OVERVIEW settings. A User Profile can be local, roaming, or mandatory. A local profile is specific to a given computer.
  • Page 14 Recent. Shortcuts to the most recently used items. SendTo. Shortcuts to document storage locations and applications. Start Menu. Shortcuts to program items. Templates.* Shortcuts to template items. These directories are hidden by default. To see these directories, change the View Options. Microsoft Windows NT Server White Paper...
  • Page 15 NetWare Networks, see the chapter “ Windows 95 on NetWare Networks” in the Windows 95 Resource Kit. For more information on configuring a client that uses Microsoft Service for NetWare Directory Services, see the online Help that accompanies the service.
  • Page 16 If roaming profiles are stored on an NTFS partition, you can choose to remove the Delete permis- sion from the default Change permissions at the NTFS level. Microsoft Windows NT Server White Paper...
  • Page 17 This allows profiles to be stored on any shared network drive. The process of downloading the profile is controlled by the client computer— all the Microsoft Windows NT Server White Paper...
  • Page 18 HKEY_CURRENT_USER\Network\drive letter. (Do not delete the value— just fill it with blank spaces.) Save the profile. For additional help, refer to the section “ Administering a User Profile Manually Through the Registry” later in this document, or 10 Microsoft Windows NT Server White Paper...
  • Page 19 Local, then the cached copy of the User Profile is opened every time the user logs on. Any changes that occur to the profile are written locally and not to the server location. Microsoft Windows NT Server White Paper...

  • Page 20: Creating A New Roaming User Profile For Windows Nt

    View options in My Computer). Log off, and then log back on to the same computer using an account with administrative privileges. 12 Microsoft Windows NT Server White Paper...
  • Page 21 Step 3. For example, create the directory mydomainuser under \\myserver\myshare. If the profile is to be stored within the user's home directory, use the directory structure \mydomainuser\profile under \\myserver\myshare. Microsoft Windows NT Server White Paper...
  • Page 22 You can select any group or a specific user when setting the permissions. However, only the user or group specified will be able to use the profile. For this reason, it is recommended that the Everyone group be given permission to use template profiles. 14 Microsoft Windows NT Server White Paper...

  • Page 23: Creating A New Mandatory User Profile For Windows Nt

    .man to the User Profile path; for example: \\myserver\myshare\mydomainuser.man. Use User Manager to create an account for establishing the template pro- file. So that you can easily identify this account, we recommend that it be Microsoft Windows NT Server White Paper...
  • Page 24 13. In the directory that the profile was copied to in Step 3, check the NTUSER.xxx file for the .man extension. If the extension is .dat, the profile will still be modifiable. Change the extension to .man if necessary. 16 Microsoft Windows NT Server White Paper...

  • Page 25: Making A Roaming Profile Mandatory In Windows Nt

    ( \\) in front of %LOGONSERVER%; doing so will prevent the variable from being read properly. See Microsoft Knowledge Base article Q141714 for more information. You can use the TemplateUser account to test changes before making them available to users by copying the adjusted profile directory to test accounts prior to rollout.
  • Page 26 If you haven't already done so, change the name of the NTuser.xxx file to NTuser.dat. (Refer to the section, “ Changing the User’ s Ability to Modify a Profile, ” in this document.) 18 Microsoft Windows NT Server White Paper...
  • Page 27 User Pro- file exists in that folder. The profile does not need to be stored one directory below the \\server\share. The profile can be nested several directories below, if desired. Microsoft Windows NT Server White Paper...
  • Page 28 In Windows NT 4.0, much of the functionality provided by individual tools in Windows NT 3.5x has been consolidated in the Control Panel System Proper- ties application. And System Properties, when used in conjunction with the 20 Microsoft Windows NT Server White Paper...
  • Page 29 (In Windows NT 3.5x, this function was available in the Main group of the Windows NT Setup pro- gram.) To delete a User Profile, select the profile name and click the Delete Microsoft Windows NT Server White Paper...
  • Page 30 If this happens, stop the service and then delete the profile. Changing the Profile Type from Roaming to Local With the User Profiles Change Type feature, a user can control which copy of 22 Microsoft Windows NT Server White Paper...
  • Page 31 Match the directory sizes in the profiles tree to the number dis- played on the User Profiles property page. If the user is currently logged on, right-click the Start button. If context menus have not been disabled, select the option to Explore and Explorer Microsoft Windows NT Server White Paper...
  • Page 32 When you click the Browse button, the following dialog box appears. It is important to note that this dialog does not allow you to create directories. You must create the required directories before you copy the profile. 24 Microsoft Windows NT Server White Paper...
  • Page 33 Explorer window automatically open to his or her profile directory with the contents displayed. In addition, administrators can click the Explore All Users option to display the All Users profile directory. Microsoft Windows NT Server White Paper...
  • Page 34 All Users profile are also available to the user— in addition to the user’ s personal User Profile programs and shortcuts. Note that the All Users profile on a domain controller does not apply to domain users logging on 26 Microsoft Windows NT Server White Paper...
  • Page 35 ProfileImagePath. Should multiple users with the same account name log on to the network, separate distinct profiles are created for each. For example, if Microsoft Windows NT Server White Paper...
  • Page 36 A dialog will prompt you to enter a Key Name. You can use any value, but you must remember this value so that you can select it during the unload 28 Microsoft Windows NT Server White Paper...
  • Page 37 For example, if you want each new user that logs on to a given computer to receive a folder called “ My Storage” on the desktop, just create this folder in the path: \%systemroot%\Profiles\Default User\Desktop. Microsoft Windows NT Server White Paper...

  • Page 38: Mandatory Profiles

    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 39: Extracting A User Profile For Use On Another Domain Or Machine

    As explained previously in this document, a user is given explicit permissions to use a profile, and these permissions can be created and controlled by an administrator or generated automatically by the system when the user first logs Microsoft Windows NT Server White Paper...

  • Page 40: Creating Profiles Without User-Specific Connections

    HKEY_CURRENT_USER\Network. This key has subkeys that list the persis- tent drive connections by drive letter. For each of these subkeys, there is a value of UserName. If alternate credentials must be supplied to make the con- 32 Microsoft Windows NT Server White Paper...

  • Page 41: Troubleshooting User Profiles With The Userenv.log File

    Reboot the computer. Logging information will be recorded in the root directory of the C drive as UserEnv.log. You can use Notepad to view the log file. A sample log is pro- vided next. Microsoft Windows NT Server White Paper...
  • Page 42 = 0x102 RestoreUserProfile: Leaving. UpgradeProfile: Entering UpgradeProfile: Build numbers match UpgradeProfile: Leaving Successfully ApplyPolicy: Entering ApplyPolicy: Policy is turned off on this machine. LoadUserProfile: Leaving with a value of 1. hProfile = <0x60> ========================================================= 34 Microsoft Windows NT Server White Paper...

  • Page 43: System Policy – An Introduction

    You can do this by either manually changing the registry or by using System Policy. This path can even be a local path such that each machine has its own policy file, but if a change is necessary to all machines, Microsoft Windows NT Server White Paper...

  • Page 44: Policy Replication

    HKEY_CURRENT_USER key in the registry. 36 Microsoft Windows NT Server White Paper...

  • Page 45: Additional Implementation Considerations

    If so, computers from a certain locale may benefit from retrieving policy files from a machine that is close at hand, as opposed to using a domain controller that may not be nearby. Microsoft Windows NT Server White Paper...
  • Page 46 If after considering these issues, you conclude that System Policies will sim- plify administration of your system, use the System Policy Editor to create the appropriate individual and/or group policies, as explained in the next section. 38 Microsoft Windows NT Server White Paper...

  • Page 47: The System Policy Editor

    To install the System Policy Editor from the Windows 95 compact disc: Insert the Windows 95 Upgrade compact disc in your CD-ROM drive. Open Control Panel, and click Add/Remove Programs. Click the Windows Setup tab, and select Have Disk. Microsoft Windows NT Server White Paper...

  • Page 48: Updating The Registry With The System Policy Editor

    To ensure that the system uses the latest administrative information, the System Policy Editor reads the custom .adm files each time it starts. For detailed instructions when creating .adm files, see the section “ Creating 40 Microsoft Windows NT Server White Paper...

  • Page 49: Configuring Policy Settings

    If the box is checked, it is implemented. When the user next logs on, the user’ s computer conforms to the policy. If the option was checked the last time the user logged on, Windows NT makes no changes. Microsoft Windows NT Server White Paper...

  • Page 50: Setting Folder Paths Back To Defaults

    On a Windows NT Server-based machine in the domain where the policy file will apply, open the System Policy Editor. From the Start menu, click Programs, then click Administrative Tools (Common), then click Sys- 42 Microsoft Windows NT Server White Paper...
  • Page 51 (Depending on the number of workstations affected, this could be very time consuming.) Log on to the Windows NT-based workstation to download and enact the policy. Microsoft Windows NT Server White Paper...

  • Page 52: Creating Alternate Folder Paths

    This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. After you install the service pack, you can work around the problem by modifying the registry as explained next.

  • Page 53: Deploying Policies For Windows Nt 4.0 Machines

    To retrieve the policy file from a specific location: Open either the specific machine policy or the Default Computer policy, and navigate through the Network category and System policies update subcategory to reach the Remote update option. Check the Remote update box. Microsoft Windows NT Server White Paper...

  • Page 54: Deploying Policies For Windows 95 Machines

    NetworkPath for the existence of the Config.pol file. Note that the default mode for a Windows 95-based machine is Automatic. 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 55: Modifying Policy Settings On Stand-Alone Workstations

    Log on as administrator, open the System Policy Editor, and from the File menu, select Connect. Type the computer name of the workstation to be modified, and click Enter. A dialog will appear displaying the user name of the currently logged on Microsoft Windows NT Server White Paper...

  • Page 56: Creating A Custom .Adm File

    The content of this section is also documented in the Windows 95 Resource Kit and the Windows 32-bit Software Developer’ s Kit, which are available on the Microsoft Developer’ s Network or through Microsoft Sales. This section refers extensively to the following .adm files: Common.adm—...
  • Page 57 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...
  • Page 58 END PART REQUIRED— Generates an error if the user does not enter a value, for example: PART !!MyPolicy EDITTEXT REQUIRED VALUENAME ValueToBeChanged END PART EXPANDABLETEXT— Writes the value to the registry with data 50 Microsoft Windows NT Server White Paper...
  • Page 59 Policy Template, and press OK. This reloads the structure, and your new entries will be available. (You do not need to perform this step if you modify a file before starting the System Policy Editor; the reload is done automatically Microsoft Windows NT Server White Paper...

  • Page 60: Configuring System Policies Based On Geographic Location

    To build fault tolerance into this configuration, you can take advantage of the distributed file system (Dfs) available for the Windows NT Server 4.0 oper- ating system platform. Dfs, which runs as a service, can provide a share that 52 Microsoft Windows NT Server White Paper...
  • Page 61 Note that the the Dfs host server must be running for this fault tolerant structure to work. (Although Dfs software currently supports a single host server, Microsoft is developing a fault-tolerant version of Dfs for a future release of Windows NT.) For more information on the Dfs server and client components, see http://www.microsoft.com/ntserver/info/distributedfilesystem.htm.

  • Page 62: Registry Keys Modified By The System Policy Editor Default Templates

    \Control Panel \Desktop Registry Value Registry Data Description Wallpaper REG_SZ Off = value is removed; On = text of path to wallpaper TileWallpaper REG_SZ Off = 0 or value is removed; On = 1 54 Microsoft Windows NT Server White Paper...

  • Page 63: Color Scheme

    Remove folders from settings on Start menu Description: Removes the Control Panel and Printers folders from the Settings menu. Removing the Taskbar, Control Panel, and Printer folders causes the Settings menu to be re- moved completely. Key: HKEY_CURRENT_USER \Software \Microsoft Microsoft Windows NT Server White Paper...

  • Page 64: Settings Taskbar

    Completely removes the Find option from the Start menu. Key: HKEY_CURRENT_USER \Software \Microsoft \Windows \CurrentVersion \Policies \Explorer Registry Value Registry Data Description NoFind REG_DWORD Off = 0 or value is removed; On = 1 56 Microsoft Windows NT Server White Paper...

  • Page 65: My Computer Drive Icons

    Registry Data Description REG_DWORD NoNetHood Off = 0 or value is removed; On = 1 Network Neighborhood Display Category: Windows NT Shell Subcategory: Restrictions Selection: No Entire Network in Network Neighborhood Key: HKEY_CURRENT_USER \Software \Microsoft Microsoft Windows NT Server White Paper...

  • Page 66: Network Neighborhood Workgroup Contents

    HKEY_CURRENT_USER \Software \Microsoft \Windows \CurrentVersion \Policies \Explorer Registry Value Registry Data Description REG_DWORD NoDesktop Off = 0 or value is removed; On = 1 Start Menu Shut Down Command Category: Windows NT Shell 58 Microsoft Windows NT Server White Paper...
  • Page 67 Off = 0 or value is removed; On = 1 Registry Editing Tools Category: System Subcategory: Restrictions Selection: Disable registry editing tools Description: Disable user’ s ability to run Regedit.exe or Regedt32.exe. Key: HKEY_CURRENT_USER \Software \Microsoft Microsoft Windows NT Server White Paper...
  • Page 68 Off = 0 or value is removed; On = 1 Key: HKEY_CURRENT_USER \Software \Microsoft \Windows \CurrentVersion \Policies \Explorer \RestrictRun Registry Value Registry Data Description Number Increment REG_SZ Off = value is removed; On = text of applica- Starting with 1 tion name 60 Microsoft Windows NT Server White Paper...

  • Page 69: Custom Programs

    \Explorer \User Shell Folders Registry Value Registry Data Description Desktop REG_SZ Off = value is removed; On = text of UNC path to folder. Default = %USERPROFILE%\Desktop Start Menu Subfolders Category: Windows NT Shell Microsoft Windows NT Server White Paper...
  • Page 70 Custom Network Neighborhood Description: Specifies the UNC path the folder is to use to create the folders, files, and shortcuts the user receives when navi- gating through Network Neighborhood. Key: HKEY_CURRENT_USER \Software \Microsoft \Windows 62 Microsoft Windows NT Server White Paper...
  • Page 71 Windows NT Shell Subcategory: Restrictions Selection: Only use approved shell extensions Key: HKEY_CURRENT_USER \Software \Microsoft \Windows \CurrentVersion \Policies \Explorer\ Registry Value Registry Data Description EnforceShellExtensionSecurity REG_DWORD Off = 0 or value is removed; On = 1 Microsoft Windows NT Server White Paper...
  • Page 72 Disable context menus for the Taskbar Description: Removes the context menus for the tray, including the Start button, Tab control, and Clock. (This option was added in Service Pack 2.) Key: HKEY_CURRENT_USER \Software 64 Microsoft Windows NT Server White Paper...

  • Page 73: Network Connections

    Explorer and also removing the menu items from the Context menu of My Computer and the Tools menu of Explorer. (This option was added in Service Pack 2.) Key: HKEY_CURRENT_USER \Software \Microsoft \Windows \CurrentVersion \Policies Microsoft Windows NT Server White Paper...
  • Page 74 REG_SZ Off = 0 or value is removed; On = 1 Logon Scripts Category: Windows NT System Selection: Run logon scripts synchronously Description: Determines whether the shell waits for the logon script to 66 Microsoft Windows NT Server White Paper...

  • Page 75: Task Manager

    Enables or disables the display of the Welcome screen when the user logs on for the first and second time. (This option was added in Service Pack 2.) Key: HKEY_CURRENT_USER \Software \Microsoft \Windows \CurrentVersion Microsoft Windows NT Server White Paper...

  • Page 76: Remote Update

    Display error messages. Off = 0 or value not present; On = 1 LoadBalance REG_DWORD Off = 0 or value not present; On = 1 Communities Category: System Subcategory: SNMP Selection: Communities Key: HKEY_LOCAL_MACHINE \System 68 Microsoft Windows NT Server White Paper...
  • Page 77 NOTE: There may be multiple entries in this subkey. Public Community Traps Category: System Subcategory: SNMP Selection: Traps for public community Key: HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \SNMP \Parameters \TrapConfiguration \Public Microsoft Windows NT Server White Paper...
  • Page 78 This setting is specific to Windows NT Workstation. Key: HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \LanManServer \Parameters Registry Value Registry Data Description REG_DWORD AutoShareWks NT Workstation specific: Off = 0; On = 1 70 Microsoft Windows NT Server White Paper...
  • Page 79 Registry Value Registry Data Description REG_DWORD DisableServerThread Off = 0 or value is removed from registry; On = 1 Server Scheduler Category: Windows NT Printers Subcategory: Sharing Selection: Scheduler priority Key: HKEY_LOCAL_MACHINE \System \CurrentControlSet \Control Microsoft Windows NT Server White Paper...
  • Page 80 Decimal = 1-10; default = 2. Authentication Time Limit Category: Windows NT Remote Access Selection: Max time limit for authentication Description: Defines the maximum time limit in seconds for authenti- cation to occur. Key: HKEY_LOCAL_MACHINE 72 Microsoft Windows NT Server White Paper...
  • Page 81 Key: HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \RemoteAccess \Parameters Registry Value Registry Data Description AutoDisconnect REG_DWORD Off = value is removed, On = time in min- utes in hexadecimal. Decimal: minimum = 0; default = 20. Microsoft Windows NT Server White Paper...
  • Page 82 Off = value is removed from registry; REG_SZ can be used if On = text of UNC path to folder. no variables exist.) Default = %SystemRoot%\ Profiles\All Users\Desktop. Shared Start Menu Path Category: Windows NT Shell 74 Microsoft Windows NT Server White Paper...
  • Page 83 (Note: REG_SZ can be On = text of UNC path to folder. used if no variables exist.) Default = %SystemRoot%\Profiles\ All Users\Start Menu\Programs\ Startup Logon Banner Category: Windows NT System Subcategory: Logon Selection: Logon banner Microsoft Windows NT Server White Paper...
  • Page 84 Do not display last logged on user name Description: Enables or disables display of the last logged on user name when the user presses CTRL+ALT+DEL and the logon dialog is displayed. Key: HKEY_LOCAL_MACHINE \Software \Microsoft \Windows NT \CurrentVersion \Winlogon 76 Microsoft Windows NT Server White Paper...

  • Page 85: Extended Characters In 8.3 File Names

    Subcategory: File system Selection: Allow extended characters in 8.3 file names Description: Short file names with extended characters may not be viewable on computers that do not have the same char- acter code page. Microsoft Windows NT Server White Paper...

  • Page 86: Read Only Files – Last Access Time

    User Profile is deleted. Key: HKEY_LOCAL_MACHINE \Software \Microsoft \Windows NT \CurrentVersion \Winlogon Registry Value Registry Data Description REG_DWORD DeleteRoamingCache Off = 0 or value is removed; On = 1 78 Microsoft Windows NT Server White Paper...

  • Page 87: Slow Network Detection

    When the user is presented with a dialog box requesting User Profile information, this specifies the amount of time in seconds before the dialog box is closed and the default is accepted. Key: HKEY_LOCAL_MACHINE \Software \Microsoft \Windows NT \CurrentVersion \Winlogon Microsoft Windows NT Server White Paper...
  • Page 88 Registry Value Registry Data Description Show REG_DWORD Off = 0 or value is removed; On = time in sec- onds in hexadecimal. Decimal = 0-600; default = 30. 80 Microsoft Windows NT Server White Paper...

  • Page 89: Start Banner

    Windows NT Shell Subcategory: Start banner Description: Hides the arrow and "Click here to start" caption that ap- pears on the taskbar when you start Windows NT. Key: HKEY_CURRENT_USER \Software \Microsoft \Windows \CurrentVersion \Policies \Explorer Microsoft Windows NT Server White Paper...
  • Page 90 Registry Value Registry Data Description NoStartBanner REG_DWORD 0 = enabled; 1= disabled. 82 Microsoft Windows NT Server White Paper...
  • Page 91 Kit for version 4.0. For the latest information on Windows NT Server, check out our World Wide Web site at http://www.microsoft.com/backoffice or the Windows NT Server Forum on the Microsoft Network (GO WORD: MSNTS). Microsoft Windows NT Server White Paper...

  • Page 92: User Profile Flowcharts

    These flowcharts illustrate how User Profiles operate within the Windows NT 4.0 operating system, and give the administrator an at-a-glance look at the procedures to take and the internal processing that occurs when User Profiles are implemented under Windows NT 4.0. 84 Microsoft Windows NT Server White Paper...
  • Page 93 No changes will be written to the server, and will be available on to the Windows NT 4.0 profile subsequent logons. directory are necessary. Flowchart 1. Administrator’ s First Tasks Microsoft Windows NT Server White Paper...
  • Page 94 Ask user preference for written to the profile Part 2) server or local copy stored on the server. and load (continue to Part 2) (continue to Part 2) Flowchart 2. User Logon (Part 1) 86 Microsoft Windows NT Server White Paper...
  • Page 95 Load the User Profile Set USERPROFILE environment variable Check build number for version Different? Same? Process UserDiff Registry changes (from major version change) Apply System Policy Save settings to Registry Flowchart 3. User Logon (Part 2) Microsoft Windows NT Server White Paper...
  • Page 96 Try to create directory Deny logon Use default profile Use cached profile and return to and return to original flowchart original flowchart Flowchart 4. User Logon – Accessing Server-based Profile 88 Microsoft Windows NT Server White Paper...

  • Page 97: System Policy Flowchart

    Does Machine- User setting. Specific Policy exist? Does Default Read Machine-Specific Policy Computer Policy and write Registry entries exist? Read Default Computer Policy End policy process and write Registry entries Flowchart 5. Policy Application Microsoft Windows NT Server White Paper...

  • Page 98: Existing Windows Nt 3.5X Roaming Profile

    A domain user has an existing Windows NT 3.5x mandatory profile and moves to a Windows NT 4.0-based computer where the user will have a mandatory profile. What currently exists: A myuser.man file exists in the folder \\myserver\myshare. 90 Microsoft Windows NT Server White Paper...

  • Page 99: Creating A New Windows Nt 4.0 Roaming Profile

    A new user will be logging onto Windows NT 4.0-based computers only, and will be using a mandatory profile. What currently exists: Nothing currently exists for the user in \\myserver\myshare. Administrator action: In User Manager, specify the User Profile path with Microsoft Windows NT Server White Paper...

  • Page 100: Creating A New Mandatory User Profile For Windows Nt

    NTuser.dat file, which is located in the root of the user's profile folder, to NTuser.man. User action: None. For more information: See the section “Making a Roaming Profile Man- datory in Windows NT 4.0.” 92 Microsoft Windows NT Server White Paper...

  • Page 101: Recent Updates To Profiles Since Retail Release

    In Service Pack 2, support was added to give the administrator the ability to disable this behavior and use the path specified in the shortcut properties. For more information, reference Microsoft Knowledge Base article Q158682. Microsoft Windows NT Server White Paper...

  • Page 102: Recent Updates To Policies Since Retail Release

    All Users programs directory. This has been corrected in Service Pack 3. The Microsoft Office 97 Resource Kit contains .adm files that administra- tors can use when configuring the Office environment for their users. This is available now from Microsoft.
  • Page 103 APPENDIX D – RELATED The articles below can be referenced either on TechNet or by using the KNOWLEDGE BASE Microsoft Knowledge Base on Microsoft’ s Web site: ARTICLES http://www.microsoft.com/kb/. Profiles Q141714 How to Use %LOGONSERVER% to Distribute User Profiles Q154120 Debugging User Profiles and System Policies in Windows NT 4.0...
  • Page 104 Q156432 Windows NT 4.0 Policy Restriction Error at Logon Q155956 Cannot Restore Default Setting for Shutdown Button Q163215 System Policies May Not Work With Third-Party GINA DLLs 96 Microsoft Windows NT Server White Paper...

This manual is also suitable for:

Windows nt 4.0

Table of Contents

Save PDF