Re: how many licenses?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



thanks, I think that cleared it up


Gregg Hill wrote:
William,

I have already answered your question, "Is there a need for licenses for the home computers that connect to the server from the outside?" See the bottom of page 13 of the PUR for clarification of remote access.

The key here is in my previous statement, "...the person accessing the work computer from home is the primary user of the work computer...." If that is true, and you have a server CAL for each of your users to connect to the server while at work, then to access the work computers remotely via a Windows 2003 Terminal Server requires only the additional TS CALs, one per user.

Your OS license for each desktop allows remote access to that desktop from ANY computer, as long as the **person connecting is the primary user of that work computer** to which you are connecting.

The only license needed for the home computers **IF the person accessing the work computer from home is the primary user of the work computer**, is a TS CAL to connect to your 2003 TS.

So, in simple terms, you have:
1) a 2003 server
2) your 2003 server (or another 2003 server) is running Terminal Services
3) you have a 2003 server CAL for each user to work from their respective desktops
4) you have a 2003 Terminal Services CAL for each remote user to connect to the 2003 TS
5) your remote users **who are the primary users** of their respective desktops do NOT need additional server CALs


If you had a Windows 2000 terminal server, then any remote user running 2000 Professional or XP Professional would NOT need a TS CAL.

As far as checking CALs, how many did you buy and install on the server? If you bought 10 Windows Server 2003 CALs and you have 10 users, then each of those 10 users can connect at work or remotely back to their own work desktop. The only additional CALs needed are for accessing the 2003 TS itself, and those are Windows Server 2003 Terminal Services CALs.

"So if every work desktop is already covered we would only need 5 TS CALS" is correct.

Did that clear up your questions?

Gregg Hill


"william kossack" <kossackw@xxxxxxx> wrote in message news:tcKdnTKMb8SVhEjeRVn-gg@xxxxxxxxxx


Is there a need for licenses for the home computers that connect to the server from the outside?

I'm not sure we can count on the work computers having a server CAL. Is there a way of checking each desktop before buying an additional CAL?

Everyone has their own work desktop computer.

So if every work desktop is already covered we would only need 5 TS CALS

Gregg Hill wrote:

William,

When you said you want workers to be able to access their work computers from home, I took that to mean that the workers are already covered by a server CAL at work. If that is the case, and the person accessing the work computer from home is the primary user of the work computer, to access the work computers via a Windows 2003 Terminal Server requires only the additional TS CALs, one per user. As long as the user is accessing their own work computer, i.e., they are the primary user of the work computer, you do not need additional server CALs.

See the PUR doc at http://www.microsoft.com/licensing/resources/downloads/default.mspx

Gregg Hill




.



Relevant Pages

  • Re: Possiblity of adding a second Exchange server to an SBS2003 domain
    ... On the CALs, You'll loose the 5 CALs from the remote SBServer, and ... The Exchange Server 2003 is running here as well ... we have a remote office with 6 users. ...
    (microsoft.public.windows.server.sbs)
  • Re: TS Licensing problem
    ... And is the server OS in Per Seat or Per Server ... client could not connect to the remote computer. ... Remote clients are W2000 ... but it wasn't my intention to mix up CALs ...
    (microsoft.public.win2000.termserv.apps)
  • Re: SBS2003 with Server 2008 Terminal Services
    ... Customers running SBS 2003 R2 can use their CALs to access additional servers running Windows Server 2003, Exchange Server 2003 and SQL Server 2005 Workgroup Edition on the SBS 2003 R2 network. ... See the licensing questions section for additional information on SBS 2003 R2 CALs. ... Remote Web Workplace rather than VPN. ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote desktop protocol
    ... Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2 ... Administration of the server ... If they really need that kind of remote access they will need to ... They already have the cals ...
    (microsoft.public.windows.server.sbs)
  • Re: Reassign CAL on SBS2003
    ... There mostly users who are out of the office and connect via Remote Desktop ... On a standard server I ... The message from licensing _can_ happen even though you are within your ... and how many CALs? ...
    (microsoft.public.windows.server.sbs)