Thanks, everyone for the help. Our new laptops arrived today and I plan on a rollout after the holiday break (January 6th). I hope I gave myself enough time.

Mark

Doh - I actually didn’t realize the “Multiple Partition Image - Single Disk” could do a single partition! I just tried a capture using this and it seems to work fine - haven’t had a chance for a deploy yet. I guess since I foresee only rarely changing partition sizes, this option would work fine.

@Mark-krikunov said in Lock out Setting:

computers it self on a timer, but this can be removed by students

Not via a domain GPO. If the setting is configured by GPO is a rule and can’t be changed.

As for the linux side there isn’t a gpo equivalent so each instant would have to be configured.

It should. OS isn’t really that relevant. Its the component software: webserver software, php, and mysql that you need to make sure is compatible.

@isaiah658 Just wait until you try out the new ZSTD compression. 🙂

@Sebastian-Roth said in Updating FOG and retaining settings:

@willian Upgrade will rewrite the DHCP config of your FOG server. So make a backup copy if you have modified it.

I could even clone the server for testing but later I will see how I do.

As well make sure you read und understand this before you upgrade: https://forums.fogproject.org/topic/13488/fog-1-5-7-officially-released

Is there any important information in this topic about this issue? I read everything but I saw nothing related.

Thanks.

@george1421 thanks for pointing me to the conf file! Changing the default option to the 2nd choice did the trick and now it boots straight to OS. I guess it got hung on the 1st choice.

Here is the line I changed from:
default_selection 1
to:
default_selection grubx64
in /var/www/html/fog/service/ipxe/refind.conf

My next article will be on load-balancing FOG’s web frontend and database backend… I’ve just not wrote it yet… Don’t wait on me, it might be a while.

Why would you want to run both clonezilla and FOG? FOG uses partclone which is the same program clonezilla uses. That said, it’s one thing if you wanted to use a CloneZilla Image on a host. We do have support for that, by simple creating the Image definition and setting the Image Manager to Uncompressed. FOG, however, has many more options readily available and configurable via the GUI. Again, this is not to say you cannot use Clonezilla images with FOG. However, FOG manages hosts, inventory, images, and much more through a simple web gui. Running clonezilla is possible, but still means you have the manual tasks to complete.

I guess we need to understand the why of this more so we can try to help you out more.

@george1421

I used to see the issues with warm boots on older versions. That seems to not be the case in the latest version.

@astrugatch The link is in my signature. Testing is suspended by request of @Sebastian-Roth until the 20th of this month. The last test results can be seen on the site.

Thank you to all for your answers.

I think, i will use the safe approach : i will clone my existing Golden Win 7 image in Virtual Box.
With the cloned image, i will install Ubuntu with Grub and upload the new “Golden Dualboot Win7/Ubuntu image”.

In my ref image, i do … nothing 'cause all conf", softs and scripts are run at the post-deployement …

I will try this approach and “i will be back” with the results.

Thank you for “the right way” 😉

[Mod Note] duplicate post from here: https://forums.fogproject.org/topic/13807/error-update-database-after-capture-image

I guess I would have to ask you a question of what are you trying to accomplish by not having FOS Linux reboot after its done with imaging? What is your goal here?

I’m seeing the not registered static text here:
/var/www/html/fog/lib/hooks/bootitem.hook.php
/var/www/html/fog/lib/fog/bootmenu.class.php

I would look in the bootitem.hook.php first.

as well as in the language files in
/var/www/html/fog/management/languages/

Your dhcp server needs to send the boot file name ipxe.efi for uefi based systems and undionly.kpxe for bios based systems.

If this is just a one off system you can manage dhcp option 67 by hand. If you want it to automatically adjust based on the target computer there are instructions here as long as your dhcp server is windows 2012 or newer or linux based: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

As we have had so many requests about this topic I have tried to sort this out and properly fix it. Turned out to be quite hard but I hope I got it now without causing any other harm.

@Tom-Elliott Can you please take a look at this commit and let me know if something jumps at you that could cause us trouble. I mean I have tested things a bit but as I had to change code right in the FOGController class I am unsure about side effects this might cause. What do you think?

@TigerTran What Linux OS do you have? My guess is you have Ubuntu, right?

Did you read what is mentioned in the official release message? https://forums.fogproject.org/topic/13488/fog-1-5-7-officially-released

Please make sure you say NO if asked about removing and re-installing PHP and Apache when upgrading to 1.5.7 on Ubuntu!!! There is an issue within the installer trying to switch to MariaDB that causes a problem on Ubuntu installs otherwise. If you have such an issue see here: https://forums.fogproject.org/post/126476 and https://forums.fogproject.org/topic/13447/lost-database

@ITCC Let us know what exactly you are trying to achieve. The AD settings are meant to be used for domain join and from what you write I get the impression that you want to misuse “Name Change/AD Join Forced reboot” to forcefully log off people from their machines. Maybe this is just a misunderstanding on my side but you keep calling it “force logout” and therefore I get the impression.

There are other ways of doing this. The web is full of it:

https://answers.microsoft.com/en-us/windows/forum/windows_7-security/how-to-force-logoff-from-command-line/8e7507e0-12c8-4ac7-8d5e-a1917e4af997 (using shutdown /l /f command) https://social.technet.microsoft.com/Forums/en-US/1c525aa7-5b09-45fb-ad47-56c41f1df2bc/force-user-logoff?forum=win10itprogeneral (using GPOs)

If you can’t make it work this way you need to explain to us what exactly you want to do. We won’t change this otherwise!

Just as a side node: I have not really looked into what needs to be changed but I can imagine this being a change in the fog-client code as well. There are many other things that needs fixing before we’d get to change that in fog-client.

You are more than welcome to dig through the code yourself and implement the change. I am not saying it cannot be done.

@Wayne-Workman Sorry this has been without attention for a long time! Not only this topic but all the others:

https://forums.fogproject.org/topic/11868/how-to-change-colors-on-bandwidth-graph
https://forums.fogproject.org/topic/11999/bandwidth-line-colours
https://forums.fogproject.org/topic/6912/can-i-change-the-colors-of-the-tx-rx-graph

I played with the things mentioned in the other topics and figured that it seems to pick colors just by itself if we don’t force it to use our colors. When I remove the color scheme as described I get the following picture:

fog-bandwidth.jpg

Please vote if you find this appropriate. Sure the more nodes you have the less obvious distinct colors there are. But from it’s still better than using a successive shade of whatever color you start from.

I’ve tested this in three different browsers on a Linux machine. I would imagine this working nicely on Windows and Mac OS browsers as well. What do you think @Tom-Elliott?