[Samba] TS licensing problem on samba domain
ssureshot at gmail.com
Mon Jan 30 07:07:37 MST 2012
I can confirm that this is an issue. We went through this to great
lengths. I can also confirm that after you install the licensing it will
not keep track of the issued calls properly. I also remember that since
it isn't working properly that you may still be on the temporary install
and after the term period it will not function.
We had a third party work with this and they were able to get the cals
to function with specific schemas added to samba and ldap. This allowed
it to work and keep track of cals properly but the error in Licensing /
Diagnostics was still there.. The licensing was working and looked like
it would not expire.
I went through great lengths on this one and found no resolution aside
from special schemas..
On 01/29/2012 08:08 PM, Andrew Bartlett wrote:
> On Sun, 2012-01-29 at 12:02 -0500, Ludovic Rouse-Lamarre wrote:
>> We have recently joined a Windows Server 2008 R1 on our samba domain as
>> a domain member. The samba domain controller runs Samba version 3.4.9 on
>> FreeBSD 8.2.
>> We use the Windows Server as a terminal server for our domain users who
>> need an accounting application called Acomba. Therefore we have added TS
>> User CALs to the server in question. The TS Licensing Server was
>> activated and the licenses were installed succesfully.
>> The problem comes when we use the Licensing Diagnosis tool inside the TS
>> Configuration application. It then reports that it cannot find the TS
>> Licensing Server and that we are still within the grace period.
>> I have also called Microsoft and they have confirmed to me that this is
>> a technical issue and that the licenses are correctly installed. I get
>> the feeling however that when I tell them I use a Samba domain
>> controller they won't be of any help.
> Microsoft has gone to great technical lengths to support Samba3 domains.
> It may well be that some functionality of Microsoft products relies on
> an AD domain (which we are providing with Samba4), but do not assume
> that they will be hostile.
> If they claim an interoperability issue, we can refer that to the group
> within Microsoft that specifically deals with interoperability issues
> for us.
> Andrew Bartlett
More information about the samba