@greg-plamondon said in Windows Boot manager set as default after imaging:

Windows Boot Manager after successfully imaging a PC.

My bet is after FOG pushes the image and the workstation reboots, LAN will still be set until Windows OOBE runs, then windows set the boot order to WBM. I’ve seen this happen on my VM I use for MDT reference image build.

If you were using Dells, Dell has a CCTK tool you can use to reset the boot order.

A little google-fu shows that this is a particularly annoying issue when you have a dual boot computer. One solution that was posted was to set a firmware password once the boot order is set. From the one post I saw, if there is a firmware password, windows can’t mess with firmware settings.

@tom-elliott
Thanks Tom

@tom-elliott said in Data missing from the database after host is imaged.:

Fixed in working.

Basically what was happening was the other1 field is used to send emails. That part still can happen (as any value that’s not an email will just not receive an email), but it was clearing the field after it sent the email out.

I just commented out the line as I cannot remember exactly why I was clearing it to begin with.

Thanks Tom!

@greg-plamondon Thank you I’ll update the tutorial with the new information too.

I’m aware of the issue and have already fixed this in the working branch.

@wayne-workman I searched for some time and couldn’t find anything. I will give those links a try.
Thanks!

Thanks for testing.

The reboot was all that was needed, sorry for not trying that immediately.

You can mark this as solved.

@wayne-workman @Tom-Elliott
Thanks for the help guys! I was able to get it re-installed although I have one issue, I will open another thread for that.
Thanks again!

@Greg-Plamondon The new video is interesting as is seems to show that it finds the interface eth0 but is not able to bring it up within 35 seconds. What kind of client model is this? Are you able to FOS boot this very same machine at a different location? I kind of doubt but what do I know. 😉

@ylber you can get the code from from working_dev branch in git repository.

@wayne-workman
That Worked!

[root@10fogserver MonitorFogStorageNodes]# git log -1 commit bb920e4367b5076ac2bb7bb70575ec4b647d5aee Author: wayneworkman <13314799+wayneworkman@users.noreply.github.com> Date: Wed Feb 21 13:53:10 2018 -0600 Fix spacing in evaluations [root@10fogserver MonitorFogStorageNodes]# ./MonitorNodes.sh [root@10fogserver MonitorFogStorageNodes]#

Thanks @Wayne-Workman

Rather than changing FOS /etc/fstab file, I believe it would be better to pass it as a kernel argument like clamMount=x.x.x.x:/some/clam/av/dir and have the script mount that dynamically. Then it can be user adjustable like image mounts are already.

@greg-plamondon The instructions were in both documents. The one I linked and one that Wayne linked. Unfortunately it happens more often then you might think. There are some documents out in the wild that recommend you setup the fog account to install the software and manage the syste (which is the wrong way).

@joe-schmitt

Thanks Joe.
Solved.

@Greg-Plamondon If you ever see an issue where the web UI doesn’t load, take a look at the apache logs - see my signature on where to find those on your FOG server.

i really would like to hear wayne speaking 🙂

@george1421
Thanks for all your help on this. Next time I will make sure I am running the same branch.

having issues with trying to upgrade from dev-brnach to working right now. I will update as soon as i get the upgrade resolved.
Thanks.