Windows Forum

Ask something
Discussion Locked

Virtual "C" drive with Terminal Server

0 helpful
4 replies

by italo

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I had implemented Terminal Server over a Windows 2000 Server, the probles is that our applications (developed with Visual FoxPro) use a c:\temp and a c:\repositorio on each machine. When we run the applications remotley with Terminal Server on more than one client we have a share error (one user open the application first) and the second user can't open the application because is wainting for the unlock of the files shared in the directories.

What can we do?

Thansk!

Italo

4 replies

by black panther

Is it possible to re-write the application to create a separate /temp directory for each user that accesses ie

c:\temp\user1
c:\temp\user2 etc

by italo

It was one of our initial options but it's extremely costly, for that reason I want to know if is possible to assign a virtual "C:\" for each Terminal Server session or something else without modify our applications.

Thanks anyway

by bfilmfan

Since the code is running on the Terminal Server, what is the point of trying to create virtual C: drives out on the client? Other than emulation, applications running on the Terminal server can't access the remote clients.

Time to mark this one down as an expensive lesson in software project design and re-work the code.

by p.j.hutchison

Best thing to do is use profiles ie
%USERPROFILE%\Local Settings\Temp
%USERPROFILE%\Application Data\Repositorio

Which should get round the problem

This discussion is closed to new replies.