1

Apologies if this has been asked already, searching the web reveals lots and lots of threads about installing the Win8 beta on VMware but not the other way around.

I am trying to install VMware Server 2.0.2 on a Windows 8 Preview machine. It appears to install correctly but I cannot then reach the web based homepage to configure virtual machines, i.e.

https://localhost:8333/ui/

gives the error that the "connection attempt to localhost was rejected. The website may be down or your network may not be properly configured".

Has anyone had any success running VMware Server 2.0.2 on Windows 8 Preview? If so were there any gotchas you needed to avoid?

dumbledad
  • 16,305
  • 23
  • 120
  • 273

2 Answers2

1

I don't think it will ever be resolved. VMware Server was declared End Of Availability in January 2010; There will be no support for Windows 8.

Your best try would be trying launching the services in compatibility mode, but why would you do that? Why not use the much more advanced VMware Player or VMware Workstation products?

iTayb
  • 12,373
  • 24
  • 81
  • 135
  • Interesting. I'd assumed VMware Server was more advanced than VMware Player (which runs fine on Win8). There are some things we've failed to get working in Player (64 bit, copying existing VMs, …) but it sounds worth my while diagnosing them and giving up on VMware Server. Thanks iTayb – dumbledad May 31 '12 at 08:15
  • 1
    @dumbledad VMware Player is far advanced than VMware Server, as it's still being developed. VMware Server isn't getting any new features for a while now. VMware Player may be limited as it is a freeware version of the VMware Workstation. By the way, VMware Server's successor is VMware ESXi (and is free as well for basic usage). However it is designated for enterprise solutions and not for an individual usage. – iTayb Jun 01 '12 at 16:36
0

I've found a way to run it on Windows 8.

On my PC with a x64 version of Windows 8, when I installed VMware Server 2, I found there was a service called VMware Host Agent that cannot be run. When I opened the system Service Manager and clicked to launch this service, it gave me the error.

My solution is to create a service with the same command string and set it to start automatically by using the "sc create" command in cmd.exe. And it worked for me!

LittleBobbyTables - Au Revoir
  • 32,008
  • 25
  • 109
  • 114
eggfly
  • 21
  • 3