I have just installed Windows 2003 server and configured it to run Terminal Server. I had a problem figuring out how to let users log into the terminal server, but was able to get that cleared up(http://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/Q_21202594.html#12551842
But this is my first time setting up and implementing a Terminal server. I was hoping I could get some pointers or links that would apply to my specific needs. That is, I'm setting up Terminal server as a plan B since a client/server application fell on it's face working over the client's VPN. The client has a main location, and 3 remote offices. Roadrunner is the ISP for all locations and providing the VPN hardware and connectivity. The Client/Server application is based on Pervasive SQL, and should have worked with no problem over the VPN. But the vender does not support the WAN environment, and I'm unable to contact Pervasive directly. So that's where I'm at today, implementing Terminal Server so that the 3 locations can connect, and use the client/server application. Only one user from each location will be connecting, and I do see a need to support some users to connect from home.
The Windows 2003 Server is hosting the Client/Server application on the same box running as Terminal Server. A normal client workstation requires that a drive mapping be made that points to the Server's Shared Database folder. While on the server, I don't need the drive mapping as the PSQL client knows where the DB folder is. But while logged via Terminal Server, it's getting various errors which I can't put my finger on yet.
So this leads to my main question. When setting up a terminal server, and the applications (Outlook, Client/Server DB, ect..) that I want users to run on their own virtual session, do I have to install the client piece of the software, and map the drive just like I would need to do at a normal workstation client?
Thanks for any help and assistance!!