YES!
I had not realised I needed to copy the encrypted output string from FOGCrypt.exe to the web-based UI. It joined the domain after a few seconds of sitting at the login screen without intervention.
Thank you SO MUCH for the responsiveness and help. You guys rock. It looks like I’m going to trash the Acronis Snap Deploy. So far, FOG is better.
Thought I’d add a follow-up.
@Wayne-Workman - many thanks for the recommendation of Debian and for the https://wiki.fogproject.org/wiki/index.php?title=Debian_8 link.
I’m back to two working FOG servers (one for each domain/subnet) and got a nice bonus: With the Ubuntu servers, Veeam Backup and Replication wouldn’t do a VeeamZIP job on the server, only on its replica (which made backups on the host with the replicas much longer than the host to the FOG servers. But the Debian servers can have a VeeamZIP job done on them, so now my nightly backups are much more balanced. 
Thanks, again to @Tom-Elliott and @Wayne-Workman for the help. I really appreciate it. You guys rock.
I had a similar issue, but (dumb) lucked into a solution.
Dell Optiplex 3040, BIOS set for UEFI: Onboard NIC (IPv4) first, Windows Boot Manager second.
Installed Win10 Enterprise from USB. After the install and first time on the desktop, before installing anything else, a reboot would come out of the UEFI network boot with Preparing for Automatic Repair. (I gave it plenty of time — about 14 hours! — never got past that screen.) I installed again and got the same results.
I made one change in the BIOS: added a check to ‘Enable Attempt Legacy Boot’ and then installed again. This time, at the first reboot, the screen went dark and … nothing. Manually powered off and back on and was able to log into Windows. But the next reboot, again the screen went dark and stayed that way. So I removed the check from ‘Enable Attempt Legacy Boot’ and now Win10 is working fine, normal reboots, exiting from the UEFI network boot into Windows.
Hope that might be helpful to someone.
Thought I’d add a follow-up.
@Wayne-Workman - many thanks for the recommendation of Debian and for the https://wiki.fogproject.org/wiki/index.php?title=Debian_8 link.
I’m back to two working FOG servers (one for each domain/subnet) and got a nice bonus: With the Ubuntu servers, Veeam Backup and Replication wouldn’t do a VeeamZIP job on the server, only on its replica (which made backups on the host with the replicas much longer than the host to the FOG servers. But the Debian servers can have a VeeamZIP job done on them, so now my nightly backups are much more balanced.
Thanks, again to @Tom-Elliott and @Wayne-Workman for the help. I really appreciate it. You guys rock.
@tom-elliott
Thanks. For the record the option is --no-check-certificate
Followed directions at https://wiki.fogproject.org/wiki/index.php?title=Debian_8 for configuring Debian 9.3 (stable), but don’t have enough space to clone the FOG project, so quit before installing git.
Used wget https://github.com/FOGProject/fogproject/releases/download/1.4.4/fog_1.4.4.tar.gz (which used to work with Ubuntu Server) but received
ERROR: The certificate of ‘github.com’ is not trusted.
ERROR: The certificate of ‘github.com’ hasn’t got a known issuer.
What’s the next step?
@wayne-workman
Debian (stable), here we come…
@wayne-workman - current: 1.4.4 (which is still – for now – working on the Ubuntu 16.04 server for patrons) it was the server for staff that got clobbered (I run IT for a public library and have two networks on separate VLANs.)
@tom-elliott - just read through and am wondering if I’d be better installing a different distro? Opinion?
This morning, PCs were stuck in a reboot loop because they couldn’t get to the FOG server. After bypassing PXE, I started repairing FOG server with re-install. This has worked in the past, but not today: at http://<ip address>/fog/management there was only a blank page.
Wiped the root partition (left /images) and reinstalled Ubuntu 16.04. Ran apt-get dist-upgrade (lots of updates), configured IP address, rebooted and then tried to install FOG.
I have tried installation multiple times. I get Failed! (Will try later) on the following packages one or more times (apache2 every time):
apache2
libapache2-mod-php7.1
php7.1
php7.1-cli
php7.1-gd
php7.1-mbstring
php-gettext
(One installation attempt failed at ‘Adding needed repository’.)
When it gets to the part of checking packages, I get OK for everything. But when prompted to use a web browser to do the Database Install/Upgrade, the page is blank.
The blank page’s source has html tags, head tags, and body tags. Nothing more.
Not sure of next step. Log files (where?) Suggestions?
@Tom-Elliott
Just installed version 1.3.3 / SVN Revision: 6061 — installed without a hitch.
@Tom-Elliott
Using the instructions at https://wiki.fogproject.org/wiki/index.php?title=Installation#Current_development_version I ran the installation. The only problem I noted during installation was a failure of backing up database. There was no prompt for ‘Press [Enter] key when database is updated/installed.’ I still get a blank page when trying to go to http://<ipaddress>/fog/management and mysql still shows the same four databases (none for FOG).