[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 138
  • Last Modified:

Duplicating a virtual machine for testing/development purposes

I have a fairly big project coming up in which I need to upgrade a third party application currently running on a hyperv 2008 R2 host. The application and its backend database reside on the same VM. The client portion of this application resides on a separate VM also running on a hyperv 2008 R2 host.

Instead of performing the upgrades on the production systems I want to create duplicate/mirror copies of these two systems. Unfortunately, I do not have a test/development network segment to put these system in and I believe they will require access to resources in order to function properly. Resources such as Active Directory.

My plan is to simply take a copy of the .vhd files, attach them to newly created VMs. Bring the VMs up with no network connection:
- change the name
- change the IP address
- join them back to the domain after renaming & readdressing them and turning network connections back on.

Am I missing a step? Should I sys prep these systems in order to remove the SIDs, etc?
1 Solution
Jayaraja JayaramanCommented:
also if there any custom developments or anywhere the urls are hardcoded then you will be in trouble...
Sir LearnalotCommented:
Yes, sys prep the machines otherwise you may have a conflict with the existing machines
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You only need to Sysprep the machines if using in Production and for various management, e.g. System Center and WSUS.

When you change the name, IP Address, and add back to the domain, the machine will be fine, and will not "conflict" with an existing machine! The re-joining of the domain, will give you Domain SID.

It's the Machine SID, which Sysprep can change, and other machine-specific info used by WSUS and System Center.

you can have a read of the following:-

from the article

The final case where SID duplication would be an issue is if a distributed application used machine SIDs to uniquely identify computers. No Microsoft software does so and using the machine SID in that way doesn’t work just for the fact that all DC’s have the same machine SID. Software that relies on unique computer identities either uses computer names or computer Domain SIDs (the SID of the computer accounts in the Domain).

The Machine SID Duplication Myth (and Why Sysprep Matters)
Liam SomervilleCommented:
If there is any way you can migrate your VMs to an isolated test server, that would be best. All you'd need is a license for 2008 R2 since Hyper-V is free. That way you avoid the headaches re-integrating your machines to a production network and give yourself a safe place to do this kind of testing in the future.

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Tackle projects and never again get stuck behind a technical roadblock.
Join Now