2014-06-05 09:05 AM
The WFA Installation and Setup Guide, on page 13, step 1, reads (WFA 2.2 in this case but I think previous versions said something similar):
accounts that have administrator privileges, for security purposes.
It is not uncommon for storage related administrators who have an account with administrative privledge but not the actual "default administrator account" to be the designated individual to install this product. As such, a customer has asked "what impact" it would be if installing the product as a non-default but privileged account? In a large account this could be problematic. Further questions I have include;
2014-06-05 09:29 AM
@ When the documentation says "default administrator account" it does not say "domain" or local builtin on the server. Which does it mean?
Any user who is in Group "Administrators" be it local or domain should be fine.
@ Why? is there a known issue or is it just that it has not been tested?
I don't know all reasons but some things don't work unless you login as the Administrator user i.e. a user with Administrative privileges. What I have noticed and remember is that some WFA applications access the windows registry and a non-administrator user doesn't have the right for it.
WFA service by default runs using the Local account, and if the local account doesn't have all permissions , WFA functioning could be affected.
But I haven't tested much on this area.