Hi TKremer
I've got almost the same problem. A old SCCM 2007 service on Windows Server 2008 R2 witch can provision AMT 3.2.0 to version 8.1.20.
We have created a new Windows 2012 Server with SQL 2012 and SCCM 2012 (Comodo certificate). The team have provisioned AMT 5.1.0 to version 8.1.20 successfully. But we have a lot of machines with AMT 3.2.30. All of these have failed with the same error in the event log. "A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 80."
TLS1_ALERT_INTERNAL_ERROR (80) from Event ID: 36887 Source: Schannel
amtopmgr.log
**** Error 0x1f53b410 returned by ApplyControlToken~ $$<SMS_AMT_OPERATION_MANAGER><07-22-2013 16:52:11.910-60><thread=6940 (0x1B1C)>
Fail to connect and get core version of machine C60024001.ccad.canterbury.ac.uk using provisioning account #1. $$<SMS_AMT_OPERATION_MANAGER><07-22-2013 16:52:11.911-60><thread=6940 (0x1B1C)>
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.~ $$<SMS_AMT_OPERATION_MANAGER><07-22-2013 16:52:11.920-60><thread=6940 (0x1B1C)>
At the moment this looks like a Windows Server 2012 problem as one of my colleagues has provisioned AMT version 3.2.30 using Windows 2008 R2 with SQL 2012 and SCCM 2012.
I've been working on the changes Microsoft have made to the Security Channel settings in Server 2012 but so far have been unsuccessful.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL\
Which OS are you on?
Tony Bennett
Canterbury Christ Church University