Sorry for the unclear/confusing descriptions. Basically you can look at OMSA Web Server and OMSA Remote Enablement features as a complimentary client/server pair. Please allow me to briefly explain: when you browse to https://remote-host:1311/ you are accessing the OMSA Web Server service on the remote machine and it in turn is interacting on your behalf with the low-level OMSA management instrumentation software on that host. You have the option to install OMSA Web Server on your own machine locally and browse to https://localhost:1311/ and enter the IP address of the remote server to manage a remote server that has Remote Enablement. This is the only way to manage a host whose operating system does not support OMSA Web Server, such as ESXi. Alternatively it enables you to install OMSA Web Server only in one place and configure all hosts in the network with OMSA Remote Enablement.
I hope that clears things up. Let me know if I can provide any more information or assistance.
DELL-Jonathan S
153 Posts
0
September 24th, 2012 10:00
Hi there,
Sorry for the unclear/confusing descriptions. Basically you can look at OMSA Web Server and OMSA Remote Enablement features as a complimentary client/server pair. Please allow me to briefly explain: when you browse to https://remote-host:1311/ you are accessing the OMSA Web Server service on the remote machine and it in turn is interacting on your behalf with the low-level OMSA management instrumentation software on that host. You have the option to install OMSA Web Server on your own machine locally and browse to https://localhost:1311/ and enter the IP address of the remote server to manage a remote server that has Remote Enablement. This is the only way to manage a host whose operating system does not support OMSA Web Server, such as ESXi. Alternatively it enables you to install OMSA Web Server only in one place and configure all hosts in the network with OMSA Remote Enablement.
I hope that clears things up. Let me know if I can provide any more information or assistance.