Re: Licensing Error Messages that don't make sense

Brandy,

Thanks for the information! I've done as directed by you and the KB
article, and event 202 is still appearing in my application log. I'm not
clear what the licensing console on a member server should display for a
*correctly* configured member server, but here's what I've got:

(This is all from the Licensing console on one of the Server 2003 Standard
member servers)

*Purchase History Tab:*
I visited all four of my member servers (two running 2000 Server and two
running Server 2003 Standard) and configured licensing as suggested. Each
time I completed that process on a member server, the Purchase History
showed an additional "purchase" of 30 licenses for that date. Because the
results were not as expected, I went thru this process more than once for
some of my servers. There are now 7 history items listed in this window;
Six of them are identical, showing a purchase of 30 licenses. One shows a
reduction or removal of 150 licenses, which I did because it appeared that
my actions had resulted in a total of 180 licenses being
purchased/installed.

*Products View Tab*
Four columns appear at the top of this window. They are, in order from left
to right:
Per Device or Per user Purchased
Per Device or Per User Allocated
Per Server Purchased
Per Server Reached
Four products are listed. Here they are, with their respective values for
each of the four columns:
Microsoft BackOffice 0 0 0 0
MS Exchange Server 2003 0 0 750 0
MS SQL Server 7.0 0 0 27 0
Windows Server 30 153 35 26

*Clients Tab*
Many users appear here; even ones that pre-date the domain and user accounts
that have been deleted and/or no longer exist. Every single user listed is
counted as Unlicensed Usage, and nobody falls under Licensed Usage. The
only product shown in the Products column is Windows Server.

*Server Browser Tab*
If I select any server listed within the network and right-click & choose
properties, The Products View tab shows the proper licensing mode (Per
Device or Per User) for Windows Server, and Licenses Purchased shows "n/a".
The exception to this is if I select the SBS 2003; the Products View tab on
that server shows Windows Server as using Per Server licensing mode, with 35
Licenses purchased. Interestingly (to me), the listing for Exchange Server
2003 that appears here shows Per Server licensing with 750 (?!) licenses
purchased.

(Remember, all these results appear in the Licensing console opened from a
*member* server running 2003 Standard.)

The Licenses console in SBS 2003 shows 30 installed licenses (25 of them
appear in the lower window, in 5 groups of 5).

I hope this clarifies my situation.

Thanks again for the help so far.

Bryan


""Brandy Nee [MSFT]"" <v-branee@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:v7qlr$wdFHA.2788@xxxxxxxxxxxxxxxxxxxxxxxx
> 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: Windows Server 2003 DC not issuing licenses to Win2K TS/Citrix ser
    ... Change the licensing setting for each Windows Server 2003 Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Software cost of setting up a TS server?
    ... additional Windows server in an SBS domain did require another SBS CAL. ... One email response I received from MS licensing that really got my analysis ... The FAQ regarding needing addition CALs ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing Error Messages that dont make sense
    ... member server on the Server Browser tab using the method you describe. ... I will try your suggestion to delete and recreate the licensing information ... Check the status of Licensing Logging service and make sure it is ...
    (microsoft.public.windows.server.sbs)
  • Re: XP Home User Temp Licence from W2K TS Box
    ... Keep an eye on the TS Licensing Manager on the 2003 DC, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... CALs issued. ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Software cost of setting up a TS server?
    ... My first real look into licensing was for a 2000 TS, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... that an additional Windows server in an SBS domain did require ... Several others disagreed and said the SBS CALs ...
    (microsoft.public.windows.terminal_services)
Loading