It’s awesome that we can put notes on a particular host via the Host Description field.
Could data in this field (if present) be included on the Image Task Completed emails underneath Mac Address?
This would be useful for such notes as “Please install XYZ software manually after imaging, licensing info is 123”, or other host specific details.
Ubuntu 14.04.3
SVN 4380 Cloud 5419
On a fresh install, an upgrade to newer trunk version, or a reinstall of the existing fog_trunk contents, FOG clients will begin to throw 404 errors for everything;
11/18/2015 12:50 PM Middleware::Communication URL: http://fog-server/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=90:B1:1C:7D:6B:FF||00:00:00:00:00:00:00:E0&newService=1
11/18/2015 12:50 PM Middleware::Communication ERROR: Could not contact FOG server
11/18/2015 12:50 PM Middleware::Communication ERROR: The remote server returned an error: (404) Not Found.
Going off of constant refreshing the folder view while running a couple installs, I’m guessing the symbolic link (which I had to manually create in the first place) gets wiped out right around this area here:
* Backing up old data.........................................OK
* Copying back old web folder as is...........................OK
* Copying new files to web folder.............................OK
Here’s the fix, just needs to be run once install.sh has finished completely:
Make a symbolic link at /var/www/html for fog, and point it at /var/www/fog
ln -s /var/www/fog /var/www/html/fog
Ta-da, no more 404s!
@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.
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.
@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