TFSAdmin Forum Rss Feed

New Post: Does this tool support SharePoint 2013?

mskold — Sun, 14 Apr 2013 09:11:15 GMT

Hi Leo
Please note that SP2013 still supports Classic authentication, but you can only configure it through PowerShell, not from the UI.
For more info abou sp2013 authentication, please refer to http://technet.microsoft.com/en-us/library/jj219571.aspx

New Post: Does this tool support SharePoint 2013?

lgrin7654321 — Sat, 13 Apr 2013 21:55:11 GMT

Hi gholliday,

One thing to keep in mind is that it seems that SharePoint 2013 supports ONLY claims-based authentication now. The way to Tool is now, it doesn create a permissions entry in SharePoint for classic-mode (Windows domain) authentication, but that entry doesn't grant the rights to SharePoint that it says (so if you use the Tool to give someone Full Control of a SharePoint portal, there is a classic-mode entry in SharePoint permissions that says "Full Control," but the user will get denied when they try anything on the portal.)

So I think that for SharePoint 2013, you not only have to support claims-based authentication, but you have to make sure the Tool never tries to grant classic-mode authentication as it does now. This is only for SharePoint 2013 -- TFS 2012 seems to support both modes, as you noted.

What I don't get is, if SharePoint doesn't allow classic-mode authentication anymore, why does it still let the tool create those entries in SharePoint permissions? Probably a bug that Microsoft needs to fix.

Leo

New Post: Does this tool support SharePoint 2013?

gholliday — Tue, 09 Apr 2013 23:46:38 GMT

Thanks for the detailed issue report.

I've had confirmation that TFS2012 and SharePoint 2013 in claims-based authentication mode is a supported configuration (* see below), so we'll make sure support for claims-based identities gets added to the TFSAdmin tool in a future release.

The TFS docs for sharepoint say that “NTLM is the recommended authentication”, but don't explicitly rule-out claims-based authentication.
http://msdn.microsoft.com/en-us/library/vstudio/dd578615.aspx
http://msdn.microsoft.com/en-us/library/vstudio/hh667648.aspx

The TFS / Project Server Integration docs explicitly call it out as not supported, but it’s not clear whether that applies ONLY when integrating with TFS/Project Server
http://msdn.microsoft.com/en-us/library/vstudio/hh674251.aspx

New Post: Does this tool support SharePoint 2013?

lgrin7654321 — Tue, 09 Apr 2013 00:15:12 GMT

Hi tjanders,

We were also having this issue, so I did some research.

Turns out that SharePoint 2013 only supports Claims-based authentication (the "i:0#.w|" prefix denotes this mode of authentication). So only by granting rights directly in SharePoint (and verifying that you have the "i:0#.w|" prefix) can you get the new rights to work.

The TFS Administration Tool, on the other hand, grants rights using Classic mode Authentication (windows domain\user), which has been deprecated in SharePoint 2013. So until the Tool is updated to administer SharePoint rights using claims-based authentication, it won't work for SharePoint 2013 (and furthermore, you'll have duplicate entries for users in SharePoint permissions, one entry being for Claims-based authentication, and another for Classic mode authentication).

Here are some links that help explain this:

http://sharepointengineer.blogspot.com/2012/10/i0w-claims-or-classic-authentication.html#!/2012/10/i0w-claims-or-classic-authentication.html
(explains the meaning of the "i:0#.w|" prefix.)

http://technet.microsoft.com/en-us/library/jj906556.aspx
Key line: “The most common reason for failed authorization when you are using Security Assertion Markup Language (SAML) claims-based authentication is that the permissions were assigned to a user's Windows-based account (domain\user) instead of the user's SAML identity claim.”

http://extreme-sharepoint.com/2013/03/07/claims-based-authentication/
Key text: The latest version of SharePoint – SP 2013 – supports only Claims based Authentication. From Central Admin, when you create a web application, you can only specify authentication types and methods for claims-based authentication ( See below screenshot). [Note: Windows Classic mode authentication is deprecated in SharePoint 2013 and can be configured through Windows PowerShell only if needed. However, it is not recommended practice. ]

Hope this helps.

Leo

New Post: Does this tool support SharePoint 2013?

tjanders — Thu, 21 Feb 2013 18:03:16 GMT

We are currently running TFS 2012 with SharePoint 2013 database version 15.0.4420.1017. When using the TFS Admin Tool version 2.2 to grant SharePoint permissions, the permissions do not work properly after they are committed. The users are added to the SharePoint portal site with the permissions specified in the TFS Admin Tool, but the user permissions are not respected by SharePoint. In other words, the users are listed in SharePoint Site Permissions with "Full Control", but running "Check Permissions" for that user results in "None". The users added by the TFS Admin Tool have the account format <Domain>\<UserName>.

Granting the permissions directly from the Site Permissions page in SharePoint allows the permissions to work, but creates a second user of the same name with a different account. The users created by SharePoint have the account format i:0#.w|<Domain>\<UserName>.

What is the "i:0#.w|" prefix added by SharePoint, and is this a bug in the TFS Admin Tool for not adding the same thing, or some quirk about SharePoint I don't fully understand?

New Post: Can't connect to sharepoint site

gholliday — Thu, 13 Dec 2012 04:42:09 GMT

Looks like it could be a caching issue.

Try closing all copies of VS, Excel and anything else that uses the TFS OM on your machine. Then delete the following directory: %localappdata%\Microsoft\Team Foundation\

This will delete the local cache of registration data, and force the TFS Admin tool to get new data.

(According to this thread http://tfsadmin.codeplex.com/discussions/208827)

New Post: Can't connect to sharepoint site

jefflevinson — Wed, 12 Dec 2012 23:31:38 GMT

I'm getting a lot of problems with the tool coming back and saying there is no sharepoint site associated with a team project when there clearly is (i.e. you can select Project Portal from Team Explorer and it opens up just fine).

New Post: Migrating User Accounts from one to domain to another domain

montch — Fri, 30 Nov 2012 20:14:37 GMT

Did you happen to find a way to migrate your SSRS users?

Thanks, Christopher

New Post: TFS admin tool 2.1 compatibility with tfs 2012

gholliday — Sun, 25 Nov 2012 01:38:57 GMT

I've just released v2.2 which supports installing on a machine with Team Explorer 2012 and working against a TFS2012 server.

http://tfsadmin.codeplex.com/releases/view/98222

New Post: Update for TFS 2012?

gholliday — Sun, 25 Nov 2012 01:38:05 GMT

I've just released v2.2 which adds support for TFS2012.

http://tfsadmin.codeplex.com/releases/view/98222

New Post: Unable to Commit SharePoint Changes

ericrwood — Wed, 14 Nov 2012 21:13:50 GMT

Ok, I figured this one out. It had to do with how permissions were being managed by individual SharePoint project portals. It worked for some of my projects and not others. I thought something changed that fixed it, but oh no. Some of my SharePoint project have permissions managed at the parent level and inherit. This tool does not like that. You can remove the inheritance by going to the Visual Studio Team Explorer. Right click and select "Show project portal". Go all the way to the right and select site-actions-> site-settings. In advance permission, select action-> edit permissions. It will throw up a dialog warning about changing permissions. In my case I could ignore. Judge for yourself. All of the user that were at the parent level will now have the parent level permissions at the site level. You can now use the admin tool to adjust. It will not show everyone as it seem like the display is driven from the TFS project level. You can remove the unnecessary folks at the sharepoint advance permissions if necessary.

New Post: Update for TFS 2012?

mlhoop — Thu, 25 Oct 2012 14:19:25 GMT

Is the tool being updated for TFS 2012? I don't see any announcements.

New Post: All Options Greyed Out in TFS Admin Tool 2.1 once connected to TFS Server

alexvaccaro — Wed, 17 Oct 2012 16:01:07 GMT

That worked, thanks. I would have never have guessed...

New Post: All Options Greyed Out in TFS Admin Tool 2.1 once connected to TFS Server

Mozleron — Wed, 17 Oct 2012 15:36:06 GMT

In my case, it would seem the issue was rather simple. Once connected, i had to double click on the collection of interest on the left side in order to get the options to show up on the right. Seems like a little bit of a UI issue there that could be resolved by moving that event to a single click, though there might be a good reason to do it on the double.

New Post: All Options Greyed Out in TFS Admin Tool 2.1 once connected to TFS Server

alexvaccaro — Wed, 17 Oct 2012 14:14:44 GMT

Same here. Did anyone got a reply on how to solve this issue?

New Post: Unable to Commit SharePoint Changes

ericrwood — Mon, 15 Oct 2012 18:04:33 GMT

All pending changes to SharePoint fail with:

It will successfully commit changes to both TFS and the Reporting Services. This was working last week so I'm note sure what changed. Saw another thread noting this problem but no resolution. Any idea what could be wrong. I'm not even sure what SharePoint services to restart to try and resolve.

Eric

10/15/2012 2:02:32 PM: Button clicked: Pending Changes COMMIT10/15/2012 2:02:32 PM: Exception occurred Type: System.Web.Services.Protocols.SoapException Message: Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown. InnerException: - Source: System.Web.Services Target: System.Object[] ReadResponse(System.Web.Services.Protocols.SoapClientMessage, System.Net.WebResponse, System.IO.Stream, Boolean) Stacktrace: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at TFSAdministrationTool.Proxy.SharePoint.UserGroup.AddUserToRole(String roleName, String userName, String userLoginName, String userEmail, String userNotes) in D:\Work\TFSAdmin\Main\src\TFSAdministrationTool.Proxy\Web References\SharePoint\Reference.cs:line 553 at TFSAdministrationTool.Proxy.SharePointProxy.AddUserToRole(String userName, String role, String displayName, String email, String description) in D:\Work\TFSAdmin\Main\src\TFSAdministrationTool.Proxy\SharePointProxy.cs:line 83 at TFSAdministrationTool.Proxy.TeamFoundationServerProxy.SharePointAddUserToRole(String teamProject, String userName, String role) in D:\Work\TFSAdmin\Main\src\TFSAdministrationTool.Proxy\TeamFoundationServerProxy.cs:line 657 at TFSAdministrationTool.Controllers.MainController.OnCommitChange(PendingChange pc) in D:\Work\TFSAdmin\Main\src\TFSAdministrationTool\Controllers\MainController.cs:line 109

New Post: TFS admin tool 2.1 compatibility with tfs 2012

bpmerkel — Thu, 20 Sep 2012 12:56:41 GMT

I am getting an exception using Add User(s)->Browse after installing VS2012. From the Output panel:

9/20/2012 8:52:16 AM: Button clicked: User Configuration BROWSE
9/20/2012 8:52:16 AM: Exception occurred
                       Type: System.ArgumentException
                       Message: Object of type 'Microsoft.TeamFoundation.Framework.Client.IdentityManagementService' cannot be converted to type 'Microsoft.TeamFoundation.Framework.Client.IIdentityManagementService'.
                       InnerException: -
                       Source: mscorlib
                       Target: System.Object TryChangeType(System.Object, System.Reflection.Binder, System.Globalization.CultureInfo, Boolean)
                       Stacktrace:    at System.RuntimeType.TryChangeType(Object value, Binder binder, CultureInfo culture, Boolean needsSpecialCast)
   at System.RuntimeType.CheckValue(Object value, Binder binder, CultureInfo culture, BindingFlags invokeAttr)
   at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig)
   at System.Reflection.RuntimeMethodInfo.InvokeArgumentsCheck(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at TFSAdministrationTool.Proxy.TeamFoundationServerProxy.ShowAddGroupControl(IWin32Window parentWin)
9/20/2012 8:52:19 AM: Button clicked: User Configuration CANCEL

New Post: TFS admin tool 2.1 compatibility with tfs 2012

wjanssens — Thu, 13 Sep 2012 06:46:10 GMT

I haven't countered any issues but I would like the suggestion of Richard (rhundhausen) to include the concept of team's in the tool.

New Post: TFS admin tool 2.1 compatibility with tfs 2012

felickz — Wed, 12 Sep 2012 18:53:05 GMT

i'll second that ... "Are there any known issues?"

New Post: TFS Admin Tool says "SharePoint Status unavailable"

Mozleron — Tue, 14 Aug 2012 22:46:56 GMT

I have just experienced this same issue on Windows 7 with TFS 2010, SharePoint 2010, VS 2010 and TFS Admin tool 2.1.31204.0.

I solved it by going into the Cache directory mentioned by enrigrossi and deleted the most recent of the <GUID>_http directories.