Hello,
I am trying to provision some laptops with sccm 1602 current branch. When trying to run the configure and discovery task sequence I am getting errors. I checked the smsts log and I am getting the following errors "Failed to write to file, possible reason - insufficient permissions in the selected folder. The file exist but write/modify access to it is denied. The file name contains invalid characters (ConfigAMT.Log).
@We are having an issue using VNC and the Manageability Commander Tool. The issue is that we have 3 systems provisioned but only one of the 3 systems is able to remote into the others via AMT KVM. For example: System A can remote into System B and System C. System C cannot remote into B or A. Likewise System B cannot remote into C or A.
Has anyone had this issue and have knowledge on how to fix it?
The systems are Dell Latitudes E7440 (system A), Latitude E6440 (system B), and Latitude E6530 (system C).
All have Windows 8.1 Enterprise.
All provisioned using Intel SCS version 11
All accessible via their web URL (https://SystemX.site.corp:16993)
Reviewing parts to make a computer for work, i was more or less set on z170 boards when i stomped on Q170 which as i read has a feature called vpro. It is my understanding that over a hardware chip Vpro let do some work on a computer from distance, and also to automate some IT related maintenance tasks like backup scheduling if im not wrong, or even accessing your files remotely without the need to load the os. However im not sure if any of those or any other feature i have not yet heard of is at the reach of a sole self employed worker or a Small home Office working platform. I have no idea if any of those capabilities are for example available on some Windows edition, or if there are free or affordable software around, or even if some or most of them are actually managed from the bios manager.
Could you clarify me if im wasting efforts looking in that q170 vpro direction because is not meant nor usable for this use scenario. Or are there in fact advantages on it, like making your desktop accessible from your laptop for some tasks.
Keep in mind main use in the computer will be multitasking around content related, and data managing. Anything that could help in terms of productivity, either making some tasks faster, or easier with less manual input or automation will be highly appreciated.
Hi All,
So I have gone through the steps to get the SCCM 2012 Add On configured. I had some issues with getting Intel AMT: Discovery working, but I've resolved that now and now I am trying to run the Intel AMT: Configuration Task Sequence. I'm having a lot of issues with this one and it seems to be failing on me. I was hoping that someone here has had some experience with this and can assist?
I've attached my SMSTS.log file which is coming up with a few errors when I'm trying to run the script. I'm seeing errors about DNS, FQDNs, Event IDs about incorrect usernames and passwords etc (screenshot attached for that one)
Basically I've been looking into this one for a while now and I'm banging my head against the desk. How does one get this to work? I've not really seen anything online which has a solution for this.
Hello,
After I configured AMT in MEBx, I am not able to access the web UI on port 16992, nor able to connect via any tool. Port seems to closed (based on the telent console behavior) so I suspect the problem should be in the MEBx configuration or HW support. For the MEBx configuration, I was able to configure other PCs (different HW) successfully which brings me to believe the setup may be correct.
If I'm able to configure it in MEBx and enable it in BIOS is it still possible there is an incompatible HW in the path? How could I narrow this down and find the piece that may cause it?
(Q77 chipset, AMT v8)
Thank you for suggestions,
Tomas Fabry
Honeywell International
Hi,
we have a VPN server with SSTP connection, which authenticated by user credentials and Server certificate on 2012 R2.
Now i must implement SSTP connection with user credentials and user certificate.
I found that there are many solution to store user certificates not in their OS, but in the TPM or IPT. Fine.
maybe has someone the documentations how to configure all this?
how i can import the certificates into IPT?
how i can say to VPN client - hey, please use a certificate from IPT?
thank you very much!
I would like to manage my vPro-clients by using microsoft SCCM. However, if I choose 'out of band management --> discover management controllers', nothing happens.
Can somebody help me?
The following messages can be found in the logfile amtopmgr.log
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Reading Discovery Instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{53F9FDEF-4DF3-43A7-9EF4-94A5926085D8}.RDC... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, 'GUID:7A7A25F0-45A3-4D69-A5A4-8EA6BB814E36' SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine PC1 (pc1.testlab.com), ID: 6 - 192.168.0.12 from Resource GUID:7A7A25F0-45A3-4D69-A5A4-8EA6BB814E36. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 6 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Finish reading discovery instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{53F9FDEF-4DF3-43A7-9EF4-94A5926085D8}.RDC SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Parsed 1 instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Send task to completion port SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
Auto-worker Thread Pool: Current size of the thread pool is 1 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: 1 task(s) are sent to the task pool successfully. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
Auto-worker Thread Pool: Work thread 3860 started SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 3860 (0x0F14)
STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=SCCM SITE=C01 PID=2084 TID=2776 GMTDATE=Wed Apr 09 06:06:09.218 2008 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:29 2776 (0x0AD8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:29 2776 (0x0AD8)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 192.168.0.12:16992. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
CAMTDiscoveryWSMan::CreateWSManConnectionOptions - No acct/password available for wsman connection SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Error 0x80090308 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Error 0x3afb9e0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Error 0x80090308 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Error 0x3afb9e0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
CAMTDiscoveryWSMan::DoSoapDiscoveryForAMTDevice: unable to perform soap based discovery to amt device 192.168.0.12 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Auto-worker Thread Pool: Succeed to run the task . Remove it from task list. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:49 2776 (0x0AD8)
AMT Discovery Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:49 2776 (0x0AD8)
Auto-worker Thread Pool: Work thread 3860 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:07:10 3860 (0x0F14)
Auto-worker Thread Pool: Work thread 3860 exiting. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:07:10 3860 (0x0F14)
Auto-worker Thread Pool: Current size of the thread pool is 0 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:07:10 2732 (0x0AAC)
Incoming Connection from 192.168.0.12:16994. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Incoming data is - Configuration version: PKI Configuration. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Count : 8 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
UUID : 4C4C4544-0034-3610-8033-C6C04F46334A SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Warning: AMT device 4C4C4544-0034-3610-8033-C6C04F46334A is a SMS client. Reject hello message to provision. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Waiting for incoming hello message from AMT devices... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Incoming Connection from 192.168.0.12:16994. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Incoming data is - Configuration version: PKI Configuration. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Count : 9 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
UUID : 4C4C4544-0034-3610-8033-C6C04F46334A SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Warning: AMT device 4C4C4544-0034-3610-8033-C6C04F46334A is a SMS client. Reject hello message to provision. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Waiting for incoming hello message from AMT devices... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
We're half way into a deployment of new pcs all with vPro. My AMT SCS Console is full of new UnProvisioned sytems. Do I attempt to provision them now, say with a script run on each system (RMT) or wait for SCCM SP1 and hope that there will be built-in hooks to provision the systems there?
We need some help. We are receiving an SSL error when attempting to remote configure our Dell notebooks
We have a Go Daddy CA for provisioning our Dell notebooks. However, we are still unable to remote configure our vPro equipped systems.
Lan Setup:
Our Active Directory suffix is mycompany.corp (.corp is our AD Zone)
Our DHCP option 14 issues a suffix of pb.mycompany.com (.com is our Unix based zone)
Our Go Daddy CA is pb.mycompany.com
Our RCS server is pbvproap01.pb.mycompany.com
Error message from one of our notebooks:
Operation: Configuration
Date and Time: 8/22/2016 11:13:55 AM
Error Code: 3221246495
Severity: Failure
UUID: 4C4C4544-0030-3810-8047-C2C04F565931
Intel AMT FQDN: Notebook1.pb.mycompany.com
Intel AMT IPv4: 192.168.164.5
Server Name: pbvproap01.mycompany.corp
Description: An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable.
Failed while calling
WS-Management call
GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error
0xc000521c: A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target.
Valid certificate for PKI configuration not found.
we have > 500 computers with 500 GB hard drives and I noticed that most are filling up at an alarming rate. the culprit was the Intel(R) Management and Security Application Local Management Service (lms.exe) is creating a log file
%systemroot%\sysWOW64\gms.log.
I cannot find how to configure the log file or the service to limit the growth of the file. I had to disable the Intel(R) Management and Security Application Local Management Service, then delete the file.
My question is, what is this service logging and why and why does it fill up the hard drive? here is a small snipet from the log as it appears to be connect to ports:
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:Connected to HECI driver
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57073
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1752
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57077
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1768
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57081
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1752
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57085
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1772
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57089
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1768
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
I got motherboard which takes roughly 30 seconds to reach POST screen (or UEFI screen if I keep pressing Del button). Manufacturer tech support replied that it is Intel vPro and Intel SBA makes board so slow to power-up, and this is perfectly normal. Is it?
How to avoid this delay? Enabling / disabling AMT and Trusted Computing does not make any difference.
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://10.234.10.84: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://10.234.10.84: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'm running auconfig to define a test system in the RCS server. I exported the xml file from the SCS console which shows SCSVersion 9.1.0.90 and when I run auconfig on the workstation to import the configuration, I get the following errors:
2014-07-08 15:06:12:(ERROR) : ACU.dll, Category: LoadXMLFromFile: The value of the SCSVersion tag in the profile is not applicable to this Intel(R) SCS version.
2014-07-08 15:06:12:(ERROR) : ACU Configurator, Category: Exit: ***********Exit with code 37. Details: Error with the XML file. The value of the SCSVersion tag in the profile is not applicable to this Intel(R) SCS version.
The client information is as follows:
MEBx Version 9.0.0.0025
FW Version 9.0.20.1447
LMS Version 9.5.10.1628
MEI Driver Version 9.0.0.1287
MEI DeviceID PCI\VEN_8086&DEV_8C3A&SUBSYS_18E7103C&REV_04\3&11583659&0&B0
SOL Driver Version 9.5.10.1586
SOL DeviceID PCI\VEN_8086&DEV_8C3D&SUBSYS_18E7103C&REV_04\3&11583659&0&B3
Any ideas or potential solutions would be appreciated. FYI, I have changed the values in the xml file to match each one of the version values listed for the client with no joy.
Thanks in advance for any assistance.
TB
I have never had a VPro machine, but I want to know if the following scenario would be possible before I purchase a few VPro machines.
The computers will be used by clients and I do not want them to access the network which is connected to the main network interface, as a result the main NIC will be disabled in windows. All windows users will only have access to the WiFi network.
If the main NIC is disabled for windows, can I still use it to connect to VNC using VPro/KVM? Just to clarify I do not want to connect using the wireless NIC, but the NIC that is actually disabled in Windows.
Hi Everyone,
I've just run the INtel AMT: Configuration task sequence and that's worked successfully but it's showing up as 'detected' instead of 'externally provisioned'. I've had a look at the AMTOPMGR.log and I'm getting the following logs.
If anyone could please let me know what the best way to get this up and running, that would be great.
Running BIOS MYBDWi5v.86A.0030.2016.0527.1657
I would like to redirect storage to my NUC so that I can install OS on it by booting an ISO I have on my Laptop.
I use Intel vPro Platform Solution Manager, and I redirect storage pointing at my ISO.
Booting NUC...
I can see some activity on my NIC, although it is not going fast. Someting like 100 kbps. After some time is stops and boots the already installed system from its local HD.
When I boot into UEFI BIOS, I can choose to boot redirected media... but it skips it... and boots on local harddrive.
What am I missing?
Regards, Lars.
I would like to manage my vPro-clients by using microsoft SCCM. However, if I choose 'out of band management --> discover management controllers', nothing happens.
Can somebody help me?
The following messages can be found in the logfile amtopmgr.log
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Reading Discovery Instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{53F9FDEF-4DF3-43A7-9EF4-94A5926085D8}.RDC... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, 'GUID:7A7A25F0-45A3-4D69-A5A4-8EA6BB814E36' SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine PC1 (pc1.testlab.com), ID: 6 - 192.168.0.12 from Resource GUID:7A7A25F0-45A3-4D69-A5A4-8EA6BB814E36. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 6 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Finish reading discovery instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{53F9FDEF-4DF3-43A7-9EF4-94A5926085D8}.RDC SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Parsed 1 instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Send task to completion port SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
Auto-worker Thread Pool: Current size of the thread pool is 1 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: 1 task(s) are sent to the task pool successfully. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
Auto-worker Thread Pool: Work thread 3860 started SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 3860 (0x0F14)
STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=SCCM SITE=C01 PID=2084 TID=2776 GMTDATE=Wed Apr 09 06:06:09.218 2008 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:09 2776 (0x0AD8)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:29 2776 (0x0AD8)
AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:29 2776 (0x0AD8)
CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 192.168.0.12:16992. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
CAMTDiscoveryWSMan::CreateWSManConnectionOptions - No acct/password available for wsman connection SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Error 0x80090308 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Error 0x3afb9e0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Error 0x80090308 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Error 0x3afb9e0 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
CAMTDiscoveryWSMan::DoSoapDiscoveryForAMTDevice: unable to perform soap based discovery to amt device 192.168.0.12 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
Auto-worker Thread Pool: Succeed to run the task . Remove it from task list. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:30 3860 (0x0F14)
AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:49 2776 (0x0AD8)
AMT Discovery Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:06:49 2776 (0x0AD8)
Auto-worker Thread Pool: Work thread 3860 has been requested to shut down. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:07:10 3860 (0x0F14)
Auto-worker Thread Pool: Work thread 3860 exiting. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:07:10 3860 (0x0F14)
Auto-worker Thread Pool: Current size of the thread pool is 0 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:07:10 2732 (0x0AAC)
Incoming Connection from 192.168.0.12:16994. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Incoming data is - Configuration version: PKI Configuration. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Count : 8 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
UUID : 4C4C4544-0034-3610-8033-C6C04F46334A SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Warning: AMT device 4C4C4544-0034-3610-8033-C6C04F46334A is a SMS client. Reject hello message to provision. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Waiting for incoming hello message from AMT devices... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:15:56 2756 (0x0AC4)
Incoming Connection from 192.168.0.12:16994. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Incoming data is - Configuration version: PKI Configuration. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Count : 9 SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
UUID : 4C4C4544-0034-3610-8033-C6C04F46334A SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Warning: AMT device 4C4C4544-0034-3610-8033-C6C04F46334A is a SMS client. Reject hello message to provision. SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Waiting for incoming hello message from AMT devices... SMS_AMT_OPERATION_MANAGER 09.04.2008 08:26:41 2756 (0x0AC4)
Hi
If I follow the instructions in the blog post "Simple AMT WS-Eventing in PowerShell with the High Level API" at Simple AMT WS-Eventing in PowerShell with the High Level API - IT Peer Network the output from the event does not include the address of the machine sending the event. Somehow I think this is rather an important piece of data.
What seems to be happening is that the ReferenceParameter not is not being filled. I've been trying different things one thing I tried was:
$delmode = [Intel.Manageability.Events.DeliveryMode]::Push
$sub = New-Object Intel.Manageability.Events.Subscription($lstn,$wsfilter,"MyPMD-000",$delmode)
$sub.SenderIDPlacing
ReferenceParameter
$sub.SenderIDPlacing = [Intel.Manageability.Events.SenderIDPlacing]::HTTPHeader
$amt.Events.WSEvents.Subscribe($sub)
The output is then as the blog page describes.
My questions are:
1) Is this the expect behaviour?
2) in the method void Subscribe( Subscription subscription, DigestAuthentication digest, XmlDocument referenceParameters ) what would the xml document be like and how is it defined?
Thanks
we have > 500 computers with 500 GB hard drives and I noticed that most are filling up at an alarming rate. the culprit was the Intel(R) Management and Security Application Local Management Service (lms.exe) is creating a log file
%systemroot%\sysWOW64\gms.log.
I cannot find how to configure the log file or the service to limit the growth of the file. I had to disable the Intel(R) Management and Security Application Local Management Service, then delete the file.
My question is, what is this service logging and why and why does it fill up the hard drive? here is a small snipet from the log as it appears to be connect to ports:
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:Connected to HECI driver
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57073
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1752
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57077
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1768
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57081
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1752
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57085
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1772
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] Port: 57089
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] LMS:connection attempt was failed on socket:1768
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: <-- _connect Status: 4294967295
(8424)[2016-08-24 12:17:52.760175] [LM_DEBUG] PFOR: --> _connect
I am looking into buying a few used Lenovo ThinkCentre M92p computers but I am not sure if the last owner has setup the admin password for Intel vPro on them.
Does everything get reset if I remove the small battery on the computer?