Bringing you news, technical articles, and other useful content about Visual Studio ALM and Team Foundation Server
More videos »
Ran in to a situation a couple of days ago where i needed to log into a Team Foundation Server as a different user - and since Visual Studio/Team Explorer "remembers" your last credentials you don't have a chance to re-enter these credentials. This information is cached even after removing and re-adding the server in team explorer. Which begs the question - where is it cached?
Turns out we are relying on Windows to do this for us. To dump this cache all you need to do is go to control panel > User Accounts > Manage Your Network Passwords select the Team foundation Server and choose remove - viola! Next time you go into Team Explorer you will be prompted for a new set of credentials.
The new SkyDrive client also seems to "mess up" credential management for *hosted* TFS Server (tfspreview.com) -- if the SkyDrive client is connected under a different Windows Live ID than you use for tfspreview, you will lose the ability to connect to TFS preview through Visual Studio (confirmed 2010 and 2012) with error codes of TF31003 or TF30063. Richard F. wrote the problem up with a workaround here: blogs.blackmarble.co.uk/.../A-fix-for-my-failure-to-login-to-TFSpreviewcom-problems.aspx -- but hopefully the SkyDrive and/or ALM teams can get a fix in place in the near future!
Not sure from which Windows version/environment you took the screen shots, but just to point out that on Win7 Pro, which is the default in my software firm, the link is called "Manage your Credentials" and this opens the "Credential Manager".
From there, you get the "Windows Vault", which store the credentials as described above.
Grant Holliday also pointed out this can be done using "cmdkey [/list:servername]" from the command line.
This doesn't work if you use the online identity manager thing from visualstudio.com. None of my instances show up in the credentials manager.