How do you disable Intel KVM user consent requirement

Essentially AMT, the vPro feature that allows for remote power on, has its own processor. This is often called the Manageability Engine (ME). It can request DHCP addresses. At the same time, it's smart enough to know when the OS has control of the NIC. In that case, it lets the OS handle DHCP and just uses the same IP. When the OS is down (system is off, or NIC driver is not installed or failing), AMT will take over making DHCP requests as needed.

Implementation of OOB is not a trivial exercise by any stretch, and takes a significant amount of planning and investment. Simply turning on vPro is not enough, you have to have the back-end architecture to support it as well. Unless you are ready to immediately implement out-of-band management, my recommendation is to leave vPro turned off, because by default, vPro is pre-provisioned with root CA keys from well-known vendors (e.g. VeriSign, GoDaddy). An attacker with access with your network could purchase an AMT cert and provision your machines without you ever knowing...

Since vPro uses PKI, once properly provisioned the architecture is actually quite secure, as clients will then only trust a caller that possesses the AMT private key that originally associated the machine. vPro can be configured to provide notification to users when a remote session is active (depending on your company's policies).

With that said, our shop uses vPro. We manage several hundred remote workstations that have no on-site IT support. vPro gives us the capability to perform troubleshooting at the hardware level and provides remote power-on capability, features that are not available via remote desktop.