VM Distribution Point (s)

many moons ago.. virtualised Windows Server / ISS / SMB share configured as per docs

I would say it's safe to assume most organizations are using VM's for their on prem Jamf Instances and DPs. Most places run multiple "servers" on their server hardware, each being in its own VM. Is there something specific you are needing to know?

When we were on prem our DP was on a separate VM from our Jamf Server. It was just a SAN storage share that was housed on the same Server as the rest of our application storage shares.

Jamf Pro never communicates with distribution points. It only stores details for connecting to them. It'll have no idea whether it's real or virtual.

There's no reason a VM shouldn't work as a distribution point for Jamf Pro as long as it works as a standard file server.

I use a synology for the larger packages that jamf cloud has drama with. easy to keep in sync with the JAMF sync app; one user configured for rw and one for r/o. had to get the firewall configured so all the clients could see it, but it works well for larger packages.

VM or physical isn't really relevant, but please please please PLEASE enable HTTPS access for your file shares if you have any concern for their performance...

If you're using SMB then macOS has to mount the file system for your DP in order to download a package as opposed to simply downloading it when using HTTPS.

If you're using SMB and there's any interruption in the download of a package the policy will fail as opposed to retrying the download when using HTTPS.