Following routine maintenance involving a server restart, we get reports that one of the Airwatch components is not responding. This was traced to the fact that the VM Tunnel Proxy service does not start despite being configured for automatic start. Three other Airwatch services start normally. The workaround is to manually restart the VM Tunnel Proxy service every time the server is restarted, but this does not resolve the underlying problem. Is this due to a dependency on another Airwatch service(s) that had not yet started or could there be another explanation?
