Hello dear VPro Experts,
i discovered some problems while trying to manage VPRo Clients with SCCM 2012, perhaps someone has some tips for me.
After bringing OoB Provisioning to work under SCCM 2007 we startet migrating to SCCM 2012.
Now i have some problems getting it to work again. The machines I tried to provision are fully
unprovisioned, the MEBx Password is set to our standard Password.
We double checked the Prerequisites from the MS Technet page and installed and configured the Enrollment Point and OoB-Role on
our Primary Server.
The Certificates we use were newly created via Verisign in the same way we build the working Certificates under SCCM 2007.
The Web Server Certificates from our PKI was also newly created and implemented. Mei and Heki drivers are installed and
up to date.
The Client im testing with at the moment has the AMT Version 5.0.1.
Now I get the Problem, that I can’t provision the workstation via SCCM. When I try to discover the AMT status the amtopmgr.log
brings the following errors and the client is only shown as detected.
Discover
Testclient using IP address 10.37.135.52 SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 728 (0x02D8)
STATMSG:
ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=Testprimary.testing.oursite.de
SITE=P10 PID=5240 TID=7568 GMTDATE=Di Jul 16 06:38:09.468 2013 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568(0x1D90)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568 (0x1D90)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568 (0x1D90)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568 (0x1D90)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568 (0x1D90)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568 (0x1D90)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568 (0x1D90)
DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 728 (0x02D8)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568 (0x1D90)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 7568 (0x1D90)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 728 (0x02D8)
**** Error 0x3bb9b550 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 728 (0x02D8)
DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:09 728 (0x02D8)
Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
session params : https://Testclient.testing.oursite.de:16993,2011001 SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Start Kerberos Discovery SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
session params : https:// Testclient.testing.oursite.de:16993,2484001 SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
DoKerberosWSManDiscovery failed. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Flag iWSManFlagSkipRevocationCheck is set. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
session params : https://10.37.135.52:16993,2015001 SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Description: A security error occurred SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
Discovery to IP address 10.37.135.52 succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
CSMSAMTDiscoveryTask::Execute, discovery to Testclient succeed. AMT status is 1. SMS_AMT_OPERATION_MANAGER
16.07.2013 08:38:10 728 (0x02D8)
CSMSAMTDiscoveryTask::Execute - DDR written to D:\CM2012\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1= ‘Testclient.testing.oursite.de’ P2='' P3='' P4='' P5='' SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
CStateMsgReporter::DeliverMessages - Created state message file: D:\CM2012\inboxes\auth\statesys.box\incoming\w1p7jxgk.SMX SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
General Worker Thread Pool: Succeed to run the task
Testclient.testing.oursite.de. Remove it from task list. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
General Worker Thread Pool: Work thread 728 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
General Worker Thread Pool: Work thread 728 exiting. SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:10 728 (0x02D8)
General Worker Thread Pool: Current size of the thread pool is 0 SMS_AMT_OPERATION_MANAGER 16.07.2013
08:38:10 5436 (0x153C)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 16.07.2013
08:38:29 7568 (0x1D90)
AMT Discovery Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER 16.07.2013 08:38:29 7568 (0x1D90)
AMT WOL Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 16.07.2013 09:04:22 8572 (0x217C)
AMT WOL Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER 16.07.2013 09:04:22 8572 (0x217C)
We tripple checked the admin account and password but it's the same we use to log in the MEBx and that works without problems.
Hope someone can share some lightfor this problem.