Incorrect Permissions Applied to Terminal Server Home Folders

Article translations Article translations
Article ID: 195934 - View products that this article applies to.
This article was previously published under Q195934
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


Incorrect default permissions are assigned when creating a unique Terminal Server home directory for multiple users using the following form:


User Manager (Musrmgr.exe) is the default account manager for all member servers and workstations at installation time. User Manager for Domains (Usrmgr.exe) is the default for all domain controllers at installation time. Usrmgr.exe is copied to all member servers and workstations when they join a domain to give administrators the same capability from any Windows NT system. Both versions allow the administrator to select multiple objects (users or groups) at one time and make various property changes that apply to those selected.

When running Windows Terminal Server, the Profile configuration dialog box in both versions of the utility allows the administrator to configure the home directory for Terminal Server users. When specifying the path, the variable %USERNAME% can be used to indicate the user name currently being processed. This is useful when selecting multiple users and each user must have his or her own home directory. If multiple users are selected and %USERNAME% is used, the default permissions assigned are incorrect when running Musrmgr.exe and the local path is selected or when running Usrmgr.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 is selected, the permissions applied should match the first set of permissions above.


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 the Microsoft 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.


Article ID: 195934 - Last Review: October 11, 2013 - Revision: 2.2
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB195934

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from