Error: The Credentials Supplied Conflict with an Existing Set of Credentials (197987)


The information in this article applies to:

  • Microsoft Windows 2000 Professional
  • Microsoft Windows NT Workstation 4.0
This article was previously published under Q197987
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

When you log on to a domain using mandatory profiles and mapped network drives through a logon script, you may receive the following error message:
The credentials supplied conflict with an existing set of credentials.

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem, blank out the Username key in the registry for HKEY_CURRENT_USER\Network:
  1. Log on as an administrator at any workstation.
  2. Click Start, click Run, type regedt32, and then click OK.
  3. Select HKEY_USERS, but do not open.
  4. From the Registry menu, click Load Hive.
  5. This will bring up a Load Hive dialog box. Locate the Ntuser.dat file for the user with the errors. Select the Ntuser.dat and click Open. You may enter any string for the Key Name. Use TEST for ease of use pertaining to the remainder of this article.
  6. Locate the Username value under the following key in the registry:

    HKEY_USERS\TEST\Network\Username

  7. Delete the string for Username (leaving it blank is sufficient).
  8. Select the TEST hive that you previously loaded, click the Registry menu, and then click Unload Hive.
  9. Quit Registry Editor.

MORE INFORMATION

The following is an excerpt from page 32 of the "Guide to Microsoft Windows NT 4.0 Profiles and Policies" white paper: 
   Creating Profiles Without User-Specific Connections
   ---------------------------------------------------

   In some cases, you may want to create profiles that include
   preconfigured persistent connections. However, if you need to supply
   alternate credentials when you create the template profile, this can
   cause problems for users later when the profile is used. Information
   about persistent connections is stored in the registry location
   HKEY_CURRENT_USER\Network. This key has subkeys that list the persistent
   drive connections by drive letter. For each of these subkeys, there is a
   value of UserName. If alternate credentials must be supplied to make the
   connection, those credentials are also stored here. Note that this
   includes only the domain and user account name; the password is not
   included. When the user receives this profile and logs on, WindowsNT
   attempts to reconnect the drive, but the alternate credentials are sent
   rather than those of the logged on user. Note that if the UserName value
   contains a blank string, the credentials of the logged on user are sent
   (which is the desired behavior in this case).

   To avoid inadequate credentials or wrong credentials being sent, use one
   of the following approaches: Avoid having to supply alternate
   credentials when you create the Connections to network resources in the
   shared profile by granting the user creating the template profile
   sufficient permissions in advance. Before modifying the profile to be a
   mandatory profile, run a REGINI script that removes the credentials from
   the UserName value. Do not delete the value, only the string data.
This white paper is available at the following Microsoft Web site:

http://www.microsoft.com/ntserver/management/deployment/planguide/prof_policies.asp

Modification Type:MajorLast Reviewed:10/10/2003
Keywords:kbprb KB197987
©2003 Microsoft Corporation. All rights reserved.