Setting up Terminal Server for the first time

Posted on 2004-11-11
Last Modified: 2010-04-19
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!!
Question by:Thirt
    1 Comment
    LVL 1

    Accepted Solution

    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.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    What Is Threat Intelligence?

    Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

    Scenerio: You have a server running Server 2003 and have applied a retail pack of Terminal Server Licenses.  You want to change servers or your server has crashed and you need to reapply the Terminal Server Licenses. When you enter the 16-digit lic…
    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    Internet Business Fax to Email Made Easy - With eFax Corporate (, you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
    Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now