SharePoint 2013 Remote Index with ADFS

I have two domains: A and B, each with its own SharePoint 2013 farm. I have established ADFS for the users and Farm trust as well. Users from domain A can access sites in Farm B, even when granted access through AD groups. I have also setup remote search
and search results from sites in Farm B appear in Farm A, but only if I grant permissions directly to the searching users. If not, the logs state access was denied and no remote results are returned. Any ideas?

Hi,
Please understand that Search requires windows authentication to be selected on at least one zone in the web application. If we only have ADFS configured currently, we will receive Access denied when crawl web application.
As workaround, we could extend the web application to one zone other than default zone, and configure windows authentication for that zone. Please refer to the detail step in the article below:
http://sharepointobservations.wordpress.com/2013/08/06/sharepoint-2013-configuring-search-to-crawl-web-applications-using-claims-and-adfs-2-0/
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

Similar Messages

SharePoint 2013 : Incoming Mail with NLB

I am trying to configure Incoming Email and I have (2) of each WFE & APP Servers
Based on Q&A link below
http://social.technet.microsoft.com/Forums/sharepoint/en-US/f9f1d254-0f9e-4eec-a1c7-a94252668680/sharepoint-2013-incoming-mail-with-nlb?forum=sharepointgeneral
Note that the SPLockJobType will be changed to Job in the December 2013 CU for load balancing purposes.
http://sharepoint.nauplius.net/2013/08/update-on-incoming-email-job-lock-type-change-between-sharepoint-2010-and-2013/
It is not recommended to run Incoming Email on more than one SharePoint 2013 server due to a synchronization issue Microsoft identified (hence the job lock type change).
My question: is the patch part of SharePoint Cumulative Update 15.0.4551.1511 - if not then I will apply it separately (do I apply to all the servers and would I have to run SharePoint Products and Configuration) ?
Thanks
Davinder

The patch is part of the December 2013 CU. You can use Incoming Email in a load balanced or high availability MX/SMTP routing given you have the Dec 2013 CU installed on SharePoint 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Backup Sharepoint 2013 SP1 Farm with SQL 2014 RTM "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 SP1 Farm with SQL 2014 RTM "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find information anywhere.
Regards,
Igor

This is a DPM supportability issue, I believe. Last I heard, no it was not supported. SharePoint 2013 does not support SQL 2014 until the April 2014 CU. The CU should be out soon, although it appears to have been delayed (usually comes out on Patch Tuesday,
which was this past Tuesday).
Trevor Seward
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How to properly create and configure SharePoint 2013 Search service with PowerShell?

Hello Forum,
I have installed SharePoint 2013 across three tier servers:
WFE Server (Of course, SharePoint is installed here. Bsically this is just a Web server)
APP Server (Of course, SharePoint is installed here + Central Admin + Service Apps).
SQL Server
I now want to create and configure the Search service, obviously on the APP Server, But of course the search functionality should work correctly on the WFE server to.
I want to do this via a proper PowerShell script. I found Spence Harbar's script on: (http://www.harbar.net/articles/sp2013mt.aspx), But it has three problems, and they are as follows:
1) Spence Harbar himself literally stated on his article that this script is for: "deploying on a single server farm", But what if I have three tier servers? Could anyone please help me out in suggesting the required tweaks in the
script?
2) By default Search uses the SP_Farm account, So, How can I change the script to use other dedicated account for the search service e.g. SP_SearchAcc ?
3) How can I modify the script to specify a default Search center?
4) Apart from all the three aforementioned point - Is the script missing anything?
I would greatly appreciate your inputs - Thanks !

the only differences are where you place the components. if you are doing a small server farm with a 1-1-1, most likely you just need to change the script so that you set the index and query processing component on the front end, but the others on
the app server. just a 2 second update... just keep in mind this will work, but I am making several assumptions without any knowledge of your farm, users, capabilities.
generally, there would be more of a breakout on the topology than that, but im guessing for this farm that you wont have dedicated search servers. also, a lot depends on # users (rps really), # items in index, size of VMs (RAM for query processing,
Disk for index, etc, etc), and making sure the topology works for your particular environment and needs.
if you want more detailed topology help, which aligns as closely as possible to "best practices" (not that those exist in SharePoint, go ahead and provide the total # users, average/peak RPS for search, current index size, content source types,
VM specs RAM, CPU, #/Size of drives, HA concerns/priority (obviously isn't, since only 1-1-1)
Christopher Webb | MCM: SharePoint 2010 | MCSM: SharePoint Charter | MCT | http://christophermichaelwebb.com

Search SharePoint 2013 On-Prem with Office 365

We're trying to understand federated search in SharePoint 2013, when it comes to Office 365. We have both a SharePoint 2013 on-prem environment, and an Office 365 environment. The 2 are completely separate, and have not been configured to use a hybrid model.
Is it possible to configure a Result Source in either the SharePoint environment or the Office 365 environment to index the other? Reading this
article from Technet, it indicates that you can configure a remote SharePoint farm as a Result Source:
"Remote SharePoint provides
results from the index of a search service in another farm."
But I've read on another
thread on here that this is not possible from O365.
I'm hoping that someone can provide some guidance, or point me in the right direction.
Thanks,
cflbasser

Yes, you can receive search results from an on-premise SharePoint Server 2013 farm within SharePoint Online.
Hybrid search between SharePoint Server and SharePoint online uses federated search results. Neither the on-premise farm nor SPO crawl the other location, they just send a federated search query over the fence and wait for the results.
You can search in either direction (one-way hybrid search) or both ways (bidirectional hybrid search).
The one-way search can either be SharePoint Server sending search queries to SPO or SPO sending queries to SharePoint Server which also needs a reverse proxy for securely publishing your on-premise farm to SPO.
Bi-directional hybrid search just combines both one-way methods together so either location can receive search results from the other location.
Here are some further resources to help you plan and implement hybrid search:
Hybrid for SharePoint Server 2013
Configure hybrid Search for SharePoint Server 2013
Chris O'Brien has an excellent article that describes the actual search experience. Check out Office 365 SharePoint hybrid - what you
DO and DO NOT get
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Sharepoint 2013 SSRS Interaction with Sql Server 2012 Reporting Services connecting to Sql Server 2008 R2 database

Hi
I'm working on upgrading sharepoint 2010 to sharepoint 2013 with sql server 2008 r2. I've ran into some problems but have been able to get a test farm upgraded. However to run SSRS 2013 it seems Sql Server 2012 Reporting Services are required. Upgrading
to a full sql server 2012 database isn't an option. I know that sql server 2012 reporting services can use sql server 2008 r2 as a catalog and content database so I was wondering could this be a workaround? Importantly would I need a separate machine/virtual
machine to host sql server 2012 reporting services? or could it live on the sql server 2008 r2 machine? Any pointers appreciated. Thanks Dan

Remember that SSRS must be deployed on the SharePoint server. Having said that, yes you can install SSRS 2012 SP1 on a server running SQL 2008 R2. And yes, you can use 2008 R2 as your Database Engine server while SSRS 2012 SP1 runs on the SharePoint server.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint 2013 Environment Setup with minimum resource

Hi,
Could you please advise considering below scenario
- What would be the minimum resources in order to setup SP2013 Enterprise environment?
- If we want to buy a single server from DELL as a host for all virtual machines as below, what would be the configuration for that server?
- How much RAM do we need for the host?
- How much ram / processor core allocation do we need for the VMs.
Requirments:
USER: 500 Users
Features : All OOB features / Services will be used in SharePoint 2013 Farm
Web Application : 3 Web Application, 10 Site Collection
Total Content : 100 GB
Virtual Box for entire SP2013 Environment Setup:
- SQL Server 2012 Sp1 Enterprise
- SQL Clustering / Mirroring
- SP 2013 Application Server1 (Enterprise)
- SP Application Server2
- SP Application Server3
- SP Application Server4
- SP WFE 1
- SP WFE 2
- BI Server 1
- BI Server 2
- OWA Server 1
- OWA Server 2
- Workflow Manager 1
- Workflow Manager 2
- TMG Firewall 2010
- Exchange Server 2010
- Microsoft Lync Server 2010
Thanks
srabon

It's all here:
http://technet.microsoft.com/en-us/library/cc262485%28v=office.15%29.aspx
Putting that many servers together for a 500 seat company is madness. Go for the text book small farm deployment at most, in reality you'd probably be better off just having three servers total (1 WFE, 1 App, 1 SQL).
I can't remember how much you should reserve for the hypervisor but if you allocate 1GB for that i think you're ok.
For a three server deployment you'd probably be ok with 32GB, 8GB for the WFE and App server, 7GB for SQL and one for the hypervisor. 64GB would give you a lot more comfort.
If you want more options like the enhanced workflows and OWA you'd need servers for each of those as well.
You can always overprovision CPUs on the hypervisor but more than 12 Cores would be wasted on a 3 server deployment for 500 users.

SharePoint 2013 - Incoming email with smtp alias domain

Hi All
I have configured the following for SharePoint 2013 Incoming email.
CA - Incoming email - enabled
Automatic and received mail from all servers
email server display address:
[email protected]
smtp installed on one SharePoint server and configured with
defautl domain: spservername.domain.net and alias domain:
spmail.domainname.net
emails are receiced in SharePoint lists / library are working when incoming email settings using the default local smtp domain (spservername.domainname.net) but not working when using the alias domain (spmail.domainname.net).
Can anyone advice of what I have done wrong or missing in my configuration?
Thanks in advance for your comments or advices
Swanl

trevor
I tried that but that did not work. I got this error below. Does that mean I need to create a DNS MX record for spmail.domainname.net to point it to the smtp server
spservername.domain.net
Thanks
Xuan
Swanl
It looks like you have a DNS mis-configuration in this case with regards to how your MX record is configured (if it exists at all).
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SharePoint 2013 GetPermissionCollection() Asserts with 401: Unauthorized

Good afternoon all;
I am calling the GetPermissionCollection() web service function and passing in user credentials for a user with Full Control.
I get the same assert if I set UseDefaultCredentials to true.
The call is asserting with the following message: "The request failed with HTTP status 401: Unauthorized."
If I call the same web service function on a SharePoint 2010 server, the request does not assert.
I have looked at the permissions on SharePoint 2013 and don't see anything specific to this issue.
Let me know if I need to provide more info.

Hi,
According to your post, my understanding is that you want to use GetPermissionCollection() but get 401: Unauthorized error.
Please make sure you at least have full control permission.
The issue should be caused by that the client application is not the same domain with the SharePoint farm, or the credential passed is invalid.
Here is a similar thread for your reference:
http://social.technet.microsoft.com/Forums/office/en-US/14740b0b-29f8-4742-8631-9bdcd93db4bc/permissionsgetpermissioncollection-throws-the-request-failed-with-http-status-401-unauthorized?forum=sharepointgeneralprevious
In addition, this indicates that Anonymous access has been disabled for the Webservice.
We can resolve this issue by either of the following ways:
1. Enabling Anonymous Access in the IIS Directory Security
2. Programattically assigning the Credential Cache
More information:
ASP.NET Webservices: "The request failed with HTTP status 401: Access Denied." Error
Thanks,
Linda Li
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Linda Li
TechNet Community Support

Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Team,
I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp. However, we have a coexistence environment with exchange 2007. When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
mailbox is still within exchange 2007, you get a blank login page. If you mailbox is in exchange 2013 then you successfully get the owa page for 2013. The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed. Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
the much needed mailbox lookup for a coexistance environment? A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.

Hi,
Try using AD FS claims-based authentication with Outlook Web App and EAC
http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Sharepoint 2013 - url redirects with port number added

Hi,
In our sharepoint 2013 environment, we have a custom application and in which we have a button and when we click on the button the initial url was below
http://abcd.com/apps/xyz/test.aspx
After clickin on the button it redirects to the below, where in the custom app they are using query string to append the url.
http://abcd.com:6001/apps/xyz/test.aspx?EID=7&ListID=1723aasd-ajsfs12346
And i am getting the web page cannot be displayed error.
Please help me to resolve this issue. Is there any issue in the custom code or in IIS redirect or server related configuration.
Any help is much appreciated.

Hi Krishna,
Thanks for your reply,
We have constructed the code in .cs file. And the code is
private
void Redirect(int
id)
NameValueCollection queryString;
            queryString =
HttpUtility.ParseQueryString(Request.Url.Query);
            queryString["EID"]
= id.ToString();
            queryString["List"]
= List.ID.ToString();
            queryString.Remove("AssignToMe");
//Response.Redirect(Request.Path + "?" + queryString, true);
//Response.Redirect(SPContext.Current.Web.Url + "?" + queryString, true);
            Response.Redirect(SPContext.Current.Web.Url
+ "/Pages/Request.aspx" +
"?" + queryString,
true);
Smile Always

SharePoint 2013 REST API with C# - Mapping HTTP verbs to data operations - Requesting FormDigest

SharePoint REST interface maps HTTP verbs to data operations. Endpoints that represent
Read operations map to HTTP
GET commands. Endpoints that represent update operations map to HTTP
POST commands, and endpoints that represent update or insert operations map to HTTP
PUT commands (Ref:
How to: Complete basic operations using SharePoint 2013 REST endpoints).
Is this mapping of HTTP verbs to CRUD operations a design paradigm or whether there are other technical reasons to this mapping
Is is possible to use a GET command for say an update operation or a POST for say a read operation.If so, what consideration make the choice of either usage
In the code snippet below FormDigest is requested as POST, why not use GET here?
private static string GetFormDigest(string webUrl)
//Validate input
if (String.IsNullOrEmpty(webUrl) || String.IsNullOrWhiteSpace(webUrl))
return String.Empty;
//Create REST Request
Uri uri = new Uri(webUrl + "/_api/contextinfo");
HttpWebRequest restRequest = (HttpWebRequest)WebRequest.Create(uri);
restRequest.Credentials = CredentialCache.DefaultCredentials;
restRequest.Method = "POST";
restRequest.ContentLength = 0;
//Retrieve Response
HttpWebResponse restResponse = (HttpWebResponse)restRequest.GetResponse();
XDocument atomDoc = XDocument.Load(restResponse.GetResponseStream());
XNamespace d = "http://schemas.microsoft.com/ado/2007/08/dataservices";
//Extract Form Digest
return atomDoc.Descendants(d + "FormDigestValue").First().Value;
Thanks - Abhishek

Many SharePoint REST api methods use parameters. It is much more efficient to post parameters than use query string variables. Many times complex types are sent and these require json notation objects posted in the body. In the case of "_api/contextinfo,
it is recommended to use POST rather than a GET when using sensitive data. GET responses can be cached. Since you are getting a security token back in that call it is recommended to use a POST.
http://blog.teamtreehouse.com/the-definitive-guide-to-get-vs-post
Blog | SharePoint Field Notes Dev Tools |
SPFastDeploy | SPRemoteAPIExplorer

SharePoint 2013 - Choice Column with Fill-In enabled Not Editable in Datasheet View

I have a custom list with a choice column (check boxes) set to allow for fill-ins. Before it was migrated to 2013, I had a datasheet view and was able to edit the choice field by selecting one of the choices and/or add my own fill-in.
Now in 2013 that field is greyed out in datasheet view. However, all the other choice columns which are NOT set to allow for fill-ins are editable. I get all the choices with no problems. The problem seems to be with the choice
fields that is allowing for fill-ins. Why won't this work in datasheet view?

Hi Jenkins,
It is a by design behavior that the filled-in value doesn’t show up in the list view filter options.
As a workaround, you can create an extra Single Line of Text column which saves the duplicated value of that Choice column, then filter the text column instead.
About how to copy value of a Choice column to a text column, you can set up a SharePoint Designer workflow to do the copy job and update the item.
A demo about how to update list item in SharePoint Designer workflow:
http://www.documentmanagementworkflowinfo.com/workflow/use-update-list-item-action-sharepoint-designer-workflow.htm
Thanks
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SharePoint 2013 List View with query string filter stops working after editing view from browser

I have created one list definition in which I have added one list view which will filter data from query string paramater
So when I am creating list from my list definition, view with query string filter is working fine.
But when I am modifying view from UI(I am not changing any thing , just opening "Modify View" page and then click on "Save" button), view gets stop working means it's not filtering data based on query string
Any suggestion what I am missing?
Below is my list view schema
<View BaseViewID="11" Type="HTML" TabularView="FALSE" WebPartZoneID="Main" DisplayName="$Resources:OIPLBScoreCard,viewFilterTasksByTarget;" MobileView="True" MobileDefaultView="False" Url="FilteredTasks.aspx" SetupPath="pages\viewpage.aspx" DefaultView="FALSE" ImageUrl="/_layouts/15/images/issuelst.png?rev=23">
<Toolbar Type="Standard" />
<ParameterBindings>
<ParameterBinding Name="NoAnnouncements" Location="Resource(wss,noXinviewofY_LIST)" />
<ParameterBinding Name="NoAnnouncementsHowTo" Location="Resource(wss,noXinviewofY_DEFAULT)" />
<ParameterBinding Name="TargetId" Location="QueryString(TargetId)" />
</ParameterBindings>
<JSLink>hierarchytaskslist.js</JSLink>
<XslLink Default="TRUE">main.xsl</XslLink>
<JSLink>clienttemplates.js</JSLink>
<RowLimit Paged="TRUE">100</RowLimit>
<ViewFields>
<FieldRef Name="Body"></FieldRef>
<FieldRef Name="Title"></FieldRef>
<FieldRef Name="StartDate"></FieldRef>
<FieldRef Name="DueDate"></FieldRef>
</ViewFields>
<ViewData>
<FieldRef Name="PercentComplete" Type="StrikeThroughPercentComplete"></FieldRef>
<FieldRef Name="DueDate" Type="TimelineDueDate"></FieldRef>
</ViewData>
<Query>
<Where>
<Eq>
<FieldRef Name="oipscTargetLookup" LookupId="TRUE"/>
<Value Type="Lookup">{TargetId}</Value>
</Eq>
</Where>
</Query>
</View>
I have one lookup field from "Target List" in my source list and I want to filter data based on that lookup field.

Hi JayJT,
The Miscellaneous is located in the contact list that you used for the connection.
So , you need to edit the page, then edit the contact list that you used, in the web part properties of the contact list, you will find Miscellaneous, then expand it and select ‘Server Render’ .
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Does ADFS work with SharePoint 2013 with WFEs SSL-offloaded to a F5 load balancer?

Currently we are implementing a SharePoint 2013 Production environment with 2 WFEs load-balanced by F5. SSL is offloaded to F5 and is currently working fine with Integrated Windows Authentication with NTLM. We would like to implement ADFS 3.0
later for Single Sign-on, and we are wondering if ADFS supports SSL offload.
Do we need to bind the certificate to the WFEs as well to use ADFS?
Thank you!

Just got it confirmed that ADFS supports SSL offload. There is no direct communication between SharePoint and ADFS server during the authentication process. It is always the browser that's talking to ADFS server. We just need to do the following:
Configure SharePoint URLs in ADFS as replying parties with https.
Configure AAM in SharePoint to make sure internal URL is http and public URL is https.

SharePoint 2013 Remote Index with ADFS

Similar Messages

Maybe you are looking for