Manuals / Microsoft / Computer Equipment / Server

Microsoft Windows NT 4.0 manual Updating and Changing a Roaming Profile to a Mandatory Profile

Models: Windows NT 4.0

1 104

Download 104 pages 4.81 Kb

Page 100

the extension .man. For example, use \\myserver\myshare\myuser.man. Then manually create the myuser.man folder manually in the \\myserver\myshare directory. Places the mandatory profile for the user in this new folder.

∙User action: None.

∙For more information: See the section “Creating a New Mandatory User Profile for Windows NT 4.0.”

Updating and Changing a Roaming Profile to a Mandatory Profile

A domain user has an existing Windows NT 4.0 roaming User Profile that was not upgraded from Windows NT 3.5x, and the administrator is going to man- date that the profile be read or logon will denied.

∙What currently exists: A myuser folder containing the user’s roaming profile exists in \\myserver\myshare.

∙Administrator action: Use User Manager to add the .man extension to the User Profile path, thus changing the path to \\myserver\myshare\myuser.man. Then, rename the existing folder that contains the user’s roaming profile from myuser to myuser.man. Finally, rename the 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.”

Changing a Roaming Profile to a Mandatory Profile

A domain user has an existing Windows NT 4.0 roaming User Profile that was upgraded from Windows NT 3.5x, and the administrator is going to mandate that the profile be read or logon will denied.

∙What currently exists: A myuser.pds folder containing the user's roaming profile exists in \\myserver\myshare.

∙Administrator action: Use User Manager to change the extension of the User Profile path to .man, changing the path to \\myserver\myshare\myuser.man. Then rename the existing folder that contains the user's roaming profile from myuser.pds to myuser.pdm. Fi- nally, rename the 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

Image 100

Contents

Server Operating System White Paper Guide to Microsoft Windows NT 4.0 Profiles and PoliciesMicrosoft Corporation One Microsoft Way Redmond, WA 98052-6399 USA 1997 Microsoft Corporation. All rights reserved0997 Abstract Page CONTENTS IntroductionEstablishing User Profiles - An Overview Creating and Maintaining User ProfilesRegistry Keys Modified by the System Policy Editor Default System Policy - An IntroductionThe System Policy Editor TemplatesStart Menu Shut Down Command Saved Settings Registry Editing Tools Welcome Tips Default Computer Settings Remote Update CommunitiesPermitted Managers Public Community Traps Run Command Printer Browse Thread Server Scheduler Error BeepAppendix A -Flowcharts For More InformationAppendix C - Usage Notes Registry Entries Not Included in the System Policy EditorINTRODUCTION Profiles, Policies, and the Zero Administration KitTCO and the User Before You Begin What are User Profiles and System Policies?2 Microsoft Windows NT Server White Paper Directory Replication Technical Notes Roaming UserSystem Policy systemroot%ESTABLISHING USER PROFILES - AN OVERVIEW Creating and Administering User ProfilesUser Profile Structure The NTuser.dat file contains the following configuration settings Windows NT 4.0 and Windows User Profile Differences Windows NT 4.0 fileUser Profile Planning and Implementation To change encoded User Profile information There are three methods to correct this 3. Delete the network connection and reconnect Working Around Slow Network LinksCreating a New Roaming User Profile for Windows NT CREATING AND MAINTAINING USER PROFILESTo create a new roaming user profile e Continue to Step ∙ To copy a template profile manually to a number of users ∙ To copy an existing user’s profile to another user14 Microsoft Windows NT Server White Paper Creating a New Mandatory User Profile for Windows NT To create a new mandatory User Profilecalled TemplateUser 16 Microsoft Windows NT Server White PaperMaking a Roaming Profile Mandatory in Windows NT pdm, and will check again Creating a New Roaming User Profile for a Windows 95 User Maintaining User Profiles with Control Panel System Properties Creating a New Mandatory User Profile for WindowsTo create a mandatory user profile for a Windows 95 user Deleting Profiles c\\computername See the Windows NT Server Resource Kit for more informationddays Valid profile types are will open to the profile directory used by that account Viewing the Contents of the Profiles Directory on a Local Computer The All Users Shared Profile Log Files Used by Profiles26 Microsoft Windows NT Server White Paper Profile Names and Storage in the Registry Default User Template Profilessystemroot%\Profiles\All Users\Start Menu\Programs Manually Administering a User Profile through the Registry \%systemroot%\Profiles\Default User\Desktop process. For this reason, we recommend that you use the user name30 Microsoft Windows NT Server White Paper 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 Sample Log SYSTEM POLICY - AN INTRODUCTION System Policy FilesPolicy Replication How Policies Are AppliedAdditional Implementation Considerations ∙ What type of restrictions do you want to impose on users? Installing the System Policy Editor on a Windows 95 Computer Installing the System Policy Editor on a Windows NT WorkstationTHE SYSTEM POLICY EDITOR To install the System Policy Editor from a Windows NT 4.0 Server Updating the Registry with the System Policy EditorSystem Policy Editor Template .Adm Files Your Own Custom .Adm File,”later in this document Creating a System Policy tem Policy Editor Creating Alternate Folder Paths Deploying Policies for Windows NT 4.0 Machines Deploying Policies for Windows 95 Machines 3. In the Update mode box, select Manual use specific pathModifying Policy Settings on Stand-Alone Workstations Creating a Custom .Adm File KEYNAME System\CurrentControlSet\Services\ LanManServer\Parameters 3. Choose the CLASS in which you want your custom entries to appearwould use To close the category after filling in the options, you would useChecked REGDWORD with a value of PART !!MyPolicy NUMERIC DEFAULT VALUENAME ValueToBeChanged END PART PART !!MyPolicy EDITTEXT EXPANDABLETEXT VALUENAME ValueToBeChangedMAXLEN 4 END PART VALUENAME ValueToBeChanged VALUEON “Turned On” VALUEOFF “Turned Off”Building Fault Tolerance for Custom Shared Folders Configuring System Policies Based on Geographic LocationClearing the Documents Available List 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 \\Dfsserver\Dfsshare\Customfolder, will be returned a response with three dif- ferent servers, \\Server1\Customerfolder, \\Server2\Customerfolder, and \\Server3\Customerfolder, all of which contain the same data. The client ma- chine, which can be either a Windows NT-based 4.0 machine or a REGISTRY KEYS MODIFIED BY THE SYSTEM POLICY EDITOR DEFAULT TEMPLATES Default User SettingsControl Panel Display Application WallpaperStart Menu Run Command Settings FoldersColor Scheme can start unauthorized applications. To further restrict theStart Menu Find Command Settings Taskbar56 Microsoft Windows NT Server White Paper My Computer Drive Icons Network Neighborhood IconNetwork Neighborhood Display NoDrivesNetwork Neighborhood Workgroup Contents Start Menu Shut Down CommandDesktop Display 58 Microsoft Windows NT Server White Paperremove the user’s name from the “Shut down the system” Saved SettingsRegistry Editing Tools Windows Applications Restrictions 60 Microsoft Windows NT Server White PaperCustom Programs user selects Programs from the Start menu. The user’sCustom Desktop Icons playing the folders, files, and shortcuts the user receivesCustom Network Neighborhood Custom Startup Folder62 Microsoft Windows NT Server White Paper Custom Start Menu Shell ExtensionsDisables the display of common groups when the user Explorer File MenuRemoves the File option from Explorer’s toolbar. This Start Menu Common Program GroupsNetwork Connections Explorer Context MenuRemove the Map Network Drive and Disconnect Net When enabled, link file tracking uses the configured path When this value is 1, the environment variables declaredshown in properties for the shortcut to an application in Determines whether the shell waits for the logon script toEnables or disables the user’s ability to start Task Man when the user logs on for the first and second time. Thisgroup are started. If this value is also set in the Computer Task ManagerRemote Update Default Computer SettingsCommunities Category SubcategorySelection Permitted managersWhen enabled, creates administrative shares for physical Run CommandDrive Shares - Workstation ministrators the ability to control this feature. This setting Drive Shares - Serverphysical drives. These shares were created automatically Printer Browse ThreadError Beep Enables beeping every 10 seconds when a remote jobAuthentication Retries Authentication Time LimitSelectionWait interval for callback SelectionAuto disconnectRAS Call-back Interval RAS Auto-disconnectShared Programs Folder Path Shared Desktop Icons PathShared Start Menu Path 74 Microsoft Windows NT Server White PaperShared Startup Folder Path Logon BannerEnable shutdown from Authentication dialog box Enables or disables the Shut Down button on the logonname when the user presses CTRL+ALT+DEL and the Before the user logs on, displays a custom dialog boxCategory Read Only Files - Last Access Time Do not update last access timeFor files that are only to be read, specifies do not update Cached Roaming ProfilesSelectionSlow network connection timeout SelectionTimeout for dialog boxesSlow Network Timeout Dialog Box Timeoutonds in hexadecimal. Decimal = 0-600 default = ShowREGDWORD Off = 0 or value is removed On = time in sec 80 Microsoft Windows NT Server White PaperAutorun REGISTRY ENTRIES NOT INCLUDED IN THE SYSTEM POLICY EDITORStart Banner 0 = enabled 1= disabled Registry ValueRegistry Data DescriptionFOR MORE INFORMATION User Profile Flowcharts APPENDIX A - FLOWCHARTS84 Microsoft Windows NT Server White Paper Begin Profile Process Does the Flowchart 2. User Logon Part 86 Microsoft Windows NT Server White PaperContinued from Command to Load Profile Load the User Profile Apply System Policy Save settings to RegistryFlowchart 3. User Logon Part Set USERPROFILE environment variable Check build number for versionFlowchart 4. User Logon - Accessing Server-based Profile 88 Microsoft Windows NT Server White PaperSystem Policy Flowchart APPENDIX B - IMPLEMENTING USER PROFILES Existing Windows NT 3.5x Roaming Profile∙ User action To automatically upgrade the profile, log on to the 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 Updating and Changing a Roaming Profile to a Mandatory Profile92 Microsoft Windows NT Server White Paper Important Information for Administrators Recent Updates to Profiles Since Retail ReleaseAPPENDIX C - USAGE NOTES Regarding User Logons and User LogoffsRecent Updates to Policies Since Retail Release 94 Microsoft Windows NT Server White PaperProfiles APPENDIX D - RELATED KNOWLEDGE BASE ARTICLESPolicies Windows NT 4.0 Policy Restriction Error at Logon Cannot Restore Default Setting for Shutdown ButtonQ156432 Q155956