When roaming profiles are located on a on a domain-based Distributed File System (DFS) share, they may NOT be loaded if the domain controller that hosts the DFS share and the server that stores the roaming profiles are located at two different sites that are connected by a slow link.
If the roaming profiles are located on a server in site 1 and the DFS share is on a DC in site 2, and site 1 is connected to site 2 via a slow link, you may experience this behavior, even though the user has a fast link to the roaming profile server in site 1.
To workaround this behavior, use the Group Policy Editor to set Group Policy slow link detection to Disabled at Computer Configuration / Administrative Templates / System / Group Policy.
0 comments
Hide comments
