Microsoft Windows NT 4.0 manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104

Go to page of

A good user manual

The rules should oblige the seller to give the purchaser an operating instrucion of Microsoft Windows NT 4.0, along with an item. The lack of an instruction or false information given to customer shall constitute grounds to apply for a complaint because of nonconformity of goods with the contract. In accordance with the law, a customer can receive an instruction in non-paper form; lately graphic and electronic forms of the manuals, as well as instructional videos have been majorly used. A necessary precondition for this is the unmistakable, legible character of an instruction.

What is an instruction?

The term originates from the Latin word „instructio”, which means organizing. Therefore, in an instruction of Microsoft Windows NT 4.0 one could find a process description. An instruction's purpose is to teach, to ease the start-up and an item's use or performance of certain activities. An instruction is a compilation of information about an item/a service, it is a clue.

Unfortunately, only a few customers devote their time to read an instruction of Microsoft Windows NT 4.0. A good user manual introduces us to a number of additional functionalities of the purchased item, and also helps us to avoid the formation of most of the defects.

What should a perfect user manual contain?

First and foremost, an user manual of Microsoft Windows NT 4.0 should contain:
- informations concerning technical data of Microsoft Windows NT 4.0
- name of the manufacturer and a year of construction of the Microsoft Windows NT 4.0 item
- rules of operation, control and maintenance of the Microsoft Windows NT 4.0 item
- safety signs and mark certificates which confirm compatibility with appropriate standards

Why don't we read the manuals?

Usually it results from the lack of time and certainty about functionalities of purchased items. Unfortunately, networking and start-up of Microsoft Windows NT 4.0 alone are not enough. An instruction contains a number of clues concerning respective functionalities, safety rules, maintenance methods (what means should be used), eventual defects of Microsoft Windows NT 4.0, and methods of problem resolution. Eventually, when one still can't find the answer to his problems, he will be directed to the Microsoft service. Lately animated manuals and instructional videos are quite popular among customers. These kinds of user manuals are effective; they assure that a customer will familiarize himself with the whole material, and won't skip complicated, technical information of Microsoft Windows NT 4.0.

Why one should read the manuals?

It is mostly in the manuals where we will find the details concerning construction and possibility of the Microsoft Windows NT 4.0 item, and its use of respective accessory, as well as information concerning all the functions and facilities.

After a successful purchase of an item one should find a moment and get to know with every part of an instruction. Currently the manuals are carefully prearranged and translated, so they could be fully understood by its users. The manuals will serve as an informational aid.

Table of contents for the manual

  • Page 1

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

  • Page 2

    © 1997 Microsoft Corporation. All rights reserved. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microso[...]

  • Page 3

    This guide provides information and procedures for implementing Microsoft ® Windows NT ® 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 registr[...]

  • Page 4

    [...]

  • Page 5

    Introduction ................................................................ ......................... 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 ................................ ........[...]

  • Page 6

    Upgrading Windows NT 3.5x Mandatory Profiles to Windows NT 4.0 Mandatory Profiles 30 Extracting a User Profile for Use on Another Domain or Machine 31 Creating Profiles Without User-Specific Connections 32 Troubleshooting User Profiles with the UserEnv.log File 33 System Policy – An Introduction ...................................................[...]

  • 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 C[...]

  • Page 8

    Extended Characters in 8.3 File Names 77 Read Only Files – Last Access Time 78 Cached Roaming Profiles 78 Slow Network Detection 79 Slow Network Timeout 79 Dialog Box Timeout 79 Registry Entries Not Included in the System Policy Editor ............ 81 Autorun 81 Start Banner 81 For More Information ................................................[...]

  • Page 9

    Microsoft Windows NT Server White Paper 1 Not too many years ago, information technology professionals faced a serious challenge in controlling the mounting costs of mainframe use. It seemed that everyone — clerks, writers, developers, and systems administrators — all had terminals and were using the system for everything from numbers crunching[...]

  • Page 10

    2 Microsoft Windows NT Server White Paper bilities of Windows NT 4.0, and as such these techniques can readily be adapted to accommodate a corporation ’ s specific computing requirements. In the near future, you will see additional TCO-reducing features appear in Micr o - soft Windows ® 98, Windows NT 5.0, and Microsoft Systems Man agement Serve[...]

  • Page 11

    Microsoft Windows NT Server White Paper 3 Key Terminology Directory Replication The copying of a master set of directories from a server (called the export server) to specified servers or workstations (called import co m - puters) in the same or other domains. Replication simplifies the task of maintaining identical sets of directories and files on[...]

  • Page 12

    4 Microsoft Windows NT Server White Paper from any computer. A user who has a roaming profile can log on to any computer for which that profile is valid and access the profile. (Note that a profile is only valid on the platform for which it was cr e - ated — for example, a Windows NT 4.0 profile cannot be used on a Windows 95 computer.) Roaming U[...]

  • Page 13

    Microsoft Windows NT Server White Paper 5 A Microsoft Windows NT 4.0 User Profile describes the Windows NT config u - ration for a specific user, including the user ’ s environment and preference settings. A User Profile can be local , roaming , or mandatory . A local profile is specific to a given computer. A user who creates a local profile on [...]

  • Page 14

    6 Microsoft Windows NT Server White Paper settings, and portions of the registry can be saved as files, called hives . These hives can then be reloaded for use as necessary. User Profiles take advantage of the hive feature to provide roaming profile functio n ality. The User Profile registry hive is the NTuser.dat in file form, and is mapped to the[...]

  • Page 15

    Microsoft Windows NT Server White Paper 7 Windows NT 4.0 and Windows 95 User Profile Differences Windows 95 Profiles are very similar in behavior to Windows NT 4.0 Profiles, but there are some differences. Unlike Windows NT 4.0, Windows 95 downloads and writes User Profiles to the user ’ s home directory. When the Windows 95 user first logs on, t[...]

  • Page 16

    8 Microsoft Windows NT Server White Paper home directory (or other specified directory if the location has been modified) on the server for the User Profile. If a profile exists in both locations, the newer of the two is used. If the User Profile exists on the server, but does not exist on the local machine, the profile on the server is downloaded [...]

  • Page 17

    Microsoft Windows NT Server White Paper 9 NOTE: Directories containing roaming User Profiles need at least Add and Read permissions for profiles to be read correctly. If you use Add permissions only, when Windows NT checks for the existence of the profile it will fail because it looks for the path first, and if Read rights are not given, the check [...]

  • Page 18

    10 Microsoft Windows NT Server White Paper client needs is the correct path. Note that storing profiles on a Windows NT 4.0 Server makes it easier for the administrator to open a user ’ s NTuser.dat file to make any necessary modifications. You can also store User Profiles on Novell Servers provided that the client is configured correctly and can[...]

  • Page 19

    Microsoft Windows NT Server White Paper 11 3. Delete the network connection and reconnect. Working Around Slow Network Links Slow Net (which is configured in System Policy) was designed to offer a user faster access to his or her User Profile if the system detects a slower network speed, such as a modem line connection. Instead of automatically dow[...]

  • Page 20

    12 Microsoft Windows NT Server White Paper Creating a New Roaming User Profile for Windows NT 4.0 To create a new roaming User Profile, you must first determine where the user ’ s profile will be stored. You then must create a user account (if one doesn ’ t already exist), and specify a User Profile path. Finally, you must spe c - ify whether a[...]

  • Page 21

    Microsoft Windows NT Server White Paper 13 8. Place the template profile in the appropriate location for the type of profile distribution that will be used. (The template profile, including customiz a - tions, is stored initially in %systemroot%ProfilesTemplateUser.) • If the template profile will be distributed manually to multiple u s ers : a[...]

  • Page 22

    14 Microsoft Windows NT Server White Paper 10. Copy the profile appropriate to your implementation. • To copy an existing user ’ s profile to another user: a) From the Windows NT-based machin e hosting the profile to be used, log on as an administrator. b) From the Control Panel, click System . On the User Profiles page, select the profile to b[...]

  • Page 23

    Microsoft Windows NT Server White Paper 15 Once the above steps are completed, the user receives the appropriate profile as follows: • If the user is to receive the Default User profile from a Windows NT 4.0- based workstation, the workstation ’ s default profile is used when the user first logs on. When the user logs off, the profile is automa[...]

  • Page 24

    16 Microsoft Windows NT Server White Paper called TemplateUser . 6. Using the template account (TemplateUser), log on to the local machine or domain. A new directory with the same name as the user name created in Step 2 will be created in the %systemroot%Profiles directory when you first log on. For example, if the user name is TemplateUser, the r[...]

  • Page 25

    Microsoft Windows NT Server White Paper 17 NOTES: • When entering the path to the target directory, you can use universal naming convention (UNC) names. However, if you are going to use the Browse function to locate the target directory for the profile, it is important that you first map a drive to the servershare where the profile will be sto[...]

  • Page 26

    18 Microsoft Windows NT Server White Paper Be cautious if you use the Explorer interface to make these changes. If you have the “ Hide file extensions for known file types ” option enabled (this is the default), be sure to check the properties to be sure that there are not two extensions. For example, say you want to make a profile ma n - dator[...]

  • Page 27

    Microsoft Windows NT Server White Paper 19 Creating a New Roaming User Profile for a Windows 95 User If you have Windows 95 users in your domain, you can create r oaming user profiles for them as well. To create a roaming user profile for a Windows 95 user 1. On the client Windows 95-based computer, start Control Panel, and select Passwords . 2. Fr[...]

  • Page 28

    20 Microsoft Windows NT Server White Paper Creating a New Mandatory User Profile for Windows 95 If you have Windows 95 users in your domain, you ca n create new mandatory user profiles. To create a mandatory user profile for a Windows 95 user: 1. On the client Windows 95-based computer, start Control Panel, and select Passwords . 2. From the User P[...]

  • Page 29

    Microsoft Windows NT Server White Paper 21 System Policy Editor, provides even greater functionality than Windows NT 3.5x deli v ered. Some of the features of System Properties are described next. NOTE: In Windows NT 3.5x, you used the User Profile Editor to modify User Profile properties. In Windows NT 4.0, this tool has been replaced by a combina[...]

  • Page 30

    22 Microsoft Windows NT Server White Paper button. This deletes the User Profile on the local machine, but it does not d e - lete the associated User Account. Note that sometimes the phrase “ Account Deleted ” is present in the list of profiles. These are accounts that were deleted from the User Account Database, but whose profiles still exist [...]

  • Page 31

    Microsoft Windows NT Server White Paper 23 the User Profile (local or roaming) is read when he or she logs on. (Note that the user can do this interactively while logged on.) Users do not need admini s - trative privileges to change which profile is used if the profile is not a mandatory profile. Valid profile types are: • Local Profile — A loc[...]

  • Page 32

    24 Microsoft Windows NT Server White Paper will open to the profile directory used by that account. 3. If you don ’ t know when the user last logged on, look for the NTuser.dat file with a time and date stamp that matches the Modified date displayed in the User Profiles property page. Copying Profiles Use the User Profiles Copy To button to copy [...]

  • Page 33

    Microsoft Windows NT Server White Paper 25 Viewing the Contents of the Profiles Directory on a Local Co m puter All locally cached versions of User Profiles are stored in the profiles subdire c - tory of the Windows NT root directory. The profiles su bdirectory maintains each user ’ s profile separately by generating a specific directory for each[...]

  • Page 34

    26 Microsoft Windows NT Server White Paper You may notice that in a given user ’ s profile directory, there are more files and directories than those listed in the example above. This may be due to the files and directories created by the user. For example, when the user logs on, if the server-based profile is found to be more recent than the one[...]

  • Page 35

    Microsoft Windows NT Server White Paper 27 at remote workstations. The All Users profile is workstation-specific and co n - tains the common groups for just that computer. If you want to specify programs, shortcuts, or directories to be used by everyone who logs on to a specific workstation, you should place these in the All Users profile dire c to[...]

  • Page 36

    28 Microsoft Windows NT Server White Paper multiple users with the account name John Smith log on to the computer, the first John Smith is assigned a folder named JohnSmith. Subsequent users with the same name are assigned folders named JohnSmith with a numerical suffix appended, for example JohnSmith.000 , JohnSmith.001 , and so forth. Manually Ad[...]

  • Page 37

    Microsoft Windows NT Server White Paper 29 process. For this reason, we recommend that you use the user name. 6. Click Enter. This adds the profile registry hive as a subkey to HKEY_USERS, as shown in the illustration below. 7. Edit the existing values as necessary. 8. After completing the changes, highlight the root of the user ’ s profile regi [...]

  • Page 38

    30 Microsoft Windows NT Server White Paper 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 profil[...]

  • Page 39

    Microsoft Windows NT Server White Paper 31 When you upgrade a Windows NT 3.5x mandatory profile, the profile path does not need to be modified. However, you will need to create a new ma n - datory profile with the same desired settings. To create the mandatory profile, you can remove the mandatory extension from the old profile and force a co n - v[...]

  • Page 40

    32 Microsoft Windows NT Server White Paper If a profile has permissions that differ from those needed by the user (for example, if the profile was created for a user on a different domain), the profile permissions must be changed to function correctly. As an example, suppose you have a Windows NT-based workstation that you would like to have join t[...]

  • Page 41

    Microsoft Windows NT Server White Paper 33 nection, those credentials are also stored here. Note that this includes only the domain and user account name; the password is not included. When the user receives this profile and logs on, Windows NT attempts to reconnect the drive, but the alternate credentials are sent rather than those of the logged o[...]

  • Page 42

    34 Microsoft Windows NT Server White Paper Sample Log ========================================================= LoadUserProfile. : Entering, hToken = <0xac>, lpProfileInfo = 0x12f4f4 LoadUserProfile: lpProfileInfo->dwFlags = <0x2> LoadUserProfile: lpProfileInfo->lpUserName = <administrator> LoadUserProfile: NULL central prof[...]

  • Page 43

    Microsoft Windows NT Server White Paper 35 A System Policy is a set of registry settings that defines the computer r e - sources available to an individual or to a group of users. Policies define the various facets of the desktop environment that a system administrator needs to control, such as which applications are available, which applications a[...]

  • Page 44

    36 Microsoft Windows NT Server White Paper this change must be made individually to each workst a tion. When a user of a Windows NT 4.0-based workstation logs on, if the Windows NT 4.0-based machine is working in Automatic mode (which is the default), the workstation checks the NETLOGON share on the validating d o - main controller (DC) for the NTc[...]

  • Page 45

    Microsoft Windows NT Server White Paper 37 e applied to the HKEY_CURRENT_USER key in the registry. NOTE: If a setting is ignored (gray) in the group settings, but the same setting is marked as enabled or disabled in the Default User settings, the Default User setting are used. The Default User settings take precedence over only those settings that [...]

  • Page 46

    38 Microsoft Windows NT Server White Paper • What type of restrictions do you want to impose on users? • Will users be allowed to access locally installed common group applic a - tions, or will these be overridden by administrator-defined program groups, desktop icons, Start menu programs, and so forth? • What other options are available if y[...]

  • Page 47

    Microsoft Windows NT Server White Paper 39 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 t[...]

  • Page 48

    40 Microsoft Windows NT Server White Paper 4. Browse to locate the directory x :AdminApptoolsPoledit (where x is drive A through Z) on the Windows 95 compact disc. 5. Select both Group Policies and the System Policy Editor , and then click OK to Install . It is important that you run the setup program as described above. Undesi r- able results [...]

  • Page 49

    Microsoft Windows NT Server White Paper 41 Your Own Custom .Adm File, ” later in this document. NOTE: The option to Add or Remove will be grayed out if there is a policy file currently open. Close the file in use and then change the template configur a tion. Configuring Policy Settings The configuration options available to you fall into a tree s[...]

  • Page 50

    42 Microsoft Windows NT Server White Paper • If the box is cleared , the policy is not implemented, and if the settings were previously impl e mented, they are removed from the registry. • If the box is grayed , the setting is ignored and unchanged from the last time the user logged on. Windows NT does not modify this setting. The grayed state [...]

  • Page 51

    Microsoft Windows NT Server White Paper 43 tem Policy Editor . 2. From the File menu, click New Policy . 3. The Default Computer and Default User icons will be displayed. Click the user, computer, or group to be modified. NOTES: If you need to add a user, group, or computer, you can copy and paste the settings without having to manually go through [...]

  • Page 52

    44 Microsoft Windows NT Server White Paper Creating Alternate Folder Paths You may need to create shared folders for groups of users who need a co m - mon set of tools and shortcuts. Windows NT 4.0 System Policies allows you to create such shared folders. To create shared folders and alternate folder paths: 1. On a specific server, create a folder [...]

  • Page 53

    Microsoft Windows NT Server White Paper 45 Policies Explorer 3. Add the following DWORD value by clicking Edit , New , DWORD value: LinkResolveIgnoreLinkInfo 4. Once entered, double-click this value and set the Value data to 1. Deploying Policies for Windows NT 4.0 M a chines By default, a Windows NT 4.0-based workstation checks the NETLOGON shar[...]

  • Page 54

    46 Microsoft Windows NT Server White Paper 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 fil[...]

  • Page 55

    Microsoft Windows NT Server White Paper 47 Modifying Policy Settings on Stand-Alone Workst a tions If you need to modify settings of a Windows NT 4.0-based wo rkstation user who is not a member of the domain and thus will not be able to use the policy file located on the domain, you have three options available to you: • You can create a policy f[...]

  • Page 56

    48 Microsoft Windows NT Server White Paper user for whom the changes will apply. If the user is not currently logged on, click Cancel. (The user must be logged on for the changes to take e f fect.) 3. If the user is logged on, click OK. 4. The icons Local Computer and Local User will be displayed. 5. Modify these just as you would modify a normal p[...]

  • Page 57

    Microsoft Windows NT Server White Paper 49 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[...]

  • Page 58

    50 Microsoft Windows NT Server White Paper option is selected within the lower pane of the System Policy Editor (see the di s cussion of PART and the code example below). If not specified otherwise, the value will be written in the following fo r mat when any administratory checks or unchecks the option: Checked: REG_DWORD with a value of 1 Uncheck[...]

  • Page 59

    Microsoft Windows NT Server White Paper 51 type REG_EXPAND_SZ, for example: PART !!MyPolicy EDITTEXT EXPANDABLETEXT VALUENAME ValueToBeChanged END PART • MAXLEN — Specifies the maximum length of text, for example: PART !!MyPolicy EDITTEXT VALUENAME ValueToBeChanged MAXLEN 4 END PART • DEFAULT — Specifies the default value for text or numeri[...]

  • Page 60

    52 Microsoft Windows NT Server White Paper each time the System Policy Editor starts.) Configuring System Policies Based on Geographic Location You may choose to enforce certain environment settings based upon ge o - graphic site location or vicinity. At least two methods are avai l able to do this. • Generate a System Policy that contains settin[...]

  • Page 61

    Microsoft Windows NT Server White Paper 53 will refer the client to multiple servers for the same path. For example, on a Dfs server, the administrator has defined that users connecting to the UNC path DfsserverDfsshareCustomfolder, will be returned a response with three di f - ferent servers, Server1Customerfolder, Server2Customerfolder,[...]

  • Page 62

    54 Microsoft Windows NT Server White Paper The following outlines the locations and values for registry entries that are written to a Windows NT-based workstation or server when you use the Sy s - tem Policy Editor to modify a policy. Knowing the location of these registry settings may help you to resolve problems. Default User Settings The followi[...]

  • Page 63

    Microsoft Windows NT Server White Paper 55 Color Scheme Category: Desktop Selection : Color scheme Key : HKEY_CURRENT_USER Control Panel Appearance Registry Value Registry Data Description Current REG_SZ Off = value is removed; On = text of color scheme name Start Menu Run Command Category: Windows NT Shell Subcategory : Restrictions Selection : [...]

  • Page 64

    56 Microsoft Windows NT Server White Paper Windows CurrentVersion Policies Explorer Registry Value Registry Data Description NoSetFolders REG_DWORD Off = 0 or value is r e moved; On = 1 Settings Taskbar Category: Windows NT Shell Subcategory : Restrictions Selection : Remove Taskbar from settings on Start menu Description : Removes the Taskbar [...]

  • Page 65

    Microsoft Windows NT Server White Paper 57 My Computer Drive Icons Category: Windows NT Shell Subcategory : Restrictions Selection : Hide drives in My Computer Description : Removes the ic ons for the drives in My Computer. Key : HKEY_CURRENT_USER Software Microsoft Windows CurrentVersion Policies Explorer Registry Value Registry Data Descrip[...]

  • Page 66

    58 Microsoft Windows NT Server White Paper Windows CurrentVersion P olicies Network Registry Value Registry Data Description NoEntireNetwork REG_DWORD Off = 0 or value is removed; On = 1 Network Neighborhood Workgroup Contents Category: Windows NT Shell Subcategory : Restrictions Selection : No workgroup contents in Network Neighbo r hood Key :[...]

  • Page 67

    Microsoft Windows NT Server White Paper 59 Subcategory : Restrictions Selection : Disable Shut Down command Description : Disables the Shut Down option on the Start menu. Note that this does not disable the user ’ s ability to shut down the computer using the CTRL-ALT-DEL sequence. If you want to remove the user ’ s ability to use CTRL-ALT-DEL,[...]

  • Page 68

    60 Microsoft Windows NT Server White Paper Windows CurrentVersio n Policies System Registry Value Registry Data Description DisableRegistr y Tools REG_DWORD Off = 0 or value is removed; On = 1 Windows Applications Restrictions Category: System Subcategory : Restrictions Selection : Run only allowed Windows applications Description : Restricts t[...]

  • Page 69

    Microsoft Windows NT Server White Paper 61 Custom Programs Category: Windows NT Shell Subcategory : Custom Folders Selection : Custom Program folder Description : Specifies the UNC path for the folder to use when di s - playing folders, files, and shortcuts available when the user selects Programs from the Start menu. The user ’ s profile Program[...]

  • Page 70

    62 Microsoft Windows NT Server White Paper Subcategory : Custom Folders Selection : Hide Start menu subfolders Description : Hides subfolders, such as the user ’ s Programs folder, if a custom Programs folder exists. Key : HKEY_CURRENT_USER Software Microsoft Windows CurrentVersion Policies Explorer Registry Value Registry Data Description [...]

  • Page 71

    Microsoft Windows NT Server White Paper 63 CurrentVersion Explorer User Shell Folders Registry Value Registry Data Description NetHood REG_SZ Off = value is removed; On = text of UNC path to folder. Default = %USERPROFILE%NetHood Custom Start Menu Category: Windows NT Shell Subcategory : Custom Folders Selection : Custom Start menu Description [...]

  • Page 72

    64 Microsoft Windows NT Server White Paper Explorer File Menu Category : Windows NT Shell Subcategory : Restrictions Selection : Remove File menu from Explorer Description : Removes the File option from Explorer ’ s tool bar. (This option was added in Service Pack 2.) Key : HKEY_CURRENT_USER Software Mcrosoft Windows CurrentVersion Policies [...]

  • Page 73

    Microsoft Windows NT Server White Paper 65 Microsoft Windows CurrentVersion Policies Explorer Registry Value Registry Data Description NoTrayCo n textMenu REG_DWORD Off = 0 or value is removed; On = 1 Explorer Context Menu Category : Windows NT Shell Subcategory : Restrictions Selection : Disable Explorer ’ s default context menu Description[...]

  • Page 74

    66 Microsoft Windows NT Server White Paper Explorer Registry Value Registry Data Description NoNetConnectDisco n nect REG_DWORD Off = 0 or value is removed; On = 1 Explorer Context Menu Category : Windows NT Shell Subcategory : Restrictions Selection : Disable link file tracking Description : When enabled, link file tracking uses the configured pa[...]

  • Page 75

    Microsoft Windows NT Server White Paper 67 complete or not. If the value is 0, the logon script is run during the startup of the shell and allows items in the Startup group to start. If the value is 1, the logon script completes before the shell or any items in the Startup group are started. If this value is also set in the Computer section, the Co[...]

  • Page 76

    68 Microsoft Windows NT Server White Paper Explorer Tips Registry Value Registry Data Description Show REG_DWORD Off = 0; On = 1 Default Computer Settings The following data is specific to the options found in the Default Computer po r- tion of the System Policy Editor. Remote Update Category : Network Subcategory : System Policies update Selecti[...]

  • Page 77

    Microsoft Windows NT Server White Paper 69 CurrentControlSet Services SNMP Parameters ValidCommunities Registry Value Registry Data Description Increment numbers begi n ning with 1 REG_SZ On = text of Valid Community # x ; Off = value is removed from registry NOTE: There may be multiple entries in this subkey. Permitted Managers Category : Sys[...]

  • Page 78

    70 Microsoft Windows NT Server White Paper Registry Value Registry Data Description Increment numbers begi n ning with 1 REG_SZ On = text of Trap Configuration # x; Off = value is removed from registry NOTE: There may be multiple entries in this subkey. Run Command Category : System Subcategory : Run Selection : Run Description : Allows one or more[...]

  • Page 79

    Microsoft Windows NT Server White Paper 71 Drive Shares – Server Category : Windows NT Network Subcategory : Sharing Selection : Create hidden drive shares (server) Description : When enabled, creates the administrative shares for physical drives. These shares were created automatically under Windows NT 3.51. This policy setting gives a d - minis[...]

  • Page 80

    72 Microsoft Windows NT Server White Paper Print Registry Value Registry Data Description SchedulerThreadPr i ority REG_DWORD Above normal = 1; Normal = 0, Less than normal = ffffffff Error Beep Category : Windows NT Printers Subcategory : Sharing Selection : Beep for error enabled Description : Enables beeping (every 10 seconds) when a remote job[...]

  • Page 81

    Microsoft Windows NT Server White Paper 73 System CurrentControlSet Services RemoteAccess Parameters Registry Value Registry Data Description AuthenticateTime REG_DWORD Off = value is removed , On = time in se c - onds in hexadecimal. Decimal = 20-600; default = 120. RAS Call-back Interval Category : Windows NT Remote Access Selection : Wait i[...]

  • Page 82

    74 Microsoft Windows NT Server White Paper Shared Programs Folder Path Category : Windows NT Shell Subcategory : Custom shared folders Selection : Custom shared Programs folder Description : Specifies the UNC path for the folder to use when di s - playing folders, files, and shortcuts below the division line (common groups) when the user selects Pr[...]

  • Page 83

    Microsoft Windows NT Server White Paper 75 Subcategory : Custom shared folders Selection : Custom shared Start menu Description : Specifies the UNC path the folder is to use when di s - playing the folders, files, and shortcuts the user receives as part of the Start menu. Key : HKEY_LOCAL_MACHINE Software Microsoft Windows CurrentVersion Explo[...]

  • Page 84

    76 Microsoft Windows NT Server White Paper Description : Before the user logs on, displays a custom dialog box with text. Key : HKEY_LOCAL_MACHINE Software Microsoft Windows NT CurrentVersion Winlogon Registry Value Registry Data Description LegalNoticeCa p tion REG_SZ Off = value is removed; On = text of caption LegalNoticeText REG_SZ Off = v[...]

  • Page 85

    Microsoft Windows NT Server White Paper 77 Registry Value Registry Data Description DontDisplayLastUse r Name REG_SZ Off = 0; On = 1 Logon Scripts Category : Windows NT System Subcategory : Logon Selection : Run logon scripts synchronously Description : Determines whether the shell waits for the logon script to complete or not. If the value is 0, t[...]

  • Page 86

    78 Microsoft Windows NT Server White Paper Key : HKEY_LOCAL_MACHINE System CurrentControlSet Control FileSystem Registry Value Registry Data Description NtfsAllowExtendedCharacterIn8dot3Name REG_DWORD Off = 0 or value is r e moved; On = 1 Read Only Files – Last Access Time Category : Windows NT System Subcategory : File system Selection : Do [...]

  • Page 87

    Microsoft Windows NT Server White Paper 79 Slow Network Detection Category : Windows NT User Profiles Selection : Automatically detect slow network connections Description : Enables or disables detection of a slow network. Key : HKEY_LOCAL_MACHINE Software Microsoft Windows NT CurrentVersion Winlogon Registry Value Registry Data Description Sl[...]

  • Page 88

    80 Microsoft Windows NT Server White Paper Registry Value Registry Data Description Show REG_DWORD Off = 0 or value is removed; On = time in se c - onds in hexadecimal. Decimal = 0-600; default = 30.[...]

  • Page 89

    Microsoft Windows NT Server White Paper 81 The following section describes the locations and values for useful registry entries that are available in the operating system, but not available in the Sy s - tem Po l icy Editor. Autorun Category : Windows NT Shell Subcategory: Removable media Description : Determines whether the Autorun feature is enab[...]

  • Page 90

    82 Microsoft Windows NT Server White Paper Registry Value Registry Data Description NoStartBanner REG_DWORD 0 = enabled; 1= di s abled.[...]

  • Page 91

    Microsoft Windows NT Server White Paper 83 For more information when configuring your network, refer to the following: • Windows NT Server Concepts and Planning Guide − Chapter 3, “ Mana g - ing User Work Environments ” (part of the Windows NT Server product documentation). • Kixtart Resource Kit Utility available in the Windows NT Server[...]

  • Page 92

    84 Microsoft Windows NT Server White Paper 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 impl e mented under Windows NT 4.0. APPENDIX A ?[...]

  • Page 93

    Microsoft Windows NT Server White Paper 85 Begin Profile Process: Does the user already have a profile from Windows NT 3.5x? No Yes Is the profile .usr or .man? Will the user be mandated to receive the profile for logon? No Yes Configure the user profile path for the account with: servershare<username>.man Configure the user profile path [...]

  • Page 94

    86 Microsoft Windows NT Server White Paper Workstation boots, computer account is validated, and user enters logon credentials Receive data from Domain Controller about User Account Flag as not available Does the user account contain a User Profile path? Is the server copy available? See flowchart "Accessing Server- based Profile" Yes No [...]

  • Page 95

    Microsoft Windows NT Server White Paper 87 (Continued) from Command to Load Profile Set USERPROFILE environment variable Check build number for version Load the User Profile Apply System Policy Save settings to Registry Same? Process UserDiff Registry changes (from major version change) Different? Flowchart 3. User Logon (Part 2)[...]

  • Page 96

    88 Microsoft Windows NT Server White Paper Call made to check server profile Check for .man extension in profile path Flag as mandatory Start timer, check the existence of the profile path, and after completion, stop timer No Yes Directory File Nothing Access denied error Windows NT 3.5x profile found. Generate Windows NT 4.0 profile and return to [...]

  • Page 97

    Microsoft Windows NT Server White Paper 89 System Policy Flowchart This flowchart illustrates how System Policy is applied in the Windows NT 4.0 operating system, and gives the administrator an at-a-glance look at the internal processing that occurs when policies are implemented under Windows NT 4.0. Initiate application of policy Does User-Specifi[...]

  • Page 98

    90 Microsoft Windows NT Server White Paper The following are typical user profile scenarios that you may encounter in the future or may have already encountered. Each of these scenarios includes a brief description of the situation, the current status of the profiles on the server, actions that you need to take to administer the profile properly, a[...]

  • Page 99

    Microsoft Windows NT Server White Paper 91 • Administrator action: Create a folder with the name myuser.pdm in the existing folder myservermyshare , and then place the desired mandatory profile into the new folder. • User action: None. • Notes: Once this procedure is performed, the Windows NT 3.5x profile is still available to the user sho[...]

  • Page 100

    92 Microsoft Windows NT Server White Paper the extension .man. For example, use myservermysharemyuser.man. Then manually create the myuser.man folder manually in the myservermyshare directory. Places the mandatory profile for the user in this new folder. • User action: None. • For more information: See the section “ Creating a New Mand[...]

  • Page 101

    Microsoft Windows NT Server White Paper 93 Important Information for Administrators Regarding User Logons and User Logoffs • Changes that you make to server-based profiles can be lost if you do not modify the last modification date/time stamp. When a locally cached ve r- sion of a profile is compared with the server-based profile, only the time/d[...]

  • Page 102

    94 Microsoft Windows NT Server White Paper Recent Updates to Policies Since Retail Release The following changes have been made to System Policies support since the initial retail release of Windows NT 4.0. • When a policy file was to be downloaded, if the validating domain contro l - ler name was 13 characters or longer, the policy would not be [...]

  • Page 103

    Microsoft Windows NT Server White Paper 95 The articles below can be referenced either on TechNet or by using the Microsoft Knowledge Base on Microsoft ’ s Web site: http://www.microsoft.com/kb/ . Profiles Q141714 How to Use %LOGONSERVER% to Distribute User Pr o files Q154120 Debugging User Profiles and System Policies in Windows NT 4.0 Q156568 H[...]

  • Page 104

    96 Microsoft Windows NT Server White Paper 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[...]