I have multiple client machines(HP DC8100 and DELL 790) with AMT 6.2 and above. I'm getting the following failures when trying to use host based configuration on both the 6.2 and 7.0 firmwares. My command line is \\ti-amt-01\amtconfig\acuconfig.exe /output console /verbose /lowsecurity configamt \\ti-amt-01\amtconfig\amtconfig.xml /decryptionpassword ****
I have also included my unecrypted xml file that I am using to load. I have starred out the password. My guess is that some of the options selected are admin mode only? I need to push this out to a few thousand machines so any help would be great!
2014-02-26 17:20:10: Thread:2724(ERROR) : ACU Configurator , Category: ConnectServer Source: Src\WMIAccess.cpp : ConnectToNamespace Line: 129: A call to this function has failed - (0xc000278b) (Invalid namespace -2147217394)
2014-02-26 17:20:10: Thread:2724(DETAIL) : ACU Configurator , Category: WMI_GetRequiredRealms Source: Src\SBAWMIMethods.cpp : SBAWMIMethods::WMI_GetRequiredRealms Line: 259: A call to this function has failed - (0xc000278b) ((ExecMethod WMI_GetRequiredRealms) Failed to connect to the RCS. Invalid namespace (0xc0002779). )
2014-02-26 17:20:10: Thread:2724(ERROR) : ACU Configurator , Category: ConfigAMT failed Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 3279: A call to this function has failed - (0xc000278b) (Connection to the Remote Configuration Service is necessary, but the RCSParameters tag is missing in the profile. (RCSAddress))
2014-02-26 17:20:10: Thread:2724(DETAIL) : ACU Configurator , Category: -END- Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 3281: ***** END ClientControlConfiguration ******
2014-02-26 17:20:10: Thread:2724(DETAIL) : ACU Configurator , Category: -END- Source: Src\ActivatorDll.cpp : ClientControlConfiguration Line: 3387: ***** END ClientControlConfiguration ******
2014-02-26 17:20:10: Thread:2724(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : wmain Line: 1223: ***********Exit with code 68. Details: Invalid parameter was found. (RCSAddress)
we have the same Problem. SCS is 184.108.40.206b, SCS Addon for SCCM 220.127.116.119, the documentation used was the one in the downloaded packages.
In the meantime tried provisioning with SCCM alone - works with our on CA, if I enter the hash value of our root CA into every AMT MBEx Setup Menu. So it seems to be a Problem with at least the documentation.
At the Moment I am trying to reduce the configuration Profile to the bare Minimum, to get a hint where exactly the Problem Comes Comes from. If someone has a solution, please share it.
Matthias - who hates the auto-correction-Feature within Win8 :-)
Just tested with the bare MBEx Settings Profile.xml - same result. Will check the acuconfig command line Options used in configure.bat inside the Configure-Package and the used MBEx Settings Options tomorrow.
Same problem here....exit code 68 for Intel AMT versions 5 & 6.....7 & 9 working fine...used this guide: http://sccmguru.wordpress.com/2013/12/20/integrating-configuration-manager-2012-r2-with-intel-scs-9-0-part-1/ Integrating Configuration Manager 2012 R2 with Intel SCS 9.0 – Part 1 : Introduction | SCCM GURU
I'm not sure if this is the same issue others are experiencing, but I resolved this by generator a profile with the ACU Wizard (ACU_Wizard/ACUWizard.exe). I was previously attempting to apply a profile generated with the Intel SCS Console, but this profile tries to talk but to the SCS server, and unless you have the appropriate infrastructure configured, it apparently won't be able to communicate back to this server.
Refer to https://helpdesk.kaseya.com/entries/88640858-vPro-Can-you-implement-a-vPro-machine-with-Kaseya-when-it-s-configured-through-Remote-Configuration- vPro - Can you implement a vPro machine with Kaseya when it's configured through Remote Configuration Service (RCS) : Ka…