[THIN] Re: Citrix Infrastructure Design

MessageI did get it to accept the path as \\%profloc%\%username%, but it would 
not substitute the value of the variable at logon.  It tried to map to a server 
named %profloc%.

I played around a bit more and was able to change the AD object with net user 
/homedir, but that's not what you want either.

I believe your best bet would be to set a %hdloc% variable (switched HD = 
homedrive, as opposed to prof=profile) to server\share:

Then use the following in the logon script:

;map the X: drive to local file server
net use x: /delete
net use X: \\%hdloc%\%username$%
;set the environment variable to local file server for programs that use this 
variable.
set homeshare \\%hdloc%\%username%

 ----- Original Message ----- 
  From: Robertson, Russell 
  To: thin@xxxxxxxxxxxxx 
  Sent: Thursday, November 13, 2003 3:35 PM
  Subject: [THIN] Re: Citrix Infrastructure Design


  Spencer

  We cannot add variables to the Connect X: field in an AD user account,  it 
comes up with "not a valid network shared directory name".

  Does it work for you?

  Thanks

  Russell
    -----Original Message-----
    From: Spencer Sun [mailto:ssun@xxxxxxxx] 
    Sent: 13 November 2003 16:10
    To: thin@xxxxxxxxxxxxx
    Subject: [THIN] Re: Citrix Infrastructure Design


    Have you tried setting the variable to server\share (note the lack of 
double wacks at the beginning) and then it as Connect X: \\%profloc%\%username% 
 ?

      ----- Original Message ----- 
      From: Robertson, Russell 
      To: thin@xxxxxxxxxxxxx 
      Sent: Thursday, November 13, 2003 2:35 PM
      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). 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 server\ London share

        While PROFLOC in NY would = \\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: