|
-
Jul 1st, 2003, 04:52 PM
#1
Thread Starter
New Member
Visual Basic and Application Server
What does it take to move a Visual Basic app, that usually runs in a client-server environment, to an application server? Or this is not possible?
Your help is much appreciated.
Thanks.
-
Jul 3rd, 2003, 03:13 AM
#2
Retired VBF Adm1nistrator
Are you referring to Terminal Services or some new fangled Microsoft technology ?
Microsoft MVP : Visual Developer - Visual Basic [2004-2005]
-
Jul 3rd, 2003, 08:42 AM
#3
Thread Starter
New Member
I am not sure. A server where all applications are installed (instead of client machines). This is supposed to save money in terms of upgrading, and so on. Because work is done on one machine instead of 1000 users desktops. I heard about this, but don't know how it is done.
Thanks for answering.
-
Jul 18th, 2003, 09:50 AM
#4
Retired VBF Adm1nistrator
That is Microsoft Terminal Services that you are referring to.
It comes with Microsoft Windows Server, but you must license the client seperately.
Client Licenses are far cheaper than it would cost to purchase Windows Professional. You are given a grace period of 90 days from the time users first start using Terminal Services until a time when they will be denied access to the server unless you purchase Terminal Services Client Access Licenses.
All processing etc. is done on the server itself, so you can use very low-spec client machines.
In theory you could run Office XP sortof on a Win3.11 machine
Microsoft MVP : Visual Developer - Visual Basic [2004-2005]
-
Jul 18th, 2003, 11:04 AM
#5
Thread Starter
New Member
Thank you plenderj.
Good information.
-
Jul 18th, 2003, 11:14 AM
#6
Retired VBF Adm1nistrator
You're welcome, and if you need a quotation on the software - juse e-mail me
[email protected]
Microsoft MVP : Visual Developer - Visual Basic [2004-2005]
-
Jul 18th, 2003, 11:59 AM
#7
Thread Starter
New Member
Could you elaborate more about the architecture or point me some where I can do the research?
What I like to know is:
(a) I assume I need a machine for the server
(b) which software (Windows 2000 server, MS Terminal Services) runs on which machine.
(c) and so on.
Thanks.
-
Jul 19th, 2003, 07:50 AM
#8
Retired VBF Adm1nistrator
"Microsoft Terminal Services" comes as part of "Microsoft Windows Server".
So if you install Windows 2000 Server or Windows 2003 Server on a machine, you can install Microsoft Terminal Services as a part of that.
Then you install the Microsoft Terminal Services Client on client machines, and that allows the user to log in to terminal services.
Each user has their own desktop that appears inside the terminal services client.
Imagine it is a proper individual personal computer running on terminal services, and you are viewing it through terminal services client.
Applications are executed on the server itself - so you can have very low-end hardware on the clients - the only requirement is that the computers be able to run terminal services client.
Microsoft MVP : Visual Developer - Visual Basic [2004-2005]
-
Jul 21st, 2003, 12:29 PM
#9
Thread Starter
New Member
-
May 9th, 2004, 09:14 PM
#10
Fanatic Member
Microsoft Terminal Services looks great....
However looks pretty expensive!
If I understand correctly, You need a Windows 2000 Server running...(costs a fair bit)
and then each terminal needs its own licence, at around $100 US a year ???
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|