@vascomorais Seems like your question has mostly been answered, but I wanted to pipe in on your comment ‘I can ask the forum’. YES! These forums are amazing. There are numerous people(Including senior developers) that will respond quickly and intelligently and assist you with problems you have with the system. I can’t say enough good about this community.
Hope FOG works for you, it’s been a lifesaver for me and my organization!
Philip
@imagingmaster21 That’s what I’m working on now. Previously I wasn’t syspreping because I was scared of unattend. But others have convinced me I need to stop being a wuss and try to learn myself real good. I’m almost there. In fact as we speak I just sysprepped a reference image machine and I’m about to capture and test deploy it.
@george1421 I originally didn’t follow your guide to install and activate fpm, I had assume it was default. Once I followed the guide(not without cursing and much looking up of VIM guides), and got it installed and activated my web interface came back up and my clients waiting to image started communicating with FOG again.
I’m still not 100% that it’s fixed or if the last step(restarting PHP and Apache) simply reset the problem and it’s going to reappear in a few hours. I’ve been watching it run for 45 mins or so now and it at least appears to be stable. But we’ll see if it completes overnight or not.
Just wish I had remote capability so I could monitor from home instead of having to come to the office.
Philip
@george1421 Alright. That’s working. Unfortunately another problem that I thought might occur has come to pass. It’s nothing you guys can help with I think though. The whitelist is blocking what FOG needs to install. I’ll have to figure this out. Probably grab a wireless hotspot to connect to at least for long enough to install.
I’ve been fighting with my superiors for months about this network being too restrictive. Ugg.
Thanks again.
So I found the problem. It was a PEBCAK issue. Essentially I had also instituted a group policy restricting membership of the Local Admin group and had forgotten to add my locally created admin to the group policy. So as soon as it created the user and got domained it immediately removed it from the admin group.
Luckily I had a USB with Kali on it laying around so I just hopped on and elevated privilege on a user so I could fix the problem that had arose.
Sorry for wasting the communities time.
Philip
@Sebastian-Roth So good news and bad news. The bad news is that I am running a Ubuntu server. Good news is that the failed update appears to have saved me from problems. At least my server still seems to be functional. My other problem(my problem, not FOG problem it turns out, stupid fast boot), is fixed(crossed fingers) and I’m capturing with my 1.5.5 server right now. Guess I’ll wait to try updating again until 1.5.8 comes out. 
Philip
Good evening,
I’m running into a couple of problems, but the one that pertains here is a similar problem while trying to upgrade from 1.5.5 to 1.5.7(I think, sorry I’m at home right now trying to get some research done before going back to work tomorrow). I haven’t checked the logs yet, but it’s failing at the same point. I’ll check tomorrow to see if my log is the same and let you know. I’m hoping upgrading solves my other problem, if not I’ll post another post about that one later.
Philip
@george1421 thank you for your responses. The timeout is fine the way it is, as long as I understand how it functions. Just need to turn it up while I join 100 clients to it. 
Though, since you say it’s probably a layer 8 problem on the group based multicast, I’ll try to find the time to run a few experiments on my side and see if it’s now working. I have a fairly simple network (air gaped single subnet educational lab), so that shouldn’t be the issue.
The repeating multicast would be handy but, as you say, there are certainly potential issues there as well. Again, as long as I understand the mechanic I can work with it! Thanks again for your answers(and all your help in the past as well).
Philip
Good afternoon,
I’ve been using FOG for a year or two now and love it. However, one thing that still confounds me is how the multicast feature works. I have a couple (semi)specific questions:
How does the ‘Timeout’ function? In previous imagine solutions I’ve used every time you join a new client to the multicast it restarts the timeout, but that doesn’t seem to fit the way I see FOG multicasts function.
If clients don’t join catch the multicast before the timeout hits, they seem to just sit there patiently, not doing anything. Will the multicast restart at the end of the push, thereby catching the latecomers?
I’ve tried using the ‘Multicast to group’ feature in the past(I think one version ago), but it never worked for me(and seemed to be broken on the coding side from feedback I had got at the time), and I haven’t tried with the current release, is it more functional at this point? Or is it a layer 8 issue on my side?
I appreciate your patience and responses, I know most of this I could probably figure out by trial and error, but I’m extremely multi-hatted and short on time(aren’t we all?) and sometimes it’s easier just to get feedback from those who know rather than experimenting myself. (also, I hope these haven’t been answered before, I tried to search but that link seems to be broken for me…)
Philip
I know this is an old topic, just wanted to reiterate that this fixed my problem. The weird thing is that this wasn’t a problem until today. Been using Fog with the same laptops, same basic install of Windows 10 for around 1.5 years now, and today was the first time I saw this error. Went and turned off fast boot and it works great. Yay for forum search functions.
Philip
@vascomorais Seems like your question has mostly been answered, but I wanted to pipe in on your comment ‘I can ask the forum’. YES! These forums are amazing. There are numerous people(Including senior developers) that will respond quickly and intelligently and assist you with problems you have with the system. I can’t say enough good about this community.
Hope FOG works for you, it’s been a lifesaver for me and my organization!
Philip
@tom-elliott Updated the production server and it is now multicasting. As a side note though I tried to start a ‘test’ session of multicast, the same name I had used pre-update, and it did the same thing(started and instant ended). But if I picked a new name that I hadn’t used before, it appeared to start and wait for connections normally.
Philip
@walkerit To expound a bit on @Quazz 's comment, I ran into this yesterday myself. There’s two different config locations that I found needed to be updated. One of them I’m led to believe will only come into play if you update the server, but the other (export? https://wiki.fogproject.org/wiki/index.php?title=Change_NFS_location) is what was causing my permission issues.
Hope that clears it up when you do change your storage location.
Philip
@tom-elliott Here to report that the working branch appears to have fixed the issue. Currently have two clients imaging off of a multicast.
As a continuation of this: Are there any known things you’ve broken in the working path that means I shouldn’t just update my production server with it and have the added ease of functional Multicast?(Yes, I understand its the working path and no promises can be made, just asking if there’s any known issues.
Philip
Sounds good. I’ll get working on that and let you know what I find.
Philip