Need vCenter Server 4.0 and VMWare Server 2.0.2 running on same server.

[sdoyle]

Ok... Nevermind WHY I need to do this as it'd be a very long explanation but I need to get vCenter Server and VmWare Server 2.0.2 for Windows (the now free pre-ESX vmware server product NOT an older version of vCenter) running together on the same bare-metal WIndows Server 2008 R2 installation and I've almost got it but with one minor issue...

Here's what I've done:

1.) Install vSphere vCenter Server (default settings) and the add-ons. Check to make sure it's working ok.

2.) Install VMWare Server 2.0.2 for Windows and change the default ports (I add a '1' in front of them to be 18222 and 18333).

Now they both function just fine... until I reboot. After rebooting the server the two vCenter services ""Vmware VirtualCenter Server" and "VMWare VirtualCenter Management Website" have not started on boot. (The Vmware server Web Access service and all other services are fine.) AND starting those two services manually works fine. They just don't want to start on boot by themselves.

I am quite sure this is some kind of Tomcat conflict between the two instances but unsure of how to resolve it.

Just to reiterate before someone gets confused I'm talking about getting this VMWare Server 2.0.2:

http://www.vmware.com/support/server2/doc/releasenotes_vmserver202.html

I know the two products don't integrate I just have a very good reason to need a small VM running outside of the ESX infrastructure being managed by this vCenter installation. So I would like to leverage this server to run that small VM on VMWare Server while also being my vSphere infrastructure's vCenter Server.

TIA,

Sean

[sdoyle]

No ideas?

Am I posting in the wrong section?

[sdoyle]

Ok... I got it working. Not sure if it's entirely reproducible but for posterity's sake here are the steps I believed fixed it:

i. While installing VMWare Server for Windows 2.0.2 do not choose default port options. Change the port numbers (e.g. 8222 -> 18222)

ii. After installing both vSphere vCenter and VMWare Server 2.0.2 for Windows together on the same machine you will have a problem whereupon the "VMWare VirtualCenter Service" and the "VMWare VirtualCenter Management Webservices" services will not start up on boot (they will start on manual commnd). I have devised the following workaround:

1) Go to "C:\Program Files (x86)\VMware\VMware Server\tomcat\conf" and edit the file "server.xml" (notepad might not work well, If so download Notepad++)

2) Change line #43

Before:

4) Go to Services and set those two services to "Automatic (Delayed Start)".

5) Restart and check to make sure all services have started (NOTE: Delayed Start services may take a few extra minutes to start up, check to see if other Delayed Start services are all started).

[ElioteArg]

Hi! I'm having the same problem! I have vCenter Server 4.1 and VMware Server 2.0.2 installed on the same Windows 2003 R2 SP2 x64 Enterprise host. I didn't change those lines you say yet. I've just put some services to depend on others and reboot. If it doesn't work, I will try to do what you said. However, as far as I read on the VMware Server manual, vCenter and VMware Server can coexist on the same host.

I hope it works! If not, I hope your solution works for me too.

[Kahonu84]

Aloha - Why not make one of the instances a VM??

Bill

[ElioteArg]

Hello VMware Community! Finally I got it! It was a problem with both instances of Tomcat working at the same time, because both of them are configured to use ports 8005 and 8009. So, changing one of them (lines #43 and #175) solved the problem. However, after restarting the host, VMware Server Host Agent service started and stopped after 5, 10 seconds. In my case, I had to modify the authorization.xml file in "C:\Documents and Settings\All Users\Application Data\VMware\VMware Server\hostd" (Remember that I have a Windows 2003 R2 SP2 x64 Enterprise). The problem was that that file didn't show permission to log with a local administrator. So, I modified line 8 and wrote "<ACEDataUser>LOCALHOST\Administrators</ACEDataUser>"

For me it was not necesary to change HTTP (8222) and HTTPS (8333) ports.

I hope it helps you!