Need some help with drive mapping in terminal services for both mac and pc
 

We have a hosted server running Elusiver Terminal Server Pro. Runs a dream :thumb:

All the clients can log in and have their sessions. All good

Issue is we want to be able to map a folder/drive ( drive D) that holds images onto the clients actual desktops (rather than the sessions) so when they log in, they can transfer files from one machine to another. Now various sources say this is best done that the share is on the TS client, mapping back to the client desktop but I cant quite get my head around it.

Oh and also , into the mix we have one mac user running OS 10.5 that is the main user of images so we have to get it working on the mac as well.


Anyone help out a frustrated IT admin :)

the blurb for elusiva suggests it does "local drive mapping" -- which I take to mean you map a share onto your local desktop, and thats what you want to do isnt it

mmm yes I think so, but putting it into practice is proving somewhat an issue.grrrr

are the desktops located over a wan?

and are you using the MS remote desktop client

Yes, the users are all remote users, the server is hosted by fasthosts.

The PC's are using the Remote desktop client as is the mac.

I am testing the mac as it is now and whilst I can connect to the session fine, I am doing this :brickwall on the local drive mapping

Right sorted the printing as the latest version of RDC for mac allows remote printing so that is all fine. It also says you can share the local mac drive/folder but that does not work for some reason ???

Firewall rules checked, the mac even has the drive sharing and the TS group policy seems to be fine ???

If you are using the RDC and depending on the version, before connecting to the server, click "options", select the "Local Resources" tab then click "More" and you local drives are there..