@Lenain
Solved now, I will open a new post for WOL problem. Thanks 😉

Check in time cannot be changed. The checking time out can be but this is not what you’re looking for.

It is highly doubtful checkins are causing issues as they are not spamming the server very often (one check every 5 seconds per machine.) If it were a server spamming issue it would most likely come from progress reporting as that checks in every 3 seconds. However the slowdown on images is the main issue as quazz and Wayne pointed out.

While I suppose removing intermediary requests could help lessen the work stop/start, this would be primarily micro-optimizing as all the checkin does is update state, if needed, and decide if it is safe to start doing the tasking.

@THEMCV rc10 is pushed, albeit a couple days later than I wanted to.

@gerald.stachl

I solved this question, i hope it may help someone.

FOG 1.3-RC1 on CentOS 7.0. Unicast deploy working. Even multicast was working.

After a system reboot, MulticastManager didn’t start again:

Sep 4 06:01:28 clonacion FOGMulticastManager: PHP Fatal error: Call to undefined method MulticastManager::getBanner() in /opt/fog/service/FOGMulticastManager/FOGMulticastManager on line 13

It didn’t matter if I added a multicast task: udp-sender process didn’t start because service didn’t start before (you’ll see only one FOGMulticastManager in process list --ps–, it’s the parent which forks periodically one child process (but this one will die at GetBanned method invocation).

If I commented GetBanner() invocation out at /opt/fog/service/FOGMulticastManager/FOGMulticastManager, then it failed at next method call to object MulticastManager.

I found TWO “MulticastManager” class, one of them extends FOGBase (at lib/fog directory) and the other one extends FOGService (at lib/service directory). Only the last one has defined methods like GetBanner(), etc. By any reason, it uses in some cases wrongly the first one (even when it used the second one after installation because it worked before).

So, I renamed MulticastManager class that extends FOGService to MulticastManagerService, and I changed the code to use that. After that, service FOGMulticastService starts with no problems, it works. I did the same thing with rest of services: FOGScheduler,…

I resume (for service MulticastManager: repeat it with other services in /opt/fog/services directory):

Edit /opt/fog/service/FOGMulticastManager/FogMulticastManager file: modify line 8 from $ServiceClass = FOGCore::getClass(‘MulticastManage’); to $ServiceClass = FOGCore::getClass(‘MulticastManagerService’);

Rename file /var/www/html/fog/lib/service/multicastmanager.class.php to /var/www/html/fog/lib/service/multicastmanagerservice.class.php (/var/www/html/fog is the path to fog web service)

Edit /var/www/html/fog/lib/service/multicastmanagerservice.class.php and modify the name of this class (line 2) from “class MulticastManager extends FOGService” to “class MulticastManagerService extends FOGService”

In the video @ 9 seconds, did you reboot the machine? Why did it appear to reboot?

Also - FOG does not use ISO files for imaging. You must first capture an image using FOG before you can deploy it.
0_1473376357244_iso.png

@Wayne-Workman @Tom-Elliott 127.0.0.1 worked! I did not test localhost with a reinstall since that worked.

My load just went up a lot, but I’ll see if it drops after a few minutes.

Thanks for the help!!!

@george1421
Ok thanks.
My problem is solved now, i’v updated Fog.

@Joe-Gill Honestly this is usually the case with the “love / hate” relationship that so many people on the internet have with FOG. I’m not saying you’re not good at this, you are and are a valued community member. But people will often simply do something wrong and blame fog, or they just don’t understand how things function and when it doesn’t work, they blame fog. I have the feeling that these people have these sorts of issues with non-fog things too.

I do my best to keep the wiki updated, and clear. It’s kind of this huge monster with all these old pages that I have no idea what to do with besides to just make notes about them being old or what version they apply to. On one hand, I’d like to just wipe the slate clean, but on the other hand the older pages have value and do help in some capacity sometimes.

But, the more people we have here on the forums that will help, the better. The more people that are willing to write good documentation, the better. The more people willing to make video tutorials, the better. We just need more willing people - to really push out tutorials and documentation and help. Because simple things like what you found you did today - that ruins some people’s attitudes towards fog, and that’s a shame. And if everyone that had issues asked here, we may not have enough time to answer them all. This summer was especially difficult on the forums, with upwards of 70 new posts daily. The forums is getting very close to one-million views a month… And that’s simply because FOG is growing in popularity because it’s a superior project and open-source. It’s time it also grew in community volunteers as well.

@kleanthis This might be it: https://forums.fogproject.org/topic/2928/image-management-blank-page

It’s not required, it’s optional.

You will find the printer helper program that Joe made quite useful.
Basically, manually install the printer, then fire up the helper program, it will give you the values to use in the FOG web UI.

If you have issues getting the printer to deploy, you can plug these values into the helper’s Add Printer section and if somethings wrong it’ll give you an error about it. Download the latest version of it from here:
https://github.com/FOGProject/fog-client/releases

I want to make a video all about it, but I don’t have a network printer at home. 😞
Anyone want to donate an old network printer?

@Gary-Kulovics said in Fog Client won't join Domain:

9560

Invalid character in name.

@Wayne-Workman
I feel dumb now, should have tried that yesterday. Simply deleting those folders/doing another git clone and everything is working fine now. Thanks a lot for the help!

@Sebastian-Roth said in USB NIC PXE Boot?:

The PC/notebook/tablet/whatever device you are trying to PXE boot with this USB NIC needs to have specific drivers for this USB NIC chip in the BIOS!!

I suppose now we must record the device that the adapter worked on, too. I didn’t think of this but it makes sense.

#wiki

This is already known about and has already been fixed.

I suppose this is dependent upon how your clients, vs your server, communicate to the internet.

There could be the issue I created, though I’m starting to think your fogserver is not necessarily supposed to be going through the proxy itself?

@Joe-Schmitt Done. Also put links from the FOG Client article and an older article to it as well.
https://wiki.fogproject.org/wiki/index.php?title=Power_Management

I know this thread is quite old, but I wanted to include another possible cause because Google searches seem to bring you back to this thread.

I was experiencing the same issue with my Windows 7 Fog clients, and resetting the encryption data did nothing. It turned out to be the time was quite off on the client, so it was never able to authenticate with the Fog server. Once the time was corrected, the client connected and everything worked fine (hostname, join, etc.).

Just in case someone else runs into this issue, hopefully this can save you some time.

Well… This is embarrassing.

Good news I fixed it, i get into the PXE menu now! 😄

I do have a different question now, when I click boot from hard disk in the pxe menu it doesn’t load the operating system, any ideas for that?

For the issue relating to TFTP this is what happened:

I set up a packet scan on both the DHCP and PXE server and after analyzing the packets i noticed there were two different packets sending a different option 66 and option 67. One was right pointing to the FOG server and Undionly.kpxe the other however pointed to the DHCP server. Apparently an old image deployment software was still working even though the options weren’t configure anymore. I removed these and everything worked great!

@Wayne-Workman Thanks so much for your reply Wayne. I really appeciate the info. Also, we just went ahead just now and updated it to 1.3.0.

@Quazz is correct.