Once you get to the point of being able to see your VM on the LAN, I drop the web admin console and that goofy ActiveX control in favor of a Remote Desktop Connection. Not only is the user experience so much more pleasant (like being able to full-screen) but you also have additional features like the ability to expose client drives to the VM to simplify moving things around. This is especially handy when your Remote Desktop Client is the Virtual Server itself. I've noticed in some instances (like when the VM is not attached to a Domain) that Remote Desktop cannot resolve the machine name properly. I've been able to resolve this by creating a Virtual Network that includes the Guest OS and the Virtual Server NIC. Once the Client OS is attached to both the Virtual Server NIC and the Virtual LAN, the name resolution kicked in. My suggestion is to always attach you VMs to the same domain as the Virtual Server and the Client machines that are accessing it. Windows Integrated Security plays much nicer when you don't have to deal with domain boundary issues.
If this sounds too complicated, and your running your VMs on your laptop, you might want to look into Virtual PC. It gives you the improved user experience without having to go thru RDC. Be advised that there are less features and you limited to a single processor.
0 comments:
Post a Comment