I'm trying to set up for bare metal Hyper-V host deployments, and I've run into a problem trying to add the needed PXE Server.
When I try to add our existing PXE Server using the VMM Admin console, it goes on for a while and than fails with error 2912. Doing a lot of investigating, it appears this is because the VMM agent running on the PXE Server cannot communicate with the VMM Server to see if the machine is allowed to PXE boot, and eventually fails.
From working with DPM, I know it is necessary to supply the agent with the appropriate credentials to communicate with the server; if the server is in a different domain, or in an edge/perimeter network. I suspect the same is true for VMM, but I cannot see any way to give the agent the appropriate credentials. (I did find some references, but they were using SC 2007.)
So the question is: how do I give the VMM agent the necessary credentials to communicate with the VMM Server when the agent is on a system not in the VMM Server's domain?
Thanks in advance.
- Mark