@brent could you specify exactly at which point of the installation you see this error? If you notice the installer hangs or fails specifically during the “pinning” stage, it is likely a name resolution issue.

I’ve found a solution for this: you need to manually edit the Windows hosts file at C:\Windows\System32\drivers\etc\hosts and add an entry with your FOG server’s IP address followed by the name “fogserver”. This ensures the SmartInstaller.exe recognizes the server and can download the certificate properly.

@brent I don’t recommend this solution.

But I did test something similar many years ago: https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-proof-of-concept-blog

There is also this method: https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

Another choice is to create an iscsi target and connect the fog server to that iscsi target to the /images directory on the fog server.

But FOG Project only supports using a linux computer with the FOG Storage node configured loaded as valid.