Using tf.exe with TFS RTM running inside VPC
I have TFS RTM running inside VPC (computer "A"). The VPC is running on computer "B", joined to domain. I would like to access TFS both with Team Explorer and tf.exe from computer "C" joined to the same domain.
Team Explorer works well, because of authorization window pops up when I connect server. The pop-up window allows me to use default computer's "A" local user credentials instead of my real one on "C". But when I'm trying to use tf.exe - it says that I'm not authorized to access the server.
I guess that problems happens because of tf.exe uses my real credentials from "C" when accessing TFS.
I see only two solutions for that:
1. Add "A" computer to my domain, grant permissions for my domain user to access TFS.
2. Make tf.exe to use "A" local user when accessing TFS
I could not do 1, when I try to add "A" to domain it says that it failed to do something with RPC. And I don't know how to perform 2.
Thanks for any help in advance.
Re: #1 - VPC machines should join to the domain fine - we do it all the time. Make sure your normal networking is working fine. A web search on "join domain rpc error" shows a bunch of possible explanations. I think this would be better as you could skip the credentials dialog (assuming you added the domain users). However, there would be some additional pain to set this up since you'd have to switch the TFS service account to a domain user, as we would need to run as a user that could query the domain for user information.
Re: #2 - tf.exe has a /login option, so you can do tf command /login:user (we'll prompt for the credentials) or /login:user,pass to pass those credentials.
Now, *normally* if you're doing a tf command on a server you don't have access to, you get a credentials prompt (after getting the TF30063 error). We only skip that credentials prompt if you're in "noprompt mode" - either you passed /i or /noprompt, or you're doing something (like redirecting the command) so we put ourselves into noprompt mode. I'm assuming one of those are the case since this didn't "Just Work" and it sounds like you didn't get prompted for your "machine A" credentials.
