This project has moved. For the latest updates, please go here.

Connect to local drives

Topics: User Forum
Dec 30, 2008 at 6:16 PM
Great product. Much better than the Microsoft Remote Desktops that are a part of the Windows 2003 admin pack.

This is probably a very simple question and I'm almost embarrassed to ask, but I have not been able to see how to allow local drives to be redirected. I have version 1.7C.

Thank you.
Coordinator
Jan 12, 2009 at 8:56 PM
New or Edit existing connection

RDP Tab
Local Resources sub tab

Automatically connect to these .....

Is that what your looking for?
Jan 13, 2009 at 2:01 PM

Yes - Thank you

John Rose
Database Administrator

FoundationIP - Part of CPA Software Solutions

Direct Dial: +1 612-236-9917
Email: jrose@foundationip.com
Fax: +1 612-332-0080

Computer Patent Annuities North America LLC / FoundationIP
900 Second Avenue South Suite 1560
Minneapolis, MN 55402

CPA is a leading provider of outsourced legal support services and the world's top intellectual property management specialist. , For further information about our products and services go to www.cpaglobal.com.




RobChartier <notifications@codeplex.com>

01/12/2009 03:56 PM

Please respond to
Terminals@discussions.codeplex.com

To
jrose@foundationip.com
cc
Subject
Re: Connect to local drives [Terminals:43200]





From: RobChartier

New or Edit existing connection

RDP Tab
Local Resources sub tab

Automatically connect to these .....

Is that what your looking for?

Read the full discussion online.

To add a post to this discussion, reply to this email (Terminals@discussions.codeplex.com)

To start a new discussion for this project, email Terminals@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorized.

If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************
Mar 19, 2010 at 2:50 PM
jrose2 wrote:
Great product. Much better than the Microsoft Remote Desktops that are a part of the Windows 2003 admin pack.

This is probably a very simple question and I'm almost embarrassed to ask, but I have not been able to see how to allow local drives to be redirected. I have version 1.7C.

Thank you.

It would be great if this product had a flag to the RDP \ Local Resources so that we could eliminate network drives from the 'Disk drives' selection box.  Might be too dificult a task to mirror the Microsoft ability to select individual local drives to include in the RDP session (and make it difficult to import connections to other users) but would be of great help if I could at least have the RDP session ignore any network drives that I have mapped to my local PC/laptop.  As it is now, when I check this RDP\Disk drives selection I end up with all of my local network drives appearing in my terminals session and all I really want are what are truly only my actual local devices.  Running XP 32-bit.

RDP Tab
Local Resources sub tab

Automatically connect to these .....

Steve Hough

 

 

Aug 5, 2010 at 4:54 AM
I've noticed in v1.9a on Windows 7 64bit -- that the button labelled "Disk Drives & Plug and Play Devices...." does nothing. So, can't use Terminals to RDP and share a drive.
Aug 20, 2010 at 12:22 PM
Sikosis wrote:
I've noticed in v1.9a on Windows 7 64bit -- that the button labelled "Disk Drives & Plug and Play Devices...." does nothing. So, can't use Terminals to RDP and share a drive.

I have same experience on Windows 7 32b :-( The previous versions of Terminals works fine. Is there any workaround or fix for this?

Aug 23, 2010 at 5:32 AM

In the release notes in v1.9a it says: "Ability to select individual Drives and Devices added (Device selection is on or off at the moment)"

It might be this on or off thingy that is preventing from selecting anything (off by default?) or maybe there's a problem with win 7 (mine is x64). I've read a thread in here where individual drive selection feature was requested. Then it was implemented in the beta.

If there is a setting somewhere that enables drives' selection can anyone write instructions on how to enable it?

Aug 23, 2010 at 8:52 AM

I am using 64-bit Windows 7 and drive selection it is working on the version that I am running.

This isn't the v1.9a version, but rather was built from the source code a couple of months ago. 

Aug 31, 2010 at 11:49 AM
sgmoore wrote:

I am using 64-bit Windows 7 and drive selection it is working on the version that I am running.

This isn't the v1.9a version, but rather was built from the source code a couple of months ago. 

Does your version include the old 1.8 Disk Drive select method with a separate check box (the same as for Printers, Serial Ports)? The new 1.9 version has a separate button for selecting drives. But when I click it - nothing happens (this was the case for me with v1.9 beta and v1.9a - if this was not changed since the beta release then there is a chance I'm missing some setting to enable it).

Currently I am using 1.8 that allows to select all drivers for access in a terminal session.

Aug 31, 2010 at 1:11 PM

It has a separate button which opens a dialog box and allows me to select the drives that I want to share.

Sep 1, 2010 at 1:29 AM

Do you mean the button called "Disk Drives & Plug and Play Devices..." ... because when I click that, nothing happens.  Where's the configuration files for Terminals kept ? Just wondering, if I can just edit a text file or registry entry in the meantime.

Sep 1, 2010 at 12:49 PM
Edited Sep 2, 2010 at 6:40 PM

Configuration details are in the terminals.config file, so you can edit it with notepad, (such make sure you have a backup and that Terminals is not running when you edit it.).

For each connection you will have a line such as 

 desktopSize="AutoScale" colors="Bit16" sounds="DontPlay" redirectDrives=""

you can try changing this to, for example, 

 desktopSize="AutoScale" colors="Bit16" sounds="DontPlay" redirectDrives="C:;E:"

or

 desktopSize="AutoScale" colors="Bit16" sounds="DontPlay" redirectDrives="true"

 

 

Sep 2, 2010 at 9:03 AM

Just tested sqmoore's suggestion.

It works perfectly.

I did a search-and-replace on my  terminals.config and changed the redirectDrives value for 300 hosts in just a minute

@ sqmoore: I think there's a typo in your post:

it should be

redirectDrives="C:;E:"
and not
redirectDrives=""C:;E:"

 

Sep 2, 2010 at 2:53 PM

I am running Vista 64 bit using Terminals 1.9a and I can get my local drive redirected with no problem, but my network drives do not show up. I remember this working in an older release. Sure enough, I have version 1.7e laying around and when I use that version all my drives, local and mapped network drives show up. I tried sqmoore's suggestions and changed the terminals.config in my 1.9a version file accordingly with all my network mapped drives and still only see my one local drive.

John Rose




"tomium" <notifications@codeplex.com>

09/02/2010 04:03 AM

Please respond to
Terminals@discussions.codeplex.com

To
jsrose@cpaglobal.com
cc
Subject
Re: Connect to local drives [Terminals:43200]





From: tomium

Just tested sqmoore's suggestion.

It works perfectly.

I did a search-and-replace on my terminals.config and changed the redirectDrives value for 300 hosts in just a minute

@ sqmoore: I think there's a typo in your post:

it should be

redirectDrives="C:;E:"

and not
redirectDrives=""C:;E:"

Read the full discussion online.

To add a post to this discussion, reply to this email (Terminals@discussions.codeplex.com)

To start a new discussion for this project, email Terminals@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com


The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.
If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.

Sep 2, 2010 at 6:43 PM

To tomium

You are correct, there was a typo . My apologies. 

I have edited my original entry to correct this.

 

To Jrose2

You could try setting redirectDrives="true" rather than specifying drive letters.

This works for me on my laptop (32-bit XP Professional), but not on my desktop (64-Bit Windows 7) where it just redirects my local drives (including all the drives allocated to SD Cards and MMC drives etc), but not the mapped drives.
But even Mstsc does not allow me to select mapped drives on Windows 7 which it does on XP.



Sep 2, 2010 at 7:02 PM

Thank you sgmoore for your feedback. I did have the redirectDrives set to "True" originally and got the same results.

I will have to respectively disagree on your assertion that Mstsc does not redirect network drives. I just tested that and the network drives are showing from My Computer on the remote server. All drives except C are mapped network drives.



I'm using version 6.0.6002.18005 of mstsc.exe connecting to a Windows 2003 Server.

Thank you for your continued efforts.

John Rose
Database Administrator

CPA Global
jsrose@cpaglobal.com
Direct: 612.236.9917
Mobile: 612-308-0215
Fax: 612.332.0080

900 2nd Avenue South, Suite 1560
Minneapolis, MN 55402

CPA Global is a leading provider of outsourced legal support services and the world's top intellectual property management specialist. For further information about our products and services go to www.cpaglobal.com.



"sgmoore" <notifications@codeplex.com>

09/02/2010 01:43 PM

Please respond to
Terminals@discussions.codeplex.com

To
jsrose@cpaglobal.com
cc
Subject
Re: Connect to local drives [Terminals:43200]





From: sgmoore

To tomium

You are correct, there was a typo . My apologies.

I have edited my original entry to correct this.

To Jrose2

You could try setting redirectDrives="true" rather than specifying drive letters.

This works for me on my laptop (32-bit XP Professional), but not on my desktop (64-Bit Windows 7) where it just redirects my local drives (including all the drives allocated to SD Cards and MMC drives etc), but not the mapped drives.
But even Mstsc does not allow me to select mapped drives on Windows 7 which it does on XP.


Read the full discussion online.

To add a post to this discussion, reply to this email (Terminals@discussions.codeplex.com)

To start a new discussion for this project, email Terminals@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com


The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.
If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.

Sep 2, 2010 at 8:10 PM

>  I did have the redirectDrives set to "True"

It actually has to be "true" (ie lowercase). (Perhaps not in older versions, but certainly in 1.9a). 

> I will have to respectively disagree on your assertion that Mstsc does not redirect network drives.

That's not quite what I said. I said it doesn't to it for me under Windows 7.  

Actually I investigated this a little more and it appears the net use's were marked as 'unavailable' despite the shares being available and in use (but via the UNC name rather than the drive letter).

Once I remapped them, they work in both Mstsc and terminals.

 

Sep 2, 2010 at 8:53 PM

Thanks for the feedback.

Yes, I did have lower case "true" originally.

I will investigate the net uses. When I do a net use from the command prompt several of my drives show a status of "Disconnected", yet I can access the drives from a command prompt or from My Computer. This looks like it may be an issue with how my drives get mapped via domain login script. So we may be on to something here.

Thanks again.

John Rose



"sgmoore" <notifications@codeplex.com>

09/02/2010 03:10 PM

Please respond to
Terminals@discussions.codeplex.com

To
jsrose@cpaglobal.com
cc
Subject
Re: Connect to local drives [Terminals:43200]





From: sgmoore

> I did have the redirectDrives set to "True"

It actually has to be "true" (ie lowercase). (Perhaps not in older versions, but certainly in 1.9a).

> I will have to respectively disagree on your assertion that Mstsc does not redirect network drives.

That's not quite what I said. I said it doesn't to it for me under Windows 7.

Actually I investigated this a little more and it appears the net use's were marked as 'unavailable' despite the shares being available and in use (but via the UNC name rather than the drive letter).

Once I remapped them, they work in both Mstsc and terminals.

Read the full discussion online.

To add a post to this discussion, reply to this email (Terminals@discussions.codeplex.com)

To start a new discussion for this project, email Terminals@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com


The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.
If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.

Sep 15, 2010 at 6:36 AM
prejudiced wrote:

In the release notes in v1.9a it says: "Ability to select individual Drives and Devices added (Device selection is on or off at the moment)"

It might be this on or off thingy that is preventing from selecting anything (off by default?) or maybe there's a problem with win 7 (mine is x64).

That statement about the device selection means that you can only either enable or disable device mappings at this stage.
I don't have any devices that get mapped through this method so I don't have a way to code and test adding individual device selection so it was added as an on or off option for now.
As for drives, they can be individually selected per drive.

When you click the button it does through all drives listed in your system and gathers their information to display the list of drives in the selection box but it does have some error control so that it won't display invalid drives.
I see in the issue thread there is an exception logged there about the problem but I haven't had a chance to check it yet. Might try looking tomorrow if I get some time.

If you can produce any more error logs from the problem that would make it a lot easier to find.
You may need to configure the Terminals.log4net.config to produce log files if you are not getting any.
or download this one and put it in your terminals directory when you run the program and it will create a logs directory in there for you:
http://dl.dropbox.com/u/37057/Terminals.log4net.config