king daddy
asked on
moving VM to datacenter from office
Greetings,
I want to move a VM to the datacenter and have it run there permanently. Downtime is not an issue so I was thinking of just shutting it down and copying the VM folder between data stores, disabling networking, setting to a VM Network there, then powering it up and changing the IP address. Will that work? Do I need to alter DNS in AD? Lastly, will users be able to use the same shortcut created by the previous install when it was in the office?
Thanks
I want to move a VM to the datacenter and have it run there permanently. Downtime is not an issue so I was thinking of just shutting it down and copying the VM folder between data stores, disabling networking, setting to a VM Network there, then powering it up and changing the IP address. Will that work? Do I need to alter DNS in AD? Lastly, will users be able to use the same shortcut created by the previous install when it was in the office?
Thanks
ASKER
Thanks for responding.
OK. The datacenter is on a different subnet connected to the office over a TW point-to-point connection. I know I am going to change the IP, but wasn't sure if a manual change was required in DNS to point the new subnet. It is static so not sure if DHCP will play into this.
I use VMware and have previously moved VMs by copying (when permissible) but these moves were within the office, not between sites with different IPs.
DNS name is used on the shortcut, not IP, so that should work. If not, I can just uninstall and reinstall.
OK. The datacenter is on a different subnet connected to the office over a TW point-to-point connection. I know I am going to change the IP, but wasn't sure if a manual change was required in DNS to point the new subnet. It is static so not sure if DHCP will play into this.
I use VMware and have previously moved VMs by copying (when permissible) but these moves were within the office, not between sites with different IPs.
DNS name is used on the shortcut, not IP, so that should work. If not, I can just uninstall and reinstall.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Lucky indeed.
I was planning on changing the IP in DNS while it was copying over so when I fired it up DNS was ready to go. I have logged on too many times, so credentials are cached.
Thanks again for verifying this method should work.
I was planning on changing the IP in DNS while it was copying over so when I fired it up DNS was ready to go. I have logged on too many times, so credentials are cached.
Thanks again for verifying this method should work.
Essentially, the best thing for you to do is shut down the virtual machine in Hyper-V, export the virtual machine and while exporting, place it on the target Hyper-V Server which is inside your datacenter. Once it's been exported, use Hyper-V to load the virtual machine, and make any changes to the network configuration that may be required. Fire it up and then away you go. DHCP should always take care of DNS so generally that is not a problem you need to think about.
And yes, as long as the computer name doesn't change, the old shortcut should work, provided of course DNS updates accordingly, and the shortcut is to the DNS name and not the old IP address.