Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: A domain user cannot access a TFS 2010 server after you migrate the user and their SID history to another domain

FIX: A domain user cannot access a TFS 2010 server after you migrate the user and their SID history to another domain

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You add a user to a domain (domain 1).
  • You add a Microsoft Visual Studio Team Foundation Server (TFS) 2010 server to a different domain (domain 2).

    Note Domain 2 trusts domain 1.
  • You add the user to the TFS server. The user can now access the TFS server.
  • You migrate the user and their security identifier (SID) history from domain 1 to domain 2.
In this scenario, the user can no longer use their domain 1 credentials to access the TFS server.

Note This occurs within 24 hours of the migration.

↑ Back to the top

Cause

This issue occurs because of a synchronization issue during the daily synchronization job on the TFS server. When this issue occurs, the TFS server marks the domain 1 user account as invalid.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To apply this hotfix, you must have Visual Studio Team Foundation Server 2010 Service Pack 1 installed on the computer.

Restart requirement

You may have to restart the computer after you install this hotfix if the affected files are being used during the installation. We recommend that you close all Microsoft Visual Studio 2010-related components before you install this hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported versions of Visual Studio Team Foundation Server 2010
File nameFile versionFile sizeDateTimePlatform
Microsoft.teamfoundation.admin.dll10.0.40219.43025,618,01626-Oct-20129:11x86
Microsoft.teamfoundation.build.server.dll10.0.40219.430445,54426-Oct-20129:11x86
Microsoft.teamfoundation.build.server.plugins.dll10.0.40219.43046,72026-Oct-20129:11x86
Microsoft.teamfoundation.framework.server.dll10.0.40219.4301,103,47226-Oct-20129:11x86
Microsoft.teamfoundation.server.deploy.tfcollection.dll10.0.40219.430562,31226-Oct-20129:11x86
Microsoft.teamfoundation.server.dll10.0.40219.430221,79226-Oct-20129:11x86
Microsoft.teamfoundation.servicing.dll10.0.40219.43066,66426-Oct-20129:11x86
Microsoft.teamfoundation.testmanagement.adapter.dll10.0.40219.43093,82426-Oct-20129:11x86
Microsoft.teamfoundation.versioncontrol.server.dll10.0.40219.430618,11226-Oct-20129:11x86
Microsoft.teamfoundation.versioncontrol.server.plugins.dll10.0.40219.43026,76826-Oct-20129:11x86
Microsoft.teamfoundation.versioncontrol.server.proxy.dll10.0.40219.43090,24826-Oct-20129:11x86
Microsoft.teamfoundation.warehouse.dll10.0.40219.4303,526,76026-Oct-20129:11x86
Microsoft.teamfoundation.workitemtracking.server.dataaccesslayer.dll10.0.40219.430589,99226-Oct-20129:11x86
Microsoft.teamfoundation.workitemtracking.server.dataservices.dll10.0.40219.430143,52026-Oct-20129:11x86

↑ Back to the top

Workaround

To work around this issue, replace the domain 1 identity with the domain 2 identity within the TFS server, and then access the TFS server by using the domain 2 credentials. To do this, type the following command at a command prompt:
TFSConfig Identities /change /fromdomain:domain1 /todomain:domain2 /account:AccountName /toaccount:AccountName
Note If the domain 1 identity only had access to the TFS server through Windows group membership, the TFS administrator may have to grant access to the domain 2 identity.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information about the Identities command, go to the following MSDN website:
General information about the Identities command

↑ Back to the top

Keywords: kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, kbhotfixdev, kb

↑ Back to the top

Article Info
Article ID : 2741905
Revision : 1
Created on : 1/7/2017
Published on : 11/27/2012
Exists online : False
Views : 291