Hello,
Win 8.1, VS2013, TFS2013, Server2012 Standard
I'm writing this post more as providing feedback in case it's useful, and also to eventually be able to transition to update 4, but for now I've had to fallback to update 3 so I can continue to work unhindered.
The context: I was running all the above on a PC that due to a minor display failure ending up having to be replaced with an entirely new unit (long story made short). The setup was a Win 8.1 host with 3 VM's; one the domain controller, one a TFS, and a build server done primarily for the experience of it. I made no changes to the new unit's OS and simply moved data over and installed all my applications on the new PC. This was the first time I had moved VM's, but in the end the export and import seemed to go smoothly. Unwisely I installed VS2013 update 4 during this changeover; I say unwise because I was changing more than one thing at the same time. That's not a complaint about VS updates - I think they're great. Thanks for them!
The problem: When VS on the new PC wouldn't connect to TFS I wasn't sure if it was a program problem or my transfer technique. Some of my research indicated the client TFS cache might need to be cleared if I had connected to 2 different TFS installations from the same VS client. I thought that might be my problem as I had been going back and forth between the old TFS location and the new one during testing, so I cleared the cache and it seemed to work; but only for a while. After struggling with it, I uninstalled update 4 and reinstalled update 3. Update 3 connected to the moved TFS before I could even get my eyes back to the screen, where I had been waiting for long durations for update 4 to finally state TFS could not be contacted.
I had noticed a message in update 4 to contact Microsoft if there were long delays or problems bringing up update 4, so I decided to post here. If there is a better place I should have posted, please teach me and I'll move the post.
Thanks.
Best Regards,
Alan