Hi,

When trying to configure Intel AMT on a testPC the Intel AMT:Configuration fails. Intel AMT is added in SCCM 2012 R2. The Intel SCS: Platform Discovery - and Intel AMT: Discovery task sequences are installed.

When I look in the smsts.log file after trying to run the Intel AMT: Configuration it says the following:

Active directory function pDirObject->SetObjectAttributes failed with error -2147024891 (Access is denied.: LDAP Provider: 00000005: SecErr: DSID-031A1256, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0). ).  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

tep out UpdateADObjectPassword InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

Step out CreateADObject InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

AD object creation failed. An Active Directory interface internal error occurred.  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

Active directory function pDirObject->SetObjectAttributes failed with error -2147024891 (Access is denied.: LDAP Provider: 00000005: SecErr: DSID-031A1256, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0). ).  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

onfigure Profile Failed: An Active Directory interface internal error occurred.  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

Active directory function pDirObject->SetObjectAttributes failed with error -2147024891 (Access is denied.: LDAP Provider: 00000005: SecErr: DSID-031A1256, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0). ).  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

(0xc0003a99).  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

An Active Directory interface internal error occurred.  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

Active directory function pDirObject->SetObjectAttributes failed with error -2147024891 (Access is denied.: LDAP Provider: 00000005: SecErr: DSID-031A1256, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0). ).  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

(0xc0003a99).  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

***** END ClientControlConfiguration ****** InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

*********** InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

Exit with code  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

3.  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

Details: Failed to configure this Intel(R) AMT device.  InstallSoftware 1/12/2015 11:32:01 1604 (0x0644)

Anyone had this problem, and has a sollution for it?

Thanks,

Sander.

Hello,

I'm setting up a Supermicro server with an X10SAE board and I have issues getting AMT KVM to work.

I set everything in the AMT ME bootup interface and also configured via KVM Console (KVMControlApplication.exe) to "KVM Status: Enabled - all ports". Here, I was not sure which "Default visibile monitor" to choose, so I tried each of them. Result was always the same:

With any VNC viewer, I can connect to the server. I can authenticate and successfully log in. After that, the attached screen on the server shows a red/yellow flashing border and a connection icon in the right upper corner. When I move the mouse or press a keyboard key in the VNC client, I can see these actions being performed on the server screen.

BUT: The problem is, that the VNC client stays clear. Depending on the VNC client I use, the window stays always black or red. This is independent of the state the server is in, i.e. it's the same if the server is in POST/BIOS/booting up, or the operating system has fully booted. Nevertheless, the client gets notified by the changes of the screen resolution, so the VNC window changes size when the server changes from POST to booting up and then again when reaching the GUI.

Depending on the VNC server I use, the VNC client terminates after a short time (less than a minute) without comments, or tries to reestablish the connection. Interesting enough, Real VNC shows the error message

0x8086210E: Internal KVM failure

which is, according to the "Intel AMT implementation and Reference Guide" an "Internal failure". Not very helpful.

I'm stuck here. Help would be appreciated.

The Intel Active Management Technology webinterface shows:

Platform

Computer model: X10SAE

Manufacturer: Supermicro

Baseboard

Manufacturer: Supermicro

Product name: X10SAE

Version: 1.01

BIOS

Vendor: American Megatrends Inc.

Version: 3.0

Release date: 05/20/2015

Processor 1

Manufacturer: Intel

Family: Intel® Xeon® processor

Socket: SOCKET 0

Version: Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz

Intel® Active Management Technology firmware version: 9.1.1-build 1000     

Thanks in advance,

Christian

Hello,

I'm setting up a Supermicro server with an X10SAE board and I have issues getting AMT KVM to work.

I set everything in the AMT ME bootup interface and also configured via KVM Console (KVMControlApplication.exe) to "KVM Status: Enabled - all ports". Here, I was not sure which "Default visibile monitor" to choose, so I tried each of them. Result was always the same:

With any VNC viewer, I can connect to the server. I can authenticate and successfully log in. After that, the attached screen on the server shows a red/yellow flashing border and a connection icon in the right upper corner. When I move the mouse or press a keyboard key in the VNC client, I can see these actions being performed on the server screen.

BUT: The problem is, that the VNC client stays clear. Depending on the VNC client I use, the window stays always black or red. This is independent of the state the server is in, i.e. it's the same if the server is in POST/BIOS/booting up, or the operating system has fully booted. Nevertheless, the client gets notified by the changes of the screen resolution, so the VNC window changes size when the server changes from POST to booting up and then again when reaching the GUI.

Depending on the VNC server I use, the VNC client terminates after a short time (less than a minute) without comments, or tries to reestablish the connection. Interesting enough, Real VNC shows the error message

0x8086210E: Internal KVM failure

which is, according to the "Intel AMT implementation and Reference Guide" an "Internal failure". Not very helpful.

I'm stuck here. Help would be appreciated.

The Intel Active Management Technology webinterface shows:

Platform

Computer model: X10SAE

Manufacturer: Supermicro

Baseboard

Manufacturer: Supermicro

Product name: X10SAE

Version: 1.01

BIOS

Vendor: American Megatrends Inc.

Version: 3.0

Release date: 05/20/2015

Processor 1

Manufacturer: Intel

Family: Intel® Xeon® processor

Socket: SOCKET 0

Version: Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz

1. ME Bios 10.0.0.0004 / ME 9.0.1.1333

2. Just 1 display is attached

3. I'm using the onboard graphics for the chip and the HDMI display. There is a DVI port on the motherboard, too, but I am not using that.

4. IP is 192.168.1.10. This is on the LAN.

5. Direct connection  

Thanks in advance,

What does "Unknown PCH found" & Unknown CPU/Platform type" means in Intel Platform confidence test? I am using server board S1200V3RP.

Hello!

I'm using intel AMT to drive PC's drive via ISCSI... but I have a customer who doesn't have local DHCP. Can I configure RDM for static IP?

Thanks!

Is it possible to set IP addresses remotely on the Intel NUC model NUC5I5MYHE using vPro?

We have our internal DNS using an internal domain name that is not the same as the external domain name. It will not be possible to change this configuration.

Is it possible to acquire a externally signed certificate to allow remote configuration of the vPro devices?

One idea that I have is to create a certificate for provisionserver.example.com and may be add a subject alternative name to provisionserver.example.local. Would this work and if not what will work?

I think that having different internal and external domain names is relatively common.

Thanks

Hi All,

I'm new to V-pro can you please help with these questions?

Do we need management server at each location for implementing v-pro

Does it work with Wireless LAN?

we can manage through Internet as well?

any idea on pricing for enabling it, cost of licenses

I have a customer setting up a driver respository for their standard platforms.  They need the drivers in the repository to be in sys/inf format for automatic builds on the target platforms.  The Intel chipset driver is only available as an exe.  Is there a way to get the inf type driver files from the exe?

Our client has 2 lenovo models ThinkPad Helix & ThinkPad S1 Yoga. Both are connected wirelessly and the client is is not able to get them provisioned using landesk. After looking at the logs our initial assessment is that since Landesk uses remote provisioning therefore due to non availability of wireless profile Wifi Nic is not connected and therefore devices are not getting provisioned. Also client mentioned that due to presence of ACL there was a probelm in the provisioning of some of there devices. We contacted Landesk in this matter and they responded that it is not an issue in which they can help us and we have to ask Intel about it.

Attached are the logs for your review. Need a second opinion on this.

I would like to ask if AMT functionality is available (can be used) on a system which has a motherboard with Intel iAMT (Standard Manageability) and a non vPro processor. Specifically the chipset is Intel® Q150 Express and the processor is Core i3-6100.

If AMT functionality is available in such a system which exactly AMT features are available?

What extra functionality is it provided when a vPro Processor is installed in a motherboard with Q150 chipset?

I want to make sure about these before I buy a computer with this configuration.

Please point out any related documentation, if available.

Thanks in advance for your response...

Hello,

I'm setting up a Supermicro server with an X10SAE board and I have issues getting AMT KVM to work.

I set everything in the AMT ME bootup interface and also configured via KVM Console (KVMControlApplication.exe) to "KVM Status: Enabled - all ports". Here, I was not sure which "Default visibile monitor" to choose, so I tried each of them. Result was always the same:

With any VNC viewer, I can connect to the server. I can authenticate and successfully log in. After that, the attached screen on the server shows a red/yellow flashing border and a connection icon in the right upper corner. When I move the mouse or press a keyboard key in the VNC client, I can see these actions being performed on the server screen.

BUT: The problem is, that the VNC client stays clear. Depending on the VNC client I use, the window stays always black or red. This is independent of the state the server is in, i.e. it's the same if the server is in POST/BIOS/booting up, or the operating system has fully booted. Nevertheless, the client gets notified by the changes of the screen resolution, so the VNC window changes size when the server changes from POST to booting up and then again when reaching the GUI.

Depending on the VNC server I use, the VNC client terminates after a short time (less than a minute) without comments, or tries to reestablish the connection. Interesting enough, Real VNC shows the error message

0x8086210E: Internal KVM failure

which is, according to the "Intel AMT implementation and Reference Guide" an "Internal failure". Not very helpful.

I'm stuck here. Help would be appreciated.

The Intel Active Management Technology webinterface shows:

Platform

Computer model: X10SAE

Manufacturer: Supermicro

Baseboard

Manufacturer: Supermicro

Product name: X10SAE

Version: 1.01

BIOS

Vendor: American Megatrends Inc.

Version: 3.0

Release date: 05/20/2015

Processor 1

Manufacturer: Intel

Family: Intel® Xeon® processor

Socket: SOCKET 0

Version: Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz

1. ME Bios 10.0.0.0004 / ME 9.0.1.1333

2. Just 1 display is attached

3. I'm using the onboard graphics for the chip and the HDMI display. There is a DVI port on the motherboard, too, but I am not using that.

4. IP is 192.168.1.10. This is on the LAN.

5. Direct connection  

Thanks in advance,

Hello,

before sorry for my English !

I have a problem with a digest user authentication. I use wsman on Linux console.

I create a digest user with CIM_AccountManagementService and this step run perfectly.

When I try to use this user to launch any other wsman command, they don't work but when I'm connect on the WebUI with this user I can execute other wsman command.

I think it's a credential problem but I'm not sure and I'm not how create credential with wsman for my digest user.

Anypeople can help me ?

Thanks for your response.

Mickael.

Hi guys,

We have configured an environment with Intel SCS and intel vpro enabled clients. We have successfully created policies and have distributed these to our clients. All of the funtions/settings are working as expected, we are using the following policy

Profile Name: KerberosProfile

Profile Type: Intel AMT

Network Settings

     FQDN will be the same as the Primary DNS FQDN

     IP will be taken from DHCP

Active Directory Integration

     Active Directory OU:OU=AMT Objects,DC=Demo,DC=local

Access Control List (ACL)      

     User 1: administrator

          User Type: Digest

          User has both remote and local access to the realms listed below

          Realms: Redirection, PT Administration, Hardware Asset, Remote Control, Storage, Event Manager, Storage Administration, Agent Presence Local, Agent Presence Remote, Circuit Breaker, Network Time, General Info, Firmware Update, EIT, Local User Notification, Endpoint Access Control, Endpoint Access Control Administrator, Event Log Reader, User Access Control

     User 2: Demo.LOCAL\AMT-Admins

          User Type: Active Directory

          User has both remote and local access to the realms listed below

          Realms: Redirection, PT Administration, Hardware Asset, Remote Control, Storage, Event Manager, Storage Administration, Agent Presence Local, Agent Presence Remote, Circuit Breaker, Network Time, General Info, Firmware Update, EIT, Local User Notification, Endpoint Access Control, Endpoint Access Control Administrator, Event Log Reader, User Access Control

     User 3: adminkvm

          User Type: Digest

          User has both remote and local access to the realms listed below

          Realms: Redirection, PT Administration, Hardware Asset, Remote Control, Storage, Event Manager, Storage Administration, Agent Presence Local, Agent Presence Remote, Circuit Breaker, Network Time, General Info, Firmware Update, EIT, Local User Notification, Endpoint Access Control, Endpoint Access Control Administrator, Event Log Reader, User Access Control

     User 4: Demo.LOCAL\Domain Users

          User Type: Active Directory

          User has local access to the realms listed below

          Realms: Redirection, PT Administration, Hardware Asset, Remote Control, Storage, Event Manager, Storage Administration, Agent Presence Local, Agent Presence Remote, Circuit Breaker, Network Time, General Info, Firmware Update, EIT, Local User Notification, Endpoint Access Control, Endpoint Access Control Administrator, Event Log Reader

Transport Layer Security (TLS)

     Server authentication used for remote interface

     Server Authentication Certificate Properties:      

          Certificate Authority: TEMPCA-IntelSCS.Demo.local\Demo Temp CA

          Certificate Template: IntelTLSaccesscertificate

          Common Names (CNs) in certificate: DNS Host Name (FQDN), Host Name, SAM Account Name, User Principal Name, UUID

Network Configuration  

     WiFi

     Do not enable synchronization of Intel® AMT with host platform WiFi profiles

Wired 802.1x

802.1x setup: 802.1x Setup1

Protocol: EAP-TLS

Root Certificate Authority: Demo Temp CA, Demo, local      

          Certificate Authority: TEMPCA-IntelSCS.demo.local\Demo Temp CA

Certificate Template: IntelSCSprovisioningcert

Common Names (CNs) in certificate: DNS Host Name (FQDN), Host Name, SAM Account Name, User Principal Name, UUID

Do not allow roaming identity

Do not verify RADIUS server certificate subject name

Enable 802.1x for Intel® AMT even if host is not authorized for 802.1x

Keep 802.1x session after boot to allow PXE boot for 60 minutes

Trusted Root Certificates

Below are the trusted root certificates used in this profile:

          Root certificate 1: Demo Temp CA, Demo, local

System Settings 

     Enabled Management Interfaces:

• Web UI

RFB password set

Power Management Settings: Always On (S0-S5), Timeout if idle: 0 minutes

The Intel® AMT clock will be synchronized with the operating system clock

Intel® AMT set to respond to ping requests

Fast Call for Help (within the enterprise network) is Disabled

Problem statement

Now since Intel AMT has been configured we can focus on the problem area:

We use PXE boot on a non 802.1x network to initially install machines. And during the install process machines are provisioned using Intel SCS, with the configuration described as above. When machine is running in full windows we are able to perform all actions like remote control, power feature like shutdown and cold reboot etc.

But if we now try to reinstall the machine the process fails.

Machines, where intel AMT has now been configured they can no longer PXE boot, neither on 802.1x enabled network nor on network without 802.1x. What we are seeing is that machines are able to PXE boot, but during the transfer of WINPE. The PXE boot process stards, boot.sdi is downloaded and then starts the process where WINPE is downloaded. This download fails randomly between 30%-70%. We are using IP helper, and have tried placing the machines on the SAME VLAN as the server, but we get Errorcode 1460 on WDS which indicated TFTP timeout. Just for the sake of testing, we have also tried to set DHCP options 66 and 67. But I must emphasize that, the SAME machine works just fine if we delete the Intel Vpro configuration from BIOS.

Conclusion:

We think that this problem is related to Intel AMT intercepting network communication. But what we find odd is that the problem occurs both on 802.1x enabled and network without 802.1x, why is PXE boot process being effected by enabling/configuring INTEL AMT? Has anyone seen this problem or anything like this? I am wondering if there can be something in the policy that we have attached.  During testing, we have also tried to remove the following

     Enable 802.1x for Intel® AMT even if host is not authorized for 802.1x

Keep 802.1x session after boot to allow PXE boot for 60 minutes

1. Because we are still struggling to get this to work on a non 802.1x network. Any help, pointer and tips is much appreciated as we have exhausted most of our options regarding testing J

Thanking you all in advance for your contribution.

Best regards,
Sean

Hi All,

I have run into some issues getting AD integration working. This is what I have done so far:

-Purchased certificate from comodo.

-Setup a server installed SCS 11.0.0.214 and MS SQL.

-Setup a basic profile and configured machines with ACUconfig.  Machines show up in the console and are able to be managed. Everything just worked.

-Then I setup a profile with AD integration. Gave the service account access to the OU where the objects will be created per this article(https://communities.intel.com/community/itpeernetwork/vproexpert/blog/2015/03/18/tightening-up-intel-scs-service-account-permissions-for-managing-intel-amt-computer-objects-in-microsoft-active-directory). The service account is a local administrator on the client machine and the service account is an administrator on the server.

When I export the profile (specifying the service account as the account) and run it with ACUConfig I get the following output:

2016-05-24 14:16:04:(INFO) : ACU Configurator , Category: HandleOutPut: Starting log 2016-05-24 14:16:04

2016-05-24 14:16:05:(INFO) : ACU Configurator, Category: : ACUConfig 11.0.0.214

2016-05-24 14:16:05:(INFO) : ACU Configurator, Category: -Unknown Operation-: CJMCHY1.domain.edu.au: Starting to configure AMT...

2016-05-24 14:16:21:(INFO) : localhost, Category: AMT Interface : Wire support:************** 1

2016-05-24 14:16:28:(ERROR) : 4C4C4544-004A-4D10-8043-C3C04F485931, Category: ADInterfaceInternal error: pSdoMachine->GetUserSDO (\\domaincontroller) failed with error 2147943717.

2016-05-24 14:16:29:(INFO) : localhost, Category: AMT Interface : Wire support:************** 1

2016-05-24 14:16:52:(SUCCESS) : ACU Configurator, Category: Exit: ***********Exit with code 0. Details: Success.

The machines do not show up in the SCS console, I can get to the machine through the webui but I cannot login with any account. The AD accounts are created in the OU.

Is there anything I should be checking? Please help

-Ross

Hi,
First of all, Sorry for the bad english.

I am a little confused about amt and vpro.

We are going to buy 15 new computers and we want to activate kvm.
There are several cpu with vpro support but in turkey we were unable to find a motherboard with vpro support.

We want to buy dell 3020 sff pc. It has i5-4590 cpu in it but motherboard doesnt support vpro.

I am going to setup amt for the first time, do i really need vpro supported motherboard or vpro cpu is enough alone?

Any detailed information would help.

Trying to test Optiplex Optiplex xe2 "Auto on" tool. http://prntscr.com/ba4til

1) It has been done 10 test. Auto on been setted up at different time. 6 test were succeed, 4 failed. I mean PC won't on at the specified time. !In this case shutdown were done by pressing power off button on unit!

2) Soft shutdown (via Windows) It has been done 10 test and they all been successful.

Why does hard shutdown work this way? Tried to find explanation info on internet, with no luck. Asked this question in amd forum, still under moderation.

please advise

Hello,

I am currently managing approx. 30 Intel AMT-enabled boards (DQ77KB), running (various versions of) Windows

Querying and setting their on/off state (using the WSMAN interface) works. VNC works as well.

However, after some period of time, these boxes stop responding - I get no reply from the management interface at all.

It can take as little as 5 minutes, or as much as 5 days, for the problem to manifest.

As a workaround, I added zabbix warnings and manually power-cycle the unresponsive boards.

This morning, 28 boxes were down, resulting in a massive loss of service (and a few of my managers getting angry at me)

I tried searching the forums to no avail, with most of the questions left forgotten or unreplied.

Please help!

Hello everyone,

I am working with SCCM 2012 R2 (Current branch version 1511) and I manage about 100 000 computers.

I am interested with the AMT Technolgy which can permit us to power on computers or manage other system settings

As you know in SCCM 1511, the "Out Of Band Management" and the "Enrollment Point" have been revemoved (depreciated) from the product.

We still can install the Intel SCS for SCCM add-on which add collections, task sequences and packages but how can I "manage" computers after intel AMT is configured ?

The Out of Band menu is no present anymore.

Does anyone have already integrate this feature on his hierarchy ? Is still effective with 1511 version ?

Any help regarding this topic is welcome !

Jérémie

Good Morning Guys,

I'm currently looking into deploying Intel SCS with my SCCM 2012 R2 environment.  I've gone through all the steps mentioned in this guide (Integrating Configuration Manager 2012 R2 with Intel SCS 9.0 – Part 1 : Introduction | SCCM GURU ) and have got to the stage where I'm running the various Task Sequences.  I can run the first one which is Intel SCS Platform Discovery, which runs fine, but when I get to the second stage, which is Intel AMT Discovery, it errors out.  There's nothing wrong with the task sequence through SCCM, as it's running the discover.bat file without problem, but when it's running that file, it fails.

Below are the SystemDiscovery logs from the workstation. 

I have not been able to find anything online about this error and haven't been able to see anyone who is having the same problem as I am.  Any help would be greatly appreciated.

2016-07-13 16:31:06: Thread:3388(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:31:06

2016-07-13 16:31:06: Thread:3388(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:31:06: Thread:3388(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:31:06: Thread:3388(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:31:06: Thread:3388(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:31:06: Thread:3388(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:31:31: Thread:3128(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:31:31

2016-07-13 16:31:31: Thread:3128(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:31:31: Thread:3128(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:31:31: Thread:3128(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:31:31: Thread:3128(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:31:31: Thread:3128(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:32:10: Thread:2320(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:32:10

2016-07-13 16:32:10: Thread:2320(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:32:10: Thread:2320(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:32:10: Thread:2320(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:32:10: Thread:2320(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:32:10: Thread:2320(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:41:58: Thread:3796(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:41:58

2016-07-13 16:41:58: Thread:3796(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:41:58: Thread:3796(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:41:58: Thread:3796(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:41:59: Thread:3796(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:41:59: Thread:3796(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:52:14: Thread:3748(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:52:14

2016-07-13 16:52:14: Thread:3748(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:52:14: Thread:3748(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:52:14: Thread:3748(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:52:14: Thread:3748(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:52:14: Thread:3748(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-13 16:54:17: Thread:3332(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-13 16:54:17

2016-07-13 16:54:17: Thread:3332(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-13 16:54:17: Thread:3332(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-13 16:54:17: Thread:3332(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-13 16:54:17: Thread:3332(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-13 16:54:17: Thread:3332(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).

2016-07-14 08:23:07: Thread:2448(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2016-07-14 08:23:07

2016-07-14 08:23:07: Thread:2448(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 101: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...

2016-07-14 08:23:07: Thread:2448(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering

2016-07-14 08:23:07: Thread:2448(ERROR) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 291: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).

2016-07-14 08:23:07: Thread:2448(ERROR) : ACU Configurator , Category: SCS::Exception Source: Src\ActivatorMain.cpp : wmain Line: 1256: Configurator exception occurred. (0xc0000052) (Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b). )

2016-07-14 08:23:07: Thread:2448(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 22 - An internal exception occurred when processing the request. Details: Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. Failed to verify the file signature chain. either connect the computer to the Internet, or manually download and install the root certificate update package from the Microsoft update catalog. C:/Users\clint\Desktop\Intel AMT Actions\ACU.dll A certificate chain could not be built to a trusted root authority. (0xc0003f7b).   (0xc0003f7b).