@JYost
Thank you George…this pointed me to the etc/network/interfaces file where I found that the dns-search field only had “domain.local” and was missing “domain.com”. Once I added that into the dns-search field all was good and FOG was able to see devices which were online (denoted by green Windows icon).
Thanks again guys…great support as always!!!
Go ahead and mark this as solved.

That was painless!! Worked great. Thanks guys!!

Running Fog 1.5.8 on Ubuntu 16.04LTS

We just received several Lenovo T14’s and I’m unable to Pxe boot them. We are able to image earlier models (T460,T470,T480,T490 series) without any problem. During Pxe boot it gives me an error “No network interfaces found, your kernel is most probably missing the correct driver!” Looking at a similar issue it appears I may need to update the kernel. Any assistance is greatly appreciated!!
Cheers,
John

@Tom-Elliott
Correct…I understand the image should not be joined to the domain, and its not…I’m referring to devices which I’m either imaging for the first time or re-imaging. I will attach the fog.logs for devices which failed and which succeeded in being renamed and joined to the domain. Sometimes it renames them fine but doesn’t join it to the domain. Other times it doesn’t do either, or does both fine. It’s been hit or miss.

Good morning, I’d like to know what the preferred best practice is regarding new and pre-existing AD computer accounts when using FOG. Should pre-existing accounts (devices being reimaged) be deleted, deleted and recreated, reset, or just left alone to be overwritten? Same question applies to new computer accounts - should we create computer accounts prior to imaging or should we leave FOG to do that? I’m asking this because we continue to have problems with FOG naming PC’s and joining them to the domain - works only about 50% of the time and I’m trying to eliminate this as a potential cause. Thanks in advance!

Good morning,
The section of the fog.log you are looking at is dated 3/16…if you scroll down you will see the section from Friday…which brings to mind another question…why are there still fog.log entries from back in March and then appended with the log entries from Friday?

Cheers,
John

Today I have been reimaging a stack of laptops (Lenovo T460, T470, and T480’s) and was successful for about 8 in a row without any problems. The current device (Lenovo T490) has been successfully imaged in the past, but today for some reason it is not being renamed or joined to the domain (4 failed attempts in a row). I am pre-configuring the device in the web interface (and ensuring that I have the AD information entered as well as the checkboxes to rename and join domain).
I am running FOG 1.5.8 on the server, the image has FOG client 0.11.15). We’ve had many issues in the past with devices periodically not renaming or joining the domain, but since I started to use the web interface to pre-configure the hosts and create the task things have been working much better (I used to use the DOS/Pxe boot setup previously to create the task).
I’ve attached the C:\Fog.log file for you to review as I’m not entirely sure what the error messages should be telling me. Any help would be greatly appreciated.
NOTE - the laptop has an Intel I219-V NIC, Windows 10 v.1909, Single drive.
Thanks,
John YostHE-L002107-FOG2.log

I’ve always wondered why when we click on HOSTS from the top menu it brings us to a blank screen and from there we have to click on SHOW ALL HOSTS. It makes more sense to immediately show a list of all the hosts. It’s an extra, unnecessary click no matter what your intentions are (i.e. show all hosts, add host, etc.)

In the web interface when I go to Add New Host, I enter the hostname, MAC address, select the desired image to be applied, then scroll down to the Active directory section at the bottom. I place a checkmark in “Join Domain After Deploy” (which populates the fields with the AD information INCLUDING Name Change/AD Join Forced reboot). I save this information, then go back into Hosts, Show all hosts, I select the host I just created, then click on the Active Directory tab at the top and all the fields are empty. I select Name Change After Deploy, it again populates MOST of the fields except Name Change/AD Join Forced reboot. I check this option and save again. Thereafter when I go into the host all of the AD information is populated as it should be. My question is why do I need to enter/save the AD information twice - is this normal behavior or do I have a setting somewhere misconfigured?

@JYost
Thank you George…this pointed me to the etc/network/interfaces file where I found that the dns-search field only had “domain.local” and was missing “domain.com”. Once I added that into the dns-search field all was good and FOG was able to see devices which were online (denoted by green Windows icon).
Thanks again guys…great support as always!!!
Go ahead and mark this as solved.

Greetings,
When I create a new workstation in the Fog Host Management screen it initially shows up with a green Windows Icon as shown below:

After a minute or so the Windows icon disappears and I am presented with a Red exclamation as shown below:

This behavior is similar on 10 of our 11 FOG servers. The only server which is working normally is the one we rebuilt completely last week. When I create new hosts on that one the Windows icon stays and doesn’t change into a Red exclamation. Any ideas as to what could be causing this?
NOTES: We recently upgraded all of the 11 FOG servers to version 1.5.8. Prior to the upgrade ALL hosts on ALL servers were displayed with a Red exclamation similar to what they are now. Post upgrade - the only server not displaying Red exclamations’s on the hosts is the server we rebuilt completely (Reinstalled Linux, Installed & Configured FOG). Obviously this is a configuration issue, but I’m not even sure what that column in Host Management is for - I presume an indicator of successful 2-way communication between client and host?
NOTE: We were forced to recreate the certificate on several servers due to problems during the upgrade - Sebastian assisted us with this.

Thanks in advance,
John