Hi,
In a SEC install there are 2 "service" accounts as detailed here:
http://www.sophos.com/en-us/support/knowledgebase/113954.aspx
One is for the services of the management server and database access ,e.g. SophosManagement.
The other is for the clients to update from the SophosUpdate share. This one is for example: SophosUpdateMgr.
SophosUpdateMgr is added to the default updating policy so that when the clients get the policy they can read from the share.
Both of the above accounts aren't required to be administrative.
Then there are the accounts you use SEC as. When you run the protet wizard, this is essentially for creating remote scheduled tasks on the clients you are deploying to. This account requires to be able to logon to the Sophos Management Server and also to be an administrator on the target clients. For this reason, typically you would use an account that is a domain admin, as when you add computers to a domain, the domain administrators group is added to the local administrators group on the client.
So in a domain, the deployment account would typically be in the format [domain]\[account], where the account is a member of the domain admins group or an account which has administrative rights on the target client.
Regards,
Jak
That's correct, the SophosUpdateMgr account should really only have enough rights to read from the SophosUpdate share to allow the clients to update. The clients use this account in their policy to update, that is all.
The account you push installs to the clients needs full admin rights on the target computers and the ability to log on to the management server in order for the Sophos Management Service to impersonate the account to deploy.
Regards,
Jak