Unable to Provision CIRA in Admin Based Provisioning

[HoldenJolley]

Hello,

I have devices that have been setup for AMT, but when they try to get provisioned for CIRA I get an error message, INVALID_PT_MODE (3). I have tried two different devices, and they both get the same error message, is there a way to know what specifically is causing the error message?

[Suneesh]

Hello HoldenJolley,

Good day.

Could you confirm which mode you are using Admin Control Mode or Client Control Mode. Please also share the ECT logs from both endpoints for us to analyze.

Intel® EMA Configuration Tool (ECT) Logs:

1. Download the tool from the following link: Intel® EMA Configuration Tool
2. Installation:

• Download and unzip the tool.
• Double-click the .msi file and follow the installation prompts.

1. Run the Tool:
2. a. Open a command prompt as an administrator (or use Windows PowerShell*).
3. b. Navigate to the installation folder (default: C:\Program Files (x86)\Intel\EMAConfigTool).
4. c. Run the following command:
5. EMAConfigTool.exe --verbose

Regards,

Suneesh_Intel

[HoldenJolley]

Here you go, let me know if there is anything else that you need.

[Suneesh]

Hello HoldenJolley,

Good day.

Thank you for sharing the logs.

Please provide the following details for further analysis:

• Mode of configuration (ACM/CCM):
  • CCM Mode: No certificate required for provisioning; however, EMA agent must be manually installed on each endpoint.
  • ACM Mode: Allows provisioning without user consent on the endpoint.

Also, please let us know:

• Intel® EMA software version
• Number of endpoints to be provisioned
• Location of endpoints (local or remote)

Regards,

Suneesh_Intel

[HoldenJolley]

Hello,

I am doing the ACM Mode, the software version is Intel® EMA v1.13.1.0, I am currently just testing on the two, but once we get the issues resolved, it would probably be in the hundreds at a minimum, increasing yearly as we replace existing endpoints. The endpoints are a mix of remote and local as we have multiple locations.

[Suneesh]

Hello HoldenJolley,

Good day.

Please perform the following steps to mitigate the issue:

1. Unprovision from MEBx: Fully unprovision the endpoint from MEBx.
2. Reinstall EMA Agent: Reinstall the EMA agent file on the endpoint.
3. Configure MEBx: Access MEBx and configure it with the appropriate domain from the certificate chain.
4. Restart: Restart the endpoint or the EMA services running on it.

Regards,

Suneesh_Intel

[HoldenJolley]

Hello,

I tried manually setting it up but now it says provisioning record is not present.