June 15, 2010 at 11:58 am
We moved our Team Foundation Server from one domain to another following Microsoft's instructions they have outlined. On the server, it also has a SQL Server 2005 instance for Team Foundation Server to use. However, after the fact, we've been running into little bugs here and there and I've found that everything appears to stem from the SQL Server security login still being linked to the old domain account. The server used to be on the DOMAIN.local domain and has been moved to the DOMAIN.com domain.
The problem is that the SQL login hasn't changed as part of the process. According to SQL, the login is DOMAIN\TFSService. We created the same account on the new domain as well. The problem appears to be that the SID is still pointing to the old domain's account with the same username.
How do I redirect this Login to be pointed to the correct account on the new domain?
June 15, 2010 at 12:18 pm
I think you need to drop and recreate the login if it did not transfer. Did the SQL Server host get moved OK? Is the service account set to a domain level account?
June 15, 2010 at 1:41 pm
That's what I was afraid of. When you say the host, I'm assuming you mean the server that SQL Server is running on. If that's the case, it did get moved over OK. The service account is a domain level account. When it's not fully qualified, the names are actually identical between the two domains (DOMAIN\TFSService). When they are fully qualified, they are different (DOMAIN.local\TFSService vs DOMAIN.com\TFSService).
I'm assuming the dropping of the login is really my only option then. It's never as easy as it seems.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply