[THIN] Re: Citrix Infrastructure Design
- From: "Claudio Rodrigues" <crodrigues@xxxxxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Thu, 13 Nov 2003 13:35:26 -0500
Although you can set a home directory on AD you can delete the mapping upon
logon I think.
In this case you could have a script that would retrieve the machine name or IP
address that is connecting (this you can get no problems) and map the home
drive letter to the closest server otherwise performance will be indeed pretty
bad for some applications/operations. This means you would need local home
directories for all users on all locations.
My 2 cents...
Cláudio Rodrigues
-----Original Message-----
From: Robertson, Russell [mailto:Russell.Robertson@xxxxxxxx]
Sent: 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
Other related posts:
