Problem
When trying to enable vPro to use in Kaseya, you get the following or similar error (in bold) on the vPro logs on vPro -> Administration -> vPro Logs page for the affected machine:
12:23:39 pm 21-Jan-15 Enable
2015-01-21 12:23:06:(INFO) : ACU Configurator , Category: HandleOutPut: Starting log 2015-01-21 12:23:06
2015-01-21 12:23:14:(INFO) : ACU Configurator, Category: -ConfigAMT-: :Starting Unified configuration flow...
2015-01-21 12:23:19:(ERROR) : ACU Configurator , Category: ConnectServer: A call to this function has failed - (0xc000278b) (Invalid namespace -2147217394)
2015-01-21 12:23:19:(ERROR) : ACU Configurator , Category: ConfigAMT failed: A call to this function has failed - (0xc000278b) (Connection to the Remote Configuration Service is necessary, but the RCSParameters tag is missing in the profile. (RCSAddress))
2015-01-21 12:23:19:(ERROR) : ACU Configurator, Category: Exit: ***********Exit with code 68. Details: Invalid parameter was found. (RCSAddress)
12:23:39 pm 21-Jan-15 Detect
2015-01-21 12:23:21:(INFO) : ACU Configurator , Category: HandleOutPut: Starting log 2015-01-21 12:23:21
2015-01-21 12:23:21:(INFO) : SCSDiscovery, Category: -SystemDiscovery-: machineid.machinegroup: Discovering the System information...
2015-01-21 12:23:38:(SUCCESS) : SCSDiscovery, Category: Exit: ***********Exit with code 0. Details: Success.
Solution
This implies that the machine has been configured using Remote Configuration Service (RCS). As such, it now needs to talk to the Remote Configuration Service (RCS), which is the Intel tool that gets installed when configuring a vPro Proxy with a certificate. The reason for this is either (a) it was configured with an RCS before or (b) it was configured manually, so only a RCS can override it.