Follow

Enabling vPro

QUESTION

In my VSA, I would like to enable vPro on my agent machines and seem to encounter issues with this. What do I do from here?

 

ANSWER

See the following FAQ information concerning vPro in KDPM 3.5 and later.

A red row in the vPro screen means that there's a new entry in the vPro Error Log (viewable per-machine by clicking on the "View Logs" link in the logs column). Viewing the log entry will provide more details for why the activation failed, but here are the most common causes:

1) The machine has been activated by an external source. When you activate AMT, it requires setting a password. If the machine hasn't been activated and doesn't have a password, then we can automatically set the password when activating. If it has been activated previously, then we need to know the password. You can use the "Set Password" feature to set the password to the pre-existing password, which should then let us activate it

2) The machine has had AMT disabled in the BIOS. By default, the machines come unactivated. It is possible to manually disable AMT, which prevents future activations from succeeding. Unless someone has manually disabled it, this isn't likely the case, but it is possible.

3) The agent's Set Credential account is not an administrator. To detect vPro, the Set Credential account needs to be a user on the machine. To activate AMT, the account needs to be an administrator.

4) The machine is activating, but enabling KVM (aka Keyboard, Video, and Mouse) is failing. To enable KVM, either the KServer or the vPro Proxy needs to be able to connect to the vPro machine on port 16992, 16994, and 16995. If the vPro machine has a public IP address and has those ports open, or if it is on the same LAN as the KServer and there is no firewall between it, then this should work. If not (say if the machine is behind a NAT or if there is a firewall between the vPro machine and the KServer), then you need to set up a vPro Proxy on the same LAN which has access to the vPro machines on those ports. You can do that with the Advanced -> Create vPro Proxy menu option; the system will automatically assign vPro Proxies to vPro machines during detection or during vPro Proxy creation based on network topology. You can manually assign a vPro Proxy using the Advanced -> Manually Assign vPro Proxy menu option, and you can see the associated proxy by enabling the vPro Proxy column in the machine list (using the arrow that appears in the column header when you hover your mouse over the columns).

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.