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 **
As you indicated in your (edited) post, this situation is more likely a result of scripted installs in general - although AutoSPInstaller can be updated (and has been) to implement workaround/fixes for known issues in scripted installs or SharePoint in general (e..g. adding accounts to local groups, etc.).
Can you tell more some more about your SQL back-end:
* Version/build of SQL
* Standalone, clustered, or AlwaysOn?
* Was the install account a sysadmin at install time, or just dbcreator & securityadmin?
* Any other relevant details?
Thanks
Brian