Once SQL server installed we experience troubles while starting the SQL agent which starts then immediatly stops if we do not put it in the server local Administrators group. We use only AD service account (simple user, no special rights). This may be caused by the FILESTREAM bug (not sure).
As a workaround to avoid putting the SQLagent in the local Administrators groups we put the AD service account in the SQLServerMSSQLUser$%COMPUTERNAME%$InstanceName group then restart the agent. Once restarted we remove the AD service account from the SQLServerMSSQLUser$%COMPUTERNAME%$InstanceName group and it therefore works fine without error. All this is done using PowerShell to automate installations (moreover 150 instances).
Is there another (better) way to solve this issue?