@tom-elliott
Thanks Tom

I am having issues with the UEFI boot order being changed to Windows Boot Manager after successfully imaging a PC.
I have to manually enter BIOS and change the boot order back to LAN
This makes imaging PC at remote sites very difficult, I would have to drive to the remote site and change the BIOS settings and that’s just not going to happen.

Does anyone know of a workaround for this issue?
I am using Lenovo ThinkCentre PC’s

does anyone have a cleanup query to cleanup hosts in the database that haven’t reported back in a specified amount of time?

@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!

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

Found it.

WOW that was fast

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

@greg-plamondon I’ve yet to hear of imaging causing a change on the other tags. Only during registration does this happen. I’ll take a look at the inventory update script, maybe I missed something?

I have found a work around using the “Other Tag #2” for now.
Thanks!

@george1421 said in Data missing from the database after host is imaged.:

@greg-plamondon So just for clarity, if you disable your fog post install script from running (from the master script) the Othertag data is removed from the database?

I could see if you might have altered Othertag data it might happen.

Yes, the othertag is removed. Interesting enough I am able to use the “Other Tag #2” ie “iOtherTag1” field fine.

I also reverted back to fog 1.5.2 and I am having the same issue.

Ok, it doesn’t matter what I do with the scripts. the Othertag data is removed after I image the PC.

@greg-plamondon said in Data missing from the database after host is imaged.:

@george1421

if i comment out this section…

       case $othertag in
            BAY)
                . ${postdownpath}fog.log
                . ${postdownpath}fog.bay_replace-files
                . ${postdownpath}fog.drivers
                . ${postdownpath}fog.ad
                ;;
            MPMI)
                . ${postdownpath}fog.log
                . ${postdownpath}fog.canada_replace-files
                . ${postdownpath}fog.drivers
                . ${postdownpath}fog.ad
                ;;
            JET)
                . ${postdownpath}fog.log
                . ${postdownpath}fog.jet_replace-files
                . ${postdownpath}fog.drivers
                . ${postdownpath}fog.ad
                ;;	
            *)
                . ${postdownpath}fog.log
                . ${postdownpath}fog.replace-files
                . ${postdownpath}fog.drivers
                . ${postdownpath}fog.ad
                ;;
        esac

the data remains after imaging.

I take that back… The data doesn’t persist regardless if I comment it out.