UNSOLVED

bill1arch

updated

3 months ago

B

bill1arch

3 Posts

0

15772

February 23rd, 2004 13:00

Windows License Question and Remote Access

We planning to purchase a new server (PE 1600, w/ Windows 2k3 Small Business server). We have 15 workers, and also want to access our server from home at night. We just need file and print sharing for now, and I do not undersand the license restrictions (ie 5 CALs, etc). Could some explain or send a link that could help us in our goals, or better explain the licenses and procedures for remote access. We need to order a new server ASAP.

Current setup:

cable modem-to-router-to-hub-to-server.

As always, any help is appercaited.

  • ulysses1

    2 Posts

    784

    0

    Posted February 25th, 2004 19:00

    Windows licenses are legal rights to access programs or software, in your case legal rights to access your server by your 15 users. You will need to purchase 15 licenses. You also will have to decide if you want your server to be access by "device" or by "user". By device means only the PC's you assign, by user means from any machine any where. Here is this link that I hope will help you to better undestand licenses. http://www.microsoft.com/resources/sam/lic_whatis.mspx

  • WebExec

    135 Posts

    784

    0

    Posted February 27th, 2004 03:00

    There are 2 licencing modes. Per seat, and per server. Most folks are on per seat.

    Per seat means that each client (workers) has a license of some sort. Per server give you the "free" 5 that come with the purchase of server 2003.

    If your clients or "workers" all have computers running licensed copies of win 2000 or XP your fine because this is the seat license you need. The same goes for people connecting remotely.

    Message Edited by WebExec on 02-27-2004 09:03 AM

  • bill1arch

    3 Posts

    785

    0

    Posted February 27th, 2004 12:00

    So if all of my co-workers have a licensed copy of windows 2000, XP then i should not have any problems with the number of users (up to 15) connected to the server for file print sharing? How does do the windows 98se machines factor in?

    Thanks for the help

  • bill1arch

    3 Posts

    785

    0

    Posted February 27th, 2004 13:00

    I am new to VPN. I was think that Windows 2k3 would allow connection through internet from one static IP to  the office.

    Are you recommending an VPN appliance for security?

    We have a cable modem attached to a router that will attached to a switch then to the server. Our home users all have cable modems.

  • WebExec

    135 Posts

    785

    0

    Posted February 27th, 2004 13:00



    So if all of my co-workers have a licensed copy of windows 2000, XP then i should not have any problems with the number of users (up to 15) connected to the server for file print sharing? How does do the windows 98se machines factor in?

    Yes, if your co-workers all have licensed copies they are fine, same goes for the Win 98 machines. What type of remote access are you planning on implementing? I suggest a mid-range VPN appliance.
  • WebExec

    135 Posts

    785

    0

    Posted February 28th, 2004 02:00

    Security would be one concern of many. The idea of punching a hole in my router to let traffic onto my network is something I don't like.  You sound like your at a smaller site that may not have huge budget. Protected yet simple is a good approach in my opinion. The type of exposure as well as all the roles the server will need to perform make me skiddish. Appliances (your router, firewall, VPN) take the brunt of the burden while the server sits safe and sound dealing with authenticated traffic. There are some decent low cost appliances out there that are good solutions.

  • eugp

    3 Posts

    785

    0

    Posted February 28th, 2004 04:00

    I would like to have answers here clarified.

    5 Client Access Licenses = Either;

    5 machines (device license) regardless of what user is logged in, OR

    5 users (users license) regardless of what machine or location they log in from.

    BUT NOT BOTH!

    So, if you need your users to log into the server remotely, you must set up your licenses as user, because if you set them up as device, the additional device asking for permission to access the server from a remote location will then need another license, which would be 30 device licenses for the original poster.

    However, if you set up the licenses as user, only those users will be able to access the server, but they may do so from anywhere. If you hire another employee they would either need another license, or two employees would have to share a user id.

    Just because a machine is installed with a licensed copy of XP does not mean it is allowed server access, it must also have a server CAL, either assigned to the user logged onto the machine, or the machine itself.

    It is also my understanding that if the first license is device, the rest of the license group must also be device. And that once a license is either device or user, it cannot be changed.

    Am I also correct that to access a server with terminal services would need an additional terminal services license? Or would a user license using terminal services to access remotely be accepted?

    I suppose I could ask this over at the MS support site, but it seemed like an appropriate thread going.

    Thanks for any help,

    Eugp
  • WebExec

    135 Posts

    785

    0

    Posted February 28th, 2004 06:00


    I'm pretty sure that I'm not wrong here since we just went through a true up with MS.

    When you install a MS server product you ge the option to set licensing for per server or per seat. Depending on the version of server you are installing he names are different. Server = 5 User, Seat = Device or in other words machine. Also If you choose seat the 5 "free" go away. You get the 5 included users only  when selecting per Server licensing.

    MS OS licenses cover the device (the computer) and only the device. If you needed a license for every user than just about every family in America is in violation of the TOS.

    "Just because a machine is installed with a licensed copy of XP does not mean it is allowed server access, it must also have a server CAL, either assigned to the user logged onto the machine, or the machine itself."

    I believe this is incorrect. The licensed copy of the OS acts as the CAL for "per seat" servers. If you had a dummy terminal (to use terminal services/Citrix) or a Linux box than yes you would need a CAL

    I'm not an expert on licensing by any means and it can get confusing as heck. This is coming from being in charge of the licensing for my organization and participation in numerous MS true ups. As always I can and may be wrong but so far so good with our 33 servers and 1700+ clients. Now I may have to run off the MS and see if spread any bullxxxx.

    Message Edited by WebExec on 02-28-2004 02:08 AM

  • WebExec

    135 Posts

    785

    0

    Posted February 28th, 2004 06:00


    @eugp wrote:

    5 Client Access Licenses = Either;

    5 machines (device license) regardless of what user is logged in, OR

    5 users (users license) regardless of what machine or location they log in from.

    BUT NOT BOTH!


    Forgot to take a stab at this one. This is true but once you choose device (which = seat) you cannot go back.
  • theJapester

    1 Rookie

    •

    42 Posts

    472

    0

    Posted March 5th, 2004 04:00

    Where to begin? Microsoft licensing these days is so confusing...

    First, if you have 15 users running Windows 2000 Pro or Win98SE or whatever and you buy a copy of SBS (Small Business Server) that comes bundled with 5 CALs (i.e. Client Access Licenses), then you are still short 10 licenses/CALs. The client OS licenses only cover the client. Your server CALs are what cover connecting those clients to a server.

    From a generic Windows server standpoint, you still need a server CAL for each device or user (you have to decide which up front) that will be connecting to your server. In the case of SBS, its even trickier. You have to have SBS CALs, which are above and beyond standard server CALS because they include licenses to things like Exchange (and in the case of SBS Premium: SQL Server and ISA Server), that a standard server CAL doesn't cover. Back to your above example, if your users are connecting from work and from home, you are now short 10 SBS user CALs. (User CALs because you have 15 users connecting from potentially 30 or more devices.)  Each single SBS CAL runs for $99 list price, but is less if buying from a provantage ($332.70/5) or an Open License agreement. Figure about another grand on top of your SBS 2003 w/ 5 CALs included.

    Next, SBS doesn't run Terminal Services. Its not included, in part because its your root-level domain controller -- according to Microsoft. You can have up to two administrative remote sessions, that's it. What it does do is allow your users to connect to their actual XP desktop computers at work from home, via Remote Desktop through the SBS. They can also VPN in for file/print/email services (SBS has a nice wizard for configuring this). If what you REALLY want is Terminal Server sessions for your home users, you'd have to buy another (non-SBS) Windows 2000 or Windows 2003 server. PLUS, TS licenses in 2003 now require a separate TS CAL (separate from the server CAL). This gets expensive quickly, and with Linux breathing down Microsoft's neck I can't imagine why they wouldn't essentially give this away based on a client OS license or server CAL, but they don't anymore. Here is a link to the MS whitepaper on TS licensing:

    In summary, from the Windows Server 2003 Licensing FAQ:
    Q: What is the difference between a Windows CAL and a Terminal Server (TS) CAL?
    A: A TS CAL is required only when a user or device is accessing or using the terminal server functionality of Windows Server. A Windows CAL is required when a user or device is accessing a Windows server (except as noted in the answer directly above).

    My answer: A TS CAL is more than twice as expensive as a regular server CAL.

    Finally, a word to the wise. If you buy the server OS (SBS or whatever) bundled with your Dell server or some OEM version off the web then that server OS is permanently linked to that one server and only that one server. This is OEM licensing and works the same way as OEM client OS licenses (i.e. bundled XP with a laptop or desktop). The only way to hedge against that server someday completely dying and taking your server OS license with it is if the server is replaced by your system builder (i.e. Dell) under warranty. So if you buy an OEM/bundled SBS, or Win2003 for that matter, is to pay the extra $$$ and opt for the 3 year warranty.