I've always recommended people run FortiClient with VoodooShield. (this combo is actually a powerful pairing in our tests, try that combo in the hub) I suppose one could run it alone because it's sigs are decent, it has anti-exploit, and the web filtration is good. But I wouldn't suggest it for clickers or newbs in that configuration.
FortiClient is designed specifically as a managed, controlled endpoint solution tied to specific pieces of hardware as part of a protection fabric. If any of those pieces are missing the product is degraded and the fabric is compromised. Which is why I've always encouraged those that run it pair it with something like VoodooShield to seal up any gaps in it.
FortiClient alone, with average-joe's or clickers will universally end up with discouraging results. It's just not going to go well. It's missing too many pieces of the puzzle, there is no fabric, it's not backed by the hardware that's supposed to be backing it. I'd actually expect poor results in the hub given a solo configuration. Remember, even AVC (where Fortinet scores pretty well) has a FortiGate Controller for the Client, they are still missing a few pieces of the puzzle, but just having the gate there improves results quite nicely.
FortiClient Solo (no hardware, no adjunct support) = RISKY unless you are somewhat savvy. (but even I wouldn't roll with this config)
FortiClient w/Hardware, EMS, Sandbox = Incredibly strong.
FortiClient w/VoodooShield = What I personally believe is one of the strongest free setup without system drag.