OOB - AMT status is Detected

Hello,
I'm trying to configure Out of Band on System Center 2012 R2 Configuration Manager, after following what Microsoft publish on TechNet I couldn't provision any computers, the status was detected and not supported for some machines.
I test on computers Lenovo T400 and Lenovo T430 and both giving me the same status : Detected.
according to Microsoft Detected means: AMT capability is detected on this computer, but the out of band service point is unable to provision it for AMT. This scenario can occur when the computer has been previously provisioned for AMT outside the Configuration
Manager site and the password for the AMT Remote Admin Account or the MEBx Account has been changed and is unknown.
I don't think that those computers previously provisioned. Any one had this issue before ?
Abduljalil Abolzahab

Hi,
Here is a lenovo document about Intel AMT OOB for your reference.
http://www.lenovo.com/images/products/server/pdfs/tech_resources/thinkserver_ts440_with_amt_tr.pdf
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

OOB - AMT status Not Supported failed to establish tcp session to ip address : 16993

Hello,
We have System Center 2012 R2 Configuration Manager, we configured Out Of Band but in AMT status it's showing: not Supported.
I checked amtopmgr.log and found the following:
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.130.129.160:16993.
Also certificates are configured.
I checked device in BIOS, I found AMT enables and also I can confirm that device support intell vpro.
Thanks
Abduljalil Abolzahab

See if the link below helps.
https://communities.intel.com/thread/1813
Juke Chou
TechNet Community Support

AMT - device in 'detected' status

Hello everyone,
I'm trying to get Out of Band working, and the one machine that I'm testing for this purpose seems to be stuck at 'detected' status. I gone over the configuration steps twice, but I can't seem to pinpoint what I've missed.
Here's the log from amtopmgr.log file (this portion of the log is when I perform a "Discover AMT Status" task.
Being my first time trying to get Out of Band working, I really don't know where to start my troubleshooting efforts here.
==============
AMT Discovery Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Wait 3600 seconds...
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Reading Discovery Instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{7D90B636-860E-4509-9101-748A98871927}.RDC...
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, '16777231', 'LAB'
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine X1212 (X1212.GLLAB2.COM), ID: 16777231 IP: 172.16.16.69 from Resource 16777231.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 16777231
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
Discovery will use ip resolved from netbios:
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
172.16.16.69 SMS_AMT_OPERATION_MANAGER
12/13/2011 1:53:47 PM 4528 (0x11B0)
AMT Discovery Worker: Execute query exec AMT_GetProvAccounts
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Finish reading discovery instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{7D90B636-860E-4509-9101-748A98871927}.RDC
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Parsed 1 instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Send task X1212.GLLAB2.COM to completion port
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
General Worker Thread Pool: Current size of the thread pool is 1
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: 1 task(s) are sent to the task pool successfully.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=SCCM2012-RC1.GLLAB2.COM SITE=LAB PID=2256 TID=4528 GMTDATE=Tue Dec 13 18:53:47.749 2011 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER
12/13/2011 1:53:47 PM 4528 (0x11B0)
AMT Discovery Worker: There are 1 tasks in pending list
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Wait 20 seconds...
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: There are 1 tasks in pending list
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
AMT Discovery Worker: Wait 20 seconds...
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
4528 (0x11B0)
General Worker Thread Pool: Work thread 3188 started
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
3188 (0x0C74)
Discover X1212 using IP address 172.16.16.69
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
3188 (0x0C74)
DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER
12/13/2011 1:53:47 PM 3188 (0x0C74)
Error 0x80090325 returned by InitializeSecurityContext during follow up TLS handshaking with server.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
3188 (0x0C74)
**** Error 0x2040b350 returned by ApplyControlToken
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
3188 (0x0C74)
DoSoapDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM
3188 (0x0C74)
Error 0x80090325 returned by InitializeSecurityContext during follow up TLS handshaking with server.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
**** Error 0x2040b350 returned by ApplyControlToken
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
DoSoapDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
session params : https://X1212.GLLAB2.COM:16993 , 11001
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Description: The I/O operation has been aborted because of either a thread exit or an application request.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
session params : https://X1212.GLLAB2.COM:16993 , 11001
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Description: The I/O operation has been aborted because of either a thread exit or an application request.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Start Kerberos Discovery SMS_AMT_OPERATION_MANAGER
12/13/2011 1:53:48 PM 3188 (0x0C74)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
session params : https://X1212.GLLAB2.COM:16993 , 484001
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Description: The I/O operation has been aborted because of either a thread exit or an application request.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
DoKerberosWSManDiscovery failed. SMS_AMT_OPERATION_MANAGER
12/13/2011 1:53:48 PM 3188 (0x0C74)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
session params : https://172.16.16.69:16993 , 15001
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Description: The I/O operation has been aborted because of either a thread exit or an application request.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
session params : https://172.16.16.69:16993 , 15001
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Description: The I/O operation has been aborted because of either a thread exit or an application request.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
Discovery to IP address 172.16.16.69 succeed. AMT status is 1.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
CSMSAMTDiscoveryTask::Execute, discovery to X1212 succeed. AMT status is 1.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='X1212.GLLAB2.COM' P2='' P3='' P4='' P5=''
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\r6k9m27y.SMX
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
General Worker Thread Pool: Succeed to run the task X1212.GLLAB2.COM. Remove it from task list.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
General Worker Thread Pool: Work thread 3188 has been requested to shut down.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
General Worker Thread Pool: Work thread 3188 exiting.
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
3188 (0x0C74)
General Worker Thread Pool: Current size of the thread pool is 0
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM
2864 (0x0B30)
AMT Discovery Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:54:07 PM
4528 (0x11B0)
AMT Discovery Worker: Wait 3600 seconds...
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:54:07 PM
4528 (0x11B0)
AMT Maintenance Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:59:50 PM
2808 (0x0AF8)
AMT Maintenance Worker: Wait 3600 seconds...
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:59:50 PM
2808 (0x0AF8)
AMT Operation Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:59:50 PM
1396 (0x0574)
AMT Operation Worker: Wait 3600 seconds...
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:59:50 PM
1396 (0x0574)
AMT WOL Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 1:59:50 PM
3848 (0x0F08)
AMT WOL Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER
12/13/2011 1:59:50 PM 3848 (0x0F08)
Succeed to add new health check task to pending list.
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
6128 (0x17F0)
AMT Provision Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
6128 (0x17F0)
AMT Provision Worker: Send task to completion port
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
6128 (0x17F0)
General Worker Thread Pool: Current size of the thread pool is 1
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
6128 (0x17F0)
AMT Provision Worker: 1 task(s) are sent to the task pool successfully.
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
6128 (0x17F0)
General Worker Thread Pool: Work thread 4952 started
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
Test https://SCCM2012-RC1.GLLAB2.COM:443/EnrollmentService/AmtEnrollmentService.svc
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
[EnrollmentWrapper]: SCCMCertCredentials - finding self signed sms cert by thumbprint
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
[EnrollmentWrapper]: FindCertificate - finding in LocalMachine, store Sms, find type FindByThumbprint, validOnly = False
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
[EnrollmentWrapper]: FindCertificate - there are 6 certs in the specified store
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
[EnrollmentWrapper]: FindCertificate - Found certs via FindByThumbprint, count = 1
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
[EnrollmentWrapper]: FindCertificate - cert[0].FriendlyName = Site System Identification Certificate
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
[EnrollmentWrapper]: FindCertificate - cert[0].Subject = CN=Site System Identification
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
[EnrollmentWrapper]: FindCertificate - cert[0].Issuer = CN=Site System Identification
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
4952 (0x1358)
STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=SCCM2012-RC1.GLLAB2.COM SITE=LAB PID=2256 TID=6128 GMTDATE=Tue Dec 13 19:07:12.175 2011 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER
12/13/2011 2:07:12 PM 6128 (0x17F0)
AMT Provision Worker: There are 1 tasks in pending list
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
6128 (0x17F0)
AMT Provision Worker: Wait 20 seconds...
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:12 PM
6128 (0x17F0)
TestEnrollmentService succeed. SMS_AMT_OPERATION_MANAGER
12/13/2011 2:07:27 PM 4952 (0x1358)
STATMSG: ID=7220 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=SCCM2012-RC1.GLLAB2.COM SITE=LAB PID=2256 TID=4952 GMTDATE=Tue Dec 13 19:07:27.783 2011 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER
12/13/2011 2:07:27 PM 4952 (0x1358)
General Worker Thread Pool: Succeed to run the task . Remove it from task list.
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:27 PM
4952 (0x1358)
General Worker Thread Pool: Work thread 4952 has been requested to shut down.
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:27 PM
4952 (0x1358)
General Worker Thread Pool: Work thread 4952 exiting.
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:27 PM
4952 (0x1358)
General Worker Thread Pool: Current size of the thread pool is 0
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:27 PM
2864 (0x0B30)
AMT Provision Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:32 PM
6128 (0x17F0)
AMT Provision Worker: Wait 3600 seconds...
SMS_AMT_OPERATION_MANAGER 12/13/2011 2:07:32 PM
6128 (0x17F0)
=============
Here's a portion of the client's oobmgmt.log file:
BEGIN oobmgmt
12/13/2011 12:16:33 PM 1076 (0x0434)
Retrying to activate the device. oobmgmt
12/13/2011 12:16:33 PM 1076 (0x0434)
Get CoreVersion: 7.1.20 oobmgmt
12/13/2011 12:16:33 PM 1076 (0x0434)
New OTP generated oobmgmt
12/13/2011 12:16:33 PM 1076 (0x0434)
This version supports wireless. oobmgmt
12/13/2011 12:16:33 PM 1076 (0x0434)
Get wired ip: 172.16.16.69 oobmgmt
12/13/2011 12:16:33 PM 1076 (0x0434)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of SMS_OOBMgmt_StartConfig_Success
ClientID = "GUID:00189f1a-de20-4ca4-b2d1-42a5d370e423";
ConfigurationStartTime = "2011-12-13 12:16:34";
DateTime = "20111213171634.066000+000";
MachineName = "X1212";
ProcessID = 2312;
SiteCode = "LAB";
ThreadID = 1076;
oobmgmt
12/13/2011 12:16:34 PM 1076 (0x0434)
Successfully activated the device. oobmgmt
12/13/2011 12:16:34 PM 1076 (0x0434)
END oobmgmt
12/13/2011 12:16:34 PM 1076 (0x0434)
ON SCHEDULE OOBMgmt
12/13/2011 1:16:33 PM 1300 (0x0514)
BEGIN oobmgmt
12/13/2011 1:16:33 PM 1300 (0x0514)
Retrying to activate the device. oobmgmt
12/13/2011 1:16:33 PM 1300 (0x0514)
Get CoreVersion: 7.1.20 oobmgmt
12/13/2011 1:16:33 PM 1300 (0x0514)
Resending last OTP oobmgmt
12/13/2011 1:16:33 PM 1300 (0x0514)
This version supports wireless. oobmgmt
12/13/2011 1:16:33 PM 1300 (0x0514)
Get wired ip: 172.16.16.69 oobmgmt
12/13/2011 1:16:33 PM 1300 (0x0514)
Successfully activated the device. oobmgmt
12/13/2011 1:16:33 PM 1300 (0x0514)
END oobmgmt
12/13/2011 1:16:33 PM 1300 (0x0514)

I made some changes on the desktop end - changed the MBEx password from 'admin' (which it was giving me errors as well), to my own password. I added this new user/password to SCCM, MEBx account configuration. I ran another 'Discover AMT Status' on the device;
I review the logs (got the same errors as mentioned above), but this time I went to check the MBEx settings and I actually found some information in it that must have been setup by SCCM (see screenshot).
That was my only change to the desktop (just a password change).

Reprovision AMT Computers in Detected Status

I am new to AMT ,trying to re-provision computers sitting in SCCM2012 R2 . AMT has been setup by someone earlier.
Tried to check on Certificate authority settings appear right as per our domain admin
We have AMT collection and detection query set up for Provisioned, Detected
I verified security groups for AMT and permissions
Is their a simple way to re-provision computer from Detected status.
I tried run Discover AMT status on client in Manage Out of band.
Could you please advise steps to provision computers in AMT and any logs I can check
Requesting assistance..
RJ
RJ09

Thanks Peter for replying quickly..
I have followed this and verified all security settings and permissions.
I can access Manage Out of Band>Power Control and Power On/Off and restart pc
But Out of Band Manager Console doesn't work.
Under Tools> Serial over LAN connection is greyed out.
Status at botom shows: System: Disconnected, IDE-Re-direct and Serial Connection: Inactive
I have tried Tools>Options> connecting using PC ANSI and VT-100
I checked oobmgmt.log on various client machines and got following error
CAMTProvisionEndpoint::GetProvisionSettings: GetObject() failed: 80041002
!! AutoProvision policy disabled.
END
ON SCHEDULE
BEGIN
CAMTProvisionEndpoint::GetProvisionSettings: GetObject() failed: 80041002
For Device Collection I have Provisioning for AMT-based computers checked on Out of band management
Advise please..
RJ09

Rebuilding OOB/AMT/VPro Provisioned Machines Automating Reset

Hi All,
Does anyone have any idea how I can add Out of Band steps into a task sequence so I can unprovision and (less importantly) force re-provisioning of AMT during OSD.
We have had DNS issues with the AMT controller and the Operating System competing for the same IP address and registering different host names when machines are rebuilt with a different name.
We can reset them either manually or from the SCCM console but I'd like to remove the chance of human error if possible and make this cleaner. I have seen some information about Intel Reflector command line utility but all the links I find are dead.
Thanks,
Shaun

I have found the Intel Reflector downloads but it seems to require a client and server setup which is way beyond what I was after. Has anyone used the powershell cmdlets for IntelvPro and could give me some advice on how I might use them to unprovision a
machine?
Thanks.

OOB AMT Computer / USER object AD

Hello there,
Can somebody give me some information about the computer account object that is created by OOB in AD with turns out to be a user object if you want to find it.
The problem is that if you look in AD and use the find object standard you can not directly search for computers. Now you have the OOB computer object htere and you will find that object.
We now have thus 2 computer objects with the same nane
i placed all of the strange OOB objects to a container but the are still found.
it is very irritating if you want to ad something to a group and you have to check everytime you have the right object.
can't this be done different?

Hello there,
Can somebody give me some information about the computer account object that is created by OOB in AD with turns out to be a user object if you want to find it.
The problem is that if you look in AD and use the find object standard you can not directly search for computers. Now you have the OOB computer object htere and you will find that object.
We now have thus 2 computer objects with the same nane
i placed all of the strange OOB objects to a container but the are still found.
it is very irritating if you want to ad something to a group and you have to check everytime you have the right object.
can't this be done different?
This help?
http://technet.microsoft.com/en-us/library/cc431452.aspx

HELP!! OOB status Stuck on Detected

Hello All,
I need some OOB Intel vPro AMT support.
We have OOB up and running in our environment true SCCM 2007 R3
We have like 700 HP8200 machines running and about a 100 off them have the AMT status "detected" but get not provisioned.
Nou if i crawl true the logs there is a certificate problem.
Now if i go to a problem machine and do a full unprovision in the AMT Bios and delete the AD user/machine object(i gues this is where the cert is stored) the machine gets provisend again with succes.
As you can see i have found a solution to my problem, my next challange is to automate this!!!
How can i reset those AMT cards remotely? if SCCM can not connect to them how wil i be able to do this?
Strange thig is also if i take a look in to the AMT bios itself tis is configed with my SCCM server.
but i can not connect to it remotly and unconfigure it remotely.
please help!
many thanks
Roger

Yes, I know this is an old post, but I’m trying to clean them up.
So from the sound of this, this is not a CM07 issue but an AMT issue.
As for automating this, I’m not sure, Can you automatic set the AMT bios to un-provisioned? This question would be better suited for the Intel forum than here. They can answer that part of the question., from there you can slow piece together a script to
full automate this.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Life Events Created for Dependents in Detected Status

Hi! Please help me understand this.... When a life event (Ex: Ineligible Dependent) is processed for an employee to end the ineligible dependent coverage, a New Hire Life event is assigned in detected for the dependent. What is causing this and what should be changed to stop this. Thanks and Appreciate your help.
Vamsee

I made some changes on the desktop end - changed the MBEx password from 'admin' (which it was giving me errors as well), to my own password. I added this new user/password to SCCM, MEBx account configuration. I ran another 'Discover AMT Status' on the device;
I review the logs (got the same errors as mentioned above), but this time I went to check the MBEx settings and I actually found some information in it that must have been setup by SCCM (see screenshot).
That was my only change to the desktop (just a password change).

Error OOB SCCM 2012 R2 - AMT vPro

I am running SCCM 2012 R2 to make the provisioning of vPRO, but I'm encountering some difficulties.
At first when efetued the configuration of Intel SCS 9, unable to login normally efetued some tests shutdown and power on and functioned normally. The next day when I got to the office, was no longer running the web interface, I'm not getting login. No changes
were made in the environment during this period. When I try to make the AMT discovery in SCCM, it generates me the error "Failed to establish tcp session" and gives me the IP and the host port 16993. If I place the PSK or PKI configuration within
the MEBx, it generates a user and password error saying it can not authenticate with the Admin user.
Already redid the procedure following the Intel and Microsoft manual, but the error persists. SCCM can identify the version of vPRO, but the status it says "Can not Stand", regardless of the version ... 4.x, 5.x and 6.x, it displays the same message
every time.
This is the log of the error when I'm not using PSK setting in the MEBx that is generated in the AMT discovery of SCCM
================================================================
AMT Discovery Worker: Wait 9 seconds... SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:47 2984 (0x0BA8)
Discover INFRANOTE using IP address 10.234.9.13 SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:46 4492 (0x118C)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.234.9.13:16993. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)
DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)
Discovery to IP address 10.234.9.13 succeed. AMT status is 0. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)
CSMSAMTDiscoveryTask::Execute, discovery to INFRANOTE succeed. AMT status is 0. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)
================================================================
And this is the log generated when using PSK / PKI configuration in MEBx:
================================================================
DoPingDiscoveryForAMTDevice succeeded.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:25
5336 (0x14D8)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:25
5336 (0x14D8)
**** Error 0x1d38b100 returned by ApplyControlToken
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:25
5336 (0x14D8)
DoSoapDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
**** Error 0x1d38b100 returned by ApplyControlToken
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoSoapDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://FQDN COMPUTER:16993
, 11001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://FQDN COMPUTER:16993
, 11001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Start Kerberos Discovery
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://FQDN COMPUTER:16993
, 484001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoKerberosWSManDiscovery failed.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://IP + Port (16993)
, 15001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
session params : https://IP + port (16993)
, 15001
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Description: A security error occurred
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
DoWSManDiscovery failed with user name: admin.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
Discovery to IP address 10.234.10.84 succeed. AMT status is 1.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
CSMSAMTDiscoveryTask::Execute, discovery to "COMPUTER NAME succeed. AMT status is 1.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:26
5336 (0x14D8)
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
08/12/2014 17:01:27
5336 (0x14D8)
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\w73tgg1d.SMX
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
General Worker Thread Pool: Succeed to run the task "FQDN". Remove it from task list.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
General Worker Thread Pool: Work thread 5336 has been requested to shut down.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
General Worker Thread Pool: Work thread 5336 exiting.
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
5336 (0x14D8)
General Worker Thread Pool: Current size of the thread pool is 0
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:27
3696 (0x0E70)
AMT Discovery Worker: Wakes up to process instruction files
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:45
3728 (0x0E90)
AMT Discovery Worker: Wait 3600 seconds...
SMS_AMT_OPERATION_MANAGER
08/12/2014 17:01:45
3728 (0x0E90)
Could anyone help?
Thank you.

I wouldn't even try using CM with AMT. CM only supports some of the older Vpro chipsets. I had a case open with CSS and they literally suggested that I use the Intel software instead of CM.
John Marcum | Microsoft MVP - Enterprise Client Management
My blog: System Center Admin | Twitter:
@SCCM_Marcum | Linkedin:
John Marcum

Detection of UP/DOWN status takes over 4 minutes

Hi all,
I discovered that Grid Control detects the UP or DOWN status
of for example an IAS HTTP_Server just after 4 minutes.
Is there any setting where you can configure this
to a lower value ( 1 minute for example) ?
Thanks for any replies.....

this is default collection time, and can change by
the userI know because I changed it myself from 5 minutes to 1 minute. But why is the down status still detected by GRID after 4 or more minutes ???
Message was edited by:
Raymond Vermeer

OoB Problems with SCCM 2012 SP1 CU1

Hi around, perhaps somone has tried this things out already and has a little hint for me.
After we got OoB Managment to work under SCCM 2007 we switched to SCCM 2012 now i have some problems bringing it to work again.
We use a Verisign Certificate for Provisioning, the Firewall Ports (9971 on Server and 19992, 16993 and 16995 on Client) are opend. The autoenrollment is active. DHCP 06 and 15 are set and configured.
The IIS SSL Settings are configured to accept Client Certificates and the Bindings are set to the Web Server Template. We tried to configure it using the Verisign Certificate but it didn't work that way either.
The Webserver Template is build after the Step by Step guide from MS.
The Verisign Certificate was build the same way, Organization Unit is set to Intel(R) Client Setup Certificate. It was imported in the Personal Certificate Store, exported and implemented in the Enrollment Point.
The AD Group exists and the Oob Managment Server has the permissions it needs.
The Oob Managment Point was configured like shown in the MS Step by Step guide.
The Client i'm testing with was fully unprovisioned.
Now the only Status i get is detected and when i try to discover AMT the amtopmgr.log brings the following errors.
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
**** Error 0x1e5ab3d0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
**** Error 0x1e5ab3d0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://OurMachine.test.de:16993 , 11001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://OurMachine.test.de:16993 , 11001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Start Kerberos Discovery SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://OurMachine.test.de:16993 , 484001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoKerberosWSManDiscovery failed. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://10.37.135.52:16993 , 15001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
session params : https://10.37.135.52:16993 , 15001 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
Discovery to IP address 10.37.135.52 succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
CSMSAMTDiscoveryTask::Execute, discovery to OurMachine succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
CSMSAMTDiscoveryTask::Execute - DDR written to D:\CM2012\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='OurMachine.test.de' P2='' P3='' P4='' P5='' SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
CStateMsgReporter::DeliverMessages - Created state message file: D:\CM2012\inboxes\auth\statesys.box\incoming\vww2tcjc.SMX SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
General Worker Thread Pool: Succeed to run the task OurMachine.test.de. Remove it from task list. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
General Worker Thread Pool: Work thread 3624 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
General Worker Thread Pool: Work thread 3624 exiting. SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 3624 (0x0E28)
General Worker Thread Pool: Current size of the thread pool is 0 SMS_AMT_OPERATION_MANAGER 12.07.2013 09:36:39 9236 (0x2414)
We double checked the admin Account in the OOB settings but the password is right and i can manually log in to the MEBX with it.
Has anyone some suggestions what could be wrong?
Thank's for the help.

Yes, I know this is an old post, but I’m trying to clean them up.
Did you solve this problem, if so what was the solution?
By the sounds of thing the problem is with your certificate. Can you manually provision a Certified to any of these systems?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Problem with Out of Band Discovery resulting with Out of Band features not available in SCCM console for computers with provisioned AMT device

Hi,
We configured the Out of Band component, but are using Intel SCS RCS to provision AMT devices remotely. The remote configuration process with Intel SCS works fine; we are able to connect to the AMT web UI and we can use a free KVM tool to manage the computer
remotely.
The AMT devices are configured with AD integration, so an object is created for each of them in a specific OU. Also, an AD group is added to the AMT devices so remote PT Administration permission is granted to it. This group includes the ConfigMgr Site
Server account, the account of the server running the Out of Band Service Point and my own user account.
This configuration seems OK since when connecting to the AMT web UI, I use Windows Integrated authentication with my user account and can manage the device successfully.
So the only step remaining is running the OOB discovery to enable Out of Band features for the computers in the SCCM console. We want to use the ConfigMgr OOB console. I right-click a computer or a collection and launch the AMT discovery. I check the OOB
server log, I don't see errors; the OOB service point connects to the AMT device and discover a status of 4, which is Externally provisioned, as expected. The problem is the AMT Status, AMT Version and Provisioned AMT fields for the computer in the ConfigMgr
console doesn't get updated, even after doing display refresh.
Here's the amtopmgr.log (I changed computer name and IP address information to protect client privacy) :
General Worker Thread Pool: Work thread 364 started SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
Discover COMPUTERA using IP address 192.168.12.7 SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 2792 (0x0AE8)
DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
session params : https://COMPUTERA.contoso.com:16993 , 11001 SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:25 364 (0x016C)
DoWSManDiscovery succeeded with user name: admin. AMTStatus = 1. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
Start Kerberos Discovery SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
session params : https://COMPUTERA.contoso.com:16993 , 484001 SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
DoKerberosWSManDiscovery succeeded. AMTStatus = 4. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
Discovery to IP address 192.168.12.7 16 15:16:32 364 (0x016C)
CSMSAMTDiscoveryTask::Execute, discovery to STI17259CPCO succeed. AMT status is 4. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
CSMSAMTDiscoveryTask::Execute - DDR written to E:\SMS\MP\OUTBOXES\ddr.box SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Fill Machine Property' SID=1 MUF=0 PCNT=5, P1='COMPUTERA' P2='' P3='COMPUTERA.contoso.com' P4='' P5='' SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
CStateMsgReporter::DeliverMessages - Created state message file: E:\SMS\MP\OUTBOXES\StateMsg.box\6heghx71.SMX SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='COMPUTERA.contoso.com' 16 15:16:32 364 (0x016C)
CStateMsgReporter::DeliverMessages - Created state message file: E:\SMS\MP\OUTBOXES\StateMsg.box\rmit91js.SMX SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
General Worker Thread Pool: Succeed to run the task COMPUTERA.contoso.com 16 15:16:32 364 (0x016C)
General Worker Thread Pool: Work thread 364 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
General Worker Thread Pool: Work thread 364 exiting. SMS_AMT_OPERATION_MANAGER 2014-06-16 15:16:32 364 (0x016C)
The Management Point is up and running.
Any suggestion or advice is welcomed!
Thank you
Patrick

I found something interesting on this problem, it seems the OOB discovery process is working fine, but for an unknown reason, the site server is not receiving the information from the OOB Service Point to update the AMT Status of the client in the SCCM
database.
The log tells me that a DDR file is created to be sent to the site server. When looking into the SMS\MP\Outboxes\ddr.box folder, I see about 50 DDR files, the oldest one is dated when I started testing OOB discovery.
So the server is unable to send the files to the site server.
Also, since I started this thread, I noticed another issue that could be related to this problem. The same server is also holding the State Migration Point role, it is working fine, but when doing USMT operations, the status of the computer association is
not updated in the console (In Progress, Completed, missing USMT store path, etc.). When looking into the SMS folder on the server, I see a big backlog of SVF files containing information related to the SMP.
I looked into the log files, but didn't find the errors yet to explain this.
The computer account of the server is a member of the SMS_SiteSystemToSiteServerConnection_Stat_XXX group on the site server.
Note that status messages are being sent successfully, I see them in the Monitoring node of the console under Component State, and there is no backlog in the SMS\MP\Outboxes\statemsg.box folder.
Tnx for your help
Patrick

Network Connectivity Status Indicator for IPv6 works wrong in Windows 7 and Windows 8

Hi Folks,
I am working on testing Network Connectivity Status Indicator for IPv6 in Windows 7 and 8.
Waht is "Network Connectivity Status Indicator(NCSI)" you can refer to https://technet.microsoft.com/en-us/library/ee126135%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
I found that even if Network Connectivity Status Indicator detect IPv6 connection to http://ipv6.msftncsi.com/ncsi.txt failed.
Windows IE still use IPv6 to connect to website first, rather than stop using IPv6 and to use IPv4.
It will cause IPv6 fallback to IPv4 problem, that's 21 secs and 7 secs delay for fallback in Windows 7 and 8.
Does anyone suffer the same problem?
Or someone know how this works?
Thanks!

Hi Roger_Wang0214,
"Windows IE still use IPv6 to connect to website first, rather than stop using IPv6 and to use IPv4."
By default Windows prefers IPv6 over IPv4,we can manually configure the IPv4 prefer over IPv6 if it has result in any troubles.
Here is a link for reference :
Resolving Internet connectivity issues after World IPv6 Launch (June 6, 2012)
https://support.microsoft.com/en-us/kb/2533454
"The "Prefer IPv4 over IPv6" Fix it solution will configure your computer to prefer IPv4, instead of IPv6. By default, Windows prefers IPv6 over IPv4. If you are having problems using IPv6 to connect to some websites, this may resolve the
problem."
For a Windows 7 machine ,we can try the following fixit tool to configure IPv4 prefer over IPv6 .For a Windows 8.1 machine ,we can configure it referring to the manual part .
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents
If the DisabledComponents entry is unavailable, we can create it (DWORD (32-bit) Value).Then set a value with "0x20"to prefer IPv4 over IPv6 by changing entries in the prefix policy table.
Here is a link for reference :
How to disable IPv6 or its components in Windows
https://support.microsoft.com/en-us/kb/929852
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Holding status

Hi,
Actually we monitor error in Adapter Engine with ALM, but only error status are detected.
We want to detect message in "holding" status in Adapter Engine, with ALM or CCMS, someone would have a solution?

hi,
but holding is not an error status so why do you need to monitor it?
if holding status is shown there are two possible reasons:
1. there is en error in the queue - so you will be alerted
2. the queueing takes too long - maybe the interface was designed in a wrong way if hardware is not an issue
so the holding status should not be your concern I guess and you need
to start with the real reason for this issue and not from the end
Regards,
Michal Krawczyk

OOB warning during IPS 4260 signature update via CSM

Hi,
During the recent IPS signatures updates via CSM, i have noticed that there was warning (below).
>OOB change detected - Out of Band(OOB)and sensor configuration change happened on device. But you selected to continue deployment in case of OOB. Continuing...
what is the cause & impact of such event?
As i suspected there is a mismatch of configuration, my inline interfaces are no longer applied to the virtual sensor 'VS0'. Could it be due to the mis-synchronisation?
Apprepriate for any advice.
thanks
cash

CSM keeps an internal copy of the configuration it last pushed to the sensor.
Each portion of the configuration has a configToken assigned to it by the sensor. The config token is a base 64 encoding of that configuration portion.
Each time CSM goes to push a new configuration it will compare the configToken of it's previously saved configuration for that sensor against the configToken of the configuration currently on the sensor.
If the 2 configTokens match, then no configuration change has been made since the last time that CSM pushed a configuration to the sensor. CSM can safely push the new configuration to the sensor.
If the 2 configTokens do not match, then an Out Of Band (OOB) configuration change has been made to the sensor. This means that the sensor's configuration has been modified by something other than CSM. This may have been a user changing something through the CLI or IDM instead of using CSM.
In these situations CSM gives you the option of either stopping the push of the new configuration so the detected changes can be imported and evaluated by the user, or to go ahead and push the changes to the sensor.
If you decide to go ahead and push the changes to the sensor, the outcome of the configuration change is not guaranteed.
The sensor may wind up merging the OOB changes in with the new configuration from CSM, or the CSM changes may wind up overwriting the OOB changes.
So telling CSM to push the new configuration even when OOB changes have been detected can be risky and can cause loss of some of your configuration.
I fyou will be making changes with CLI or IDM, then it is always best to import those changes into CSM before making further configuration changes in CSM.

OOB - AMT status is Detected

Similar Messages

Maybe you are looking for