I know many of you have tried this – replicating user profile data between geographies for the purposes of improving the end user experience during log in while still providing geographic synchronicity for execs and other users that move between two different sites.
Well, lo and behold, we have an official statement about folks that do this and there are supported scenarios and non-supported scenarios because things can obviously get squirrelly.
Here are the scenarios that are described.
- Deployment scenario 1: Single file server, replicated to enable centralized backup
- Scenario 1A: DFS Namespace is not configured [SUPPORTED]
- Scenario 1B: DFS Namespace is configured – single link target [SUPPORTED]
- Deployment scenario 2: Multiple (replica) file servers for geo-location
- Scenario 2A: DFS Namespaces is configured – multiple link target configuration [UNSUPPORTED]
- Scenario 2B: DFS Namespaces is configured – multiple link targets, read-only replica on central/hub server [UNSUPPORTED]
To read the details behind these scenarios, you really have to read the entire post. It’s a doozy.
- FULL ARTICLE: Microsoft’s Support Statement Around Replicated User Profile Data
http://blogs.technet.com/b/askds/archive/2010/09/01/microsoft-s-support-statement-around-replicated-user-profile-data.aspx
kurtsh
Kurt Shintaku's Blog 