As Ken said, you'd just have to recreate the VM and point it to the disks. All the crucial stuff is maintained there outside of RAM and NIC configuration.
* * *ASB* *http://XeeMe.com/AndrewBaker* *Harnessing the Advantages of Technology for the SMB market… * On Fri, Dec 16, 2011 at 1:51 AM, David Lum <david....@nwea.org> wrote: > 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’ J**** > > ** ** > > *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 listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
