Correct. Just when you futz with the NICS watch for phantom NICS left over from the old server. You will get warnings on IP addresses still in use on these phantom nics if you use the same static IP address.
http://www.happysysadm.com/2011/01/removing-ghost-nics-after-p2v.html From: David Lum [mailto:[email protected]] Sent: Friday, December 16, 2011 1:51 AM To: NT System Admin Issues Subject: Hyper-V VM's and backups Hyper-V VM's. By default I have VM's where the config info of each VM is in C:\ProgramData\Microsoft\Windows\Hyper-V but the VHD's are on a separate drive altogether. If I have just the VHD files would it be accurate to say I can probably recover the server by just creating a new VM using the existing VHD's? I'm guessing I'd have to futz with the NIC settings and reinstall the Hyper-V client tools but otherwise I'd be OK? And amazingly no, I haven't blown the server up and have this situation for recovery, I was just askin' :) David Lum Systems Engineer // NWEATM Office 503.548.5229 // Mobile 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
