Re: License for a member server

Hi Dieter,

Thanks for your information by mail. After researched those log files, I
found the communication between two DC is correct£®Please double check the
following settings and then reset the License Logging service to see if the
issue be fixed.

I. Go to the SBS 2003 server, open ''Active Directory Sites and Services''.
Click on Default-First-Site-Name and the double click on Licensing Site on
the right. Make sure that the SBS 2003 server is the Licensing Computer.
And

1. Open Active Directory Sites and Services.
2. Click the site where the server is located
3. In the details pane, click License Site Settings.
4. On the Action menu, click Properties
5. Under Licensing Computer, please ensure the SBS server box list here.
6. Under Security tab, please ensure appropriate permissions list as
follows:

--SYSTEM - Full Control, Read, Write
--NETWORK SERVICE - Read, Write
--Domain Admins - Read, Write, Special Permissions
--Domain Controllers - Read, Write, Special Permissions
--Authenticated users - Read
--Enterprise Admins - Read, Write

Verify them and then test to see if the issue be fixed.


II. Go to the additional Windows servers, open Services console in
''Administrative Tools''. Make sure that the ''License Logging services''
is running.


III. Go to the additional DC and member servers, open ''Licensing'' console
in ''Administrative Tools''. Set the licensing mode of the additional
Windows server to ''Per Device'' mode. The number of licenses should be set
to be equal to the number of SBS client access license (CAL). You can
select License->New License from the menu and then select Windows Server
from the dropdown and specify the same number of license that your SBS
server has.

If the issue persists, please try the following steps to reset the License
Logging service of the SBS server box.

1. Stop the License Logging service. To do this, follow these steps:

a. Click Start, point to Administrative Tools, and then click Services.
b. In the list of services, right-click License Logging, and then click
Stop.

2. Delete or rename the Cpl.cfg file that is located in the
%SystemRoot%\System32 folder on the hard disk. The Cpl.cfg file contains
the purchase history of client access license (CALs).
3. Delete or rename the following files that are located in the
%SystemRoot%\System32\Lls folder on the hard disk:
-- Llsuser.lls
-- Llsmap.lls
The Llsuser.lls file contains the user information about the number of
connections, and the Llsmap.lls file contains information about license
groups.
4. Set the value of the ConcurrentLimit registry entry in the following
registry subkey to 0 (zero):
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LicenseInfo\FilePrint

To do this, follow these steps.

Warning If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Please
backup the registry keys first to avoid any unexpected thing happened you
can restore back.

a. Click Start, click Run, type regedit in the Open box, and then click
OK.
b. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LicenseInfo\FilePrint
c. In the right pane, right-click ConcurrentLimit, and then click Modify.
d. In the Value data box, type 0, and then click OK.
e. Quit Registry Editor.

5. Create a new Cpl.cfg file in the %SystemRoot%\System32 folder on the
hard disk. To do this, follow these steps:

a. Start Notepad, and then open a new blank file.
b. On the File menu, click Save.
c. In the Save As dialog box, click All Files in the Save as type box, and
then type Cpl.cfg in the File name box. Save the new Cpl.cfg file to the
%SystemRoot%\System32 folder on the hard disk.

*Important: Make sure that the new Cpl.cfg that you create uses the .cfg
extension and does not use a .txt extension. Additionally, make sure that
the Cpl.cfg file is empty. That is, make sure that the size of the Cpl.cfg
file is 0 (zero) bytes.

*Note: If you deleted the original Cpl.cfg file earlier in step 2, assign
the Network Service account Full Control permissions to the new Cpl.cfg
file that you created. To do this, follow these steps:

a. Start Windows Explorer, and then locate the Cpl.cfg file that you
created in the %SystemRoot%\System32 folder.
b. Right-click the Cpl.cfg file, and then click Properties.
c. Click the Security tab.
d. Click Add.
e. Under Select Users, Computers, or Groups, type Network Service in the
Enter the object names to select box, and then click OK.
f. In the Group or user names list, click NETWORK SERVICE.
g. In the Permissions for NETWORK SERVICE list, click to select the Allow
check box that is next to the Full Control permission, and then click OK.

6. Assign the Network Service account Full Control permission to the
%Systemroot%\System32\Lls folder. To do this, follow these steps:

a. Start Windows Explorer, and then locate the %SystemRoot%\System32\Lls
folder.
b. Right-click the Lls folder, and then click Properties.
c. Click the Security tab.
d. Click Add.
e. Under Select Users, Computers, or Groups, type Network Service in the
Enter the object names to select box, and then click OK.
f. In the Group or user names list, click NETWORK SERVICE.
g. In the Permissions for NETWORK SERVICE list, click to select the Allow
check box that is next to the Full Control permission, and then click OK.

7. Start the License Logging service. To do this, follow these steps:

a. Click Start, point to Administrative Tools, and then click Services.
b. In the list of services, right-click License Logging, and then click
Start.

8. Add the license information that you want.

For more detail information, you can refer to the following KB article:

How to reset the License Logging service in Windows Server 2003
http://support.microsoft.com/?id=883399

I appreciate your time. If the issue persists, please help me collect the
text copy of Application /System log respectively on the server box and the
Windows 2003 box.

To save a text copy of Application /System log:

A. Open Event Viewer: Start -> All Programs -> Administrative Tools ->
Event Viewer.
B. Right-click on Application/System log and select "Save Log File As?".

I am happy to be assistance of you!

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>X-Tomcat-ID: 138614447
>References: <uB$cWdp6FHA.3636@xxxxxxxxxxxxxxxxxxxx>
<wyru3jy6FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
<ewtWWk16FHA.2364@xxxxxxxxxxxxxxxxxxxx>
<3GwoW326FHA.832@xxxxxxxxxxxxxxxxxxxxx>
<OQnSIr36FHA.1184@xxxxxxxxxxxxxxxxxxxx>
<wj41oaC7FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
<uI828iB8FHA.808@xxxxxxxxxxxxxxxxxxxx>
<F6fiBCP8FHA.3764@xxxxxxxxxxxxxxxxxxxxx>
<O7VkMQP8FHA.3132@xxxxxxxxxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain
>Content-Transfer-Encoding: 7bit
>From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
>Organization: Microsoft
>Date: Fri, 25 Nov 2005 09:07:39 GMT
>Subject: Re: License for a member server
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>Message-ID: <9Edsy#Z8FHA.832@xxxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>Lines: 249
>Path: TK2MSFTNGXA02.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:225486
>NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>
>Hi Dieter,
>
>Thanks for your information.
>
>Please try to modify the registry keys like I provided in my previous post
>and then reboot the server to see if the issue be fixed.
>
>And also I would like to know if you have configured the additional DC
>licensing successfully. If not, please reproduce the issue and catch a
>screen shot for further analyze.
>
>To make a screen shot:
>A. Press Alt + Pr Scrn to capture a screen shot.
>B. From Start, go to Run, enter pbrush in the Open box, and then click OK.
>C. Use Ctrl + V to paste the screen shot to the canvas.
>D. From the File menu, go to Save and save as a JPG file.
>
>Additionally please perform the following tests to isolate the issue:
>
>1. Please check if you can open shared folders between the two DCs.
>2. Please collect IP address report using command line "ipconfig /all" (no
>quotation marks) respectively on both DCs. Mail me the output.
>3. Please get Netdiag and DCDiag report between both DCs and give me the
>result.
>
>Run "DCDiag /V > C:\dcdiag.txt" (without quotes) and "Netdiag /V >
>C:\netdiag.txt" (without quotes) on the Windows Server 2003 domain
>controller, and wait for the commands to complete and send the dcdiag.txt
>and netdiag.txt to me at v-yanniw@xxxxxxxxxxxxxx
>
>*Note: DCdiag and netdiag can be obtained by installing Windows Server
2003
>Support tools. You can install it from the SUPPORT\TOOLS folder in the
>Windows 2003 Server CD. After installing it, click Start, All Programs,
>Windows Support Tools and click Command Prompt. Type in these commands.
>
>I appreciate your time!
>
>Have a nice day!
>
>Sincerely,
>
>Jenny Wu
>Microsoft CSS Online Newsgroup Support
>Get Secure! - www.microsoft.com/security
>======================================================
>This newsgroup only focuses on SBS technical issues. If you have issues
>regarding other Microsoft products, you'd better post in the corresponding
>newsgroups so that they can be resolved in an efficient and timely manner.
>You can locate the newsgroup here:
>http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
>When opening a new thread via the web interface, we recommend you check
the
>"Notify me of replies" box to receive e-mail notifications when there are
>any updates in your thread. When responding to posts via your newsreader,
>please "Reply to Group" so that others may learn and benefit from your
>issue.
>
>Microsoft engineers can only focus on one issue per thread. Although we
>provide other information for your reference, we recommend you post
>different incidents in different threads to keep the thread clean. In
doing
>so, it will ensure your issues are resolved in a timely manner.
>
>For urgent issues, you may want to contact Microsoft CSS directly. Please
>check http://support.microsoft.com for regional support phone numbers.
>
>Any input or comments in this thread are highly appreciated.
>======================================================
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>--------------------
>>From: "Dieter Visser" <kdv@xxxxxxxxx>
>>References: <uB$cWdp6FHA.3636@xxxxxxxxxxxxxxxxxxxx>
><wyru3jy6FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
><ewtWWk16FHA.2364@xxxxxxxxxxxxxxxxxxxx>
><3GwoW326FHA.832@xxxxxxxxxxxxxxxxxxxxx>
><OQnSIr36FHA.1184@xxxxxxxxxxxxxxxxxxxx>
><wj41oaC7FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
><uI828iB8FHA.808@xxxxxxxxxxxxxxxxxxxx>
><F6fiBCP8FHA.3764@xxxxxxxxxxxxxxxxxxxxx>
>>Subject: Re: License for a member server
>>Date: Thu, 24 Nov 2005 13:38:59 +0100
>>Lines: 173
>>X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
>>X-RFC2646: Format=Flowed; Original
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>>Message-ID: <O7VkMQP8FHA.3132@xxxxxxxxxxxxxxxxxxxx>
>>Newsgroups: microsoft.public.windows.server.sbs
>>NNTP-Posting-Host: asd-slod-41c9.mxs.adsl.euronet.nl 212.129.193.201
>>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:225259
>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>
>>Hi Jenny,
>>
>>Please find my answers at the *. I did not change anything yet. I want to
>be
>>as sure as possible that I'm changing the right stuff.
>>
>>Thanks again
>>
>>Regards Dieter
>>
>>""Jenny wu [MSFT]"" <v-yanniw@xxxxxxxxxxxxxxxxxxxx> wrote in message
>>news:F6fiBCP8FHA.3764@xxxxxxxxxxxxxxxxxxxxxxxx
>>> Hi Dieter,
>>>
>>> Thanks for your update!
>>>
>>> According to my research, this behavior can occur if the LLS on member
>>> servers cannot communicate with the License Master server on your domain
>>> controllers. To resolve this issue, verify that the LLS server can
>>> establish a Remote Procedure Call (RPC) connection with the License
>Master
>>> server over the network.
>>>
>>> To isolate the problem, follow the steps below:
>>>
>>> 1. Check the Site License Settings to ensure that it is correct.
>>> a. Open "Active Directory Sites and Services".
>>> b. Click the site on which the server is located.
>>> c. In the details pane, click "License Site Settings".
>>> d. On the "Action" menu, click "Properties".
>>> e. Under "Licensing Computer", double check to make sure that the
current
>>> correct domain controller is selected.
>>
>>***
>>The site license settings are correct
>>
>>>
>>> 2. Ensure that the License Logging service is Started and Automatic on
>the
>>> current site license server.
>>
>>***
>>It's running on automatic
>>
>>>
>>> 3. Add LLSRPC to the NullSessionPipes Multi-string value at the
following
>>> registry location on the current license server:
>>>
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameter
s
>>>
>>> the NullSessionPipes should look something like this:
>>> COMNAP
>>> COMNODE
>>> SQL\QUERY
>>> SPOOLSS
>>> LLSRPC
>>> EPMAPPER
>>> LOCATOR
>>> TrkWks
>>> TrkSvr
>>
>>***
>>The register reads on that position:
>>COMNAP
>>COMNODE
>>SQL/QUERY
>>SPOOLSS
>>netlogon
>>Isarpc
>>samr
>>browser
>>
>>It's not exactly as you said, but something like it. Is that close
enough?
>I
>>did'nt change anything yet.
>>
>>>
>>> After that, restart the site license server and check the problem again.
>>> How about the result?
>>>
>>> If the problem persists, go to the servers reporting the error and run
>>> regedit.exe, locate the following key:
>>>
>HKEY_LOCAL_MACHINE\System\currentcontrolset\services\licenseServer\Paramete
r
>>> s
>>
>>***
>>The registry on the member server reads:
>>
>>EnterpriseServer is empty
>>SiteServer is the right name
>>
>>>
>>> check to see if the incorrect server name is specified. If so, change it
>>> and restart the computer.
>>>
>>> I appreciate your time and efforts to the issue. I am happy to be
>>> assistance of you and look forward to your reply!
>>>
>>> Have a nice day!
>>>
>>> Sincerely,
>>>
>>> Jenny Wu
>>> Microsoft CSS Online Newsgroup Support
>>> Get Secure! - www.microsoft.com/security
>>> ======================================================
>>> This newsgroup only focuses on SBS technical issues. If you have issues
>>> regarding other Microsoft products, you'd better post in the
>corresponding
>>> newsgroups so that they can be resolved in an efficient and timely
>manner.
>>> You can locate the newsgroup here:
>>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>>
>>> When opening a new thread via the web interface, we recommend you check
>>> the
>>> "Notify me of replies" box to receive e-mail notifications when there
are
>>> any updates in your thread. When responding to posts via your
newsreader,
>>> please "Reply to Group" so that others may learn and benefit from your
>>> issue.
>>>
>>> Microsoft engineers can only focus on one issue per thread. Although we
>>> provide other information for your reference, we recommend you post
>>> different incidents in different threads to keep the thread clean. In
>>> doing
>>> so, it will ensure your issues are resolved in a timely manner.
>>>
>>> For urgent issues, you may want to contact Microsoft CSS directly.
Please
>>> check http://support.microsoft.com for regional support phone numbers.
>>>
>>> Any input or comments in this thread are highly appreciated.
>>> ======================================================
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>> --------------------
>>>>From: "Dieter Visser" <kdv@xxxxxxxxx>
>>>>References: <uB$cWdp6FHA.3636@xxxxxxxxxxxxxxxxxxxx>
>>> <wyru3jy6FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
>>> <ewtWWk16FHA.2364@xxxxxxxxxxxxxxxxxxxx>
>>> <3GwoW326FHA.832@xxxxxxxxxxxxxxxxxxxxx>
>>> <OQnSIr36FHA.1184@xxxxxxxxxxxxxxxxxxxx>
>>> <wj41oaC7FHA.1236@xxxxxxxxxxxxxxxxxxxxx>
>>>>Subject: Re: License for a member server
>>>>Date: Wed, 23 Nov 2005 11:29:06 +0100
>>>>Lines: 614
>>>>X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
>>>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>>>>X-RFC2646: Format=Flowed; Original
>>>>Message-ID: <uI828iB8FHA.808@xxxxxxxxxxxxxxxxxxxx>
>>>>Newsgroups: microsoft.public.windows.server.sbs
>>>>NNTP-Posting-Host: asd-slod-41c9.mxs.adsl.euronet.nl 212.129.193.201
>>>>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>>>>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:224905
>>>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>>>
>>>>Hello Jenny,
>>>>
>>>>Just yesterday there started a number of error event in the viewer of
the
>>>>member server, it repeats every 6 hours - see the attached doc-. The
>>> license
>>>>logging service complains that it can't reach the SBS server. Member
>>> server
>>>>called NOODSERV, SBS server called TELSERV
>>>>
>>>>In the viewer of the SBS server nothing shows up.
>>>>
>>>>I think this shows up in the member server because I can't configure it
>>>>right. The msg : You do not have the proper privileges keeps coming up.
>>>>
>>>>Hope this helps
>>>>
>>>>Regards Dieter
>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>
>

.

Relevant Pages

  • RE: Licensing
    ... we have no directly way to move the license from your ... SBS 2003; you may have to call the license office for directly help. ... directly to a Microsoft licensing specialist. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Server licensing problem
    ... wondering query of way to check how many or who had logon to domain/server. ... restarted the server and resolved the remote ... click License mode and give me the screen shot. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: access liscensing
    ... out of usage error message although it is not up to the maximum CALs ... Firstly, to recover from this issue, please re-input the license of the ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs2003 license
    ... the SBS domain, does the server will disconnect the other user if you only ... best interest to call license office. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2k licensing Question
    ... This is an update to my previous post, when we reinstall terminal server, ... the terminal server will query Terminal Services ... The terminal server could not locate a license server in the ... Microsoft Windows 2000 Terminal Services Licensing ...
    (microsoft.public.windows.server.sbs)