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.

@svalding Hey that’s great you have it going now. Don’t forget to disable dnsmasq you started setting up. It will cause you some pain/confusion if its left running and you don’t need it.

https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

Follow the guide for the git method, dev-branch IS currently RC-1 on it.

@Gary-Kulovics @cpattersonit

Sorry for not responding sooner.

Please turn off any firewall you have on the fog server (sudo ufw stop or systemctl stop firewalld) and try again. Clear the multicast tables per the troubleshooting guide and then restart FOGMulticastManager with either service restart FOGMulticastService or systemctl restart FOGMulticastManager and try again.

If you haven’t, please go through the troubleshooting guide posted earlier. If you’re still having problems, I can help around 4:30 PM CST via Team Viewer, please send me a message via the forums here.

@Motech09 write down all of the passwords and IPs you’re using on the new server. drop the new server database (make a backup first). import a backup of the old database on the new server. open the new server’s web gui. it will ask to upgrade the database. update all of the passwords with the ones for the new server, since the new server how has all of the old passwords and IP addresses from the old database.

@Tom-Elliott It starts with this

[Sun Jul 17 07:35:03 2016] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.19 with Suhosin-Patch configured – resuming normal operations
[Tue Jul 19 07:11:36 2016] [error] [client 10.58.120.97] File does not exist: /var/www/favicon.ico, referer: http://10.58.8.20/fog/management/index.php
[Tue Jul 19 07:52:42 2016] [notice] caught SIGTERM, shutting down
[Tue Jul 19 07:53:42 2016] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.19 with Suhosin-Patch configured – resuming normal operations
[Tue Jul 19 09:51:24 2016] [notice] Graceful restart requested, doing restart
apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
[Tue Jul 19 09:51:25 2016] [notice] Apache/2.2.22 (Ubuntu) PHP/5.3.10-1ubuntu3.19 with Suhosin-Patch configured – resuming normal operations

Then I get this repeating for a bunch of IP addresses

[Tue Jul 19 09:57:46 2016] [error] [client 10.58.12.46] PHP Fatal error: Call to a member function query() on a non-object in /var/www/fog/lib/db/MySQL.class.php on line 89

@Tom-Elliott Ah ha, thank you!!

@Wayne-Workman I just wanted to update you on what I saw as I got it working.

In the multicast log, it was showing 0 tasks to be cleaned, but 3 tasks were found. Always. Every way I’ve seen here on the forums to destroy any udp casting tasks did not change the log continuing to show those 3 tasks. On two of the laptops I just happened to be trying to multicast that day, I took all source of power away and held the power button for 10 seconds. I then started a multicast task for those two, and they worked. Keep in mind that I haven’t been able to multicast for a few weeks now. I find it odd that that’s all I had to do, and on two random laptops at that.

Also with the timezone issue, the services not starting was happening before I even tried to set the timezone prefrences. I tried to set the timezone purely because my multicast log was showing dates four-five hours away. I don’t know the exact time, because the log is now reporting the dates correctly.