But you are here describing two different set of Distributed Cache.
First is about using DC on WFE server, the second is about to have server with MinRole - DistributedCache, where you are using more % of RAM.
When you are using DC on SP WFE servers, we are using 10% of total RAM, but sizing of WFE servers depends on howm any web applications, how many ...
We had the same kind of problem in one of the farm. What we did:
Stop the MMS service on the effected server (wfe) ( from central admin > system settings > manage services on server)
Check IIS and make sure their is no app pool and Site enter for MMS ( under the Services WebSite). if any entry exist for Managed Meta data service, please delete it.
If not ...
Yes , you can convert MinRole from Signle-Server farm to multiple-server farm , for example ,you can convert it to Front-end role .
Remote to this server .
Open SharePoint central admin page and click system settings .
Click Convert server role in this farm.
On the Role Conversion page, in the New Role area, click the drop-down box to select the new ...
it is kind of tricky, You have to check performance of your farm before going up or down. 10% of total memory is not bad in 16GB server. With the MinRole, it is easy to manage it as less services / unwanted service on the server...Because SharePoint automatically shutdown non-compliant services.
I would also enable the DC on the Server to make it High ...
Just disable the health analyzer rule. Monitor your disk free space via other means. The rule is nonsensical given it needs 5*RAM for free disk space, which doesn't make sense except for a full dump with a BSOD. This isn't the default for Windows (it takes a mini dump instead).
I would go with the Custom Role as your requirement is both server should be the same then only Custom Role can give you full ability. Custom role is same as what we have in SharePoint 2013( one role).
HA with 4 servers means you have to select the appropriate the role for the each servers when you configuring your servers.
In 4 Servers HA, you have to select the following roles.
2 Servers with "Application with Search"
2 servers with "Front-end with Distributed Cache"
You need a configure the load balancer in front of your WFE.
Read this technet for ...
I would install the CA server first. That's mean the server which is going to Host the Central admin web site, I will run the config wizard over there and configure the MinRole( which ever you want i.e custom, WFE, app etc).
Rest you can do in any order.
I do not see any Database Server Role for the Database Server. Why is this the case?
Fundamentally, In the non-Standalone farm (Like Tow-Tire farm), the Sharepoint is not installed on the Database Server, so that we don't need to run the SharePoint configuration wizard on it to specify its role.
Once the SQL Server is installed on a server within the farm, ...
Yes, it will created on all servers but only WFE will be serving the content for the end users. Because your DNS will point to the WFEs not APP servers.
Microsoft SharePoint Foundation Web Application is running on APP thats why SP created the web app on app server.
Check this article for more about MinRole services.
If your Service Instance is not configured to support MinRole, you must deploy the SharePoint server as Custom. If you have the source or can get the vendor to update it, yes it is possible to make it MinRole compliant.
The article Managing a MinRole Server Farm in SharePoint Server 2016 has information at the bottom about how to make a Service Instance ...
To answer your question, Front end is the server in SharePoint that handles web requests . So to handle and ease the user request load it would be a great idea to have 2 servers configured with Front end + Distributed cache.
It would be a good idea to not run 2 user profile services if you are not using the same farm for creating 2 different environments. ...
Microsoft SharePoint Foundation Sandboxed Code Service compliant on the Front End, Front end with DC or Custom MinRole.
If you have any of the above role in your farm then you can enable
the auto provision and start the services from central.
Also make sure that "SharePoint User Code Host" service is running on
server (check via services on the computer)
Go with your second option. Both servers will run UPS and thus AD Import (only one server will run the timer job, but both servers are eligible to run the timer job). You should configure Search, via PowerShell, to have all rolls on both application servers.
During the installation process you have to select the "Front-end with Distributed Cache" role and complete the configuration. Post configuration, you can apply changes to your DC if any( changing max memory, service account etc).
You should be at least on November 2017 CU level as this role introduced in that cu.
Yes, it's correct.
In MinRole, the Custom Server Role include the below services
Microsoft SharePoint Foundation Administration
Microsoft SharePoint Foundation Timer
Microsoft SharePoint Foundation Web Application
These default services are auto-provisioned by default in Custom Server Role based on TechNet.
In Custom Server Role,...
The problem has been resolved. The comment about the content web applications is somewhat correct. The thing to remember is that this is SharePoint 2016 using MinRoles. With MinRoles one does not get the option in the services on server to turn on the web application role by server. With MinRoles, one specifies which server(s) will get the WFE role.
Without using the Custom MinRole, MinRole High Availability will require a minimum of 9 servers; 3 Distributed Cache, 2 Web Front Ends, 2 Search, and 2 Application Servers. Licensing and hardware availability will determine what topology you will pick; this will determine the route for 'best practice'. I suspect many companies will continue to use a Custom ...