Scaling and adding more servers to SharePoint Foundation 2013 Search

In the last few days, we have not only been trying ourselves with different approaches, but also posted this query with Microsoft folks, Technet Forums and even LinkedIn SharePoint Groups and finally, it is clear that SharePoint Foundation 2013 Search is not scalable and thus you cannot have them spread over multiple servers - which is what we are trying to do here. (This has been confirmed by MS Support as well)
Refer the below links:

https://social.technet.microsoft.com/Forums/en-US/f175968d-9195-4d7f-a359-869e5983b845/sharepoint-foundation-2013-search-configuration-issue-2-app-servers-and-2-frontend-servers?forum=sharepointsearch

https://www.linkedin.com/groupItem?gid=58750&type=member&view=&commentID=discussion%3A5949737753292922880%3Agroup%3A58750&item=5949737753292922880&trk=hb_ntf_COMMENTED_ON_GROUP_DISCUSSION_YOU_CREATED

http://www.myfatblog.co.uk/index.php/2012/10/search-in-sharepoint-2013-foundation-versus-full-blown-server/
The above link clearly mentions the below:
The key limitation is the options for scaling, Search in Foundation appears to only be installable on one server, or at least I’ve not been able to change the topology yet. Attempting to use the New-spenterprisesearchadmincomponent cmdlet results in an exception stating "Access to this functionality requires a SharePoint Server Client Access License." Which is the error that is attached here as a reference

 



I think the solution options right now could be two:

1.       Option 1
a.       Remove the 2 App Servers completely
b.      Create a new App Server which has C Drive of 300 GB of SAN
c.       We will install the App Server components and the Search Service on this server and re-join this to the SharePoint Farm and run the Search Service only in this
2.       Option 2
a.       Completely re-install the environment, but this is not required till the Option 1 is tried out

During the above procedures, the front-ends usually continue to run but functionality such as Event Receivers, Background jobs that depend on Timer Service etc. will not work




Comments

Post a Comment

Popular posts from this blog

Using External Content Types with Stored Procedures with Input Parameters

Image
You must have tried External Content Types - the exciting new feature in SharePoint 2010 to connect to an external SQL table and provide a list where it lists, creates, updates data straight into the SQL table. People always wonder, how do you get a ECT to work with a Stored Procedure, one that has input parameters. You could do it this way... Step 1: In your SharePoint Designer 2010, create a new external content type Step 2: Connect to your SQL Server and then make sure you see the Routines (your stored procedures must be listed here) Step 3: Rt Click on the Stored Procedure name and create operations for "Read Item" and "Read List" - both are required for the External Content Type's SharePoint list to be created. During both these wizards, in the Input Parameters, your SP's Input Parameter will be listed. Here, you need to create a filter, which sends out it's value to the SP's filter. For example, if your SP's Input Parameter is @Emp...
Read more

Multi Factor Authentication, Conditional Access for Power BI

There is always a discussion on protecting Power BI access, enabling MFA, conditional access etc. This is very much possible. Please refer this article. https://powerbi.microsoft.com/en-us/blog/secure-and-audit-power-bi-in-your-organization/ I have attached a PPT with screenshots of how this works (infact, I have taken it from iGrid’s Azure Subscription) Using certain configuration, you can even block access for users, when they are not at work. Infact, you can have such a configuration done for every O365 product. You would require Azure AD Premium P1 for this and different plans are here: https://www.microsoft.com/en-us/cloud-platform/azure-active-directory-pricing This could approximately cost $6/user/month.
Read more