@Tom-Elliott said in Fog Trunk Autologging Out Immediately:

I did not update the text because I think it’s simpler to enter values in the form of “720 minutes” vs having users run calculations on their own (no offense anybody).

That said, I was unaware the logout time was being done in seconds and not performing the calculation as it had under the legacy client. (Oversight I suppose, for that i’m sorry).

This has been patched and pushed though. Thanks for letting us know.

I agree wholeheartedly and I can confirm that this is now working as it should on the latest 1.3.0-RC2 version.

thanks!

Thanks for all the help. You pointed me in the right direction and the problems have been resolved.

I always booted our Mac Minis with ipxe.efi. Just try different ones and see which one is working for you…

@george1421
and it works! Thanks very much , 4.1.2 did the trick 🙂

I have tried clearing cache, doing a reload, a CTRL reload, new incognito window and have not regained sorting. If anyone else is reading this post can you please give it a try and report back. Maybe my setup has something goobered up.

Log into fog server click Report Management Click Imaging log Set a valid Start and end date Click Search Click the column header to sort results.

@jkonney Correct, they shouldn’t be possible, though I suppose it’s not the end of the world. The issue it poses, though, is it could give you access to lower level directories. For example, if you had put in the path as “…/…/…/…/usr/bin/init” you could lose your ability to load your OS any further. Of course it’s only with FOG permissions I suppose, but capturing could be a bad time.

I feel I need to say it - FOG runs on a Linux server, man.

Start in the Wiki, read through the link George gave. There are also several installation tutorials in there.

Well, I got some good news. I was able to get a successful multicast going tonight. I am not 100% sure of what fixed it. I did several things.

Not in particular order:

Updated FOG to trunk Disabled IGMP snooping from the switches Made a change to CentOS as seen here that has to do with routing (honestly don’t think this helped) Added 232.168.1.0 for FOG_MULTICAST_ADDRESS (it wouldn’t work without that)

I plan to do more tests to really make sure it is working tomorrow and the following days. I will keep this updated if anything substantial changes.

Thank you to everyone.

@Wayne-Workman Hmm, still does it in the latest version (leaves computer with a disk size 2GB larger than the image, and you have to grow the remaining X GB to make it full capacity again). image captured and deployed on the 1.3.0 RC1. The captured machine was that way after capture, and the machines that had been deployed to also.

@Tom-Elliott Seems to have worked, thank you! Maybe I messed up the trunk upgrade last time somehow. Anyway, I’m showing 1.3RC now so that’s all I’m worried about

@kinjo said in BOOTMGR is missing:

also having this issue

got the fix people
http://www.deskdecode.com/how-to-fix-bootmgr-is-missing-error-on-windows-desktop-or-laptop/

@mpmccormick That redirect is related to the message that is displayed in the FOG Configuration area, not sure why this would redirect you immediately after logging into the Web UI. That’d be a question for @Tom-Elliott

I’ve set the FOG_MEMTEST_KERNEL in the General Settings to memtest.bin with no luck, same error. There is a file called “memdisk” in the same folder, it errors in the same way.

Never could figure this issue out. Went ahead and installed 14.04 and upgraded to trunk, and it all went smoothly.

@Towndrunk also, any time an image is done inventory is also updated automatically

@Tom-Elliott Success!! changing filename from “Firefox Setup 47.0.1.exe” to “Firefox47.exe” and renaming snapin to “Firefox47” allowed the snapin to deploy. many thanks for your help!

@kurtblah way to go, and awesome work @Sebastian-Roth!

@Sebastian-Roth Thank you for all the details on how to make this work. I haven’t been able to work on our FOG server for the last few months so it has taken me a bit to try this out. I was able to get everything working except I get an update error. The error states “The server address is not correct.” This appears to stem from an issue where the live cd doesn’t have an IP address and can not connect to the update server. I’m looking for a solution now.

Attached is the screenshot of what is happening when i try to image using one of my copied images.0_1469042166199_ntfsflag.jpg

For those who may come across this same problem…

I updated my BIOS and it resolved the problem.