What is the domain functional level of your DC?

I remember having difficulty with 2008 domain level, and I ended up having to join the domain in powershell instead of the FOG. Notice that domain does not have the .local part of it. That reallllly tripped me up for a while. Alternatively, I learned that you can do username@domain.local… at least when setting the autologin registry setting. I have not tested that in your use case, but it is something new to try

$domain = “domain”
$password = “notpassword” | ConvertTo-SecureString -asPlainText -Force
$username = “$domain\domainadmin”
$credential = New-Object System.Management.Automation.PSCredential($username,$password)
Add-Computer -DomainName $domain -Credential $credential -OUPath “OU=FOGBuilt,OU=Computers,OU=main,DC=domain,DC=LOCAL”

What is the domain functional level of your DC?

I remember having difficulty with 2008 domain level, and I ended up having to join the domain in powershell instead of the FOG. Notice that domain does not have the .local part of it. That reallllly tripped me up for a while. Alternatively, I learned that you can do username@domain.local… at least when setting the autologin registry setting. I have not tested that in your use case, but it is something new to try

$domain = “domain”
$password = “notpassword” | ConvertTo-SecureString -asPlainText -Force
$username = “$domain\domainadmin”
$credential = New-Object System.Management.Automation.PSCredential($username,$password)
Add-Computer -DomainName $domain -Credential $credential -OUPath “OU=FOGBuilt,OU=Computers,OU=main,DC=domain,DC=LOCAL”

Chiming in here… I’ve been stumped for some time after I too purchased a handful of new G8 HP Laptops.

Fortunately I found this thread, and I am glad to say that snponly.efi worked for me!

I figured posting might keeps this thread alive and relevant for others.

I have been experiencing similar issues since moving to 1903… Though I am using the 11.16 FOG client. I didn’t find that adding those two sc.exe lines in my SetupComplete helped, and after checking for errors I have ruled out the Win update issue. I am considering starting a new image from scratch again, because like Jay, I’ve gone through about a dozen different changes and might be missing something crucial.

@Sebastian-Roth Is that Modules.dll for a small fix or for debugging? I’ve seen on other posts that you can join domain the in unattend.xml file. Is there a way to join domain AND change the name?

Looking for any sort of fix or recommendations here. For now, I’m fine with throwing some duct tape on it to get back off the ground!

[EDIT: sorry didn’t see this marked as “solved”]

@jconway1006, not sure if you were able to get your web service back up.

After testing on CentOS, I found that 1.5.7 would not work, and I had to move to dev-branch (1.5.7.2)… not sure why, but it worked. Maybe a clean install on the VM server is best.

I’ve also noticed with VMware it frequently takes more than one try to get the iPXE connection. To get around it

• boot to EFI bios and try PXE network boot

• at each failed attempt, choose the shutdown option in blue screen

• rinse and repeat

Have you tried re-installing FOG? When my fog server web UI went down a month or so ago, it had to do with Ubuntu forcing updates. See post below
https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

Additionally, I’ve experienced some problems with Ubuntu and VMware… I’ve been having similar troubles, minus the virus. Still been a very frustrating week so far. It seems that updating TFTP kernel under FOG system settings did something: I played around with upgrading my pxe kernel version also tried saving under different names. I plugged those into the TFTP Server setting while I tried them. I was finally able to fully connect, though I also deleted (and re-registered) my host and image at some point during my frustrations.

(running FOG 1.5.5 on Ubuntu 16.04 -> getting ready to migrate to latest FOG on CentOS7…
figured I should probably write a post for the amount of time I’ve spent on here)