Setting up Terminal Server for the first time

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( ).

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!!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You would need to install the client piece of the software on the Terminal Server just the same as you would any other workstation that would run the software. For example, you would install MS office to the TS to allow all of the TS users to run the applications. If you need to map drive letters only for the TS users, look for the user.cmd fie in the Windows directory and make your modifications there.

Hope this helps.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.