1 Reply Latest reply on Dec 10, 2014 5:51 AM by xorixon




      I have a problem with SCCM discovery AMT status. AMT status is not present in SCCM collection, therefore I cannot run OOB console. AMT computers are "externally provissioned" by Intel SCS 9.1, but OOB discovering cannot discover this status. Here is part of AMTOPMGR.log:


      AMT Discovery Worker: Reading Discovery Instruction E:\SMS\inboxes\amtopmgr.box\disc\{1491AB4F-6048-4E83-B5B8-3230E06A1D7C}.RDC...~  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:39:49.825-60><thread=3116 (0xC2C)>

      *** [08001][10060][Microsoft][SQL Server Native Client 11.0]TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.~~  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:55.979-60><thread=3116 (0xC2C)>

      *** [HYT00][0][Microsoft][SQL Server Native Client 11.0]Login timeout expired  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:55.979-60><thread=3116 (0xC2C)>

      *** [08001][10060][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:55.979-60><thread=3116 (0xC2C)>

      *** Failed to connect to the SQL Server, connection type: AMTOM_ACCESS.  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:55.979-60><thread=3116 (0xC2C)>

      Error: Failed to get connection to the configured SQL database.  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:55.979-60><thread=3116 (0xC2C)>

      Failed to connect SMS database.  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:55.979-60><thread=3116 (0xC2C)>

      AMT Discovery Worker: Error, CSMSAMTDiscoveryWorker::ParseInstructionFile - unable to parse instruction Source,CollectionID,Collection,TP10000B,~  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:55.979-60><thread=3116 (0xC2C)>

      AMT Discovery Worker: Finish reading discovery instruction E:\SMS\inboxes\amtopmgr.box\disc\{1491AB4F-6048-4E83-B5B8-3230E06A1D7C}.RDC~  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:55.994-60><thread=3116 (0xC2C)>

      AMT Discovery Worker: Parsed 1 instruction files  $$<SMS_AMT_OPERATION_MANAGER><11-05-2014 16:44:56.010-60><thread=3116 (0xC2C)>



      I have founded a error with SQL communication (started with „TCP Provider“). Can It be communication problem between OOB role server and SQL or SQL provider?


      OOB Service Point role and Enrollment Point role are installed on new site server.








        • 1. Re: AMT DISCOVERY IN SCCM 2012 (CU5)

          The problem was solved. Out of Band Service Point role server (service SMS_AMT_OPERATION_MANAGER) must have direct access to SQL server, where SCCM site database is placed. After we have opened TCP port 1436 for new site server (OOB Service Point), AMT discovery works OK. AMT status value is now 4 - Externally Provisioned and OOB Console works too.