This article was previously published under Q195934
This article has been archived. It is offered "as is" and will no longer be updated.
Incorrect default permissions are assigned when creating a unique TerminalServer home directory for multiple users using the following form:
User Manager (Musrmgr.exe) is the default account manager for all memberservers and workstations at installation time. User Manager for Domains(Usrmgr.exe) is the default for all domain controllers at installationtime. Usrmgr.exe is copied to all member servers and workstations when theyjoin a domain to give administrators the same capability from any WindowsNT system. Both versions allow the administrator to select multiple objects(users or groups) at one time and make various property changes that applyto those selected.
When running Windows Terminal Server, the Profile configuration dialog boxin both versions of the utility allows the administrator to configure thehome directory for Terminal Server users. When specifying the path, thevariable %USERNAME% can be used to indicate the user name currently beingprocessed. This is useful when selecting multiple users and each user musthave his or her own home directory. If multiple users are selected and%USERNAME% is used, the default permissions assigned are incorrect whenrunning Musrmgr.exe and the local path is selected or when runningUsrmgr.exe and a remote path is selected.
The default permissions are applied as:
Everyone - Full Control/Full Control System - Full Control/Full Control
The default permissions should be:
Administrator - Special Access (All) (Not Specified) SYSTEM - Full Control (All) (All) UserName - Full Control (All) (All)
NOTE: When running Musrmgr.exe on a member server and a remote path isselected, the permissions applied should match the first set of permissionsabove.
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.