Previous Page | Next Page

  1. Introduction
  2. Installation
  3. Hardware Issues
  4. Filesystems
  5. Networking
  6. Security
  7. Servers
  8. Services
  9. Utilities
  10. Control Panel
  11. Printing
  12. Performance Monitor
  13. Network Monitor
  14. Event Viewer
  15. Other Issues
  16. User Accounts
  17. Groups
  18. Policies
  19. User Rights
  20. Auditing
  21. System Policies
  22. Sharing
  23. Profiles
  24. Roaming Profiles
  25. Domains
  26. Server Management
  27. Directory Replication
  28. License Management
  29. Client Administrator
  30. Netware Tools
  31. Macintosh Support
  32. RAS Server
  33. SNMP
  34. DHCP
  35. DNS
  36. WINS
  37. Mail Service
  38. Internet
  39. Internet Information Server
  40. Routing and Firewalls
  41. Items to Remember
  42. Terms
  43. Credits

Windows NT Roaming User Profiles

Roaming profiles must be replicated to all domain controllers. If a user's profile is a mandatory profile, it must be available in order for the user to logon. Use UNC name to specify path for user roaming profile. Steps to create a roaming profile:

  1. Create a shared folder where the user profiles will be stored.
  2. Assign the user profile path - The "User Manager for Domains" tool is used to create roaming profiles for users. To create the profile, double click on the username and click the "Profile" button, then set the UNC path name to the profiles directory on the server you want profiles to be stored on.

It is a good policy to store user profiles on the file server. On the client machine, a roaming profile is created using the control panel "System" applet, "User Profiles" tab. A mandatory profile is made by changing the USERNAME.DAT file to USERNAME.MAN.

Copying Profiles

User profiles are copied using the control panel system applet, user profiles tab. To copy a profile, select the profile to copy by clicking on it, then click the "Copy To" button and enter the destination.

Drawbacks

Roaming profiles may not work well for your domain if your users logon using various computers that have different software configurations. For example, an application package may be installed in one directory on one computer and in another directory on another computer. Therefore the environment PATH variable may not be able to find the application when the user is using one of the two computers. However if a uniform network environment is set up, these drawbacks can be overcome. the guest account and accounts administrator cannot have roaming profiles.

System Policy Editor

The system policy editor can be used to override registry settings on client computers in the domain and customize user environment profiles. The following registry entries may be modified by the system policy editor:

  • Hkey_Current_User
  • Hkey_Local_Machine

The system policy editor can define domain system policy for all users and computers. This policy is stored on the PDC in the file:

\\PDC\Netlogin$

On Windows NT servers, the System Policy Editor is used to control user profile settings. The authenticating domain controller gets system policies from the file WINNT40\SYSTEM32\REPL\IMPORT\SCRIPTS\NTCONFIG.POL. Therefore to have policies replicated to all domain controllers, place the NTCONFIG.POL file in the directory WINNT40\SYSTEM32\REPL\EXPORT\SCRIPTS.

System Policy Template Files

  • COMMON.ADM - For NT and 95
  • WINNT.ADM - For NT
  • WINDOWS.ADM - For 95