Intel vPro® Platform
Intel Manageability Forum for Intel® EMA, AMT, SCS & Manageability Commander
2827 Discussions

Error on Upgrading from 1.3.3.1 to 1.7.0.0

citynews
Beginner
3,866 Views

Hello,

 

we are trying to upgrade our Intel Ema Installation from 1.3.3.1 to 1.7.0.0.

The installer ask for the installation of Dot.Net 4.8.

We have installed it and the insttallation process has started.

After the part about the database, it begin the Certificate creation and the process has stopped with the following error: error creating intel ema root certificate

 

How can I solve the problem?

 

Thanks a lot

0 Kudos
23 Replies
MichaelA_Intel
Moderator
445 Views

Hi Citynews, I've sent another email to the address you provided along with sending a private message. Have you received either of those?


Regards,

Michael


0 Kudos
smolisso
Novice
436 Views

Hello guys and sorry for the delay of the answer, but me and citynews has been very busy in these days.

Finally, we have decided to migrate all the clients to new server with the 1.7 version.

 

The reasons that led us to this choice are these:

  • Update the operating system of the Server hosting the EMA from Windows Server 2016 to Windows Server 2019 and have a clean and updated installation
  • The upgrade from 1.3 to 1.7 was failed. We were able to upgrade to 1.6, so even if we was able to solve the "not connected" client problem we would still have had a version that was not updated to the latest release available
  • Updating all clients was not a difficult task. In 3 days we have practically done everything. We have an Active directory environment and we have released the new agent via GPO on all clients. The only manual operation was to un-provision the AMT on the client in the old EMA installation (1.3) before installing the new agent. In fact, without this operation, the client appears correctly on the new Server but the AMT gives the message "This endpoint is provisioned by other tool and Intel EMA does not have the record. Please use that tool or MEBx to unprovision this endpoint first"
  • If the automatic installation via GPO should fail, manually installing the new agent on a client is relatively simple, as we have a Domain environment with clients connected in Always On: just copy the agent installation files to the PC via shared folder \\CLIENT1\c$\ emaagent\ and then connecting via psexec (or with EMA Terminal) to the client command line and launch: c:\emaagent\emaagent.exe -install to install the agent for the new environment
  • No disservice for us during the migration, as the client was either on the old environment or on the new one. There was never a time when a client was "not managed" by EMA.

Many many thanks for the support and and we hope future updates will be "easier"

0 Kudos
MichaelA_Intel
Moderator
429 Views

Thank you for the update and your implementation and closing the thread with the details. From your description, it sounds like a solid implementation.


0 Kudos
Reply