RE: citrix and client access -- MIDRANGE-L

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
Not exactly what i'm looking for...
  And I even tried the *PCNAME, but that didn't work for me, so I might not
have a new enough version of client access...

tim

> -----Original Message-----
> From: rob@dekko.com [SMTP:rob@dekko.com]
> Sent: Thursday, April 25, 2002 2:36 PM
> To:   midrange-l@midrange.com
> Subject:      Re: citrix and client access
>
> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Not very clear but is this what you mean
> http://archive.midrange.com/midrange-l/200110/msg01121.html
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
> "Hatzenbeler, Tim" <thatzenbeler@clinitech.net>
> Sent by: midrange-l-admin@midrange.com
> 04/25/2002 04:20 PM
> Please respond to midrange-l
>
>
>         To:     "'midrange-l@midrange.com'" <midrange-l@midrange.com>
>         cc:
>         Fax to:
>         Subject:        citrix and client access
>
>
> This message is in MIME format. Since your mail reader does not understand
> this format, some or all of this message may not be legible.
> --
> [ Picked text/plain from multipart/alternative ]
>
>                  I was wondering if there was a way to set the workstation
> ID in
> client access, by a command line or enviornment variable..
>
>                  Purpose:
>                    I would like to set a script so when users log into our
> thin
> client machines, I could take their user id, and set the client access
> workstation Id/device description with a comparable name, instead of
> having
> the as/400 assign a dynamic virtual connection...
>
>                  Thanks, tim
> This e-mail message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain confidential or privileged
> information.  Any unauthorized review; use, disclosure or distribution is
> prohibited.  If you are not the intended recipient, please contact the
> sender by reply e-mail and destroy the message.
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential or privileged
information.  Any unauthorized review; use, disclosure or distribution is
prohibited.  If you are not the intended recipient, please contact the
sender by reply e-mail and destroy the message.