I would recommend using VMWare Fusion as they have formal support for all of this. Though keep in mind you can only run Windows in a VM on Intel Macs. Microsoft does not sell product keys or licensing beyond that of OEM for Windows for ARM.
In my environment I actually pulled the plug on Windows VM's early last year. Way too much hassle and the Windows team never wants to support them. If someone who has a Mac needs a Windows instance we point them to our VDI solutions. Local VM's are not used a frequently as they should be and are off most of the time, they love to have problems with SCCM. Nothing like a "urgent" ticket for a VM that has not been turned on in 6 months that the person needs now for some "critical" issue they are working on.
I'd be interested to see if anyone has a good work flow for this, especially since so many of us also manage Windows Environments I'm sure someone has done it.
Looks like Parallels does not offer network boot by default, you have to change settings for it. I wonder what would happen if you tossed the boot media on a flash drive and told Parallels to boot off of that. It should point to the PXE server when the installer loads to get everything. Technically this is not network boot. I do know you cannot used shared networking as PXE will not work with that, you need bridged.
This link has a promising guide, I am kinda interested to try but I am on the VPN and our PXE servers are not accessible through our VPN gateways.
Yes but it took a bit of messing about. It was about 2 years ago so an older version of Parallels. I was only able to get it to work if I wiped an existing windows VM or clone one and rename it. In other words I could not create a new VM just pxe booting.
1.The main point is you need an existing VM so the Mac address can be to imported into SCCM. I did try to create a blank VM but it never worked until I tried to wipe a working VM or clone.