@Joe-Gill Well, I suppose the first thing to try is this group that failed - but by itself, without other multi-cast tasks running. See what happens.

Since this issue isn’t really related to FOG, I’ll mark it as solved.

OK reinstalled the FOG sever again (over itself) and everything seems to have ironed itself out. I had to basically install it twice. But everything seems golden. Back to Windows 10 on a Surface image. Thank you guys.

I also added it to the wiki.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Hosts_think_they_are_not_registered_.2F_can.27t_register_.2F_other_weirdness

@spetzmax

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@Scott-Adams

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@dustindizzle11

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@Tom-Elliott
Yeah that makes since. I just rem there being an issue with the resizable option with ntfs at one time. And the fixed size worked better or was more stable. I don’t remember exactly and I’ve slept alot since then. Old habits I suppose.

Thanks.
Jason

@x23piracy It updates the next time the image is used. Regardless of capture or deploy.

@Towndrunk said in Windows 10 Domain Issue:

I imaged a computer that was activated and on the domain. After applying that imaged to another computer it says that is on the domain when I log in locally, however there is no trust relationship.

If your image is already joined to the domain, you will have nothing but problems, and major ones at that. There is no imaging solution made by anyone that would suggest taking an image from a domain-bound computer. They all suggest exactly the opposite, take an image of an un-bound system.

@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