Orphaned SYSVOL policy folders remain in place after some GPOAdmin working copy GPOs get removed
These folders remain only when GPOAdmin "check-in" or "undo checkout" commands remove the working copy from the domain. It seems it does not not happen when a "real" GPO is delete from GPOAdmin (deploy delete).
When GPOADmin executes a deletion of an object wither that is a working copy or a deployed delete we send the delete command to the GPMC GPMGMT APIs for GPMC to execute the delete.
GPOAdmin do not interact directly with AD or SYSVOL during this operation. If the delete leaves the SYSVOL component of the GPO behind after a deletion command this would be the GPMC APIs leaving the SYSVOL component behind and would be out of control of GPOADmin.
Need to engage with Microsoft to investigate on their side.
