Hello,

     I have a Lenovo M58p SFF. Basically I was messing around with the settings in Intel Management Engine and managed to disable ME State Control. After the system restarted, my cpu fan is spinning at full throttle and is quite lout. My Issue is, I cannot re-enter Management Engine, during the BIOS splash screen I have the option to press ctrl+P to enter Management engine, but the screen just goes blank for a few moments and continues to boot to windows. I've tried resetting bios;reset cmos;pull cmos battery and power cable; using cmos clear jumper;Flashing bios to the latest version; and nothing seems to work. So basically, what happened? Why can't I re-enter Intel Management Engine?

This is my MoBo according to Speccy

Motherboard

  Manufacturer LENOVO

  Model LENOVO (LGA 775)

  Version ThinkCentre M58p

  Chipset Vendor Intel

  Chipset Model Q45/Q43

  Chipset Revision 03

  Southbridge Vendor Intel

  Southbridge Model 82801JB (ICH10)

  Southbridge Revision 02

  BIOS

  Brand LENOVO

  Version 5CKT77AUS

  Date 5/7/2012

Thanks for reading, any help is much appreciated.

Hi,       

  Our network is configured with 1.x authentication along with MAB (Mac address bypass), but this sort of is a problem, when we want to provision new clients. We have been trying to configure Intel RCS, in order to cope with the problem without having any luck until now. So we figured, it might be the "right time" for a reality check with the community before we keep on banging our heads against the wall and keep on cursing the technologies

Environment description:

-           802.1x authentication enabled network with MAB.

-           New client prepared/configured with USB stick to add an 802.1x profile for IntelAMT.

Now to the problem, when we configure the clients, password and other options are sett. But we are unable to see any sort of certificate information or profile information in the AMT boot menu or what is now called, which you get after pressing Crtl + P

But because password and other settings are configured, we figure not showing certificates and policy is by design? Any how, when we now try to PXE boot nothing happens, as the Switch is only allowing EAPOL traffic. So now there are a couple of questions:

1) First off, is the configuration above mentioned ok? Or do we need to configure anything else?

2) In order for Intel SCS to work, does the server needs to be on the same vlan as the clients, even if the clients have been configured using USB pen?

3) Are there any network requirements in order to get PXE to work on an 802.1x enabled interface, i mean do we have to configure anything specifically on the switches or would it be broadcast traffic that is picked up by the Intel SCS server which in turn takes care of the rest?
4) When and 802.1x profile has been defined for Intel AMT, is a new certificated issued for each client that is PXE booted? And if so, which client receives the certificate, is it the Intel SCS server or the PXE booting client?

I cant seem to find any sort of documentation describing the purpose and theory behind 802.1x profiles and how they are used with Intel AMT, is there any documentation that I can get in order to learn more or implement this correctly? The only thing found in intel SCS is the  procedure to set it up, without describing how the concept actually works and how it can assist in different scenarios. Hope some one/anyone can help me out here. We have 15K clients that are planned to be rolled out by this solution, if this is not supported, well I guess we have to start looking for new jobs ...

Hi.

I have some serious issues when upgrading to latest SCS. While the upgrade process itself performed good (also the database upgrade completed without errors) I have 2 huge issues:

1. SCS Console cannot read my profile anymore. It shows the error "Failed to get list of Profiles. File decryption failed. Failed to decrypt profile data (0xc000028f).

2. I am unable to view my provisioned systems. When I go to Monitoring -> Systems, right click on "All Systems" and select "Show Systems" nothing happens. Tested on SCS Console local and remotely:

I downgraded and upgraded again without success. Rolling back to old version now...Any help would be kindly appreciated.

Hi,

We started deployment of Intel vPro technology via GPO:

client computers were never provisioned before, some of them in secured networks.

Such command is used:

ACUConfig.exe /verbose /lowsecurity ConfigViaRCSOnly 192.168.253.35 ProfileMain  /WMIuser domain\rcsuser /WMIuserpassword password

In result we got 60 from 490 clients have status "Configuration Failed":

problem AMT versions:

AMT 5

5.0.2 anyone of successfully configured client.(~30)

Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521f: An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable. Valid certificate for PKI configuration not found.

AMT6/7

6.0.3/6.1.1/7.1.13 rest computers status "Configuration Failed":

Initial connection to the Intel(R) AMT device failed. 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.

Questions:

about AMT5

What should I do with clients AMT version 5.0.2?  I suppose that issue with AMT version

about 6/7

What are network requirements for client and server(protocols/ports) for such kind of deployment? It might be some core firewall misconfiguration(routes,rules..). I didnt find network requirements in deployment guide.

Hi,

I'm configuring Intel SCS console 9.1.2 to provision amt devices.

I provisioned our test systems in admin mode using ACU_Wizard in windows with xml profile exported from SCS.

Everything was ok (I can see the system in the SCS monitoring) except the Configuration Profile was not set.

I tried to create a job (operation configuration) with the same profile to push it to all systems but it fails with this error:

Operation:  Reconfiguration

Date and Time: 20.11.2014. 13:29:12

Error Code: 3221225979

Severity: Failure

UUID: 5D06FE00-85CF-11E2-8634-B4B52FC958A5

Intel AMT FQDN: HRVcdPulaITE.calucem.local

Intel AMT IPv4: 10.243.3.33                        

Server Name: HRVvsPula040.calucem.local

Description: A mandatory parameter is missing or empty (OSHostName). 

The given profile require OSHostName.

My profile have optional settings:

- AD integration enabled (Always use the OS host name checked)

- ACL enabled (ad group and 2 ad users (including myself) added to the list)

- TLS enabled (CA is our CA server with server certificate template AMTRemoteConfiguration, CN in certificate: Default CNs)

System settings

- Edit IP and FQDN settings:

     - Use the following as FQDN: tried "primary dns fqdn" and AD FQDN

     - The device and OS will have the same FQDN (checked)

     - Source of the IP set to Get the IP from DHCP

     - DNS set to Update the DNS directly or via DHCP option 81

I don't know if it's related to this but it looks like the kerberos auth is not working. When I try to connect to a test system using vnc client (encryption: TLS, connection mode: INTEL AMT KVM), it doesn't accept my domain account but asks me username and password for amt admin. If I enter it, I can connect successfully.

I also noticed that if I start the acuconfig on the amt system to force it to pick up my profile, it works (but kerberos is still not working). After that I can see the profile applied in the SCS for that specific system.

I'm using this command:

ACUConfig ConfigViaRSConly RSC_Server_IP Profile_Name

What am I doing wrong?

Regards,

Igor

I have been running an dell precision m6700 with activated iAMT 8.1.40

BIOS: SOL.on, IDE Redirect:on, Redirection Port: on)

KVM is not supported because the internal GPU is disabled by DELL.

I am using the latest "Manageability Commander Tool" from SDK.

Via context menu: "Take Control" the "Manageability Terminal Tool" is opened.

Disk Redirect Works fine

Remote Command Works also fine

I am able to modify the BIOS.

Question:

How can I come into the Windows START Menu of the iAMT Client?

If I use "Remote Reboot" or "Normal Reboot" the "Manageability Terminal Tool"

screen is black or blank.

With IPMI (other machine same windows version) is it possible to get the Windows Startmenu.

Thanks in advance

Thomas

Hi,

         We have configured RCS and a basicProfile on the server side, but when we run the configurator we keep on hitting this error

2014-11-21 15:36:15: Thread:2584(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : wmain Line: 1254: ***********Exit with code 75. Details: Failed to complete remote configuration of this Intel(R) AMT device. 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 tried, at least 15 different combinations of Certificate template but no luck!

- We are running RCS as a domain user and it has been issued a certificate, which has been added to its local store.

- We have issued a TLS certificate for the mutual server part, it has been added to the machines local store.

- We have added the Enterprise CA thumbprint to Intel Mbex manually and reconfirmed that its ok.

We have followed the user guide and have added the custom OIDs as well. Reading a blog post, or discussion forum I saw that we had to use OU = Intel(R) Client Setup Certificate on the webserver template while creating the request. But it seems like the problem is occuring with the Provisioning certificate.  On the server we are seeing

2014-11-21 15:36:15: Thread:3024(DETAIL) : RCS Server , Category: Finish Configuration; (ERROR) AMT details: UUID: 4C4C4544-0057-5A10-8031-B5C04F4D3132, FQDN: PC142592.placetobe.local, IP: 10.11.12.64 . Return code: 0xc000521f . Details: 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.  Source: Src\RCSServer.cpp : CServiceModule::Log Line: 1270:

Hope someone can help us by pointing us in the right direction.

Best regards,

Sean

Hi,

I use the ACUwizard to create an AMT profile to deploy to all computers supporting vPro.

I use the latest version of Intel SCS (9.1.2).

On the section "System Settings" you've got the option to choose which management interfaces you want to enable.

One of them is "KVM redirection". Default this is configured with "user consent required before beginning KVM session".

According to the manual of SCS 9.1 there should be a button "KVM settings" next to the option "KVM redirection", but there isn't one...

Anyone got a solution to disable user consent for a kvm session ?

Kind regards,

Tom

Hallo Intel-Forum,

I just discovered that some parts of the Intel AMT V9.0 System always alters the %windir%/system32/drivers/etc/hosts file on my Win 2k12 R2 Server.

It changes the localhost address to the name, I use for the dedicated kvm-NIC. The kvm.project.local IP is set to 192.168.1.200 in the AMT system and you can connect the kvm with vnc plus.

Anyway, you can find the altered line as following:

# 127.0.0.1   localhost

127.0.0.1      kvm.project.local          # LMS GENERATED LINE

Since I am running a DNS-Server on that machine, the altered line always causes trouble.

On this machine (a new Dell T20 with Intel AMT V9) I have three dedicated NICs running:

1.: kvm.project.local with 192.168.1.200

2.: server.project.local with 192.168.1.10

3.: vm.project.local with 192.168.1.50

I am wondering why the AMT systems alters the 127.0.0.1 address. An added line i.e. 192.168.1.200 kvm.project.local could make sense, but why 127.0.0.1 kvm.project.local?

How can I prevent the AMT from changing the hosts file?

I also found those postings, but they're not really eye-openers for me, because they didn't provide any information how to solve this issue.:

a) https://communities.intel.com/thread/7093?start=0&tstart=0

and the official statement: b) https://communities.intel.com/docs/DOC-1247#jive_content_id_LMS_generated_line_in_hosts_file

"LMS generates this line when there is a mismatch between the OS  FQDN and the Intel® ME FQDN. This can happen, for example, when you swap hard drives between computers."

I would be very happy if you could find some time to help or provide some hints. :-)

Greetings from Germany,

Hermann

Hi all,

I have been asked to demo vPRO Out of Band Management to a potential customer and after looking through shed loads of documentation, I got started on testing.

The client has AMT 8.1.20 build 1366

I configured the AMT client settings in the MEBx menu (ctrl+p)

     Set password

     Set Domain

     Set IPv4 details (fixed IP etc)

     everything else is at defaults.

From the system I am using to manage from, I have managed to connect using the web browser and 'http://AMT_IP_Address:16992' and log in.

Everything here looks fine.

The problem I have is when I try to connect with VNC Viewer Plus.

     The AMT IP is in

     Security set to 'none'

     Connection type to 'Intel (R) AMT KVM'

When I click connect and enter the username and password it tells me to check user permissions (It is definitely not incorrect login details as that gives a different message)

On top of the I have installed the PowerShell module and attempted to get-powerstate and it comes back with unauthorized.

Does anyone have any thoughts or suggestions?

Thanks,

Triss

PS. if you need more info please feel free to ask.

Does it support ACHI along with RAID for sata drives?

I am thing about installing a SSD for my Win 7 OS and they all say to set the sata control to ACHI prior to installing the OS on your SSD.

Hello,

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.

Thanx

Lubor

Hi @ all,

I planned to use Intel AMT on the Clients to enable an Out of Band Management.

But unfortunately i didn't found all the answers for my questions. It will be implemented in an Microsoft server environment with AD, WSUS, SCCM etc.

Which component will deploy the certificates to the AMT-Clients, does the Certificates will be deployed by the SCCM or by the normal Certificate Server.

Maybe anyone of you could explain me, how the certificates will find their way to the AMT-Clients

Thanks in Advance

Kevin

(Sorry for my English)

i install on my pc windows 7 ultimate 32 bit os

please give me

display driver

Hi All,

Have come across a very frustrating problem with out AMT 8.x systems where the install fails due to the installed version of C++  2010 Redistributable either being a later or equal version to the one that the AMT install package is trying to install. It appears that the installer does not check that C++ is installed or even the version and just dumbly starts the install every time resulting in the error (0x13EC) as the logs show below. The only workaround I have found is to uninstall the current version using a batch file then let the AMT package install it again however that has it own set of issues due to SCCM having a dependence on the same version of C++.

This issue is holding up the entire roll-out and I am struggling to believe others have not experienced similar issues however aside from a few minor mentions there is nothing out there.

Thanks.

IntelAMT.log

------

Executing 'C:\WINDOWS\ccmcache\s\DAL\vcredist_x86.exe /q'

Flags: Wait=yes Hidden=no

!   Process returned 0x13EC

IIF will NOT initiate reboot

Exit code = 0x13EC

ResultCode = 5100

Version:

MEI:8.0.0.1262

SOL:8.0.0.1262

Hello everyone,

we are currently implementing SCS and are haveing issues with the Certificate Setup.

This is the Environment:

- We deployed one RCS Server "scs.europe.example.corp" with SCS 8.1.4.16 with a database hosted on another machine. The RCS Service is running as the User "rcsuser".
- We created a Server Certificate with IIS, stating a CN of "scs.europe.example.corp" and OU=Intel(R) Client Setup Certificate.
- The Server Certificate was signed by a Microsoft CA by using the Web Server Template.
- The Certificate Chain contains one Root CA ("Example Corp Root CA1"), followed by an issuing CA ("Example Corp Issuing CA1").
- The Server Certificate was installed (with private key) into the Certificate Store of the "rcsuser" Profile on the "scs.europe.example.corp" Server.
- Same with the Certificate Chain.
- The RCS Server runs on Windows Server 2008 R2.
- The Test Client is a HP EliteBook 8440p with BIOS V22 and AMT Firmware Version 6.2.0.1022, and runs Windows 7 Enterprise SP1 32-Bit. The HECI Driver is at version 6.0.0.1179.
- We inserted both Certificate SHA1 Hashes into the AMT ROM of the Test Client by using the usbfile Tool: usbfile -create setup.bin admin NewPa$$w0rd -hash "CA1.cer" "Example Corp Root CA1" -hash "CA2.cer" "Example Corp Issuing CA1" -v 2.1

When we now run ACUconfig on the Test Client (ACUConfig /verbose /output console ConfigviaRCSonly scs.europe.example.corp Example_EU_Clients /AbortonFailure), we get an error stating that there is an SSL issue:

An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable. (0xc000521f) ((ExecMethod WMI_ConfigAMT) Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521f: An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable.  (0xc000521f). Valid certificate for PKI configuration not found.  (0xc00007e5).  (0xc000521f). )

The SCS Console logs tha same error.

Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521f: An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable. Valid certificate for PKI configuration not found.

ACUconfig logs that the Certificate Hashes have successfully been imported:

Active certificate hashes have the following names: (0xc000005a)
15
[...]
Example Corp Root CA1
Example Corp Issuing CA1

So... did we miss anything?

Kind regards

I have an HP 8000 Elite Tower with AMT 5.2.1088 and I'm trying to provision it in my SCCM environment. After making the connection and pulling the profile from SCS, the log says that there is no valid PKI certificate, but there is an it matches the thumbprint of the one that I added to AMT. I have provisioned multiple AMT 9 systems without a problem and I have double checked that I have set this system up with the same options. Does anyone know if the cert requirements are different on older systems, or any reason this might be happening?

We're using a self-signed certificate. I have Intel SCS Console on my server and provision using the Intel Configurator and ACUConfig.exe /lowsecurity /output console /verbose ConfigViaRCSOnly SCSserver profile

Error shown here.

Exit with code

75.

Details: Failed to complete remote configuration of this Intel(R) AMT device.

Initial connection to the Intel(R) AMT device failed.

A valid PKI certificate was not found in Certificate Store of the user running the Remote Configuration Service.

I've double checked my certificate to make sure that I entered the

C:\Users\administrator\Desktop\intelscs_9.1.2.74\IntelSCS\Configurator> ACUConfi

g.exe /lowsecurity /output console /verbose ConfigViaRCSOnly SCSserver profile

Starting log 2014-12-15 13:38:06

Set compatibility mode to 9.0.

Connected to the Intel(R) Management Engine Interface driver, version

5.2.0.1008

Intel(R) AMT  in PROVISIONING_MODE_ENTERPRISE

Connected to the Intel(R) Management Engine Interface driver, version

5.2.0.1008

Failed to get data from the firmware.

(0xc0000022)

Calling function Discovery...

Calling function GetLocalSystemAccount over MEI...

Connected to the Intel(R) Management Engine Interface driver, version

5.2.0.1008

Error: failed to retrieve Local System Account using MEI; error code - 0xc0004a7

a

Host Based Setup is not supported

Function Discovery ended successfully

GetHostAndMEInfo output data:

        IsAMT:True,

        isAmtCapable:False,

        isEnterpriseMode:True,

        configurationMode:0,

        isRemoteConfigEnabled:True,

        AMTversion:5.2.50,

        isMobile:False,

        provisioningTlsMode:2,

        uuid:DCCEB490-D2A7-11DE-BBDA-8579DE5AD8D3,

        isClientConfigEnabled:False,

        hostBasedSupport:False,

        configurationState:1,

        FQDN:,

        embeddedConfigurationAllowed:False.

        isLANLessPlatform:False.

        PKIDNSSuffix:test.local

:Starting Remote configuration...

***** Start RemoteConfiguration ******

AMT Status code - An internal error has occurred in the Intel AMT device. This m

ight indicate an interface error, or an application error.

(0xc0004269)

Failed to get data from the firmware.

(0xc0000022)

Get AMT Name:Failed to get the hostname (AMT).

Changing AMT state from IN-provisioning to Pre-Provisioning in order to set AMT

OTP

***** Start StopConfigurationInt ******

Calling function StopConfiguration over MEI...

Calling function GetLocalSystemAccount over MEI...

Connected to the Intel(R) Management Engine Interface driver, version

5.2.0.1008

Error: failed to retrieve Local System Account using MEI; error code - 0xc0004a7

a

failed to initialize WSMAN client

Waiting for FW to move to Pre-Provision state(0)...

Calling function Discovery...

Calling function GetLocalSystemAccount over MEI...

Connected to the Intel(R) Management Engine Interface driver, version

5.2.0.1008

Error: failed to retrieve Local System Account using MEI; error code - 0xc0004a7

a

Host Based Setup is not supported

Function Discovery ended successfully

This system was already unconfigured. The system was successfully put in the "Pr

e Provisioned" state and the Intel(R) AMT interfaces are now closed.

***** END StopConfigurationInt ******

Connected to the Intel(R) Management Engine Interface driver, version

5.2.0.1008

Moving to Pre-Provisioning state failed. An old OTP exist in local settings stor

e.

***** Start StartConfigurationInt ******

Connected to the Intel(R) Management Engine Interface driver, version

5.2.0.1008

Activate Intel(R) AMT configuration:

(0xc0000050) (Success.

)

Waiting for FW to move to In-Provision state(0)...

The Start configuration operation completed successfully.

***** END StartConfigurationInt ******

RCSaddress=cm.test.local, RCSWMIUser=, RCSProfileName=inteltest

HP8000Elite.test.local

RCSaddress=cm.test.local, RCSWMIUser=, UUID=DCCEB490-D2A7-11DE-BBDA-8579DE5AD8D3

, ConfigMode=2, PID=, RCSProfileName=inteltest, AMTVersion=5.2.50, OldADOU=, Con

figure AMT Name= True. Configure AMT IPv4= True. Source For AMT Name= Host Name-

HP8000Elite Domain Name- test.local . Default OS Name= Host Name- HP8000Elite D

omain Name- test.local . Host IPv4= IPv4 Address- 192.168.1.207 IPv4 SubNet- 255

.255.255.0 IPv4 Primary DNS- 192.168.1.10 . Configure AMT IPv4 to DHCP mode= Tru

e. AMT IPv4= IPv4 Address- 192.168.1.207 .

***** END RemoteConfiguration ******

***********

Exit with code

75.

Details: Failed to complete remote configuration of this Intel(R) AMT device.

Initial connection to the Intel(R) AMT device failed.

A valid PKI certificate was not found in Certificate Store of the user running

the Remote Configuration Service.

I need help provisioning my AMT 5.2 HP Elite 8000 desktop. I've configured newer AMT 9 systems with this management server with the same certs and profiles so I believe that it should work. I've been using the ACUconfig included in IntelSCS_9.1.2.74 and the ConfigviaRCSonly option. I've tried using the ConfigAMT option also though. Regardless of whether I use RCS or AMT, I get this message.

Exit with code

33.

Details: Failed to configure this Intel(R) AMT device.

Initial connection to the Intel(R) AMT device failed.

A valid PKI certificate was not found in Certificate Store of the user running the Remote Configuration Service.

As far as I understand, ConfigviaRCSonly is host-based provisioning, while ConfigAMT is remote based provisioning. According to this youtube video, the cmd: ACUConfig.exe /output console configamt profilename.xml should provision on any system regardless of whether or not it supports Host-based provisioning, which this system doesn't since it's AMT 5.2 (pg 4). My management server is a VM through Hyper-V so I don't believe that configuration via USB is an option but I could be wrong in that.

Attached are my SCSDiscoveryData and my AMT Configuration Results.

Any guides or direction or questions would be helpful here.

Thanks

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:

================================================================

Could anyone help?

Thank you.

Hello!

This is my first time using any kind of board so i'm sorry if this is a dumb question. I upload my program to the board for controlling  a solenoid and it works just fine. The problem is that any time that i disconnect the power supply from the board my priogram is deleted and i have to upload it again to the board. What i am doing wrong? Is there any way to avoid this? I really need the memory to be more reliable. What can i do?

Thank you very much!

Ginna