Well super agent to good to use to serve remote sites as it will not require any credentials to download the package. No need of service account to replicate package from ePO master repository, Super Agent replication works until there is no space and ePO communication issue.
SuperAgents require less configuration and most important, support different client types due to the way clients connect.
Non windows endpoints cannot connect over UNC
FTP is not secure
HTTP requires IIS
SuperAgents only require a policy... Next
DIstributed repos - commonly used as http or unc shares. These would be used when bandwidth is reliable and local to clients. You need to create in advance and setup credentials.
superagent repos - These are typically implemented in low bandwidth scenarios or very large environments where clients are responding to a superagent wakeup call to report home. The setup is very simple via the epo agent policy. Although you can replicate like you would a normal distr repo, a key feature is lazy caching. You can create an empty repo and when configured corrctly, a client requests a.....whatever, dat,product etc and its downloaded from the epo server to the sa repo and made available to clients feeding off that sa repo and epo agent policy.
That is a brief description.
As per I know Super Agent repositories is part of Distributed repositories. So question will be which repository will be good for remote sites (UNC, Super Agent, HTTP or FTP)
If you could give some information about network connectivity (bandwidth and latency) and number of clients we could advise with more confidence.
An SA repo has advantages over the others where Agent Comms and other features could be taken into account where the others don't have these features.
McAfee Certified Product Specialist -ePO