[THIN] Re: Client drive mapping for client network drives
- From: "Raffensberger, Stephen D" <sraffens@xxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 27 Jul 2007 16:32:13 -0400
Has anyone seen this policy setting do anything?
Steve Raffensberger
Sovereign Bank
Email: sraffens@xxxxxxxxxxxxxxxxx
________________________________
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Greg Reese
Sent: Friday, July 27, 2007 4:25 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Client drive mapping for client network drives
it would be cool if it did though.
What happens if you run a subst command to make the drive appear local?
Just curious. I have no need for it.
On 7/27/07, Jason Patten <jasoncitrix@xxxxxxxxx> wrote:
As far as I can recall, Citrix does not map network drive shares, only
local drives
On 7/27/07, Anthony_Baldwin@xxxxxxxxx < Anthony_Baldwin@xxxxxxxxx>
wrote:
All,
OK, maybe this is a really stupid question, but I thought if a client
logs into Citrix with a drive mapped on their client that points to a
network share that drive would show up (maybe as a different drive
letter) in their Citrix applications, is this correct?
We have a CPS4.0/R03/W2K3SP2 farm servicing version 9.15 clients, when
they log in they see their 'fixed disks' but they don't see any of the
network drives mapped on their client PC.
If I log in I see the same thing (no client mapped network drives),
however if I get to a command prompt in the session and run a 'change
client /view' it shows my network drives mapped on my client as 'Remote'
drives.
Is this the way its always worked (I seem to remember all the client
drives showing up unless you told Citrix not to)? If not, what do I
have to do to get the drives to show up?
Thanks,
Tony
This message contains information which may be confidential and privileged.
Unless you are the addressee (or authorized to receive for the addressee), you
may not use, copy or disclose to anyone the message or any information
contained in the message. If you have received the message in error, please
advise the sender by reply e-mail, and delete or destroy the message. Thank you.
- Follow-Ups:
- [THIN] Re: Client drive mapping for client network drives
- From: Anthony_Baldwin
- [THIN] Re: Client drive mapping for client network drives
- References:
- [THIN] Client drive mapping for client network drives
- From: Anthony_Baldwin
- [THIN] Re: Client drive mapping for client network drives
- From: Jason Patten
- [THIN] Re: Client drive mapping for client network drives
- From: Greg Reese
- [THIN] Client drive mapping for client network drives
Other related posts:
- » [THIN] Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives
- » [THIN] Re: Client drive mapping for client network drives


