Hello,

We have a godaddy provisioning AMTcertificate that was issued to server A. Now we have new hardware with a different name. Do I need to "upgrade" my certificate to work with the new server ? How ?

Sorry if my question is trivial, I'm not certificate specialist.

Michel

I am currently testing vPro with SCS installed on my non-vPro desktop and a single Latitude E6530 as my vPro machine.

The AMT event log shows a "operating system lockup or power interrupt' about every 2 or 3 minutes while windows is running. According to my tests, this only happens while windows is booted, not under a linux live cd.

I'm not sure what kind of lockup is meant, but since it says 'or power interrupt' I think it should be critical enough to be noticeable during usage of the pc.

The cpu fan will not go over 1k rpm even under heavy loads. I cannot find QST or any kind of fan control option in the bios that changes this. I am pulling my hair out here. Suggestions?

Thanks

Hello,

I'm using a NUC DC53427HYE to remotely control a Gige IP camera on Linux (Debian Wheezy).

The camera is correctly detected only if it is directly plugged in the integrated Intel ethernet card, therefore I'm using a USB3->RJ45 (Gige) adapter to connect the machine to the internet.

My impression is that AMT functions are no more available out of the integrated Intel ethernet card: the adress http://<ip-adress>:16992/logon.html could not be resolved.

Am I missing some configuration parameter or direct connection to Intel NIC is the only way to have AMT working?

Hello,

We have traditionally been using SCCM 2012 natively to provision and use AMT functionality with our Dell systems (Optiplex 755 - Optiplex 7010). For a variety of reasons, we are investigating using Intel SCS for provisioning and using Kerberos to enable the functionailty in SCCM we require.

I have, however, run into a roadblock regarding some of our oldest systems (Optiplex 755s). These systems, even with the latest BIOS updates available from Dell (A22 as of this writing), are only at AMT version 3.2.60. Is there any supported way to provision these using SCS 9?

Yes, I am aware of the following section from the SCS User Guide:

Support for versions of Intel AMT lower than version 6.2 is deprecated. You can still use Intel SCS 9.0 to

configure Intel AMT 6.1 and lower. But, Intel SCS 9.0 was not validated on these versions and thus the

results cannot be guaranteed. Support agreements for Intel SCS 9.0 do not include support for issues

related to versions of Intel AMT lower than version 6.2. The information in this guide related to these

versions is provided for informational purposes only.

But I was not even clear on how to go about this, and I have attempted several things to get these going. Does anyone have an exact procedure that works to provision AMT 3.x systems in SCS 9?

Things I have tried:

1. Various ACUConfig commands (both manual and SCCM Plugin commands). Usual error message is something like 'Driver missing or invalid' (assuming because it doesn't like the old HECI driver for the old AMT version)
2. ACUConfig SendHello commands to initiate a hello command style provisioning on port 9971. This command succeeds but no packets from the system ever reach the provisioning server, confirmed using Wireshark.
3. Activator.exe (deprecated tool) commands to activate the hello message interfaces (These also did nothing)

Any suggestions or more information I can provide? I am thusfar satisfied with the SCS software, barring this particular issue. I understand the need to limit scope of support on a product like this, but since SCCM does not have the same issues provisioning AMT systems at this version, it seems odd that the native Intel product does not have support. Is there any manual process I can do to get these systems to provision with SCS?

Thanks for your time.

Other details

How can I know that laptop is running with vPro? Please Guide.

ningintelHi - running into issues with reprovisioning some systems for Out of Band in SCCM 2012 R2 that were previously provisioned in SCCM 2007 R2.  I ran through the process of unprovisioning the systems in SCCM 2007 before migrating my systems to the new infrastructure as per migration documents from Microsoft.

I was able to provision some systems (currently working with 53 systems while I work out the issues), and have the following numbers:

16 - detected vpro clients

13 - provisioned vpro clients

24 - unsupported vpro clients

The fact that I have 13 provisioned that would lead me to believe that my certificates and environment are set up properly and points me to system specific issue.  The 13 provisioned systems where provisioned in our old environment as well.

Here is the log from the AMTOPMGR.LOG file when using the "Discover AMT Status" - I've removed the IP address and full system names from the log.

AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Reading Discovery Instruction E:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{1DE76692-74CE-48D3-8D80-4CE5828FB3C3}.RDC... SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, '16779993', 'MNC' SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>exec AMT_GetThisSitesNetBiosNames NULL, '16779993', 'MNC' SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine <computername> (<fqdn>), ID: 16779993 IP: <ipaddress> from Resource 16779993. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 16779993 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>exec AMT_GetAMTMachineProperties 16779993 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

Discovery will use ip resolved from netbios: SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

<ipaddress> SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Finish reading discovery instruction E:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{1DE76692-74CE-48D3-8D80-4CE5828FB3C3}.RDC SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Parsed 1 instruction files SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Send task <fqdn> to completion port SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

General Worker Thread Pool: Current size of the thread pool is 1 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

General Worker Thread Pool: Work thread 10684 started SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Discover <computername> using IP address <ipaddress> SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

AMT Discovery Worker: 1 task(s) are sent to the task pool successfully. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>SELECT SC.SiteType FROM SMSData S INNER JOIN SC_SiteDefinition SC ON SC.SiteCode = S.ThisSiteCode SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>SELECT dbo.fnIsSnapshotInitializing(N'Site Control Data', N'') SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>select DateLastModified from SiteControl where SiteCode = N'MNC' SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

SQL>>>>> Done. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=<sccmfqdn> SITE=MNC PID=2964 TID=6520 GMTDATE=Thu Feb 13 14:30:10.716 2014 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

**** Error 0x3aa5ad60 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

**** Error 0x3aa5ad60 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

session params : https://<fqdn>:16993   ,  2011001 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

session params : https://<fqdn>:16993   ,  2011001 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Start Kerberos Discovery SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

session params : https://<fqdn>:16993   ,  2484001 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoKerberosWSManDiscovery failed. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

session params : https://<ipaddress>:16993   ,  2015001 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

session params : https://<ipaddress>:16993   ,  2015001 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

Discovery to IP address <ipaddress> succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

CSMSAMTDiscoveryTask::Execute, discovery to <computername> succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

CSMSAMTDiscoveryTask::Execute - DDR written to E:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='<fqdn>' P2='' P3='' P4='' P5='' SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

CStateMsgReporter::DeliverMessages - Created state message file: E:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\zj7ir1r4.SMX SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

General Worker Thread Pool: Succeed to run the task <fqdn>. Remove it from task list. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

General Worker Thread Pool: Work thread 10684 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

General Worker Thread Pool: Work thread 10684 exiting. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:11 AM 10684 (0x29BC)

Here are the pieces that stick out to me:

AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 6520 (0x1978)

Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

**** Error 0x3aa5ad60 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

**** Error 0x3aa5ad60 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

session params : https://<fqdn>:16993   ,  2011001 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 13/02/2014 10:30:10 AM 10684 (0x29BC)

If I try to force a provision using a sendsched.vbs {00000000-0000-0000-0000-000000000120} to the system, OOBMGMT.LOG shows the following:

ON SCHEDULE OOBMgmt 13/02/2014 10:35:00 AM 3972 (0x0F84)

BEGIN oobmgmt 13/02/2014 10:35:00 AM 3972 (0x0F84)

Retrying to activate the device. oobmgmt 13/02/2014 10:35:00 AM 3972 (0x0F84)

Get CoreVersion: 5.2.50 oobmgmt 13/02/2014 10:35:00 AM 3972 (0x0F84)

Resending last OTP oobmgmt 13/02/2014 10:35:00 AM 3972 (0x0F84)

Successfully activated the device. oobmgmt 13/02/2014 10:35:00 AM 3972 (0x0F84)

END oobmgmt 13/02/2014 10:35:00 AM 3972 (0x0F84)

For this system I upgraded the MEBX firmware from 5.2.1 to 5.2.50, with no change - this however did correct the issue for a previous system (same model, MEBX firmware) and I do have other systems with this version of firmware provisioned.

I also ran the Activator utility, and determined that the ports are open.

Also ran the Diagnostic Utility, all scans and tests returned what I would expect.

Have tried running the UnprovisionEx utility again, when I attempt to run with -tls I get "An exception occurred while atempting to unprovision (FULL) the system. The request was aborted: Could not create SSL/TLS secure channel".  When I drop -tls I get a refused connection to port 16992 and that the AMT device is invalid.

Anybody have any ideas on what is happening?  I'm at a loss to understand why I can provision some, and some I can't.

Thanks

We've just migrated our AMT 7.1 clients to a brand new SCCM 2012 R2 server. We'd like to configure our OOB AMT settings to now use the SCCM Add-on along with SCS 9.0. This seems to be a much better implementation than the pure SCCM AMT implementation.

From what I've been able to read, I'll need to install SCS 9.0 and then the SCCM Add-on. Is this sequence correct? I read a good step-by-step series about working with SCS 9.0 on the http://sccmguru.wordpress.com site. Well written series. I never did see, in the posts, any mention about installing SCS 9.0. I'd like to use Remote Configuration so I'm guessing I'll need to install SCS 9.0 by itself, correct?

I do have the setup docs for installing the Add-on for Microsoft System Center Configuration Manager. Well written as well.

Hello,

I am working on a project where my company is trying to get the SCS application working on our clients network. So far the experiment is in futility. I have managed to install the SCS Console, But have yet to detect any of the devices with AMT. Can someone point me in a direction where I can get results. We are new with this application and would greatly appreciate the help.

Tony

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)

Hi everybody,

For the last two days im getting crazy because i needed to format my computer and now i cant install any drivers, apart from that winzip and winrar, each time i click on the drivers icons, a black screen appears like doing sth in msdos but nothing happens. Before i had xp pro and i have now xp pro sp3, i tried with another cd but its same. Does anybody know anything about this?

I have an RCS server integrated with SCCM.  It is largely working.  However, on some number of SCCM clients, the Intel SCS task sequences get stuck in an "Installing" state forever, preventing any other software from being deployed. I have set timeouts on both the task sequence steps, and to the task sequence itself.  Reviewing the logs, it appears that the task actually finished, but never reports back.  This article; SCCM Task Sequence Hangs &laquo; sccm.haas.se describes a very similar scenario, except that in my case, tsmanager.exe is not running, thus i cannot stop it to resolve the issue.  The only solution I have found is to reinstall the SCCM client.  Normally, I would think this is an SCCM issue, but we have hundreds of packages and dozens of task sequences, but it is only the intel SCS ones that get stuck.  Anyone experience anything similar, or have any suggestions on how to resolve?

Hi,

I bought an Intel workstation system P4304CR2LFKN.

It was a bit of a work to update the bios on it but now it is updated.

However, as soon as I modified the SDR and FRU, the PSU Fan speed went up the wall. Extremely noisy. Running on MAX rpm ALL THE TIME.

Also, I have two PCIE SSD raid cards that crash the Windows 8 startup everytime I install them in any slot.

I

ran Intel Active System Consol and I get a scrolling alert in the bottom of the screen that says "Critical: PCIE Fat sensor reports a Fatal PCI express Unexpected Completion Error"

Windows is running fine, but everytime I try to use the intel Deployment Assist CD, it stops and cannot continue.

Can anyone help here please? Is the problem with the Bios, BMC, Windows 8, or the actual board or what can  do to investigate?

I have the Intel NUC with the I5-4250U and cannot get into the MBEx with Ctrl+P combo. F2 etc. are fine. How do I get in to configure password ? How do I set an IP address ? I load ESXi and it has a static IP, but port 16995 does not connect from SCS.

I'm new to SCCM and vPRO AMT so I'm overwhelmed with things I would like to accomplish before the deadline that was set for me.

I’ve got the SCCM down pretty good, now I would like to enable remote KVM on our vPRO workstations.

Our fleet is composed of HP 8200 Elite and higher with Win 7 x64 Ent (AMT 6.2 i believe).

I’m enabling ME/AMT in our ODS TS using BiosConfigUtility.exe /SetConfig:xxxx.txt

We have an internal CA but I would like to use a COMODOS certificate, they have a 30 day trial cert available for testing.

I would like to get SCCM/AMT to work natively before integrating with SCS unless you guys have a different opinion. (Walk before I
run...)

The goal is to configure everything remotely for each workstation.

Is there an easy step by step guide on how to achieve remote KVM using SCCM 2012 R2 and Certificate?

Thank you

p.s. I got it working using the manual password, host name, domain name configuraton and VNC Viewer Plus. I would like to avoid going to every machine unless it can be done with a script.

I have successfully provisioned a test machine (Dell OptiPlex 990, AMTv7.1) by entering the MEBX and choosing the option "Activate Network Access". I cannot seem to provision this machine with either acuconfig or the activator utility, without first manually choosing this option. Otherwise, I get errors in the logs regarding PKI certificates not being valid or connections to AMT not working.

I have a 2008R2 server with SCS 8.1 and a GoDaddy vPro cert installed. DNS is setup with provisionserver pointing to the IP of this server. The SOL driver and LMS service is installed on the target machine. The command line to configure (which works when the "Activate Network Access" option is selected in MEBX) is as follows:

C:\COnfigurator\acuconfig.exe /verbose ConfigViaRCSOnly scsserver.domain.net "Company Test Profile" /abortonfailure /adminpassword xxxxxxx

It seems that I am having trouble reopening the interface and entering setup mode? I thought the activator utility would help with this, but this also returns errors when run:

Step Into: CheckAMT
Connected to HECI driver, version: 7.1.70.1198

BIOS Version:   A02

Intel AMT code versions:
Flash:                   7.1.4
Netstack:                7.1.4
AMTApps:                 7.1.4
AMT:                     7.1.4
Sku:                     24592
VendorID:                8086
Build Number:            1068
Recovery Version:        7.1.4
Recovery Build Num:      1068
Legacy Mode:             False

Setup and Configuration:     
In process

Provisioning TLS Mode:
PKI
Step Into: CSCSER::PerformSCSRemoteConfiguration
Step Into: CSCSER::SCSSetAMTIdentity
AMT version: 7.1 Step Into: StartConfiguration

BIOS Version:   A02

Intel AMT code versions:
Flash:                   7.1.4
Netstack:                7.1.4
AMTApps:                 7.1.4
AMT:                     7.1.4
Sku:                     24592
VendorID:                8086
Build Number:            1068
Recovery Version:        7.1.4
Recovery Build Num:      1068
Legacy Mode:             False

Setup and Configuration:     
In process

Intel AMT Mode:      
Non Legacy

Remote Configuration:  
enabled

Provisioning TLS Mode:
PKI

RNG seed status:
exists

PT_STATUS_INVALID_PT_MODE: Command is not permitted in current operating mode.
Activate Intel AMT configuration:
failure
PT_STATUS_INVALID_PT_MODE: Command is not permitted in current operating mode.Step Into: StartConfiguration
Step out: StartConfiguration error 3
After StartConfiguration 3
Step Into: CheckPKIPPSPIDStatus
Connected to HECI driver, version: 7.1.70.1198
Step out: CheckPKIPPSPIDStatus error 0
Connect to : at port: 9971:Unable to connect to server! ()
Sending the hello message has failed!
Connect to : at port: 9971:Unable to connect to server! ()
Sending the hello message has failed!
Connect to : at port: 9971:Unable to connect to server! ()
Sending the hello message has failed!
Exit with code 7

I have restarted the target machine after running the activator, but it doesn't seem to make a difference. Feel like Im close to fixing this, but at a dead end?

Our environment is SCCM 2007 R2 SP3, we have been provisioning without issue for years.  We have just received new hardware, HP EliteDesk 800 G1, BIOS version L01 v02.21 (latest), ME firmware version 9.0.20.1447 (latest), Intel Windows 32bit drivers ver 9.0.3.1347 (latest). 

While these new machines fail, we are still deploying some older HP 8300's that are provisioning fine.

The process proceeds as normal until it receives the error Can NOT get OTP from target device. Provisioning log details below.

Any help would be appreciated at this point. _800

Hello,

Upgrade from SMP 7.1 to SMP 7.5 uninstall SCS. The db is still there.

I managed to install 5.5 to the existing db. Now I need to upgrade to version 9.

The upgrade guide instructs to install latest version on existing database.

Thats not going to work. I thing I need to upgrade in steps to 6 to 7 to 8 and than to 9, correct?

I don't find the links to download version 8.2 that is required for upgrade to version 9.

Or any of the other versions.

Where to I download older versions?

Regards

Kent.

I'm attempting to install the SCCMAddon package on our primary site server and getting the following errors in the log:

2014-03-28 13:43:50,670 - DEBUG: Starting

2014-03-28 13:43:50,670 - INFO : Starting Log

2014-03-28 13:43:50,686 - INFO : Version: 2.0.22.319

2014-03-28 13:43:50,764 - INFO : No previous settings found.

2014-03-28 13:43:50,998 - DEBUG: Entering SettingsViewModel.ctor

2014-03-28 13:43:51,381 - FATAL: Could not identify SCCM installation

System.NullReferenceException: Object reference not set to an instance of an object.

   at SCSWMI.WMI_SCCM_Server_DAL.GetSCCMVersion(SCCM_Version& ver)

   at SCCMConfig.DAL.SCCMProber.GetVersion(WMI_SCCM_Server_DAL wql)

   at SCCMConfig.DAL.SCCMProber.Detect()

   at SCCMConfig.Actions.ActionPerformer.Detect()

   at Intel.SCS.ACIWizard.ViewModel.WelcomeViewModel.<Init>b__8()

As shown in the log I'm using the latest version of 2.0.22.319.

Hello all,

  I am hoping that you are able to help me. I bought an Intel DQ87PG motherboard, with an Intel I7-4770s processor, to use as a small home server ( ESXi whitebox ) . What I am trying to do now ( as there are no ESXi CIM providers for Intel ,as far as I know ) is to monitor my hardware remotely  .

  I am more interested in CPU temperature etc  , stuff that I can see via BIOS and I am pretty sure that should be available using some sort of 3rd party application that utilizes the AMT feature .

Therefore, could some one recommend this sort of application , if it exists ?

Thank you in advance for your time !