HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

P2V Post-Migration question

 
SOLVED
Go to solution
DP Admin
Occasional Contributor

P2V Post-Migration question

Post-migration task, step 3:
"Modify the system hostname"

Why must I do this? I want the same machine as a virtual, not a renamed clone of it. Can somebody explain why this is not optional?

Thanks in advance,
Brit
3 REPLIES
Rob Buxton
Honored Contributor
Solution

Re: P2V Post-Migration question

During the P2V process you can select whatever host name you want, including the same one you started with. I've donw that on all the servers I've migrated.
Just make sure they're both not started at the same time!

DP Admin
Occasional Contributor

Re: P2V Post-Migration question

Update:

I performed the P2V and kept the same hostname. Indeed, as long as you don't have them on at the same time you are fine.

I did, however, encounter one other issue about the IP address, which also needed to remain the same. After the conversion, I could not assign the same IP address to the virtual NIC. I got an error that stated that the NIC had the same IP address as a "hidden" one and it would not let me continue with that address. I found MS KB 269155 (http://support.microsoft.com/kb/269155/en-us) which allowed me to see the hidden NIC, uninstall it, and assign the original host's IP address to it. Now my P is truly a V!
Also, what is the difference in the boot.ini after the conversion? I now see a "converted" windows option as the first. What's this about?

Thanks,
Brit
Rob Buxton
Honored Contributor

Re: P2V Post-Migration question

You can also just ignore the warning for the NIC, as it can't be used you can just re-assign the old address. I've never actually gone through the bother of removing the old device.

I'm not sure about the alternate boot, but I've seen at least one server that failed on the non-HP boot.
Also, if you're going to migrate any W2K Servers make sure you know the local admin account password, you may need it.