CTX238200 ..? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd D8453 Scottsdale, AZ 85262 (602) 432-8649 www.thinclient.net steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Greenberg Sent: Tuesday, July 31, 2007 12:47 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Client drive mapping for client network drives I had to re-configure my policies to test it, but I did not see the network drivers as I expected to. I can't spend more time on it now, but it seems to be acting the same way as yours... hmmm Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd D8453 Scottsdale, AZ 85262 (602) 432-8649 www.thinclient.net steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Anthony_Baldwin@xxxxxxxxx Sent: Tuesday, July 31, 2007 12:10 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Client drive mapping for client network drives Steve, On the farm where we tested we only have one policy. Are you seeing client network drives automatically showing up on your farm? Tony "Steve Greenberg" <steveg@xxxxxxxxxxxxxx> Sent by: thin-bounce@xxxxxxxxxxxxx 07/31/2007 02:31 PM Please respond to thin@xxxxxxxxxxxxx To <thin@xxxxxxxxxxxxx> cc Subject [THIN] Re: Client drive mapping for client network drives Do you have any other policies which might be overriding this one? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd D8453 Scottsdale, AZ 85262 (602) 432-8649 www.thinclient.net steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Anthony_Baldwin@xxxxxxxxx Sent: Tuesday, July 31, 2007 11:19 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Client drive mapping for client network drives Steve, Nope, they don't show up anywhere but in 'change client /view'. Tony "Steve Greenberg" <steveg@xxxxxxxxxxxxxx> Sent by: thin-bounce@xxxxxxxxxxxxx 07/31/2007 02:07 PM Please respond to thin@xxxxxxxxxxxxx To <thin@xxxxxxxxxxxxx> cc Subject [THIN] Re: Client drive mapping for client network drives Yes, you got both areas. Do they show up in other applications other than explorer? Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd D8453 Scottsdale, AZ 85262 (602) 432-8649 www.thinclient.net steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Anthony_Baldwin@xxxxxxxxx Sent: Tuesday, July 31, 2007 10:52 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Client drive mapping for client network drives Steve, The screenshots you sent didn't come through on my email, so I'm not sure if we are looking at the same thing. But, we tried setting the client\devices\resources\drives\connection and mappings policies and making sure the mfcfg.exe settings allowed drive mappings. We're still not seeing the drives show up in applications like explorer (they consistently show up in a 'change client /view', though). Thanks, Tony "Steve Greenberg" <steveg@xxxxxxxxxxxxxx> Sent by: thin-bounce@xxxxxxxxxxxxx 07/31/2007 01:02 PM Please respond to thin@xxxxxxxxxxxxx To <thin@xxxxxxxxxxxxx> cc Subject [THIN] Re: Client drive mapping for client network drives There are two settings in the policy, did you check both? First, which drives to map: Then whether or not to cnnect at logon: Steve Greenberg Thin Client Computing 34522 N. Scottsdale Rd D8453 Scottsdale, AZ 85262 (602) 432-8649 www.thinclient.net steveg@xxxxxxxxxxxxxx _____ From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Anthony_Baldwin@xxxxxxxxx Sent: Tuesday, July 31, 2007 6:26 AM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: Client drive mapping for client network drives All, According to Citrix that policy is for enabling/disabling access to 'remote drives' it doesn't automatically map remote drives (I haven't tested to make sure). Anyway, I wrote a little batch file to do it... @echo off :: change client /view |findstr /i " Remote" >%TEMP%\drivemaps.txt :: for /f "tokens=1" %%i in (%TEMP%\drivemaps.txt) do net use * %%i /p:no :: del %TEMP%\drivemaps.txt I could've swore that Citrix used to do this automatically (XP at least), but our Citrix consultant swears that I must be smoking something. Tony "Raffensberger, Stephen D" <sraffens@xxxxxxxxxxxxxxxxx> Sent by: thin-bounce@xxxxxxxxxxxxx 07/27/2007 04:32 PM Please respond to thin@xxxxxxxxxxxxx To <thin@xxxxxxxxxxxxx> cc Subject [THIN] Re: Client drive mapping for client network drives 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, <mailto:Anthony_Baldwin@xxxxxxxxx> 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.