Topics created by luiztpd

@luiztpd The rebuilding ipxe tutorial is here: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe

Make sure you have the latest FOS Linux kernel -> Web UI->Fog Configuration-> Kernel update. You will want 5.10.x series of kernels for both x64 and x32 systems.

Lastly you can update to the dev branch (suggested if you need to deploy Win10 20H2 or later versions of windows) to get the fixes for those OS’) all you need to do is change into the git repository you downloaded then do the following:

git pull git checkout dev-branch git pull cd bin ./installfog.sh

That will update your fog install to the pre-release version of 1.5.10. That release is stable and will most likely be what 1.5.10 will be released as.

Now when 1.5.10 is released you will need to switch back to the master branch this way.

git pull git checkout master git pull cd bin ./installfog.sh

These issues are typically related to how the structure is on the disk and where the data is placed. Its not really a fog issue, but an issue how the reference image placed on the golden image disk. This is important especially if your golden image is constantly recycled as you apply round 2 (through N) updates and applications. The ideal method is to rebuild your golden image every time as you upgrade your golden image.

So how to fix…

Make sure your 😄 drive is the last partition on the disk. This may require you to move or delete the recovery partition. The recovery partition is a non-resizable and sometimes non-movable partition. I also question the value of a recovery partition if you have an imaging solution in place. It is much quicker to just reimage the computer than to try to recover a failed disk. If you have done many updates to your golden image (especially over time) flush out all of your temp files and defragment the hard drive. This will (should) push all of the files towards the beginning of the disk. The idea/goal here would be to move all of the disk data below the size of the disk you will be deploying to. That makes FOG’s disk compression work a bit easier. If you are developing a golden image create that golden image on the smallest disk possible. Its is easier to expand the disk than it is to shrink it. So if you developed your golden image on a 120GB SSD, that image would deploy cleanly to 120GB disks and larger, for example.

@luiztpd said in WOl Broadcast not work:

my server fog is with network ip address 192.168.x.x / 24;
the workstations are in a vlan 172.x.x.x / 24 and other 172.x.x.x / 21!

That is probably part of your issue. Unless your vlan router support directed broadcasts the WOL messages are probably not traversing your vlan router. As a test install a workstation on the 192.168.x.x network and then test.

Then I would suggest you test WOL with a third party application (install on the 192.168.x.x subnet) and see if it can wake up a workstation on the 172.x.x.x subnet. Lets try to understand where the problem isn’t before we focus on a solution (maybe).

@george1421 Thank you!
As a precaution I have created all my images outside A.D

SOLVED

problem solved!
In fog settings >> Ad default OR I have filled in the fields in small as an example:
or = xxxx, dc = yyy, dc = zzz
Thank you all

In terms of single disk productivity is the best option because the clone of this image was on average 30 minutes in multicast mode, when I used multiple partition the time to clone the image was in 2 hours and 30 minutes.

@luiztpd which certificate did you download

@Tom-Elliott said in Debbuger.exe:

when running the isntaller, are you setting the IP address portion to your actual FOG Server’s IP Address?

yes, I am setting the ip address.