Is there a graceful way to reset a machine ID? Problem with cloning and capture machine(s)...

[MrCheesecake]

In standing up a new batch of Win 10 machines, I created a template VM that's tweaked just the way I like it.  Before using that template to build an instant clone pool, I created a clone to become my provisioning/capture machine.  I've found an interesting "feature" where AppVol sorta-kinda sees my provisioning machine and thinks it's attaching app disks to it for updating, but it's actually attaching the disk to the Instant Clone parent.

I'm thinking the best/safest way to proceed is to just rebuild my provisioning machine from scratch and perform all the same tweaks as my clone parent but was wondering if anyone else has run into this and has other ideas to address this.

[sjesse]

You want your provioning machine to be a direct clone of your parent images, with only the app volumes agent running. You should have your provisioning machine in its own ou different then the clones, and you should use local accounts to prevent things like this from happening. If you don't and create a generic provisioning machine, apps the require the sid of the machine to be consistent won't work.

[Ray_handels]

Also, change the name of the provisioning machine after cloning, this way it won't interfere with other machines available.

And as sjesse said, add it to a different OU preferably without policies applied!! These might be captured within your appstacks.