Eric This idea is on the table, but since we don't use DFS yet, and as Ron pointed out, we are not sure yet how much control we can exert of what's replicated. Thanks for the answer. Russell -----Original Message----- From: Foote, Eric [mailto:EFoote@xxxxxxx] Sent: 13 November 2003 13:49 To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Citrix Infrastructure Design Use Microsoft DFS with AD Sites and set the sites to include the local IP segments, sessions within the site will be directed to the local DFS replica based on the IP address of the Citrix server and fail-over to the remote DFS replica only if the local is not available. Eric Eric M. Foote Detroit Medical Center Intel Server Group Leader Security Group Leader OP 5-1625 3663 Woodward Ave. Detroit, MI 48201-2403 (313) 578-2310 EFoote@xxxxxxx Pager (888) 352-6303 Fax (313) 578-2310 -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Robertson, Russell Sent: Thursday, November 13, 2003 1:16 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Citrix Infrastructure Design Hi I have a scenario which I'd love comments on as someone on the list must have similar infrastructure. Windows 2000 AD, all in one domain, mostly Citrix XPe FR2. Say we have two Citrix servers, one in London and one in New York. I work in London and my terminal server home directory in AD is set to a share in London. I want to access apps in both London and New York. But when I access an app in New York my TS home directory points to London and the performance of the app sucks, especially if the app uses the TS home dir for ini files, etc. What is the experience of other admins out there? The example above is compounded by servers and users being in other locations throughout the world, Houston, Algeria, Kuala Lumpur, etc. and all users may need to access any or all servers. Thanks Russell