Comments for Brian Harry's bloghttps://blogs.msdn.microsoft.com/bharry
Everything you want to know about Visual Studio ALM and FarmingFri, 09 Dec 2016 23:14:12 +0000hourly1Comment on News from Connect(); 2016 by RAJESH RAMAMURTHYhttps://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-245395
Fri, 09 Dec 2016 23:14:12 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-245395@FM: Could you reach out to me at rajr@microsoft.com? The issue you mentioned could be due to the team foundation administrators group missing membership in project administrators group. I want to see if the upgrade caused this.
]]>Comment on News from Connect(); 2016 by FMhttps://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-245215
Fri, 09 Dec 2016 16:14:40 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-245215We did some migration tests from TFS 2015 Update 3 to TFS 2017 RTM and noticed one permission issue: Although the user is a member of [Team Foundation]\Team Foundation Administrators he gets a “permission denied” error when trying to add a user to a group within the team project. Only when the user is a direct member of [Team Project]\Project Administrators it seems to work.
]]>Comment on News from Connect(); 2016 by Taylor Lafrinere (MSFT)https://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-245185
Fri, 09 Dec 2016 15:11:27 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-245185@Frank: The latest shipped version of the Windows Shell Extension will continue to work against TFS 2017. We just won’t be rereleasing it. Feel free to reach out to me at taylaf@microsoft.com if you have any questions.
]]>Comment on News from Connect(); 2016 by Frankhttps://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-245135
Fri, 09 Dec 2016 13:44:16 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-245135As there will we be no TFS Powertools 2017 – what happens to the Windows Explorer Shell Extensions for TFS Source Code Operations?
]]>Comment on News from Connect(); 2016 by Will Lennon - MSFThttps://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-244585
Thu, 08 Dec 2016 15:39:34 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-244585@Nathan Overbey
Regarding your TFVC workspace issues, can you please contact me directly at wlennon@microsoft.com? I’d like to learn more about this issue.
]]>Comment on News from Connect(); 2016 by Nathan Ovhttps://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-244035
Wed, 07 Dec 2016 21:10:10 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-244035I found that the issue with the workspaces seems mostly isolated to VS2010 client. Thought I went mention this in case someone else runs across this
]]>Comment on News from Connect(); 2016 by Aaron Hallberghttps://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-243875
Wed, 07 Dec 2016 16:59:24 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-243875@Daniel_Steiner – a quick clarification: TFS 2017 is not using Kerberos authentication by default. It is using the Negotiate security support provider by default, which will use Kerberos if it can and will otherwise fall back to NTLM. We also left the NTLM security support provider enabled to ensure that clients which cannot handle the Negotiate provider will still work without any changes. We did extensive testing on this change to confirm that there should be no impact to existing customers. If you are seeing impacts, please let us know. You should *not* need to remove the Negotiate provider from the TFS website.

1. The URL you are using for your connection in VS. Perhaps you have a typo somewhere?
2. The identity you are using to connect to TFS. Is it the same one you used to configure your server? If not, did you add that identity to a group and/or give it permissions to the server?

Hope that helps and that you are up and running soon.

Thanks,
Aaron

]]>Comment on News from Connect(); 2016 by Brian Harry MShttps://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-243815
Wed, 07 Dec 2016 15:36:28 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-243815@DS19, Perfect. That’s one of the common causes of what you were seeing.

Brian

]]>Comment on News from Connect(); 2016 by DS19https://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-243795
Wed, 07 Dec 2016 15:03:53 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-243795@Brian
Thank you; you pointed me in the right direction; I deleted the server cache (Application Tier\Web Services\_tfs_data) and it’s ok now.
]]>Comment on News from Connect(); 2016 by Nathan Overbeyhttps://blogs.msdn.microsoft.com/bharry/2016/11/16/news-from-connect-2016/#comment-243775
Wed, 07 Dec 2016 14:51:34 +0000https://blogs.msdn.microsoft.com/bharry/?p=12385#comment-243775@Brian, hello, I’m a long time listener first time caller. I’ve hit a few snags with our builds post 2017 upgrade. First issue I ran into was the existing xaml builds were not working, received a access error (we had over a hundred of these builds). I was unable to install a 2015 controller. It would not get past username password authentication test. I gave up on that and spent a couple of days porting all those xaml builds to new format, so I’m past that but thought I would mention it as I suspect they’re may be future folks in a similar position.

However, I’m running into a new issue now with workspaces. It seems that for some existing workspaces, individuals are unable to create a new mapping for a existing workspace, receiving error access denied. We’ve tried to delete these workspaces and recreate using the same path but different user, but it doesn’t seem to completely remove the old workspace as we get error that path is already exists in the workspace that we just deleted.

I’ve been seeing several access errors, instead of listing the username in question it will list the guid?