UAG Direct Access 2010
Windows 2008R2 AD
Windows 7 Ent Clients
We want all of our users to use roaming profiles – Mainly for some printer and drive mappings, and to increase quality of life for our users (most recent lists, Office prefs, etc.)
We already have redirected folders configured for user documents. We have minimized the folders that can roam so the profile size is extremely small.
When logging users that have a roaming profile configured onto devices within the organisation, the logon time is extremely quick - 10 secs or below.
Ideally we want to provide the same experience, or at least as close to this as possible, to users logging in via Direct Access.
However, when the user attempts to login via Direct Access the login times are significantly higher - up to 8 minutes in some cases. Once they’ve logged in, the following message is displayed
There was a problem with your roaming profile. You have been logged on with your previously saved local profile. Please see the event log for details or contact you administrator
We first tried enabling the policy “do not detect slow network connections” in order to force the roaming profile to be loaded. Obviously doing this prevented the message above from appearing but increased the login times even further as the user is downloading their roaming profile on whatever connection they have at home (1-100mbit).
We then tried configuring the “slow network connection timeout for user profiles” policy in order to force the local profile to be loaded. Unfortunately, any setting I tried seemed to be ignored.
To sum up, when users work remotely using Direct Access, we want the local profile to be used, so that the login time is short as possible (ideally 30 seconds or less). Also, we want to achieve this without informing the user that the local profile is being used.
Has anyone overcome this issue and achieved the desired outcome?