Windows 2000
Windows 2000
Windows 2000
Support
This guest operating system is supported on the following VMware products:
| • |
|
VMware Workstation 4.0, 4.0.1, 4.0.2, 4.0.5, 4.5, 4.5.1, 4.5.2, 5.0, 5.5, 5.5.1, 5.5.2-Windows 2000 Professional and Server, Service Pack 1, 2, 3, or 4 (listed versions also supported with no service pack)
Windows 2000 Advanced Server, Service Pack 3 or 4
Experimental support for 2-way Virtual SMP on Workstation 5.5, 5.5.1, 5.5.2 |
| • |
|
VMware ACE 1.0, 1.0.1, 1.0.2-Windows 2000 Professional, Server and Advanced Server, Service Pack 1, 2, 3 or 4 (listed versions also supported with no service pack) |
| • |
|
VMware GSX Server 3.0, 3.1, 3.2, 3.2.1-Windows 2000 Professional, Server and Advanced Server, Service Pack 1, 2, 3, or 4
Windows 2000 Professional Service Pack 4 checked build |
| • |
|
VMware Server 1.0-Windows 2000 Professional and Server, Service Pack 1, 2, 3, or 4 (listed versions also supported with no service pack)
Windows 2000 Advanced Server, Service Pack 3 or 4
Experimental support for 2-way Virtual SMP on VMware Server 1.0 |
| • |
|
VMware ESX Server 2.0, 2.0.1, 2.1.1, 2.1.2, 2.1, 2.5, 2.5.1, 2.5.2, 2.5.3, 3.0-Windows 2000 Server, Advanced Server, and Terminal Services Edition, Service Pack 3 or 4
Virtual SMP supported |
Note: If you are installing a guest operating system through VMware VirtualCenter, be sure it is supported under the VMware product-ESX Server or GSX Server-on which you are running the virtual machine.
Windows 2000
General Installation Notes
Be sure to read
General Guidelines for All VMware Products as well as this guide to installing your specific guest operating system.
You can install a supported version of Windows 2000 in a virtual machine using the corresponding Windows 2000 distribution CD. If your VMware product supports it, you can also install from a PXE server.
ESX Server or VirtualCenter: If you are using the virtual LSI Logic SCSI adapter, you must download the driver from the download center at the LSI Logic Web site. Go to
www.lsilogic.com/support/ and look for the LSI20320 SCSI adapter driver for your guest operating system. For details on installing this driver, see the VMware ESX Server Administration Guide.
Before installing the operating system, be sure that you have already created and configured a new virtual machine.
Windows 2000
Installation Steps
1 Insert the Windows 2000 CD in the CD-ROM drive.
2 Power on the virtual machine to start installing Windows 2000.
3 Follow the installation steps as you would for a physical machine.
Windows 2000
VMware Tools
Be sure to install VMware Tools in your guest operating system. For details, see the manual for your VMware product or follow the appropriate link in the knowledge base article at
www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=340.
After you install VMware Tools, you must change your Windows 2000 screen area to be greater than 640x480 pixels; if you do not change it, Windows 2000 uses the standard VGA driver, and your performance will suffer.
Windows 2000
Enabling Sound in a Windows 2000 Guest
VMware GSX Server: The sound device is disabled by default and must be enabled with the virtual machine settings editor (VM > Settings) after the operating system has been installed. To set up the virtual machine to play sound, see Configuring Sound in the GSX Server documentation.
Windows 2000
Known Issues
Windows 2000
Guest Screen Saver
VMware Workstation: On a Linux host with an XFree86 3.x X server, it is best not to run a screen saver in the guest operating system. Guest screen savers that demand a lot of processing power can cause the X server on the host to freeze.
Windows 2000
Service Pack 3
A Windows 2000 guest with Service Pack 3 installed might fail to boot. A dialog box appears, saying "The Logon User Interface DLL msgina.dll failed to load."
VMware Workstation, VMware ACE or VMware GSX Server: For a workaround to this problem, see the VMware Knowledge Base:
www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=907.
VMware ESX Server: You can resolve this problem by installing Service Pack 4.
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, and then use a text editor to add the following line to the virtual machine's configuration file:
MAGICBOOT1 = 700
If a value of 700 (representing 700 microseconds) does not enable you to start the guest operating system, experiment with higher values. Increase the number to 800 for the second try, 900 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 might need to assign a higher magicboot1 value. For faster boot times, you can experiment with values between 1 and 700 to find the smallest value that allows the virtual machine to boot.
Windows 2000
Installation Hangs
VMware GSX Server: If the installation of the guest operating system hangs, search our Knowledge Base at
www.vmware.com/support/kb/enduser/std_adp.php for a possible answer to your problem.
Windows 2000
Disable PAE in ESX Server Virtual Machines
EXS Server 2.5.x: Although ESX Server 2.5.x virtual machines are compatible with Physical Address Extension (PAE), they are not optimized for it. As a result, guest operating systems with PAE enabled might experience poor performance. For best performance, VMware recommends that you disable PAE in guest operating systems. For more information and instructions on disabling PAE, see the knowledge base article at
www.vmware.com/support/kb/enduser/std_adp.php?p_faqid=2020.
EXS Server 3.0: Note that disabling PAE also disables NX (no execute) and ED (execute disabled) features found in recent AMD and Intel processors. These features are not supported by ESX Server versions before ESX Server 3.0.
Windows 2000
ESX Server Virtual Machine Running Windows Might Fail to Power On If Not Rebooted after VMware Tools Installation
EXS Server 2.5.x: After you install VMware Tools on an ESX Server 2.5.x virtual machine that is running Microsoft Windows, the VMware Tools installer asks you to reboot the virtual machine. If you choose not to reboot at that time, and subsequently remove power from the virtual machine, either by using the button Power Off Virtual Machine in the remote console, or by shutting down the ESX Server, you might then be unable to power on the virtual machine again. When you attempt to do so, the virtual machine might fail to boot up, displaying the message STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE. To avoid this problem, after installing VMware Tools, be sure to reboot the virtual machine when the VMware Tools installer prompts you
