I’ve been using VMWare Server on my server at home for some time for experimental purposes on different setups with clients, servers and networks. I think it’s an amazing tool and very valuable and useful. Today I decided to upgrade my installation from 1.0.3 version to 2.0.0. I encountered some issues I had to solve, but I soon got it to work. Here is how…


When finished downloading the installation file of almost 600 Mb from vmware.com and starting the setup, it recognized my previous installation and began the upgrade process. In the beginning of the installation I got a message that a policy set by the administrator that prevented this installation. I had no idea what policy this was, but when I started the setup a second time it suggested that I didn’t install this product to a domain controller, but I continued anyway, since I have no choice right now.

Then it began to install, but after a while it complained about “Error 1718: File was rejected by digital signature policy”, this occurs when trying to install a large package and Windows have too low virtual memory to verify its signature. There is a hotfix for Windows 2003 Server (not for XP) for this on Microsofts website (KB 925336), which I downloaded and installed.

After that the installation went through and all virtual machines was automatically imported and started. The main difference I noticed right away was that there were no longer a console, but everything is now a web interface (VMWare Infrastructure Web Access 2.0.0) which actually works very well and I’m also used to this platform since we’re using VMWare Infrastructure and most other products from VMWare at work also.




I did some virtual hardware upgrades, upgraded VMWare Tools and there were no problems at all, everything seems to be up and running as it should.

No related posts