@FlareImp Issue fixed with

DELETE * FROM hostMAC where hmPrimary = '0';

@Tom-Elliott That did not have an impact. still seeing ${serial} on the host list. If it helps I am also seeing at the bottom of my host management page

${pingstatus} ${host_name} ${deployed} ${image_name} ${serial}

@FlareImp said in Showing Last Check-in Time:

dumb question but where would I find the log file for hooks?

See my signature.

@flareimp There’s other options as well. You could do either of the below.

The below script is a one-use script that someone could run manually. After updating the IP via the OS configuration, you can run this script that will update all the FOG IP bits for you.
https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

This next script below will continuously update FOG’s IP settings to match the local interface IP address. You could package this with the fog server image you have so everything just works out-of-box.
https://github.com/FOGProject/fog-community-scripts/tree/master/MakeFogMobile

The change worked great, Thank you!!!

@tom-elliott sweet! Thanks Tom!

@sebastian-roth Thank you and @george1421 for your assistance it this matter. It worked great!

Thanks again and keep up the great work!

@sebastian-roth That took care of the problem.

Thank you all.

You were correct, using DCC is not an option. I did find that by using the CMD prompt and entering

bcdedit.exe /enum

it will display your working Windows Boot Manager but not the extras. However, if you use

bcdedit.exe /enum firmware

it will display all the different WBMs, even the faulty ones.
I am currently trying to build a script that will remove the false entries.

@FlareImp I guess you need to elaborate a bit more on how your whole network is structured for us to be able to understand and give appropriate information.

@tom-elliott Awesome, working like a charm, thank you.

@tom-elliott your the man! that was the issue. My Node was set to support 0 clients. thank you all for your awesome product!

@flareimp It should not. I’m about to release 1.5.2 (considering the bugs listed) which means you’ll have to edit the file again on install.

You can help simplify this by doing:

mv /var/www/fog{,_back} ln -s /var/www/html/fog /var/www/fog

@george1421 Thank you very much! I was able to modify the script to fit our setup. Everything is working smoothly now.

Thanks again!

@FlareImp It looks like the TVNE-Fog server didn’t have the whole image. The pic on the left is larger (at least the d1p2.img is) than the one on the right.

in the interim, you could always setup rsync until toms worked his magic :-)…

0_1490232257603_upload-4f63a6f9-f6b1-4705-8725-3b5b9e53acec

Apparently with 0.2.88 (maybe earlier but before that for us was 0.2.69) they added a “note” feature

The picture shows the (note:) line now which shows the Storage location and the Image name.

Please follow here: https://forums.fogproject.org/topic/9344/your-database-connection-appears-to-be-invalid

@FlareImp Glad you got it fixed.

@Wayne-Workman In my test envirement I am running the RC versions on Ubuntu 16.x. When I setup the new servers they will all be fresh installs as well.