Hello, we need to perform P2V of servers on Server 2008 R2. The method I see on the Microsoft page is "live migration," using failover clustering & shared discs. Is there not a simpler way of performing this P2V migration? We've attempted installing SCVMM on the 2008 R2 machine, but this is not working properly, as the administrative console "cannot connect to the server," even though the services are installed, started, pointed at the same port as the admin console, and even on the same machine.
If anyone could suggest a better way, or a more understandable way of doing P2V on Server 2008 R2, it would be greatly appreciated.
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
When I open SCVMM Managment Console I receive error "Unable to connect to the Virtual Machine Manager server localhost. The virutal machine manager service on that server did not respond. Verify that virtual machine manager has been installed on the server and the virtual machine manager service is running. Then try to connect again. If the problem persists, restart the VMM service."
So no, I can't even open the console.
I have attempted re-installing using default ports (with the exception of the BITS port that was causing issues with P2V when we had simple Server 2008, not the R2 beta) to no avail. As well as restarting the service, and the entire machine, still to no avail.
I have also attempted to point the VMM to the static IP & netbios name of the server, once again, to no avail.
Any ideas?
I am now receiving a smorgasbord of different errors, such as..
You cannot access Virtual Machine Manager server localhost.
Contact the Virtual Machine Manager administrator to verify that your account is a member of a valid user role and then try the operation again.
ID: 1604
This is starting to look like a MS bug, as every time I start the service & attempt to connect, it crashes with the following in the event log:
The Virtual Machine Manager service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service.
after this.....
A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x2148074253. The internal error state is 10001.
Damn betas...
It is ok to post so much in a row.
This may make you sigh, but I would uninstall the SCVMM, uninstall the management console, reinstall SCVMM using ALL DEFAULTS, reinstall the management console and then launch the management console as a domain administrator and post back.
On a side note, I have been using SCVMM in my environment also and the VMM service crashes and restarts every 10-25 minutes. I haven't been able to figure out why as of yet. This means that on P2V conversion I have to start it, it gets to 10% and crashes, restart it it picks up where it left off and gets to 20% and crashes, etc. =[
You could try using the free VMWare converter and then conver the vmdk file to a vhd.
http://www.vmware.com/prod
http://vmtoolkit.com/files
I know this would be an expense, but Acronis does a FANTASTIC job of managing the P2V process, converting file types, etc. Check out www.acronis.com.
I just did a Hyper-V P2V that worked flawlessly!
I used Macrium reflect to back up a system that was running 32-bit Server 2008 Standard on a Supermicro dual Xeon to a Hyper-V.
Here's what I did:
Used Macrium Reflect to back up the Supermicro.
1. Create the Virtual machine with no network adapter
2. Add a second hard drive to that VM
3. In an existing VM, also add that hard drive. Start the existing VM
4. Format the drive and copy the Macrium backup to it.
5. Stop that VM, start the new VM with the Macrium restore CD.
6. Restore from the drive created in step 4.
7. Start the new VM, disable the network adapter. (I did this as the physical machine contained webs, etc. and need to run during this process)
8. Shut down the VM, add an adapter from Hyper-V
9. Start the new VM.
10. Disable the adapter in the physical machine
11. Enable the adapter in the new VM
Other notes, I had to clear the Arp table in the Cisco ASA as the new IP addresses were the same.
I only one Error in the event log, the parallel port service wouldn't start. I disabled the port in the registry.
See http://support.microsoft.c
Also, I was required to re-activate which was successful.
All of the webs, ftp, etc are publishing perfectly!
-
Robert
Business Accounts
Answer for Membership
by: dfxdeimosPosted on 2009-02-04 at 09:34:22ID: 23550733
There is no such thing as "Server 2008 R2".
So just to review, you have:
1) Server 2008 x64 Machine
2) The Hyper-V role installed
3) The SCVMM installed on that same machine
4) The proper exceptions in the firewall to allow the SCVMM to connect to "localhost:port" (whatever the port is... 8100 I think)