Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am working on a scheme to clone a production, domain-joined virtual machine, bring that machine up off the network in order to prepare it to be converted to a template.

One issue that comes to my mind is that I will have an issue removing it from the network as it won't be able to reach any domain controllers. Is there any way around this?

share|improve this question
up vote 5 down vote accepted

What problem are you experiencing? This should work fine.

  1. Clone the server to an isolated network.

  2. Remove the cloned server from the domain. You'll get an error that a domain controller cannot be contacted, but the cloned server will end up in a workgroup.

  3. Sysprep it.

  4. Convert to template.

share|improve this answer
oh yes, this makes sense. This behavior is what I want anyhow, as I want to leave the current (source) machine happy in the domain. – MattUebel Jun 11 '14 at 13:47

A domain client doesn't need to be connected to the domain in order to disjoin it. The only caveat being that the computer account in the domain will be orphaned and you'll need to delete it manually.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.