Navigation

Search

Categories

On this page

Use Remote Desktop to access Windows virtual machines running under VmWare Server or MS Virtual Server
Your Intel EMT64 CPU has to have VT support to run 64-bit guest Windows OSes on VmWare Server
"Service Unavailable" error when accessing VmWare Server web admin running on Windows 2003 Server R2 x64
Microsoft Virtual Server R2 SP1 on Vista x64 and Intel Core 2 Duo CPU

Archive

Blogroll

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

RSS 2.0 | Atom 1.0 | CDF

Send mail to the author(s) E-mail

Total Posts: 48
This Year: 15
This Month: 0
This Week: 0
Comments: 8

Sign In
Pick a theme:

 Saturday, February 03, 2007
Saturday, February 03, 2007 12:19:30 PM (Eastern Standard Time, UTC-05:00) (  |  |  )

If it takes too long to redraw the screen when you access your remote virtual machine using VmWare Server Console or Microsoft Virtual Server admin page, consider terminaling into your virtual machines using Remote Desktop or Terminal Server client. UI works as fast as with any "real" remote PC. Entry-level Windows XP Home and Vista Home don't support Remote Desktop, but all Pro, Business, Media Center Edition and other flavors of Windows Vista, XP and 2003 work just fine. One of my co-workers told me Remote Desktop can be used for VmWare Workstation access, but I also tested VmWare Server and Microsoft Virtual Server R2, and those two also do it.

To enable Remote Desktop access a few things usually need to be done:

1. Enable RD access:

2. Ensure your user account is a member of the Administrators group.
3. The password on your user account is not blank.

The only issue I had with this setup was sometimes I couldn't ping the virtual machine due to networking issue. But when that happens all attempts to access that virtual machine over the LAN fail, including NetBIOS file shares, web access - anything.

Comments [0] | | # 
 Thursday, January 18, 2007
Thursday, January 18, 2007 10:08:20 PM (Eastern Standard Time, UTC-05:00) (  |  |  |  |  )

I need to test my software on a variety of 64-bit Windows versions. I hoped I would be able to use Microsoft Virtual Server, which I've been successfully using for a while for 32-bit tests (including German, Russian and Korean flavors of Windows - quite a feat for a Ukrainian with English as a second language), but to no avail - at this point even latest MS Virtual Server is unable to host 64-bit guest operating systems. So despite enjoying being lazy, I was forced to check out free VmWare Server. I hoped to run it on my main Vista x64 dev box, but VmWare Server did not install correctly on Vista x64. That was quite a setback for my product delivery schedule, because I realized I needed another box with 64-bit Windows 2003 Server on it to be sure I could run VmWare Server. I dug through my closet with PC parts and after combining what I had with $200 worth of parts bought from NewEgg.com I had a modest 64-bit box with Pentium D 805 and 1GB of DDR memory. VmWare has installed without a problem, but when I attempted to install Windows XP x64 VmWare Server told me that my Pentium D CPU is no good because when it comes to Intel CPUs, 64 bit guest OSes can run only on EMT64 units with Virtualization Technology (VT) support! Fortunately, my dev desktop had Core 2 Duo E6300, which does have VT support, and both Pentium D and Core 2 Duo use the same LGA 775 package, so I was able to simply swap CPUs and ta-da! - after that VmWare finally started cooperating and is installing XP x64 guest OS as I'm typing this article.

Conclusion: If you want to run 64-bit guest OS in VmWare using Intel CPU you will need a box with a processor supporting Virtualization Technology, and run Windows 2003 x64 as a host OS.

Comments [0] | | # 
Thursday, January 18, 2007 12:25:19 AM (Eastern Standard Time, UTC-05:00) (  |  |  )

After installing VmWare Server on 64-bit Windows 2003 Server R2, I was unable to access VmWare Server's web admin page due to Service Unavailable error. VmWare support forum suggests to remove .NET Framework 2.0, which seems to help some people, but I fixed the problem by repairing .NET Framework 2.0 installation after VmWare server was installed. To do that go to Control Panel -> Add/Remove Programs, select .NET Framework and hit Change/Remove button. In the dialog select repair and let it run. After that both Default Web site and VmWare web site were running fine.

Comments [1] | | # 
 Sunday, December 17, 2006
Sunday, December 17, 2006 2:29:12 PM (Eastern Standard Time, UTC-05:00) (  |  |  |  |  |  )

Microsoft Virtual Server R2 SP Beta works really well on Vista x64 and Intel Core 2 Duo E6300 CPU, which has Virtualization support. Installer was not completely hands-off - I had to add CGI module to IIS7 manually - otherwise VSWebApp.exe was treated as downloadable file and not as CGI module. MS needs to update VS installer to automate this step.

Please note that although MS Virtual Server R2 Beta can run on Vista x64, it can't host 64-bit OSes. To host 64 bit OSes you would need free VmWare Server installed on x64 Windows 2003 Server, and either AMD 64 bit CPU or Intel EMT64 CPU with Virtualization Technology (VT) support (like Core 2 Duo E6300 or E6400 CPUs).

Comments [0] | | #