The creation of the SPC "Windows Virtual Machine" is causing problems for AD operations. Computers with this child SPC object cannot be deleted using automated scripts and this is causing workflow problems where we are using Hyper-V to stage sample client OS computers.
Is there a way to prevent or stop Hyper-V from making that SPC object for client OSes? I would like to make it so that the Client OSes on a particular Hyper-V host do not create extra SPC objects in AD. This way I don't have to re-write all my scripts and services that Delete computer accounts from AD. When computer objects have child objects, I think they become containers in the eyes of AD and so cannot be deleted using AD calls that work fine on computer objects that do not have children.