Maybe I am mistaken, but it appears to me that vmserver 2 is actually a step back, forcing some users to buy other products. On server 1 it was possible to configure it to be used by several users (via console), but with server 2 it needs special permissions, and these do not work, effectively restricting usage to a single user. With Linux guests it is not a big issue, but Windows guests can only be accessed through console.
Maybe I have something incorrectly configured, or maybe I do not understand something:
1. I cannot add anyone to permissions
2. I found no permissions suitable for a guest user (like a student in the class)
3. I found no option to make machines auto starting at the host boot.
4. Server 1 had clear instruction how to access console through the firewall tunnel - server 2 doc is mum, and new model of access makes it much more difficult - I guess I need to open several tunnels (4 ?) before I can install viewer and see anything.
I installed it twice on two different versions of Linux (FC2 - vmserver 1.0.6 worked ok) and RHEL 4.7, same effect. Browser manuals, vmware website, but nothing. It does not like accidental oversight, rather change of the policy.
-
Another issue - suggesting ESXi might be rather tricky proposition - for the shool which reuses old monitors there is very little chance that they can afford high end servers, and all machines on HCL are new, high end, and on the expensive side. What are the chances of ESXi running on generic no-name clone, even recent vintage ?
Tadeusz