Windows NT administration: what is User Manager for Domains primarily used for in a Windows NT domain environment?

Introduction / Context:
Windows NT distinguished between tools for account/group management and tools for machine membership and file permissions. “User Manager for Domains” was the central console for managing domain user and group accounts and their related properties such as logon scripts and profile paths. Identifying the correct administrative function avoids confusion with Server Manager and file system tools.

Given Data / Assumptions:

• Environment: classic Windows NT domains (PDC/BDC model).
• We focus on the role of “User Manager for Domains.”
• Other administrative tasks exist but are handled by different tools.

Concept / Approach:
User Manager for Domains manages domain accounts and their attributes. It does not join computers to a domain (that is done on the workstation/server itself or via Server Manager) and does not change NTFS ACLs (done in File Manager/Explorer or via command-line ACL tools). System policies are edited with “System Policy Editor,” not created by User Manager, although User Manager can store profile and script paths in account properties.

Step-by-Step Solution:

Verification / Alternative check:
In the user’s properties dialog, the “Logon script” and “Profile path” fields confirm this functionality.

Why Other Options Are Wrong:

Common Pitfalls:
Assuming one MMC/console does everything; NT split responsibilities among multiple tools.

Final Answer:
Assigning a logon script to a user or a group of users.