Vmware tools 5.1 windows 2000 server

If you do not want to upgrade to Service Pack 4, you can work around the problem. Be sure the virtual machine is not running, then use a text editor to add the following line to the virtual machine's configuration file:. If a value of representing microseconds does not enable you to start the guest operating system, experiment with higher values.

Increase the number to for the second try, for the third try and so on until the guest starts. If you are booting multiple virtual machines or running other stressful workloads at the same time, you may need to assign a higher magicboot1 value. Before upgrading our infrastucture we did a lot of testing in a lab environment of course. Still we run into a problem when upgrading the productiv envrionment:.

I know we are having the year ! During figuring out what the problem could be a colleague came quite upset to me, asking if something with the terminal sever is wrong, because first customer start complaining. At this point of course we stoped the migration of the Win2k VMs. Also I couldnt see any differnece to our lab, where we of course run Win2k on vSphere 5. After thinking a wihle about it my only idea was to extend the testing with a lot of RDP connections. And here we go….

Meantime searching the net i came through a new topic at VMware community, where someone descripted exactly the same problem. Some days later this thread got quite long with more and more people reporting the same, but all without a resolution.

We have three ways of running guests. VMWare claims is a known issue and provides a workaround for your usage, the workaround is to disable logging within the VMTools until a fix is issued. In putting the workaround in place, it seems that I could not find the tools.

In my testing procedure, I determined that the RPC errors mentioned above seem to be cause by the tools configuration missing from the server, once you put the configuration in place and restart the VMTools service, all seems to be well. Below are the contents of the tools. Once the file is in place, restart the VMTools service.

I hope this corrects the issue you are reading this for and you can go about your day and have cake ….. Also, I find it interesting that people are still finding this article when an update was supposed to correct the issue.

Thanks for the post this works well. Not all of us work in perfect VMware environments where we have the capacity and time to upgrade to VMware 5. Thank you for the great work around! Is this a workaround or a fix for the documented error.

In creating the tools. I want to fix the error but if it would be better to patch the hosts I can look into scheduling downtime. That is, unless you can quickly schedule downtime. FYI: I was trying this fix and after restarting the VM Tools service a VMware Tools installer window briefly flashed up and then it rebooted my server without giving me an option to defer. My production server at am in the morning on a weekday no less.

Thank You!! You are commenting using your WordPress. You are commenting using your Google account.