Hi Kyle,
1. To be sure i'm talking about the right certificate. The AMT TLS certificate is created from the Webserver Template, is that right? If that's the case the Subject Name is set to 'supply in the request' at the moment. It was set to 'Build from...DNS name' before but we changed it.
If the TLS certificate is created from another template please let me know.
Up to now we have the Verisign Server certificate for the first contact, the Webserver Template and the AMT Provisioning template. We build them after the instructions for SCCM 2007.
Are there any more certificates or templates we need?
Under SCCM 2007 it worked great with these templates. SCCM 2012 generated some unusual errors so we tried to provision the clients with SCS 8.2.
2. We get the OTP Error from two clients, the third seems to have had some problems with the unprovisioning under SCCM 2007 and gives us a Hash error cause the Servername and Certificate changed.
The OTP error stays even after some days of waiting.
Actually the provisioning seems to start cause the AD object is being generated and we find the proper data in the Mbex after the error occured. But managing the client afterwards is not possible because SCS counts the provisioning as an error.