RE: Licensing Error Messages that don't make sense



Hello Bryan,

Thank you for posting to the SBS Newsgroup.

>From your description, I understand that you have 26 SBS 2K3 users, and on
the SBS 2K3 server, three is error 202. If I have misunderstood your issue,
please let me know.

Please see my information below:

Is there a member server in your SBS 2K3 domain? Based on my experience,
this issue may be recorded if licensing is not properly configured on
additional member servers. If there is another Windows server on the
domain, it will use one CAL to connect to the SBS server and should point
to it for licensing. The SBS CALs will cover those same clients accessing
that member server.

Go to the member server, click Start -> Run, type "Services" and click OK.
Check the status of Licensing Logging service and make sure it is running.
Click Start, point to Administrative Tools and click Licensing. In the
licensing window, switch to the "Server Browser" tab. Expand the domain and
the member server name. Open the product properties (Windows Server) of the
member server. Change the licensing mode to "Per Seat" for Windows 2000 or
to "Per Device or Per User" for Windows Server 2003 and click OK. In the
window, click License -> New License. Select "Windows Server" from the
drop-down list and specify the same number of licenses that your SBS server
has. Click OK to close the dialog box.

After doing these steps on the member server, wait for a few minutes and
then go to the SBS 2003 server to see if there is any new licensing warning
occurs.

For more information, please see the following KB article:

327644 How to configure licensing on an additional Windows server in an SBS
http://support.microsoft.com/?id=327644

In SBS 2K3, there is either User CAL or Device CAL. You need to check with
the Windows Small Business Server 2003 Client Access this paper and know
what CAL you are using now.

I am appreciated your time and hope this information helps. If anything is
unclear, please let me know. I am looking forward to hearing from you!

Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • Re: Add a DC to remote site via VPN
    ... I believe the licensing is the same on ... one in California are PE 1900 servers. ... that for the SBS migration but because of the OEM licensing I can't do ... server and reinstall W2K3, join it into the domain and ship it to ...
    (microsoft.public.windows.server.sbs)
  • Re: Licensing, CALs and Server 2003
    ... As an example, a BDC can become a PDC, but an RODC will not be anything but ... have a change starting in Server (and SBS) 2008. ... Windows Server farm where the roles can be distributed. ... As for the licensing questions, best to speak with a licensing ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS on two systems
    ... The following is a direct copy and paste from the Microsoft Licensing Product Use Rights Documents found at: ... Running Instances of the Server Software. ... the second SBS to boot will see the first (in my ... The same SBS install, ...
    (microsoft.public.windows.server.sbs)
  • Re: Software cost of setting up a TS server?
    ... The first time I looked at a TS licensing document, ... Regarding whether or not all other Windows servers are covered by SBS CALs, ... Windows Server 2003 Client Access License ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing model
    ... SBS doesn't do concurrent licensing. ... Historically speaking, in the Windows server world ... CALs for each server on our network, and the number of CALs on a given ...
    (microsoft.public.windows.server.sbs)

Loading