[THIN] Re: Citrix Infrastructure Design

  • From: "Ron Oglesby" <roglesby@xxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Thu, 13 Nov 2003 15:03:58 -0600

Ahh that's right. I generally do this with profiles but profiles allow
the variables,..,,,,,, the home dir wont cuz it tries to create it!!!!
Ahhhhhhhhhhh

 

S H I T 

Sorry. Yeah I would then say its time to use the same settings but with
a script set the home dir based on the variable there.....

 

Screw up number 73 for the day.

 

Ron Oglesby

Senior Technical Architect

 

RapidApp

Office 312.372.7188

Mobile 815.325.7618

email roglesby@xxxxxxxxxxxx

 

-----Original Message-----
From: Robertson, Russell [mailto:Russell.Robertson@xxxxxxxx] 
Sent: Thursday, November 13, 2003 2:36 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Citrix Infrastructure Design

 

Ron

 

This is what we are looking at now. We haven't been able to get this to
work quite right. I guess you are adding the %PROFLOC%\%USERNAME%
variables to the upper box (the Local Path) in the Terminal Servers
Profile Path tab (since AD won't let you put the environment variable in
the lower field, Connect X: to \\yada\yada <file:///\\yada\yada> ). This
means that the %HOMEPATH% variable should set to whatever is in the
Local Path, right? This doesn't work for us. How would users see the new
TS home dir?

 

Where are we going wrong?

 

Thanks

 

Russell

 

        -----Original Message-----
        From: Ron Oglesby [mailto:roglesby@xxxxxxxxxxxx] 
        Sent: 13 November 2003 13:44
        To: thin@xxxxxxxxxxxxx
        Subject: [THIN] Re: Citrix Infrastructure Design

        2003 makes this a non issue but does the same basic thing I am
about to show you (only at a GPO level)

         

        Set a system ENV variable on each (requires a reboot)

        Profloc=

         

        PROFLOC is short for profile location. Lets assume that in each
site you have a home dir structure that can be accessed like
so:\\Server\Share\%username%

         

        Well  with PROFLOC in London would = \\London <file:///\\London>
server\ London share

        While PROFLOC in NY would = \\NY <file:///\\NY>  server\ NY
Share

         

        Now in the user's Terminal Server home dir path setup this
%profloc%\%username%

         

        Works like a champ.  Now if you want to use a standard home dir
you still can you just HAVE to set this in TS properties for the user,
just ensure that in London the PROFLOC ='s the normal path. This will
keep it from hitting the user at the home dir and having to set PROFLOC
on the desktops too.

         

         

         

        Ron Oglesby

        Senior Technical Architect

         

        RapidApp

        Office 312.372.7188

        Mobile 815.325.7618

        email roglesby@xxxxxxxxxxxx

         

        -----Original Message-----
        From: Robertson, Russell [mailto:Russell.Robertson@xxxxxxxx] 
        Sent: Thursday, November 13, 2003 12: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: