A. If you move VMs between multiple Hyper-V server hosts or a cluster of Hyper-V server hosts, you need to ensure that the virtual networks have the same name on every Hyper-V server. If the virtual networks don't have the same name when you move a VM from one Hyper-V server to another, the VM might not connect to any virtual network and as a result, the VM would completely lose connectivity. If the VM fails to connect to a virtual network and loses connectivity, you'll get an error message stating that the virtual network doesn't exist.
Naming virtual networks the same on all your Hyper-V hosts should correct your problem. If a VM has defined a static MAC address, then the static MAC address should also be preserved when you move the VM between virtual hosts.
Free Online Event! Virtualization:Get the Facts! Register now and attend this free, live in-depth online conference on November 13 and 20, 2008, produced by Windows IT Pro. All registrants are eligible to receive a complimentary one-year digital subscription to Windows IT Pro (a $49.95 value)!
Ease Your Scripting Pains with the Flexibility of PowerShell! Join MVP Paul Robichaux on December 11, 2008 at 11:00 AM EDT as he equips you with PowerShell basics in 3 introductory lessons, each followed by a live Q&A session—all on your own computer!
Order Your SQL Fundamentals CD Today! Learn how to use SQL Server, understand Office integration techniques and dive into the essentials of SQL Express and Visual Basic with this free SQL Fundamentals CD.
Maximize Your SharePoint Investment: Get Your Data Moving Watch this web seminar now to learn how to maximize your SharePoint investment! Join us as we take a look at the complex business of securing, accessing and managing vast amounts of information in a global network and various ways to get your data moving.
Register
