To remedy a potential issue as written here: http://techmikael.blogspot.no/2014/10/caution-if-you-have-used.html, would it be possible to patch this using autospinstaller, granting the correct rights to the farm account?
Comments: ** Comment from web user: brianlala **
Comments: ** Comment from web user: brianlala **
Some related posts:
* http://www.ericshupps.com/2014/05/sharepoint-2013-search-errors-and.html
* https://social.technet.microsoft.com/Forums/sharepoint/en-US/7f5c7179-17d8-44d3-9da4-4072d561de92/adding-an-administrator-for-the-search-service-application-in-central-admin-deletes-all-membership?forum=sharepointsearch&prof=required
* http://social.technet.microsoft.com/wiki/contents/articles/23610.troubleshooting-sp-2013-exception-cannot-alter-the-role-spsearchdbadmin-because-it-does-not-exist-or-you-do-not-have-permission.aspx
In fact, I found that there are other databases (e.g. Subscription Settings, Config DB (!)) to which the Farm Account doesn't have db_owner after a scripted install.
Brian