samba - Jul 2015 - Credential Manager problem (error 0x80090345) and older samba versions

Dear samba ppl, 

	I have the same problem as described in this link [1] (error
0x80090345 when trying to open Credential Manager under Windows 8.1)
with a machine joined to an NT4 style domain with a samba 3 DC. So far
the only workaround is to uninstall the updates mentioned in the
thread. The problem was fixed for samba 4 as mentioned here [2]. Is
there any chance that this might be fixed for samba 3 too? This error
basically makes samba 3 no longer usable as domain controller if
Windows 8.1 (propably Window 10?) is joined to the domain. I know that
samba 3 is not officialliy supported any longer, but still I'm running
into the problem that I have to use CentOS 5 on some machines for some
more months which only supports samba 3. 

	[1]
https://social.technet.microsoft.com/Forums/windows/en-US/47faab6b-d717-4068-bee4-c694811e0066/credential-manager-problems-error-0x80090345


	[2] https://bugzilla.samba.org/show_bug.cgi?id=11097 [1] 

	Thank you for all your hard work with samba and your help with this
issue!

 Profitieren Sie von der sicheren E-Mail-Übertragung Ihrer Daten mit
einer kostenlosen E-Mail-Adresse der Telekom.
www.t-online.de/email-kostenlos

Links:
------
[1] https://bugzilla.samba.org/show_bug.cgi?id=11097

On Mon, 2015-07-27 at 14:55 +0200, jochen.g.paul at t-online.de
wrote:
> Dear samba ppl, 
> 
> 	I have the same problem as described in this link [1] (error
> 0x80090345 when trying to open Credential Manager under Windows 8.1)
> with a machine joined to an NT4 style domain with a samba 3 DC. So far
> the only workaround is to uninstall the updates mentioned in the
> thread. The problem was fixed for samba 4 as mentioned here [2]. Is
> there any chance that this might be fixed for samba 3 too? This error
> basically makes samba 3 no longer usable as domain controller if
> Windows 8.1 (propably Window 10?) is joined to the domain. I know that
> samba 3 is not officialliy supported any longer, but still I'm running
> into the problem that I have to use CentOS 5 on some machines for some
> more months which only supports samba 3. 
> 
> 	[1]
>
https://social.technet.microsoft.com/Forums/windows/en-US/47faab6b-d717-4068-bee4-c694811e0066/credential-manager-problems-error-0x80090345
> 
> 
> 	[2] https://bugzilla.samba.org/show_bug.cgi?id=11097 [1] 
> 
> 	Thank you for all your hard work with samba and your help with this
> issue!
G'Day,

The challenge here is that the BackupKey protocol has not been
implemented for the NT4 DC.  It would require a refactor, not just a
re-configuration to operate in such a mode, but currently it only
operates in the AD DC. 

Your best option therefore is to upgrade the domain to being an AD DC,
using the classicupgrade tool, or if that is impractical due to the
size/complexity of your site, to commission a developer to enable the
code in the NT4 DC code.

Thanks,

Andrew Bartlett

-- 
Andrew Bartlett                       http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba