Intel vPro® Platform
Intel Manageability Forum for Intel® vPro Fleet Services, EMA, AMT, SCS & Manageability Commander.
3084 Discussions

Re-provision hosts that support only vPro Essentials

shyork
Beginner
156 Views

Hi

 

Our organisation has recently deployed some devices that only support vPro Essentials.

We'd not been made aware that there was different hardware, so deployed our standard vPro configuration, which includes Remote KVM.

These hosts appear in the Endpoints list, but show with the Intel AMT Status as "Not provisioned", and show Intel® AMT setup status: Retry Activation on Reconnect on the Endpoint details page.

 

I've created a new Endpoint Group, and configured this to not include Remote KVM, generated the new config file, copied this to one Endpoint and restarted the EMA Agent service. This has moved the Endpoint to the new Group, but the AMT setup status remains Retry Activation on Reconnect.

 

Is there anything we can do with these hosts to provision them easily, or do we need to unconfigure and then deploy the new Group / Agent to them? Or, with them being vPro Essentials only, will they always show in that state and we should just leave them in the existing group?

I understand we will still be able to do power management on these Endpoints, but not use the KVM via EMA.

Thanks

0 Kudos
3 Replies
Arun_Intel1
Employee
146 Views

Hi Shyork,


We see that you are not able to use the remote KVM with the environment setup in vPro essential or standard.


You are right, we would not be able to use the remote KVM option apart from the vPro Enterprise or Full AMT machine.


Please find the article given below for your reference for the same:

https://www.intel.com/content/www/us/en/support/articles/000090499.html


Thanks & Regards

Arun

Intel Customer Support Technician

intel.com/vPro


0 Kudos
shyork
Beginner
101 Views

Hi Arun

 

Yes, I know we can't use the remote KVM on these devices, the question is really how I can provision them correctly..

As they have have already done the agent install, what is the best way to tackle them:

  1. Leave them as they are, and accept that they show "Not provisioned" (because they can't be provisioned)
  2. Do a full un-provision and then redeploy the agent to them, with the new config file.
  3. Another way to move them to the correct config.

If option 2, is there an easy / quick way to do this on ~50 devices, preferably that does not include a visit to each one. 

If option 3, what is the way to do this? A replacement of the config file and Service restart did nothing.

Thanks

0 Kudos
Arun_Intel1
Employee
81 Views

Hello shyork,


You may have to fully unprovision and then reprovision the endpoints manually if the endpoints are remotely connected, else you may use the DHCP option 15 if the endpoints are connected to the companies domain.


Please find the article given below for provisioning the endpoints manually from MEBx.

https://www.intel.com/content/www/us/en/support/articles/000058945/software/manageability-products.html


Please follow the action plan upon one endpoint and then you may follow the same on the other endpoints once this is provisioned and CIRA connects.


Please feel free to revert for any further query!


Thanks & Regards

Arun

Intel Customer Support Technician

intel.com/vPro





0 Kudos
Reply