Posts made by Malos

Hello, I’ve got a Windows 10 golden image for UEFI all configured and up and running. It works magically!

But, I’m running into an issue where after setting the boot order to PXE first, I’ll deploy my shiny image and when it runs through configuring the machine Windows will revert the boot order to put Windows Boot Manager first. I don’t want that at all since it means the box won’t PXE boot on it’s own anymore. Any idea how to stop windows from screwing around with boot order?

I’ve maybe figured that Fast Startup “feature” is the culprit responsible, and am currently re-capturing my image with a sysprep stage 4 specialize command of “powercfg /H off” to disable hibernate (and disable Fast Startup by association), so I’ll find out in a moment whether this idea worked or not, but I’m not very hopeful as the OS reboots a few times during device installation portion of OOBE and I’m thinking the specialize steps may not take effect before these reboots. Guess I’ll see in a bit…

Is Windows 10 One touch imaging for UEFI possible now, given the OS’s propensity to make these arbitrary boot order changes? It worked great under 7, and I’m thinking 10 under legacy/mbr works fine as well, but MBR’s not an option for us anymore due to Bitlocker/TPM 2.0

Is there a way to reduce how often the fog node’s are checking back into the master server’s mysql?

Yeah, I figured client check-ins would take more bandwidth as well but nope! The yellow in this graph is all 3306 node to master traffic. All of the sites do this actually, it’s just particularly noticable in this location due to the current sub-par DSL connection (replacing it is a WIP).

And, I didn’t include it previously but will now, they’re all running Fog 1.4.4 on Ubuntu 16.04. No replication is going on at present

Hello! A few of my sites have a crummier than normal WAN connection, and the FOG Node’s connection back to the master server on port 3306 is using up a not-small percentage of the overall traffic utilization.

In my environment, the clients report back into the master server, and the local storage nodes are serving up tftp boot files and also keeping replicated copies of images so they’re not imaging over the wire.

What’s this mysql connection effectively used for?

Is there any way to reduce it, or eliminate it all together?

@Developers, how about it? Does fog replication service resume or restart transfers being made from the master storage node to non-master nodes?

@Tom-Elliott After upgrading to latest trunk (SVN 4398), instead of save_group, the page now refreshes over to deletemulti, the button typo remains, and the task remains.

http://fogserver/fog/management/?node=task&sub=deletemulti

@Tom-Elliott Ah, ok very nice.

./install.sh -?

indicates that I can use the following to install fog trunk with a correct DocRoot on Ubuntu 14.04.3

./install.sh -D /var/www/html/

Thanks!

@Tom-Elliott Will some kind of change be made within the installer to reflect a new document root for fog? I don’t know when apache2 changed their doc root, or if that’s an ubuntu thing

@Tom-Elliott Yep, it’s there now for me as well.

@ch3i I meant image replication from master node to storage nodes, I’m sorry. Edited OP for clarification

Does FOG resume an interrupted (either server, lan/wan outage, etc) image replication from master host to storage node in the way that an rsync --append-verify job would, or does it start over with whatever file it finds as not matching, or something else?

@Tom-Elliott
As you suggested, changing in opt/fog/.fogsettings

docroot="/var/www/";

to

docroot="/var/www/html/";

and then r erunning the installer does create /var/www/html/fog, and creates a link to said folder at /var/www/fog

After re-running the installer, clients are able to connect no problem.

@Tom-Elliott

Location only. Interesting to note that trying to install the location plugin under 4394 clean install doesn’t work.

You can enable the plugins section, you can click on Location to activate it for installation, it disappears permenantly from the Activate Plugins list, but the Install Plugins screen is empty, as if you’ve not activated location at all.

@Tom-Elliott Running a

grep -n -e "DocumentRoot"  /etc/apache2/sites-available/*

results in

/etc/apache2/sites-available/000-default.conf:12:       DocumentRoot /var/www/html
/etc/apache2/sites-available/001-fog.conf:4:    DocumentRoot /var/www/
/etc/apache2/sites-available/001-fog.conf:12:    DocumentRoot /var/www/
/etc/apache2/sites-available/default-ssl.conf:5:                DocumentRoot /var/www/html

/opt/fog/.fogsettings has

docroot="/var/www/";

@Wayne-Workman I’m wondering if this issue isn’t linked with one of my other open bug reports at https://forums.fogproject.org/topic/6174/svn-4380-cloud-5419-on-ubuntu-14-04-3-fog-client-404-not-found

/var/www/html/fog/%whatever% isn’t valid on my ubuntu install, the link to /var/www/fog doesn’t get made, seemingly. If the installer is trying to drop files to an invalid path, boom missing msi.

@Psycholiquid Reinstalled and upped to latest SVN 4394. Issue persists, unfortunately.

Comparing two identical installs side by side, the notes for 4394 “Maybe fix the task deletion so it doesn’t try adding the Save group elements on a non-host node page.” seem to make a lot of sense.

On the problematic box the button is “Delete all selected s?”, which certainly lines up with “Delete all selected groups?” of the groups page, rather than “Cancel selected tasks?” of the working instance.

Sounds like Tom is hard at work!

@Psycholiquid Maybe! That’s been my experience as well, my existing install that was a slightly older SVN had it no issue, but this fresh install it’s missing.

@Tom-Elliott This is reproducible, here’s the steps that I have recorded in my wiki;

• Install Ubuntu Server 14.04.3 LTS from iso
• sudo passwd root
• set your static IP info
• su - up to root, and run
• apt-get update && apt-get -y dist-upgrade && shutdown -r now
• once it’s back up:
• apt-get install -y subversion && svn co https://svn.code.sf.net/p/freeghost/code/trunk@4393 /root/fog_trunk && cd ~/fog_trunk/bin/ && ./installfog.sh

Run through the install as usual, and perform a
ls /var/www/html
Result: no fog folder/link. Creating it manually does resolve client connectivity, but a re-running of installfog.sh wipes out the manual link.

@Psycholiquid Interesting. I spun up a new server myself and I too can delete tasks no problem. I wonder what’s up with my existing week old but matching SVN install.

On freshly installed and upgraded Ubuntu 14.04.3, installing SVN 4393,
The following files are present in /var/www/fog/client
FOGCrypt.zip
FogPrep.zip
FogService.zip (the legacy client)

Missing:
FOGService.msi (the new client)

Noticed it when I was reinstalling a box to test out something else.