After setting up Hyper-V for live migrations, the VMMS.exe is listening on port 6600 and works correctly. After restarting the server, the VMMS.exe service is up and running, however it is not listening on port 6600. But if I simply restart the VMMS.exe service, it then is now listening on 6600. I have also set the service to delayed start and that appears to work. However I have to wait until the service starts before I can manage any VM's that run on the local server. Delayed start seems like a Band-Aid fix. Is there any fix for this issue? Is something not in place or running so the VMMs.exe service can bind to port 6600? Firewall is all off while I troubleshoot this issue.