Yeah, this is a pretty common request. It's exceptional difficult to figure out what VMs would be in this job if run right now based on the current selection of container objects. Sure, I could write code to parse out all VMs within the various container types (and there are a lot, folders, datastores, resource pools, tags, even vCenter), but then I'd also still have to deal with potential excludes (either by VM or potentially also by container). That's a lot of code to deal with something Veeam already obviously does during job start, and what if my logic doesn't exactly match the Veeam logic (for example with excludes, etc). It would be really nice if there was some function call to just return the VM objects that a job would process based on the current objects selected in the job. I'm sure I could poke at the functions and likely eventually figure it out, but a nice, standard way to do this would be really useful.