boston Posted November 8, 2017 Report Share Posted November 8, 2017 (edited) Hi, I'm trying to capture a new reference image. I'm getting the "Capturing a domain-joined computer is not supported. Please disjoin from the domain prior to capturing." error message. The VM is not on a domain. gpupdate /force was ineffective The registry keys specified here contain no values (which is how it should be): Is this an appropriate situation for Sysprep, or does anyone know of a softer approach? Edited November 8, 2017 by boston Asked about Sysprep Quote Link to comment Share on other sites More sharing options...
Jeff Harris Posted November 8, 2017 Report Share Posted November 8, 2017 Was the VM on a domain at one time? Or was the VM on the domain, then you took a snapshot before dis-joining the domain? Quote Link to comment Share on other sites More sharing options...
boston Posted November 8, 2017 Author Report Share Posted November 8, 2017 I tried a SysPrep just now. No effect. Quote Link to comment Share on other sites More sharing options...
boston Posted November 8, 2017 Author Report Share Posted November 8, 2017 23 minutes ago, Jeff Harris said: Was the VM on a domain at one time? Or was the VM on the domain, then you took a snapshot before dis-joining the domain? Hi Jeff, Yes it was, I joined it so I could get to a network share and pull down software. Quote Link to comment Share on other sites More sharing options...
Jeff Harris Posted November 8, 2017 Report Share Posted November 8, 2017 Do you have snapshots of the VM? Quote Link to comment Share on other sites More sharing options...
boston Posted November 8, 2017 Author Report Share Posted November 8, 2017 13 minutes ago, Jeff Harris said: Do you have snapshots of the VM? No, it's a brand new one I spun up. I'm thinking just make another one, but skip the domain add? Quote Link to comment Share on other sites More sharing options...
boston Posted November 9, 2017 Author Report Share Posted November 9, 2017 Yeah there must have been some lingering registry entry beyond those mentioned in the article I linked, marking the VM as domained. I made a new VM and was able to continue forward. Thanks! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.