Re: DataBase over WAN: ASP vs. Terminal Server Costs?

Arno R wrote:
> Hi all,
>
> I am involved in a project where a client needs a new database over a
> wan (30 or more locations).
> The client is a health-care organisation that 'services' mentally
> disordered people.
> They use Win2003 Server at the moment. All the client PC's are
> Win2000 or Win XP.
>
> At this moment there are two different approaches/ideas considered.
> -- to develop an ASP-web application. (not by me)
> -- to develop an Access97-TerminalServer application. (by me)
> The developing, licencing and the maintenance-costs are very
> important in the decision-making-process.
>
> Until this moment I never went the 'ASP-Route', so ASP is not an
> option (for me).
> If they want me to do the job I will propose the A97-TS approach.
> I can deliver the Access97 runtime (I own the ODE) so there is no
> problem with that.
> (There will be some installation-issues with the Access runtime but I
> think I can handle that)
>
> I read in this ng that TS would be a good approach in a wan-scenario.
> However I have NO idea of the TS-licensing costs.

Terminal Server licensing is complex so ultimately you should dig through
Microsoft's articles on this, but I can tell you that each user "connecting" to
the Terminal Server needs a license to do so unless you purchase the kind of
license for your server that is "per processor" rather than "per connection".
The former while simpler sounding is a lot more expensive targetted at sites
that want hundreds or thousands of users (not your situation).

Older versions of Windows Server Edition granted one connection license if the
user doing the connecting was using NT 4.0 or higher of an operating system.
With the newer versions of Windows Server that is no longer the case.

Once connected they also need licenses for any apps they run. If you install
the Access app on the server using the Access Runtime then you are off the hook
there. If you use full Access then every connecting user must hold an Access
license. If using the Runtime watch out for things like using Outlook to send
messages or doing merges to Word. Those features would require that the remote
user have license to those pieces of software.

Bottom line is the TS solution would get you up and running a lot faster and
will allow you to retain the rich Access interface that you have now, but it is
not a free lunch.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com


.

Relevant Pages

  • Re: can someone help clear this up?
    ... Terminal Services Client Access Licenses are assigned to the client, ... The Terminal Services License Server ...
    (microsoft.public.win2000.termserv.clients)
  • openvpn for windows server
    ... -My requirement is client should have 192.168.10.0/24 ipaddress and it ... I am able to connect client to server, but i am not able to ping any ... I am attachting the server config and client config file, ... # clients or if a connecting client has a private ...
    (comp.os.linux.networking)
  • RE: Demand Dial Problems
    ... I think you might be right on the License issue. ... Office) connected and the server that has been connecting (Indy Branch ... connect to SBS and got some error message. ...
    (microsoft.public.windows.server.sbs)
  • Re: Client disconnected problem
    ... Resetting a thin client to the factory default is ... That would lead to the issueing of a new license (the ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Client on the PPC. ...
    (microsoft.public.windows.terminal_services)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)