Posts made by Kureebow

Here are the results for ls - al

[root@localhost fogproject]# ls -al
total 16
drwx------. 4 fogproject fogproject 146 Jun 3 2022 .
drwxr-xr-x. 4 root root 37 Jun 3 2022 …
-rw-r–r–. 1 fogproject fogproject 18 Mar 31 2020 .bash_logout
-rw-r–r–. 1 fogproject fogproject 193 Mar 31 2020 .bash_profile
-rw-r–r–. 1 fogproject fogproject 604 Jun 3 2022 .bashrc
drwxr-xr-x. 3 fogproject fogproject 31 Jun 3 2022 .config
drwxr-xr-x. 4 fogproject fogproject 51 Jun 3 2022 .mozilla
-rwxr-xr-x. 1 fogproject fogproject 681 Jun 3 2022 warnfogaccount.sh
[root@localhost fogproject]#

These are the results for pwd

[root@localhost fogproject]# pwd
/home/fogproject

Looking for a way to to possibly upgrade our FOG server to 1.5.10. I tried the git pull method and received the following response.

[root@localhost fogproject]# git pull
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[root@localhost fogproject]#

I am truthfully not sure how we installed initially.

If a fresh installation is what we need that is fine I just want to make sure I go about this in the most effective manner.

Thanks for any assistance you can provide.

We are currently running on CentOS 7 if that is needed.

@george1421 Sorry for the late response I have been out of my office for a family emergency. This is the response I got when attempting that command. Thanks

[root@localhost fogproject]# git pull
fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[root@localhost fogproject]#

This seems like a dumb question but is there a way for us to “Upgrade to FOG 1.5.10” without a complete uninstallation?

Thanks.

@Sebastian-Roth my network supervisor is looking into the Spanning tree settings. However, he did ask if FOG has the capability to boot with a usb drive for the time being. We are rushed to get some devices imaged today.

I am encountering an error and am racking my brain here. Please see below. Thank you all so much!

udhcpc: sending discover
udhcpc: no lease, failing

@sebastian-roth Here you go sir

@sebastian-roth I believe I have the imaging issue resolved it was unrelated. However, good news! It did work one time. I reimaged the PC after adding the MAC address to the list of additional MACs and then post image after logging into the machine with the local account I got a message at the bottom right of the screen saying FOG had to perform actions and then the device shut down and joined the domain.

After getting excited that we finally had it working I tried on another device with no success. I added the additional MAC and reimaged but after sitting for 15 minutes or so I have had no message appear.

Thank you!

@sebastian-roth

After adding the mac Address I have been unsucessful in getting this device to reimage. This was not an issue prior. The device gets to a certain percentage then will not move forward. I let the device image overnight and after 15 hours it never moved past 94.39%.

Thank you for your help.

@sebastian-roth I tried following the directions on Dells Website to enable MAC Passthrough in Bios but I do not see an option listed anywhere. We are using Dell 3190’s. When I look in the system information section I do see the MAC Passthrough address listed but I do not see an option to enable it.

@sebastian-roth This is a laptop using a USB NIC adapter.

@sebastian-roth For instance. When we did the full host registration and inventory we entered the name MSSTWLCT403F3 for this device as seen in the snip-it below.

When we deployed the image to the device containing the FOG Service it re-added itself to the Host list waiting for approval with the following new name.

So our name change command is not working from when we manually put in the name of the device through full host registration and inventory.

I’m not trying to be wordy just trying to explain the Best I can.

Although the mac addressed between these two devices are showing differently in WEBUI they are the same device.

@sebastian-roth So this host is the same device. This was named by serial number. The host MSSTWLHM2C8G3 is DESKTOP-4Q9J25B. When I boot to FOG on the device it shows as MSSTWLHM2C8G3 but when inside of windows the name still shows as DESKTOP-4Q9J25B.

@sebastian-roth Is this what you need?

@sebastian-roth The host named Desktop-1RPRNDG is registered with FOG because when I PXE Boot to fog it does show registered at the top and the device is listed in the WebUI along with its correct host name that was assigned during the full host registration and inventory.

Both devices are on the same subnet, VLAN, and are both sitting in front of me in my office. However, the server is plugged into one switch while the host device is plugged into another. I can try putting them on the same switch to see if I get a different result.

Here is more of the fog.log

Thank you!

@Sebastian-Roth I have tried removing the service and reinstalling as well as using groups to reset the encryption data with no luck.

Please forgive my ignorance but I can see the errors but don’t know how to make heads or tails of it.

fog.log

Yes we do have it installed.

We are working on bringing our fleet into fog as hosts in the hope that during registration setting the hostname might eliminate some post time in naming the devices and joining to the domain.

Our first attempt has been unsuccessful. I made sure to set the Active Directory defaults in the webUI and told the device during registration I wanted it to join to the domain.

This device also did not change its computer name to what we entered for the hostname during the full registration and inventory.

Any help with this is greatly appreciated!