That's what I ended up doing, and it seems to have worked fine. Hyper-V assigned a new MAC address to the new server, and sysprep took care of the SID.
I'm absolutely loving Hyper-V. I don't have any experience with VMWare, so I can't compare them, but as a server virtualization noob I have to say this is just the coolest. Of course, if my physical server that's hosting multiple virtual servers konks out, I'll probably end up cussing the technology and longing for the days when one server being down only meant that one server was down rather than many... From: Ken Schaefer [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2008 7:17 PM To: NT System Admin Issues Subject: RE: Copying VHD Files You don't need to do any of that (the export/import stuff) Just create your base machine, and shut it down (e.g. after sysprep) Then copy/rename the VHD file. Create a new machine in Hyper-V, and say to use an existing hard disk. Point it to the VHD you copied. Run NewSID if you didn't sysprep your base image. Cheers Ken From: Jon Harris [mailto:[EMAIL PROTECTED] Sent: Thursday, 24 July 2008 1:52 AM To: NT System Admin Issues Subject: Re: Copying VHD Files Simple answer yes but you do have some loops to go through to use the machine as separate machines. You will have to export them base machine and then re-import the machine. Done right is not too bad. Jon ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
