Re: Licensing Error Messages that don't make sense

Brandy,

Thanks again for the info. I've already been thru steps 1 & 2 several
times; all member servers are running the Licensing Logging service and all
are using Per Device or Per User mode, and I've added 30 licenses to each
member server on the Server Browser tab using the method you describe.

I will try your suggestion to delete and recreate the licensing information
and post back with results. Am I correct in thinking that only domain
controllers participate in license replication? If I delete and recreate
the licenses on the SBS DC, will any follow-up action be necessary on the
member servers? Perhaps I'll need check for the items listed in steps 1 & 2
and redo any that appear to be needed?

Thanks again,

Bryan



""Brandy Nee [MSFT]"" <v-branee@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:SZXkTFLeFHA.3404@xxxxxxxxxxxxxxxxxxxxxxxx
> Hello Bryan,
>
> Thank you for posting back.
>
> I understand that you have four member servers. Please see my suggestion
> below:
>
> 1. 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.
>
> 2. 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 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.
>
> 3. The possible cause of the 202 error message is that License Manager has
> a corrupted or incorrect purchase history record. To resolve the issue,
> please follow the steps below:
>
> I suggest that perform a full backup before you perform following steps:
>
> Backing Up and Restoring Windows Small Business Server 2003
> http://download.microsoft.com/download/b/d/8/bd8e1a40-d202-429a-8eb7-26300d6
> 2bcc9/BKU_bkuprstr.doc
>
> 1. Stop the License Logging service.
>
> 2. Delete or rename the following files on the primary domain controller
> or
> the enterprise server:
>
> - Cpl.cfg, which contains all of your purchase history and is located in
> %Systemroot%\System32.
> - Llsuser.lls, which contains the user information on number of
> connections
> and is located in %Systemroot%\System32\Lls.
> - Llsmap.lls, which contains License group information and is also located
> in %Systemroot%\System32\Lls.
>
> 3. Restart the License Logging service.
>
> 4. Re-add the appropriate license information.
>
> For additional information, please see the following article in the
> Microsoft Knowledge Base:
>
> KBLink:194065.KB.EN-US: How to Reset License Manager Throughout an
> Enterprise
> http://support.microsoft.com/?id=194065
>
> Hope this information helps. If you have further questions or concern on
> the issue, please feel free to let m 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: 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: XP Home User Temp Licence from W2K TS Box
    ... Note also that there are already *9* temporary Per Device TS CALs ... MCSE, CCEA, Microsoft MVP - Terminal Server ... A 2003 TS Licensing Server can handle TS ... * then you have to install the licenses on the 2003 TSLS. ...
    (microsoft.public.win2000.termserv.clients)
  • 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)
  • Re: Licensing Help
    ... You cannot assign TS CALs, not to specific users and not to ... Regarding the consolidation of your TS Licensing Servers: ... you can let the 2003 TS Licensing Server handle all of the ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing Error Messages that dont make sense
    ... *correctly* configured member server, ... (This is all from the Licensing console on one of the Server 2003 Standard ... Device or Per User) for Windows Server, ...
    (microsoft.public.windows.server.sbs)
Loading