Error during EMA Agent Installation/Start

[maksymr]

Hello 

Trying to install EMA Agent onto some of my machines, and for each of them I receive this error

[2024-08-23 07:33:56.0 AM] \Agent\MeshManageability\agent\MeshService\ServiceMain.c:1828 Error executing fetchTrustedPolicy. Last error: 6
[2024-08-23 07:34:25.66 AM] \Agent\MeshManageability\agent\MeshService\ServiceMain.c:1828 Error executing fetchTrustedPolicy. Last error: 6

Tried to look for the "fetchTrustedPolicy" or "error 6", but nothing came up.

Is there any specific reason I get this error? 

Thank you!  

[vij1]

Hello maksymr,

Greetings!

To better understand the issue, please select one of the endpoints, click on view, and send me what you are seeing. I would like to know where the endpoint is located (same EMA server domain or not).

If you are using Admin control mode, please send me a picture from the settings tab.

Regards,

Vijay N.

[maksymr]

Hello, 

I apologize for the late reply - the problem is that I can't see this endpoint on EMA. I tried to install the agent for the endpoint to appear there, but even though it shows "running" status on the endpoint itself - it does not appear in the endpoints list. 

Tried installing the agent to both EMA host and other machines in the same network, still getting the same result... 

(The endpoints Im trying to install to are not vPro supported win10 machines)

Any help will be very much appreciated, thank you! 

[vij1]

Hello maksymr,

Greetings!

I hope this message finds you well. We are following up to check if you were able to complete the actions we previously recommended. Please reply to confirm, so we can continue assisting you with a resolution.

Looking forward to your reply.

Regards,

Vijay N.

[vij1]

Hello Maksymr,

Greetings!

For non-vPro machines, only in-band connections work with user consent. No out-of-band connections are supported. 

To assist further, could you please provide us with the following details:

OS version of the server

SQL version

Location of both (physical or virtual)

Will they be on the same server machine?

Authentication mode: Local, Azure AD, or Windows AD

Intel® EMA software version to be installed

Number of endpoints to be provisioned

Location of endpoints: local or remote

Your prompt response will help us ensure the setup is aligned with your requirements.

Best regards,

Vijay N.

[maksymr]

Sure, this is totally clear, that it's only about in-band connections, it's what I was aiming for, pretty much. 

OS Version: Windows 10 Enterprise 22H2 (build 19045.3803)

SQL Version: 16.0.1000.6

Location: same machine

Authentication: Local

EMA Version: 1.13.1.0 

Number of endpoints: Current target is 3, to see full capabilities and understand if it'll fit my needs, then I'm aiming towards adding more endpoints. 

Location of endpoints: Local network for now (including the machine running EMA)

Please let me know if you need any more details, 

Thank you!

[vij1 · Accepted solution]

Hello maksymr,

Greetings!

I wanted to share some important information regarding the installation of the Intel® EMA Server:

1. Supported Operating Systems:

• Microsoft
• Windows Server 2019
  • Note: The getPFX API requires the Intel® EMA Server to be installed on Windows Server 2019 or later.
• Microsoft Windows Server 2022
  • Note: Crypto for Intel ME 11 systems is disabled by default on Windows Server 2022.

1. Supported SQL Server Versions:

• Microsoft SQL Server 2017, 2019, and 2022 (English-US version only) are supported.

Please ensure that your environment meets these requirements for a successful installation.

Let me know if you need any further assistance.

Best regards,

Vijay N.

[vij1]

Hello Maksymr,

Greetings!

I hope this message finds you well. I am just sending a follow up if you have any questions from the previous post. If so, please let us know.

Regards,

Vijay N.

[vij1]

Hello Maksymr,

Greetings!

If further assistance is necessary, do not hesitate to reply.

Regards,

Vijay N.

[maksymr]

Hello Vijay, 

Sorry for the delayed response, I've configured a Windows Server 2019 and everything seems to be working as expected, thank you!