Picking up something on Tim said, in my experience I've never needed
any CALs whatsoever. I've always had teh server serving some data
access or whatever and all connections to those services have either
been web access or similar generic calls from locally-run apps -
because I've never had any actual specific user with accounts log in
to the server and have specific user stuff on there you don't need
CALs.
Even if your VB app is using specific user logons, you may still not
need CALs because you're only transferring data to a central store.
You will need CALs if you're storing user-specific information on the
server and local user accounts require authentication with the server
and retrieve settings (like a domain logon).
So yeah, work out exactly how, what and why the VB app is connecting
to the server, how that relates to user logos and then call M$.
MOU
2008/11/12 Furry, Tim [EMAIL PROTECTED]:
Matt wrote...
The Server will be running a bespoke database application and therefore
clients will be accessing the database. The clients will _not_ be accessing
any file/print services on this server, although they will be authenticating
against it.
I started to look into this however I can't work out if they organisation
needs extra licenses for the desktops if all they are doing is authentication
and access a database that is not an MS product.
Tim replies...
It depends a lot on your application and its footprint. For instance, we put
in a Win2k3 server but I knew it was only going to serve web apps, so it
doesn't need CALs and we were able to go with a much less expensive Win2k3
version (web version, it's like $500US). I can't install MS databases on it
due to the web version but our database was elsewhere anyway.
If your clients are running a VB app that is located on the server, I think
you'll probably need CALs since each user will have to authenticate against
the server itself before running the app. If your clients are running the VB
app on local machines and it reaches across the network to access the server
for the database, you may or may not need CALs. It's my understanding that
CALs are primarily needed where users are directly accessing the server to
run some application.
Cheryl recommended calling MS, and I do too, but you need to gather the
required information first. At a former job we got three different answers
from three different MS reps, so it may pay to poke around some. We finally
decided against CALs and structured the situation to keep direct server
logins to a minimum.
HTH...don't take it for written in stone though...MS changes licensing every
so often and it's a real sore spot with small to medium sized businesses. :)
Tim
• The WDVL Discussion List from WDVL.COM •
To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or
use the web interface http://e-newsletters.internet.com/discussionlists.html/
Send Your Posts To: wdvltalk@lists.wdvl.com
To change subscription settings, add a password or view the web interface:
http://intm-dl.sparklist.com/read/?forum=wdvltalk
http://www.wdvl.com ___
You are currently subscribed to wdvltalk as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
� The WDVL Discussion List from WDVL.COM �
To Join wdvltalk, Send An Email To: mailto:[EMAIL PROTECTED] or
use the web interface http://e-newsletters.internet.com/discussionlists.html/
Send Your Posts To: wdvltalk@lists.wdvl.com
To change subscription settings, add a password or view the web interface:
http://intm-dl.sparklist.com/read/?forum=wdvltalk
http://www.wdvl.com ___
You are currently subscribed to wdvltalk as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016
Please include the email address which you have been contacted with.
