NET LOCALGROUP /ADD Command Is Slow (101711)
The information in this article applies to:
- Microsoft Windows NT Server 3.1
- Microsoft Windows NT Workstation 3.1
This article was previously published under Q101711 SUMMARY
You may experience some time delay when using
net localgroup <local group name> <user or global group name> /add
to add a user or global group to a local group if the user or global
group is not present on the local machine, but instead resides in a
domain that is trusted directly or indirectly by the local machine. In
the case of a Windows NT system that belongs to a domain, the user or
global group may belong to that domain or one of its trusted domains.
With Windows NT Advanced Server (the primary or backup controller of a
domain), the user or global group may belong to one of the domains
trusted by that domain.
To minimize such a delay, specify the fully qualified name of the user
or global group (<DomainName>\<UserName> for example) as opposed to
the unqualified form, <UserName>.
The time delay occurs because the security identification (SID) of the
user or global group has to be found. This operation in turn requires
the computer name for an active primary or backup domain controller
for the user's domain to be found, a process known as discovery of the
domain controller. The discovery process can vary in the time it takes
to complete, depending upon whether a cached computer name is
available for the specified domain.
| Modification Type: | Major | Last Reviewed: | 10/28/2003 |
|---|
| Keywords: | kbnetwork KB101711 |
|---|
|