Re: License for a member server
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Wed, 30 Nov 2005 13:29:45 GMT
Hi Dieter,
Thanks for your update!
The License Logging service is used to collect licensing information on a
server. The License Logging service is disabled by default.
The License Logging service on each server in a site replicates this
licensing information to a centralized database on a server, called the
site license server, for the site. A site administrator or administrator
for the site license server can then use Licensing in Administrative Tools
to view the licensing history for the entire site stored on the site
license server.
Typically, the site license server is the first domain controller created
for the site. In a large organization with multiple sites, the site license
server in each site collects licensing information for that site.
For your scenario, we just need one licensing logging service to collect
licensing information since there is only one site in your SBS domain. You
can safely disable the licensing logging service on the additional server.
After disabled the server of additional DC, does the issue be fixed? I
suggest you take a look at the following KB article:
The Licensing Logging service cannot find the domain controller and you
cannot manage licenses when the License Logging service starts on a Windows
Server 2003-based computer
http://support.microsoft.com/default.aspx?scid=kb;en-us;883645
More information:
Description of the License Logging Service in Windows Server Operating
Systems
http://support.microsoft.com/kb/824196/
If the issue persists, please give me the System/ Application logs of the
server box and additional DC for analyze.
And also have you tried to add the new domain admin user account to the
local administrators group? After done it, the issue still persists?
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>
<O7VkMQP8FHA.3132@xxxxxxxxxxxxxxxxxxxx>
<9Edsy#Z8FHA.832@xxxxxxxxxxxxxxxxxxxxx>
<wIFZoIN9FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
<utV#9#N9FHA.2792@xxxxxxxxxxxxxxxxxxxx>
<xSc2cCZ9FHA.4000@xxxxxxxxxxxxxxxxxxxxx>
>Subject: Re: License for a member server
>Date: Wed, 30 Nov 2005 12:34:14 +0100
>Lines: 355
>X-Priority: 3
>X-MSMail-Priority: Normal
>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: <##6S$Ha9FHA.3360@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!TK2MSFTNGP11.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:226648
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi Jenny,
>
>I did ALL the tests and followed ALL the steps from ALL your previous
posts.
>I created a new administrator and logged on the member server. I could not
>logon locally. Tried to configure the licences and this new guy did'nt
have
>the proper privileges.
>
>You must have received my logfiles by now, I don't think that clarifies
>much. Am I breaking some law when I just disable the license logging
service
>on the member server? As long as the license issue doesn't show up at the
>SBS server I'm ok, I think. Please let me know if I'm right, if so we just
>call it a day and you and I can go on with our (other) work.
>
>Thanks again for your tremendous efforts.
>
>Dieter Visser
>
>
>""Jenny wu [MSFT]"" <v-yanniw@xxxxxxxxxxxxxxxxxxxx> wrote in message
>news:xSc2cCZ9FHA.4000@xxxxxxxxxxxxxxxxxxxxxxxx
>> Hi Dieter,
>>
>> Thanks for your update. I do understand your situation and I appreciate
>> your efforts to the issue. Yes, you can disable the licensing logging
>> service on the additional DC. After you disabled the service, please also
>> perform the following tests to see if the issue be fixed.
>>
>> 1. Have you reset the License Logging service of the SBS server box? If
>> not, please try to reset it follow the steps in previous post.
>>
>> 2. Please try to create a Domain admin user account with Add user wizard
>> (server management console -> Users -> add a user), and then logon the
>> additional DC with the new user account. Please check if the domain admin
>> user account is in the local administrators group, if not, please add it
>> and then test the issue again, how about the result?
>>
>> 3. If the issue persists, please ensure logon the additional DC locally
>> not
>> domain with an local Administrator account to try to change licensing
>> mode,
>> how about the result?
>>
>> Additionally I have not received your log file by mail. If the issue
>> persists, please mail me those files again. My mail address is:
>> v-yanniw@xxxxxxxxxxxxx
>>
>> Note: please compress those files to a zip file and then mail to me.
>>
>> I appreciate your time! 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.
>>
>> --------------------
>>>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>
>> <O7VkMQP8FHA.3132@xxxxxxxxxxxxxxxxxxxx>
>> <9Edsy#Z8FHA.832@xxxxxxxxxxxxxxxxxxxxx>
>> <wIFZoIN9FHA.1240@xxxxxxxxxxxxxxxxxxxxx>
>>>Subject: Re: License for a member server
>>>Date: Tue, 29 Nov 2005 13:23:42 +0100
>>>Lines: 212
>>>X-Priority: 3
>>>X-MSMail-Priority: Normal
>>>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: <utV#9#N9FHA.2792@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!TK2MSFTNGP11.phx.gbl
>>>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:226320
>>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>>
>>>Hi Jenny,
>>>
>>>This is the stuff that drives me crazy. The most depressing thought is
>> that
>>>it must be my own doing somehow.
>>>
>>>I really truly followed your instructions but when I try to configure the
>>>licenses on the member server it keeps coming up with the privileges msg.
>> I
>>>will send you both the log files.
>>>
>>>Maybe it's a nice idea to just stop the license logging service on the
>>>member server?
>>>
>>>Hope you can find anything and thanks for your persistency
>>>
>>>Regards Dieter
>>>
>>>
>>>""Jenny wu [MSFT]"" <v-yanniw@xxxxxxxxxxxxxxxxxxxx> wrote in message
>>>news:wIFZoIN9FHA.1240@xxxxxxxxxxxxxxxxxxxxxxxx
>>>> 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.
>>>>
>>>> --------------------
>>>
>>>
>>>
>>
>
>
>
.
- Follow-Ups:
- Re: License for a member server
- From: "Jenny wu [MSFT]"
- Re: License for a member server
- References:
- Re: License for a member server
- From: Dieter Visser
- Re: License for a member server
- Prev by Date: Re: Fax Service error...
- Next by Date: Re: Renaming a small business server 2003
- Previous by thread: Re: License for a member server
- Next by thread: Re: License for a member server
- Index(es):
Relevant Pages
|
|
