I have used g4l (g4u) which uses an ftp server to host hard drive images. the windows computers will still (as with most cloning software) need to be named, domain joined, licensed, and activated after.
I built an Gold USB Stick with Microsoft Tools. You still have an Gold PC and background to update your image but I loved it to have a thumb drive around. Its the Microsoft Deployment Toolkit. You need an Client-Master, 2 Thumb Drives, an external harddrive (at least bigger than your Masters PC storage) and a Admin PC. On the client master you build the system of your dreams with all the software and configs on it. Also you will sysprep it at the end. On the Admin PC you have the Deployment Tools installed to create an answer file to make the installation nearly hands free. The first thumb drive you use as a common installation device created by the media creation tool. the second thumb drive format with two partitions. On the first partition you also put a common media creation tool-windows installer on it. The first partition should be big enough to host your modified windows image aswell. With powershell you can create an split esd file from your client-master-installation and copy this over to your Gold USB Stick. On the second partition you can put some scripts and drivers if needed.
Just to be clear this isn't a FOG limitation. This is a using Windows OEM media to create a custom image that you plan on redeploying to other OEM machines. This is a Windows EULA violation. But the bar to get a volume license is pretty low. All you need is 1 MS Windows 10 Pro volume license to deploy a custom image to any number of OEM licensed computers. You just need to get to 5 points (1 MS Windows 10 Pro volume key counts as 1, all you need is 4 others like windows server CAL license) to open a ms volume account without spending too much.