Quote:
Originally Posted by mcnallym If the user is part of a usergroup that the gateway is configured to offer office mode too then the client will use Office Mode |
We have enabled OM for all of our users and there are a handful that, for whatever reason don't get assigned an OM address. Usually reinstalling the client helps, sometimes reinstalling the OS does.
If you have more then one gateway in your Remote Access community then you will need to use Global Properties -> Remote Access -> Advanced -> Used first allocated Office Mode IP Address for all connections to the Gateways of the site. Otherwise access through secondary RA gateways won't use the original OM IP, instead it logs the access as coming from the clients LAN IP.
Quote:
Originally Posted by mhicks I was hoping to be able to force all SecureClient users to use office mode from SmartDashboard. |
If you go here:
SmartDashboard -> Manage -> Remote Access -> Connection profiles
You can edit your current profiles and check the "Support Office Mode" option under the Advanced tab. This profile *should* get pushed down to the client after you push the policy to the firewall and the client updates its site/topology (assuming the client is set to auto-update topology, 'nother ball of wax).
If you aren't using connection profiles and all of your profiles are local to the client, then you must have the user edit his profile manually and enable the office mode option. If you are using MEP and letting the user pick which gateway to connect to, then a manual edit by the user is your only option for enabling OM--as such a scenario isn't viable by using SmartCenter managed profiles.