• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Physical to Virtual conversion, does resulting VM need to be joined to AD domain?

K

KingGheedora

Diamond Member
If I do a P-to-V conversion from a physical that is joined to our work domain already, will the resulting virtual need to be joined again, or will it already joined to the domain?

Assume that I discontinue use of the physical once the VM is up and running.

Also, if I clone a virtual, would I have to join the resulting clone to the domain? I assume yes, since the clone should have a new GUID?

And if I take an image of a VM right after it's been joined to the domain, and all the software our team uses has been installed. I want to use this image as a backup in case we need to reformat. If I re-image one of our machines using this image, would that machine need to be added to the domain after being imaged?

You can see where I'm going with this. Give me the breakdown on when images, clones, and VM's need to be joined to a domain, when they were originated from machines already joined to the domain.
 
The P2V VM will still be joined to the domain since that is a software setting from within Windows.

If you clone a virtual the copy will have to be joined to the domain, but I recommend running sysprep as well.

But, in best practice images should not be taken of machines in a domain.
 
just don't ever try to P2V a domain server (or any server that is role domain server) - that is nasty if you can get to to work
 
Emulex said:
just don't ever try to P2V a domain server (or any server that is role domain server) - that is nasty if you can get to to work
Click to expand...

Wouldn't this only be an issue if you tried running both on the domain at the same time? If you took the server off the domain, did a P2V, then put the VM on the domain, leaving the physical one disconnected, things *should* be OK, no?
 
While it's not trivial, moving a Domain Controller from physical to virtual is no different than restoring it to new hardware. There are several software imaging packages that specialize in moving Windows Servers from one hardware set to another. These include the Acronis Echo Server series, Storagecraft's ShadowProtect Server, and Windows System Center Virtual Machine Manager.
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top