When deploying a search service application form central admin in a farm using a MinRole deployment the search topology gets deployed on the app server and not on the search server. After the search service application is deployed the app server will have the status not in compliance.

The same happend when creating a web app. This was created on the app server and not on the front-end server.

When creating a web app or service application from central admin there is no "detection"of the different server roles?

Creating a service app in a MinRole deployment is only possible using Powershell?

Hello Marco,

Thanks for submitting feedback for this. We are aware of this behavior which is as following please correct me if I have misunderstood on what you are trying to do.

When Creating Search Service Application from UI it deploys Search Service Application on Server from which  CA was Browsed. With Min role Config CA is provisioned on all servers in Farm. 

I am including a simple Example of one APP server and one Search Server

name of App Server : SP-APP

Name of Search Server : SP-Search

And farm was created on App server so your default CA link will point to APP server may be something like this

http://sp-app:2016

Just update this to http://sp-search:2016 as a workaround and then create Search Service Application and it will provision Search on Search Role box as expected.

Another solution would be to use PowerShell to configure Search or Update AAM for Central Admin to make Search box as default Public url for CA.

Hi Hiran,

Only Changing the CA URL to the server with the search role didn't work. The creating search service app window timed out and left a broken search service application without a Search Service Application Proxy. Removed the search service application.
After updating the AAM for central admin the search service application was created and the topology is using the server with the search role.

Hi Marco, let me also mention our Known Issues in SharePoint Server 2016 IT Preview article on TechNet.  It describes the Search provisioning issue you're seeing with MinRole and how to work around it.

The web application provisioning issue is interesting.  Can you confirm whether this was a content web application or the Central Administration web application?  Is the SharePoint Timer service running on your front-end server?

- Troy Starr [MSFT]