How to allow more remote desktop connections onto a computer 1

[djpingpong]

Hi all,

I've got an old computer that's only running MS Access and SQL Server. The purpose of this old computer is so that all the other workstations here at work would use Remote Desktop Connection to connect and run the MS Access application. Whether that's the most ideal situation or not, it doesn't matter because this was setup years ago before I started working here.

Anyway, my job now is to move the application to a newer, faster computer so it's not so slow running the application over Remote Desktop Connection.
Now, I know how to use RDC, but i'm not very good dealing with the licensing issue.

So far, I've got a new computer and I've got everything running smoothly on the new computer with regards to the Access application. The migration went pretty flawless until people started connecting to it.

THE PROBLEM:
The old computer would handle more than 10 remote connections all logged in under various accounts (admins, users)
However, the new computer would only handle 2 remote connections. How can I increase the number of RDC to connect to the new computer?

again, this is where my lack of licensing skills come in... can anyone help? Do I have to purchase anything or can I somehow configure the new computer to accept many connections like the old computer?

Side note: The 2 computers mentioned above are workstations within our domain. I tried to use Terminal Services Licensing hoping to figure it out on my own. The only thing I found out is that our Licensing server is also our domain controller and it saids that the licensing server is not activated. Not sure if this extra tid-bit helps

thanks

 

[porkchopexpress]

What OS are you using 2000/2003 server only support 2 connections by default, you will need to use it in application mode and purchace some CAL's if you want more connections. In fact you are technically already breaking the licensing if you are in remote admin mode.





When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[djpingpong]

Mmmm... that's interesting..
I didn't know how the last guy set it up... he was long gone before I started workin here..

As for the machines.. they're all running Win2k Server...
Is it possible that the CALs were purchased before... is there anyway I can check that?

There's gotta be a reason why/how the old computer can handle so many incoming remote connections

 

[porkchopexpress]

What servers are you running? You said a DC had a licence server running can you take a look on that?


Take a look at this.

http://www.brianmadden.com/content/content.asp?id=154

When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[porkchopexpress]

I think the new server will need application mode activating and being told to use the licence server. Is the new box running 2k as well?





When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[djpingpong]

Ok, let me clarify a bit here then

old computer (Server1) is current handling 10+ RDC everyday
new computer (Server2) is only accepting 2 (which is normal)
Domain controller (MainServer) has Terminal Licenses Server installed... it's the only machine in our whole network that has it installed. But i dunno how to use it

ALL 3 computers are running Windows 2000 Server

 

[porkchopexpress]

Ok i haven't used 2k terminal services in ages but as i remember you could have it installed on more than one server and the licence server will hand out licences until it reaches it's limit in your case 10.

You will need to install application mode on your new box it can be added in add/remove programs take a look at the link below.

http://support.microsoft.com/default.aspx?scid=kb;en-us;306626&sd=tech

When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[AJP69]

How quickly we forget!

One reason that many people will not upgrade from W2k Terminal services is that in W2k3 MS charges per user/device.

Under W2k any W2k PC or XP PC workstation includes a CAL (Client Access License). So if you keep it all Windows Server 2000 you will not incur costs, albeit that the functionality is less.

Now the reason you have only 2 users is that you have not installed Terminal Services, what you have is the basic 2 admin only accounts that come with every server.

You need to install Terminal Services from the Control Panel, Add Programs, Add windows components. BUT you need to do this BEFORE you install ANY apps, e.g. MS Office or MS Access Runtime.

There are also numerous bugs with the Access Runtime so you will need SP3 of the Access RUNTIME serice pack or later if you app dictates.

The licensing for W2k is incompatible with W2k3 so you can't mix and match. If you have a W2k3 server, wipe it and install 2000.

Then install the terminal server licensing on the domain controller and let it manage your CALS (it is in the same

The best config for an Access App is a multihomed server with 100mb clients on 1 nic and a GB Nic on an interserver lan. It is crap if you install the SQL server on the same box as TS, you would be better off using the old server dedicated for TS. All you do is get a couple of SERVER gigabit cards and stick them on a private GIGABIT switch on a private LAN.

Access works best on TS if you use the runtime NOT the full app, although you may install Word and Excel if you use their functions in your app (e.g. spell check).

Don't be tempted to upgrade any component of your infrastructure unless you are prepared to upgrade all of it, i.e. SQL 2005, Windows 2003, XP workstations and extra bucks for CALS.

 

[porkchopexpress]

Nice one AJP69





When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[djpingpong]

Oh, I just found something out..
apparently, our company purchased some CALs a long time ago and someone finally remembered to fill me in.

Hence, my problem is solved now because I changed the TS computer from Remote Administration to Application Server mode...

thanks all for helping..