About agent behavior in redundant configuration of EMA server

[SKubo]

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

[vij1]

Hello SKubo,

Greetings!

I apologize for the confusion earlier regarding the PDF link. 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. Here is the correct link to the guide:

EMA Server Installation and Maintenance Guide

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

As mentioned in my previous statement, I recommend using the full EMA software version. It is advised to install the Intel® EMA software along with SQL Enterprise Edition instead of the template version.

Let me know if you need further assistance or clarification.

Best regards,

Vijay N.

[SKubo]

Hello Vijay N.

When Suneesh asked me about the usage environment, I responded with the following information.
・SQL version:
⇒ Azure SQL

Due to various circumstances, it is necessary to build with Azure SQL, and we would like to proceed with building with Azure SQL as much as possible, but Azure SQL cannot support the use of failover and the migration of EMA functions from the main server to the second server. Is that so?

Also, although I was not able to access the link you introduced (because it requires signing in), I understand that the linked manual is probably for an on-premises environment, but the environment I am using is an Azure environment. Therefore, we are proceeding with construction with reference to "intel-ema-web-deployment-guide-fo-azue".

Also, I understand that "full EMA software version" refers to the EMA package, not the template, is that correct?
If you understand the above, for verification purposes, the behavior is the same even if you install it from the EMA package rather than from the template.

Best Regards,
SKubo

[vij1]

Hello Skubo,

Greetings!

I apologize for the confusion caused by the earlier email. The link I shared was incorrect. Please find the correct link to the guide for synchronizing the EMA servers. You should refer to sections 2.2 through 2.2.2.9 of the Intel® Endpoint Management Assistant (Intel® EMA) — Intel® EMA Server Installation Guide.

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

To clarify, I understand that the "full EMA software version" refers to the EMA package, not the template. Is that correct?

Yes, the "full EMA software version" indeed refers to the EMA package, not the template.

Please let me know if you need any further assistance.

Regards,

Vijay N.

[SKubo]

Hello Vijay N,

I understand the procedure you provided.

What about Azure SQL, which I asked about?

What I would like to know is whether failover from main to secondary is possible even when using Azure SQL. Is this not possible with Azure SQL?

If this is not possible with Azure SQL, I would like to consider changing and building the database.

Best Regards

SKubo

[vij1]

Hello Skubo,

I wanted to remind you that Azure SQL is a third-party tool, and it’s important to follow Azure's guidelines for taking backups. Please ensure you review and follow their suggestions to secure your data.

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

Best regards,

Vijay N.

[SKubo]

Hello Vijay N,

I understand that the failover function that I am trying to perform this time uses the EMA function and is not a function provided by Azure. Am I wrong?
I think the same can be said for SQL Server, not just Azure.

For now, I would like to change the direction of the question.

I have two questions.
The first one has not been answered clearly, but
You responded to me about the failover on "08-28-2024 09:23 AM", I would like to ask you again what is actually displayed.

"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."

I think the image you attached at that time is probably the image from that time, but the same image is attached and the relevant part is not visible.

Regarding the second point, when performing the first operation, are the main servers and secondary servers configured with "Manageability Component" installed?
Or "ManageabilityComponent" is installed and enabled only on the main server and "ManageabilityComponent" is not installed on the secondary server Is it the state?

The above installation and activation refer to the parts shown in the diagram below.

Regards

SKubo

[Suneesh]

Hello Skubo,

Greetings!

Please note that only one Manage Server needs to be running per Intel EMA instance, whether you have one or multiple servers.

While it is possible to install the Manage Server on all EMA servers, only one should be active at any given time. The process of turning the Manage Servers on or off is manual and can be done via the Platform Manager.

When installing EMA on a second server, please follow the steps outlined in section 2.2.1.1 and the subsequent sections of the installation guide. You can deploy the Manage component on the second server but remember to turn it off after the installation is complete to avoid conflicts.

Let me know if you need any further clarification or assistance.

Best regards,

Suneesh

[SKubo]

Hello Suneesh,

When installing EMA on a second server, please follow the steps outlined in section 2.2.1.1 and the subsequent sections of the installation guide. You can deploy the Manage component on the second server but remember to turn it off after the installation is complete to avoid conflicts.

=> I'm in trouble because I can't do that.
As shown in the image below, I try to log in to "Platform Manager" on the secondary server using the same global account (Windows authentication), but the message "Invalid username or password" is output and I cannot log in.

By the way, the same behavior will occur even if the "Manage component" is not installed on the second server.

After shutting down the first server above, you will be able to log in to "Platform Manager" from the second server.
The credentials used at that time are exactly the same as the username and password that failed to log in because Windows authentication is used.

Regarding my initial question, I thought that the information I received on "August 28, 2024 at 9:23 AM" might contain an image that would show how the page would normally be displayed, so I asked the question.

If the behavior is not as expected, there may be a problem with the EMA configuration/settings, so I thought this would be helpful in identifying the cause.

I would also like to confirm this with some additional information, but although EMA is configured with a distributed architecture, if the first machine is stopped, remote control of the agent will no longer be possible. I understand that it is a function of "Swarm Server", but in the case of a distributed architecture, isn't it true that even if the first server is stopped, remote control will not be possible?

Regards,

SKubo

[vij1]

Hello Skubo,

Greetings!

As we are already in communication via email on a different case, we will proceed with closing this case.

If you have any further concerns, feel free to reach out.

Regards,

Vijay N.