@Quazz
Thank you for your answer, I did not know that deployed partitions were prorated to captured partitions.
It’s clear for me now

@lebrun78 said in Need advice for network configuration:

Which architecture do you recommend?

That depends on the network components you have. What kind of router do you have? If possible I’d put the 500 educational hosts and the FOG server on the same switch/branch of your network. Don’t run it through your backbone if you can avoid it. Leaning towards setup one (above picture).

On the other hand I am not sure I understand why you’d make things more complicated by running the FOG server dual homed. Why not just have the FOG server in the educational hosts network segment and allow HTTP/HTTPS web access from the admin PCs to the FOG server across your router.

@Tom-Elliott Thank you! I can confirm this fixed the issue. Snap-ins are deploying successfully and the tasks are clearing.

Since last week, I followed this topic

https://forums.fogproject.org/topic/13887/blank-install-page/36

Installed is now completed

Thank you for your help

I have reboot the server yesterday,
Now updating database is very fast.
And I receive mails for task results…

I think the problem appeared when I set “FOG_EMAIL_ACTION”.

Thanks for your answers

Thank you
I try it now

We have made a special setting in deploy.image menu for the computers of the room. Then login and password are not requested to access to deploy menu.

#login params param mac0 ${net0/mac} param arch ${arch} param hostname ${hostname} goto host_${hostname} || goto autres :host_bug :host_win10-3 :host_i207m01 :host_i207m02 :host_i207m03 :host_i207m04 :host_i207m05 :host_i207m06 :host_i207m07 :host_i207m08 :host_i207m09 :host_i207m10 set username userlogin set password userpassword params param username userlogin param password userpassword param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme goto fin :autres login params param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fin

Here are the log when I try to list scheluded tasks
in /var/log/httpd/ssl_error_log

[Mon Jun 04 08:24:48 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:27:09 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:36:00 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:47:45 2018] [error] [client 192.168.1.10] PHP Warning: trim() expects parameter 1 to be string, array given in /var/www/html/fog/lib/fog/fogbase.class.php on line 1316, referer: https://fogus.univ-rennes1.fr/fog/management/?node=task&sub=active [Mon Jun 04 14:10:47 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 54, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 14:11:18 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 14:29:39 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 15:18:51 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active

Arnaud

@george1421

Yes, sorry to have disturbed you

This morning, I have the problem on several machines which have get 1803 update…
I have changed the dhcp configuration for this machine to point to my testing fog server. (1.5.2)
On this server, I have applied Quazz solution to set grub in place of sanboot and now my Dell machines on 1803 have started passing by PXE…

Now I have to set it to my production fog server…

Thanks for your help

@george1421
Ok great

@adrien17 I sent you a chat message earlier with some further debugging information. You should be able to see it in the little chat button next to your profile picture on the top navbar.

@lebrun78 said in Manage scheduled task:

May be examples are lacking in the documentation ?

Help us write examples? Post them here.

@wayne-workman said in Changing image to a group, I get " There is a host in a tasking ":

Commands

I ran your command, it works, thanks

Next time, I will try after each command line

@lebrun78 Thanks for letting us know. Good you got this solved! Marked as solved.

@Tom-Elliott
Trying to found the source of the problem, I’ve just created a new image, capture it from win10-3.

After reboot, I have always the same error.
In log I have the no error at capture
alt text

Where should I have a look ?

thank you

@Wayne-Workman The export will not be un-encrypted, for now, but the import CAN take unencrypted form.

@lebrun78 OK I just had a chat with the developers over this.

zstd is used for decompression of both legacy and new images (as of FOG 1.3.5). You have the option of using industry standard gzip for image compression or the new zstd for image compression. If the industry standard gzip compression is used, you “could use” any zip program to extract the image from the FOG archive (not very common and only done for a very specific reason).

The newer zstd format can achieve better data throughput (target hard drive compression and decompression) than by using the gzip format. They (the developers) switched to zstd based on a feature request to make FOG imaging even faster (the FOG Project is all about going faster) and with a tighter packed image on the FOG server (smaller disk space used on the FOG server’s hard drive).

The real decision not really a decision. Use zstd and live with the faster deployment speeds, or use gzip and deploy as the same zippy speeds the previous versions of FOG 1.3.x supported.

Really its not a decision use zstd and worry about other things in the world.

@Tom-Elliott
yes