Back story: As I have discussed here earlier, I have a client that I was going to effectively P2V a server onto itself, and one tool I was pointed at was DISK2VHD...in tests I managed to get everything to look good, the DISK2VHD system worked fine on a different Hyper-V host, but what I couldn't test was Hyper-V on the system itself before blowing away the existing 2K3 OS.
Here's my oops: Back in April I contacted Dell and asked "hey can this S/N PowerEdge run 2008 R2?". They replied "yep, just update the firmware". Last Friday I flatten the machine, install 2008 R2 with no issues, but when I got to add the Hyper-V role....the CPU does not support it, DAMN ME! What I did was ASSumed that being able to run 2008 R2 also meant it could run Hyper-V, but it can't...(insert forehead slapping "DUH" icon here). In my head I had asked them about Hyper-V but looking back at my e-mails I only asked about R2 and not Hyper-V. Anyone here do something like that, and how did you remedy it? I had been prepared for almost anything - including this - so the client is operating fine but I didn't gain the 2nd Hyper-V host server I was hoping for. They DO have another server that is Hyper-V capable but I'm not about to ask them to fork out $700 more for ANOTHER 2008 Server OS, so I am seeing if I can find it cheap (and legally) somewhere and out-of-pocket it. David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 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] with the body: unsubscribe ntsysadmin
