About agent behavior in redundant configuration of EMA server

SKubo · ‎07-30-2024

Hello,

When we have two EMA servers in a redundant configuration, and one of them is stopped and an instruction is sent to the agent, the agent does not respond.
I assume that the agent is probably communicating with the stopped EMA server and automatically switches to the other server, but what is the trigger for switching to the other server when the EMA server stops? Is it?
Will it switch automatically if we wait?
If it does switch automatically, how long will it take?

Best regards

Suneesh · ‎08-02-2024

Hello Satoshi,

Good day.

Please share us your environment details for us to troubleshoot further on the issue.

OS version of the Server:
SQL version:
Location of both: (physical, virtual)
Will they be on the same server machine?
Authentication mode: Local, Azure AD, or Windows AD
Intel® EMA software version:
Number of endpoints to be provisioned:
Will remote access to BIOS be necessary?
Location of endpoints: local or remote.
In which mode you are using EMA (ACM or CCM)

Also please share the us the EMA logs from the Server

Default Path:[System Drive]\Program File(x86)\Intel\Platform Manager\EmaLogs

Please send me the files without the date called:

EMAlog-Webserver.txt

EMAlog-Swarmserver.txt

EMAlog-Ajaxserver.txt

EMAlog-Recoveryserver.txt

EMAlog-Manageabilityserver.txt

EMA log from the endpoint:

Default Path:[System drive]\Program Files\Intel\EMA Agent\EMAagentlog

Looking forward to your response.

Best regards,

Suneesh

SKubo · ‎08-04-2024

Hello, Suneesh

I will answer the questions you asked below.

・OS version of the Server:
　⇒　Windows Server 2019 Datacenter
・SQL version:
　⇒　Azure SQL
・Location of both: (physical, virtual)
　⇒　virtual（Azure VM）
・Will they be on the same server machine?
　⇒　There were two servers, one was deployed from an Azure template and the other was built manually.
・Authentication mode: Local, Azure AD, or Windows AD
　⇒　AzureAD（EntraID）
　　　…　Command-based migration from Windows AD authentication to Azure AD authentication
・Intel® EMA software version:
　⇒　Intel® EMA v1.12.2.0
・Number of endpoints to be provisioned:
　⇒　1（For verification）
・Will remote access to BIOS be necessary?
　⇒　Yes
・Location of endpoints: local or remote.
　⇒　Remote
・In which mode you are using EMA (ACM or CCM)
　⇒　Both

We will send the log separately.

Regards,

Skubo

SKubo · ‎08-05-2024

Since I could not attach the files, I will write the contents of each log below.

〇ENA#1
[EMALog-AJAXServer]
2024-08-05 18:25:53.1302|INFO||3800|9|.ctor - MeshAjaxServer.CentralAjaxServer, EMAAjaxServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: ServerStart, 1
2024-08-05 18:25:53.5052|INFO||3800|9|AttemptServerLaunch - MeshAjaxServer.MainForm, EMAAjaxServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Server Started, ProcessID=3800, DB Schema=v39862272

[EMALog-ManageabilityServer]
2024-08-05 18:25:53.7395|INFO||5000|8|StartRedirectionSessionManager - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [0] - Information: Created RedirectionSession with throttling rate 0
2024-08-05 18:25:53.9583|INFO||5000|8|Start - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [0] - Message:Starting Manageability Server.
2024-08-05 18:25:53.9583|INFO||5000|8|Start - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: ServerStart, 0

[EMALog-RecoveryServer]
2024-08-05 18:25:50.9895|INFO||3788|7|TestDbConnection - MeshServersCommon.code.DB.ServerCommonDb, EMAServersCommon, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: Information, Database ok
2024-08-05 18:25:52.7708|INFO||3788|7|Start - EmaRecoveryServer.code.EmaCentralRecoveryServer, EmaRecoveryServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - MaxDbConnections: 4
2024-08-05 18:25:52.7864|INFO||3788|7|Start - EmaRecoveryServer.code.EmaCentralRecoveryServer, EmaRecoveryServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: ServerStart, Recovery Server starting.
2024-08-05 18:25:52.9739|INFO||3788|7|StartHttpListener - EmaRecoveryServer.code.EmaCentralRecoveryServer, EmaRecoveryServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Recovery Enabled setting is True. Starting HTTP Listener for Recovery port.
2024-08-05 18:25:52.9739|INFO||3788|7|ServerLaunch - EmaRecoveryServer.code.EmaServerLoader, EmaRecoveryServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Server Started, ProcessID=3788

[EMALog-SwarmServer]
2024-08-05 18:25:53.5520|INFO||5052|9|UpdateAgentStore - MeshServer.AgentVersionControl, EMASwarmServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Pulled Agent: Type=2, Version=11200, Time=7/10/2024 12:28:16 AM, size=4217536
2024-08-05 18:25:53.8177|INFO||5052|9|UpdateAgentStore - MeshServer.AgentVersionControl, EMASwarmServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Pulled Agent: Type=4, Version=11200, Time=7/10/2024 12:28:20 AM, size=4403904
2024-08-05 18:25:54.0677|INFO||5052|9|.ctor - MeshServer.CentralServer, EMASwarmServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: ServerStart, 1

[EMALog-WebServer]
2024-08-05 18:26:00.1302|INFO||5164|1|SetupBackendLogger - MeshWebCore.WebApi.WebApiConfig, EMAWebCore, Version=1.12.2.0, Culture=neutral, PublicKeyToken=null - EVENT: Information, Web API server is starting up.
2024-08-05 18:26:00.7864|INFO||5164|1|Initialize - MeshServersCommon.code.SiteService.WebConfigurationWrapper, EMAServersCommon, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: Information, Loading web config file at C:\inetpub\wwwroot\web.config.

〇ENA#2
[EMALog-AJAXServer]
2024-08-05 18:12:15.9754|INFO||5080|8|.ctor - MeshAjaxServer.CentralAjaxServer, EMAAjaxServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: ServerStart, 2
2024-08-05 18:12:16.2722|INFO||5080|8|AttemptServerLaunch - MeshAjaxServer.MainForm, EMAAjaxServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Server Started, ProcessID=5080, DB Schema=v39862272
2024-08-05 18:22:58.5673|INFO||5080|3|.ctor - MeshAjaxServer.AjaxWebSocketSession, EMAAjaxServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - WEBSocket login: satoshi.kubo.bp@bxoedu.onmicrosoft.com, expires in 59 minutes
2024-08-05 18:23:24.3932|INFO||5080|44|RunInternal - System.Threading.ExecutionContext, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - IIS WebSocket Closed: WsState: CloseReceived
2024-08-05 18:24:33.6900|INFO||5080|42|.ctor - MeshAjaxServer.AjaxWebSocketSession, EMAAjaxServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - WEBSocket login: satoshi.kubo.bp@bxoedu.onmicrosoft.com, expires in 60 minutes
2024-08-05 18:24:43.9391|INFO||5080|42|RunInternal - System.Threading.ExecutionContext, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - IIS WebSocket Closed: WsState: CloseReceived
2024-08-05 18:24:44.9252|INFO||5080|41|.ctor - MeshAjaxServer.AjaxWebSocketSession, EMAAjaxServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - WEBSocket login: satoshi.kubo.bp@bxoedu.onmicrosoft.com, expires in 60 minutes
2024-08-05 18:24:54.2218|INFO||5080|41|RunInternal - System.Threading.ExecutionContext, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - IIS WebSocket Closed: WsState: CloseReceived
2024-08-05 18:24:54.8343|ERROR||5080|3|Complete - System.Net.LazyAsyncResult, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - Error:Cannot connect SwarmServer
Exception Level(0):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 10.0.0.11:8089
StackTrace Level(0): at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
at MeshAjaxServer.LocalSwarmServer.OnConnect(IAsyncResult asyncResult)

2024-08-05 18:24:55.7871|INFO||5080|3|.ctor - MeshAjaxServer.AjaxWebSocketSession, EMAAjaxServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - WEBSocket login: satoshi.kubo.bp@bxoedu.onmicrosoft.com, expires in 60 minutes
2024-08-05 18:25:03.4685|INFO||5080|42|RunInternal - System.Threading.ExecutionContext, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - IIS WebSocket Closed: WsState: CloseReceived
2024-08-05 18:25:05.9816|ERROR||5080|3|Complete - System.Net.LazyAsyncResult, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - Error:Cannot connect SwarmServer
Exception Level(0):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 10.0.0.11:8089
StackTrace Level(0): at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
at MeshAjaxServer.LocalSwarmServer.OnConnect(IAsyncResult asyncResult)

2024-08-05 18:25:16.8390|ERROR||5080|3|Complete - System.Net.LazyAsyncResult, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 - Error:Cannot connect SwarmServer
Exception Level(0):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 10.0.0.11:8089
StackTrace Level(0): at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.TcpClient.EndConnect(IAsyncResult asyncResult)
at MeshAjaxServer.LocalSwarmServer.OnConnect(IAsyncResult asyncResult)

[EMALog-ManageabilityServer]
2024-08-05 18:12:16.5066|INFO||4836|8|StartRedirectionSessionManager - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [0] - Information: Created RedirectionSession with throttling rate 0
2024-08-05 18:12:16.7097|ERROR||4836|8|Start - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [0] - Manageability Server does not have access to USB-R directory, USB-R feature may not work properly.
2024-08-05 18:12:16.7097|INFO||4836|8|Start - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [0] - Message:Starting Manageability Server.
2024-08-05 18:12:16.7097|INFO||4836|8|Start - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: ServerStart, 0

[EMALog-RecoveryServer]
2024-08-05 18:12:14.3191|INFO||5020|8|TestDbConnection - MeshServersCommon.code.DB.ServerCommonDb, EMAServersCommon, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: Information, Database ok
2024-08-05 18:12:15.6785|INFO||5020|8|Start - EmaRecoveryServer.code.EmaCentralRecoveryServer, EmaRecoveryServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - MaxDbConnections: 4
2024-08-05 18:12:15.6941|INFO||5020|8|Start - EmaRecoveryServer.code.EmaCentralRecoveryServer, EmaRecoveryServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: ServerStart, Recovery Server starting.
2024-08-05 18:12:15.9285|INFO||5020|8|StartHttpListener - EmaRecoveryServer.code.EmaCentralRecoveryServer, EmaRecoveryServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Recovery Enabled setting is True. Starting HTTP Listener for Recovery port.
2024-08-05 18:12:15.9285|INFO||5020|8|ServerLaunch - EmaRecoveryServer.code.EmaServerLoader, EmaRecoveryServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Server Started, ProcessID=5020

[EMALog-SwarmServer]
2024-08-05 18:12:16.4129|INFO||4940|9|UpdateAgentStore - MeshServer.AgentVersionControl, EMASwarmServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Pulled Agent: Type=2, Version=11200, Time=7/10/2024 12:28:16 AM, size=4217536
2024-08-05 18:12:16.6629|INFO||4940|9|UpdateAgentStore - MeshServer.AgentVersionControl, EMASwarmServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Pulled Agent: Type=4, Version=11200, Time=7/10/2024 12:28:20 AM, size=4403904
2024-08-05 18:12:16.9597|INFO||4940|9|.ctor - MeshServer.CentralServer, EMASwarmServer, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: ServerStart, 2
2024-08-05 18:18:25.7397|INFO||4940|15|<RunReceivedMessageProcess>b__65_0 - MeshServersCommon.code.TcpStack.MessageManager, EMAServersCommon, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - Received ServerState for server type 1 id 1 with state AGENT_START. Endpoint count is 1. Endpoint id list is 45F94BD07148E074BAFD3F66459F6712D3F86B448656029E63A03AAAED236FFD.

[EMALog-WebServer]
2024-08-05 18:17:01.1608|INFO||7352|1|SetupBackendLogger - MeshWebCore.WebApi.WebApiConfig, EMAWebCore, Version=1.12.2.0, Culture=neutral, PublicKeyToken=null - EVENT: Information, Web API server is starting up.
2024-08-05 18:17:01.4889|INFO||7352|1|Initialize - MeshServersCommon.code.SiteService.WebConfigurationWrapper, EMAServersCommon, Version=1.12.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - EVENT: Information, Loading web config file at C:\inetpub\wwwroot\web.config.

Suneesh · ‎08-05-2024

Hello Satoshi,

Greetings of the day.

Thanks for sharing the logs.

Based on the analysis, please check the following:

1. Log into EMA using Global Admin. Adjust the Endpoint "Agent Update Interval (Seconds)" to a smaller value for faster failover.

2. Review the load balancer settings to determine how quickly a server outage is detected and traffic is redirected to the failover server.

Regards,

Suneesh

Suneesh · ‎08-13-2024

Hello Satoshi,

Thank you for contacting Intel.

This is the first follow-up regarding the issue you reported to us.

We wanted to inquire whether you had the opportunity to review the plan of action (POA) we provided.

Feel free to reply to this email, and we'll be more than happy to assist you further.

Regards,

Suneesh

SKubo · ‎08-20-2024

Hello, Suneesh

Sorry for the late reply.

1. "Agent Update Interval (Seconds)" has been set to the minimum time.

2. The load balancer settings had not been configured on the distributed server (specifically, the IP for Swarm had not been set), so we corrected the settings and checked again, but the issue persisted.

In light of the above, I would like to confirm that there is no difference with the redundancy that I understand. Am I correct in understanding that if the configuration is distributed, the operation of the EMA itself will not change even if one machine is stopped?

Regards,
Skubo

vij1 · ‎08-20-2024

Hi Skubo,

I understand that you are using a Distributed Server environment with two servers. The provisioning and connection work well when both EMA servers are operational. However, when the first server is turned off, the connection between the second server and the endpoints stops, and the endpoints are not receiving the profile changes made on the second EMA server.

Could you please confirm if you have restarted the endpoint after making the profile changes?

In a Distributed environment, there should only be one active Manageability Server. This means the Manageability Server component on the second EMA server needs to be turned off. Please confirm if you are following this step.

Let me know if you need further assistance.

Best regards,

Vijay N.

SKubo · ‎08-20-2024

Hello Vijay N,

Thank you for your reply.

As you understand, the system is configured with two machines.

The "Manageability Server Component" is also turned off on the second machine.

I may be misunderstanding something, so I would like to confirm again, but the distributed architecture configuration described in the manuals published by your company is not a redundant configuration that provides the same functions even when one machine is down, but rather is it merely intended to distribute processing and reduce the load?

If my understanding above is correct, is there a way to build a configuration that provides the same functions even when one machine is down

Best regards,

Vijay N.

SKubo · ‎08-20-2024

My apologies.
There were typos as I copied the text.

Also, for reference, what I am currently aiming for is to build a configuration as shown in the diagram below, so that even if one server stops, all EMA functions can be used as long as the other server is running. We are thinking of building an environment.

Best regards,

Skubo.

Suneesh · ‎08-21-2024

Hello Satoshi,

Greetings of the day.

The Manageability server needs to be running in the main EMA server only. If the main server fails, it is necessary to turn on the Manageability component in a secondary EMA server.

Regards,

Suneesh

SKubo · ‎08-21-2024

Hello Suneesh,

I apologize if this is already mentioned in the manual somewhere.

Is there a command or GUI operation method to perform each of the following operations?

- In a two-machine configuration, how to transfer the "Manageability component" from the main server to the secondary server

- In a two-machine configuration, how to force the secondary server to obtain the "Manageability component" when the main server is stopped

Additionally, if the above is possible, and there is no need to consider load balancing, is it correct to understand that there is no need to obtain the IPs of the Web and Swarm servers on the load balancer side?

Also, when building the servers, is it necessary to enable the "Manageability component" for each one?

Best Regards,
SKubo

SKubo · ‎08-21-2024

I apologize for bothering you during your busy schedule, but have you checked the contents I have written?

I used a translation function to write the text, so it may be difficult to read, but I have asked questions several times using "?" marks, so would it be okay if you answered the questions I have written?

I think I'm causing you trouble due to my ignorance, but I would appreciate it if you could give me an answer that would clear up my doubts a little more.

vij1 · ‎08-23-2024

Hi Skubo,

I hope my answers resolve your doubts.

Is there a command or GUI operation method to perform each of the following

operations?

1- In a two-machine configuration, how to transfer the "Manageability component" from the main server to the secondary server

We can turn on and off the Manageability component from the Platform Manager tool. This tool was installed on the server when you installed EMA software.

renditionDownload (2).jpg

2- In a two-machine configuration, how to force the secondary server to obtain the "Manageability component" when the main server is stopped

Intel is considering this improvement in future software releases. It is necessary to perform this change manually.

3- Additionally, if the above is possible, and there is no need to consider load balancing, is it correct to understand that there is no need to obtain the IPs of the Web and Swarm servers on the load balancer side?

Not applicable; an automatic alternative has not been implemented yet.

4- Also, when building the servers, is it necessary to enable the "Manageability component" for each one?

The Manageability component is required only in one server. If the Manageability server is installed on the secondary EMA servers, it is necessary to turn them off from the Platform manager.

For reference review section 2.0 Installing or Updating the Intel® EMA Server:

https://www.intel.com/content/dam/support/us/en/documents/software/manageability-products/intel-ema-server-installation-and-maintenance-guide.pdf#page=31

• Having multiple instances of the Manageability Server component server running is not supported. However, installing a second instance of the Manageability Server for failover purposes is allowed as long as the Manageability service on the second instance is stopped and disabled. If there are no active Manageability Servers, you will still be able to manage existing endpoints but you will not be able to provision new endpoints or utilize the USB Redirection (USBR) feature. If needed, in a failover scenario, this second instance can be started. When started, the Intel® EMA component server settings must be updated to point to the IP address of the new Manageability Server. Refer to Appendix - Modifying Component Server Settings on page 87 for information on modifying component server settings.

Regards,

Vijay N.

SKubo · ‎08-26-2024

Hi Vijay N.

Thank you for your reply with a screenshot of your answer to "1".

In the case of a two-server configuration, am I correct in understanding that by stopping the "Manageability component" on one server as shown in the screenshot, it will be possible to make the "Manageability component" run on the other server?

In the case of a configuration that allows failover with two EMA servers (redundancy configuration), as the last statement in your reply says, "However, installing a second instance of the Manageability Server for failover purposes is allowed as long as the Manageability service on the second instance is stopped and disabled.", so I believe that the following requirements must be met. Is this correct?

　- In the case of a two-server configuration, when performing a failover, the "Manageability component" must be installed on both servers.
　*If you do not install "Manageability component" on the secondary server, when "Manageability component" is stopped on the main server, there will be no server with "Manageability component", so we recognize that installation is essential.

　- During normal operation, the "Manageability component" on one of the servers (the secondary server) should be disabled.

　- When performing a failover, the "Manageability component" on the main server must be disabled and the "Manageability component" on the secondary server must be enabled.

　- In the settings within the EMA server, the server IP of the "Manageability component" needs to be switched from the main server to the secondary server.

I understand the other answers from 2 to 4.

Best Regards,
SKubo

vij1 · ‎08-26-2024

Hello Skubo,

Greetings!

Yes, you're correct. In a two-server configuration for Intel EMA, the "Manageability component" can typically only be active on one server at a time. If you stop the "Manageability component" on one server, it allows you to activate or run the component on the other server.

This setup ensures that only one server is handling the manageability tasks at any given time, which prevents conflicts and maintains system stability. The transition between servers is often done as part of a failover or maintenance scenario, allowing one server to take over seamlessly if the other needs to be brought down for any reason.

Regards,

Vijay N.

SKubo · ‎08-27-2024

Hi Vijay N.

I followed the procedure you told me the other day, but I wasn't able to get the results I expected.

I'd like to confirm again, but are there any manuals that tell me which parts of the server settings I need to change specifically when failing over, and the correct way to fail over?

Also, you used the word "seamless" in your answer. Is it possible to transfer functions between servers while maintaining the EMA server's functionality? If it is possible, I would like to know how to do it.

Best Regards,
SKubo

vij1 · ‎08-27-2024

Hello SKubo,

Greetings!

Please follow the steps below:

Log into EMA Platform Manager:

Once logged in, stop the Manageability Server on the first server.

After doing this, the second server will appear at the bottom of the list.

Restart the Second Manageability Server:

Select the second Manageability Server from the list.

Choose the option labeled "Launch."

The system will automatically install a package. No changes are needed during this process.

Once the installation is complete, the second Manageability Server should start functioning as expected.

Please note that you will need to perform these steps manually.

Let me know if you require any further assistance.

Best regards,

Vijay N.

SKubo · ‎08-27-2024

Hello Vijay N.

First, I would like to confirm that I am using version 1.12, but can I follow the same procedure?

Based on the above, I would like to ask a question about the information you provided.

After doing this, the second server will appear at the bottom of the list.

=> Nothing appears, what should I do?

If it is true, where will it be displayed?

Restart the Second Manageability Server:

=> I cannot log in to PlatformManager on the second server, so I cannot restart the Manageability Server, but is it okay to restart the OS? Is it strange that I cannot log in to PlatformManager?

The system will automatically install a package.

=> What is the status of the ManageabilityComponent on the second server before switching? I understand that the function was enabled when EMA was installed. Just to confirm again, should I enable or disable ManageabilityComponent when installing EMA?

The second and third images are probably the same.

Best Regards,
SKubo

vij1 · ‎08-28-2024

Hello Skubo,

Greetings!

To synchronize the EMA servers, please refer to sections 2.2 through 2.2.2.9 of the Intel® Endpoint Management Assistant (Intel® EMA) Administration and Usage Guide.

https://www.intel.com/content/dam/support/us/en/documents/software/manageability-products/intel-ema-admin-and-usage-guide.pdf

Please note that the Distributed environment is intended for the full EMA software version, not the Cloud Start version (templates). Ensure you are following the correct procedures for your setup.

If you have any questions or need further assistance, feel free to reach out.

Best regards,

Vijay N.

SKubo · ‎08-28-2024

Hello Vijay N.

Could you please tell me the following from your answer?

To synchronize the EMA server, see sections 2.2 to 2.2.2.9 of the Intel® Endpoint Management Assistant (Intel® EMA) Administration and Usage Guide.
=> Sections 2.2 to 2.2.2.9 do not exist in the URL you provided, so what are you referring to?

“full EMA software version”
=> Which version does this refer to?

I apologize for the inconvenience, but due to the time difference, I am only able to respond to one question per day, so I would like an answer to each question if possible.

Best Regards,
SKubo