When I first installed Windows 2008 Server Standard on my new machine -- I rushed to install the most recent VMWare release. The purpose of the new machine was to run as many Virtual Machines as possible and keep a working copy of most recent operating systems available for whatever testing needs arise.
I visited the VMWare Server download site, and proceeded to download VMWare Server 1.0.7, the most recent released version of VMWare Server. Yes, I knew that VMWare Server 2.0 RC2 is out -- but I generally prefer to run non-beta or release candidate offerings.
Still VMWare 1.0.7 should be compatible with Windows 2008 32-bit (x86) and 64-bit (x64) according to the website:
VMware Server for Windows Operating Systems. A master installer file containing all Windows components of VMware Server. 32-bit and 64-bit systems.However, I quickly learned through the installation process that it would not be the case -- at least not easily.
Here is what I experienced, I skipped the sometimes painful play-by-play.:
1. Just the standard VMWare Server installation screen on Windows 2008 Server for 1.0.7.
2. I choose the recommended installation of complete to keep it simple and standardized.
3. I selected the location for the installation, agreed to the license terms and the installation started. Part of the way, a critical error occurs with the OpenSSL (openssl.exe) faulting in MSVCR71.dll. Closed it and the installation continued.
4. The fun continues, OpenSSL crashes for a second time before continuing.
5. Great, now another warning from VMWare server. Warning 25301.IIS configuration failed (131073). You will have to configure the VMWare site manually. So much for the Web MUI.
6. Now a driver issue with a non-signed VMWare driver. I will just go ahead and roll the dice here and install it.
7. That was the last of the VMWare installation errors (thank goodness). I went ahead, rebooted and crossed my fingers. Very quickly I was disappointed -- the required services did not start with a Error 1068: The dependency service or group failed to start.
Based on the numbers of errors that I experienced during the installation process, I was not entirely surprised. In face all of the VMWare services failed with the same error. However, I still spent the token 30 minutes tweaking the system -- looking for the failures and doing some Google searching. Perhaps there was a solution out there. But, after looking -- I could not find a thing. Has anyone else had any luck?
From there, it was time to move on -- Let's give VMWare Server 2.0 a try!