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: Lagerman **
Comments: ** Comment from web user: Lagerman **
I'd say there is a massive problem with the rights being assigned through AutoSPInstaller. My farm account has dbowner on almost no database, and in fact isn't even authorised to the User Profile or ProfileSync database at all (oddly enough, the Installer account is in there).
For my user profile services, the application pool account is being assigned which doesn't work (FIM refuses to start no matter what). I saw that this was 'tricked' to use the app pool account, however it is indeed not 'tricked', but actually assigned.
I'm on SP 2013 w/ SQL 2014, tried both July CU and Nov CU with the same results. I'm thinking I need to ditch the script...