SBS server 2003 and Terminal Server 2003

[fixtar]

Hi,

I need to setup a remote office and at the main office have a sbs server 2003 running. Have an application that will be used eve nby remote office. Have already tried VPN setup for remote office users but seem to have an issue of disconnection and the application is not seemless.

The application provider suggested to have Terminal server setup for remote office to get connected and use the application.

Can someone pls guide me on how to setup a Terminal server 2003 to work along with SBS server 2003.

Regards,
MJ

 

[ShackDaddy]

Set up a new server in the main office running Windows 2003 Standard. Add it to the domain. Use the Add/Remove Windows Components tool to add the Terminal Services and Terminal Server Licensing components. Install the applications that you need on that server.

Alternately, if your SBS server's hardware is good enough, you could install Microsoft Virtual Server 2005 on the SBS server and set up a virtual copy of Windows 2003 Standard server and enable the terminal services as I described above.

There's more to it than that, but that should give you a direction to go.

ShackDaddy
Shackelford Consulting

 

[fixtar]

Thanks for your input.

I have installed the windows 2003 server std edition and have got my Terminal server licenses as well from my reseller.

I have joined the w2k3 server to the SBS server domain. After installing the CAL's, have created 5 users in w2k3 server as remote desktop user profile. But apparently only one out of the five can connect at a time!!

What needs to be changed or entered to allow all of them to connect to the server at any given time?

Thanks once again for your time and help

Regards,
MJ

 

[ShackDaddy]

Did you rerun Terminal Server setup from the Add Windows Components area and set it to Application mode? Sounds like you might still be running it in Admin mode, which limits the number of connections.

Also make sure you install the Terminal Services Licensing Server on that system, which it sounds like you may have already done if you've plugged CALs in.

ShackDaddy
Shackelford Consulting

 

[fixtar]

Yes i have already activated the Terminal Services lic Server on w2k3 box.

But as far as your first point switching to Application mode from Admin mode..How would i do that?

 

[ShackDaddy]

I believe that when you add the Terminal Server component, it gives you a choice during the setup wizard.

http://support.microsoft.com/kb/306626

ShackDaddy
Shackelford Consulting

 

[fixtar]

Ok got the remote users to log in to the server and run the database application. They seem to run fine in using the application.

I did notice that in the settings of Remote desktop Connection-> Local Resources-> use local printer even though thats selected, they aren't able to view it on the Terminal server while using the application.

What settings would i need to change or enable to allow them print locally from the application accessed thru terminal server?

Thanks for all your help.
MJ

 

[ShackDaddy]

The printer needs to be installed on the tserver. Log onto it while one of them is connected, and install the printer as if it was a local printer. Then the drivers will be there. Look through the ports list, and you will see that there is a TSPORT listing for the users who's currently logged on and has a printer connected. If nothing's showing up, try having the user share the printer, although I might be offbase on that.

ShackDaddy
Shackelford Consulting

 

[TechSoEasyMVP]

Actually, only the printer drivers need to be installed on the Terminal Server. Open up Printers and Faxes on the TS, and then on the main menu of that window click File > Server Properties > Drivers Tab. Then you can add the appropriate driver for the printer that the remote user(s) need.

There is a full guide to joining a Terminal Server to an SBS network here:

http://sbsurl.com/sbstss

Make sure that you've done all the things it advises so that you won't have problems later on.

Jeffrey B. Kane
TechSoEasy

http://www.techsoeasy.com