We are using Sccm 2012 R2 and want to implement Oobm. So we followed this guide in our test environment: http://sccmguru.wordpress.com/2013/12/20/integrating-configuration-manager-2012-r2-with-intel-scs-9-... Integrating Configuration Manager 2012 R2 with Intel SCS 9.0 – Part 1 : Introduction | SCCM GURU
Provisioning is working fine on Fujitsu computers with AMT version 7 and 9. But on older hardware with version 5 and 6 there is an error during configuration of the profile.
exit with code 68. Details: invalid parameter was found. (RCSAAddress) is found in the Windows event viewer.
and in the Sccm console AMT Status is Not Supported (version 6) and Detected (version 5).
Version 7 and 9 are having the status Provisioned and the out of the band management console is working.
Based on what you explained, my guess is that you are provisioning these machines using HBC (i.e. Host Based Configuration) method that is not supported in ME versions <6.2. Can you confirm?
"ProvisionServer" DNS record is not required for provision in this scenario, it's a legacy resource used by old AMT versions to find the SCS, even when you don't an Operating System.
For AMT <6.2 you must use PKI provisioning that rely on 3rd party certificates for provision, since these versions does not support HBC - In Intel Setup and Configuration Software (Intel SCS) User Guide that you can find in Intel <a href="https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20921">SCS package, chapter 10.
In order to integrate with Microsoft SCCM, you can use the https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20921 Intel SCS Add-On for SCCM installed in SCCM Server.
There is no requirement to put Intel SCS and SCCM in the same box, usually the best practice is install Intel SCS in a dedicated server/VM.