I don’t know if Tom will remove that stuff or not in the official release…

IMHO, it’s better that those are displayed, like I said before, if something doesn’t work, you can see what was last done.

@Woeler

Also,

You will get FAR better performance if you install a Linux SERVER distro into your banana pie, and use FOG Trunk instead of 1.2.0.

I recommend Fedora 22 Server and this method of getting FOG Trunk: https://wiki.fogproject.org/wiki/index.php/SVN

I sit on pages reading… you post fast, didn’t see your last post.

Glad you got it working.

I agree.

Thanks.

@cml I added it at the bottom under Win7

Yes. It´s the 1.2.0 😉 The option to change the TZ doens´t appear…

Can you try what I suggested here?

https://forums.fogproject.org/topic/2077/uni-cast-deployment-problem

It sounds A LOT like your problem, and I wonder if both of you are experiencing the same issue?

I think the re-size bug appeared again in more recent revisions, but it’s been fixed again also.

Can you upgrade and see if it goes away? Also, after upgrading and it’s still not fixed, try to re-upload the image and see if the new one is fixed?

Also - I’m not entirely sure if the developers have coded in support for Fedora 22 yet…

@Wayne-Workman said:

Inside the FOG DB, there are two multicast association tables. Can you delete all the rows in those tables, re-install FOG, and try again and see what happens?

TRUNCATE TABLE multicastSessions; TRUNCATE TABLE multicastSessionsAssoc; DELETE FROM tasks WHERE taskTypeId=8;

Via MySQL cli or phpmyadmin (easy to install)

I found where the problem was, in the /etc/php file I changed the values for a Fedora distrib :
UPLOAD_MAX_FILESIZE to 1900MB
POST_MAX_SIZE to 1900MB
but i didn’t change the value of Limit Memory (Ubuntu and VmWare) who was still at 128MB, change it to 1900MB and it works

@Matthieu-Jacquart the bzImage file has absolutely nothing to do with how snapins, printers, or the rest of the client’s operations work

Any of them so far. If I turn on the ‘Advanced menu login’ option from the dashboard, then the advanced menu is protected. But registration, memtest etc. are not.

Thanks,

Ollie

@jjacobs I’ll try replicating when I get to work.

Secure boot is turned off and legacy roms are enabled in the uefi.

I tried to mimic the settings changes that we do on our optiplex 3020’s.

I ran all the compatibility tests successfully. There was a partition error at first but I booted with gparted and took care of that.

Thanks for any help!

@Mikael said:

I was wondering if there is some replication of /var/www that is missing? How else does the menu changes get transfered to the storage host?

Also the error messages in picture in last post get me thinking that the file undionly.kpxe does not load? Because it says “/default.ipxe… OK” Should it not be undionly.kpxe there.
I have doublechecked my win 2012 DHCP for this and cannot see any fault there.

Great that you solved your issue.
Just wanted to talka little about the “default.ipxe” thing you brought up.

The boot file that the hosts use is what you specify (either in DHCP or dnsmasq). Those are always located in the /tftpboot directory. After that loads and does a few things, the hosts download default.ipxe and then give control to that and it takes over.

@Tom-Elliott said:

Linux is not windows. Change this hosts kernel device to either blank or the real device in linux.

How did you know?

@Tune389 said:

@ch3i okay thanks for the info. I try now to downgrade my fog version back to 1.2 …

That’s not supported nor advised…
To “downgrade” requires either restoring a previous snapshot (via a virtual machine) or rebuilding your FOG server from scratch…

You are exactly right. The fog server was not authenticated to the firewall. I’ll need to add a rule to automatically let it out.

Thanks!

Can you run the troubleshooting script found here: https://forums.fogproject.org/topic/4581/let-s-make-scripts

And see if it points anything out?

Run updates on the main server and nodes, make them all match.

[CODE]apt-get update
apt-get upgrade[/CODE]

Ensure FTP functions correctly on your nodes.

Also, it sounds like you’re using the location plugin ??
Ensure the locations are set properly. Reset them if you need.