@andjjru i’m not entirely familar with that part of the code, but the md5sum task must be part of the image replicator service. i knew we did that for snapins, but i didn’t think we did it for images. anyway, perhaps you should try disabling IMAGEREPLICATORGLOBALENABLED until most of the clients have had a chance to check in and reset their keys

@g-sivakolunthu while possible, it’s not what fog is made for and you would have a bunch of manual steps. you might want to look at clonezilla for imaging with online images possibly in combination with gparted for partition resizing.

@compman while that’s true, in practice zstd at a higher compression level will return a faster overall process when the bottleneck is the network.

@sjensen it might be easier to follow these instructions to resize your LVM, you’ve already done part of this, but i’m sure you can figure out what needs to be done yet. https://blog.vbonhomme.fr/extend-a-lvm-partition-after-increasing-its-virtual-disk-on-virtualbox/

@george1421 another option is fog storage servers to open up more transmit slots at a time

@Scott-B said in Host Server OS Suggestions:
fog will work on any of them, really.
I recommend Debian or CentOS, whichever you’re most comfortable with.
I don’t recommend Arch for production. Only crazy people do that.

also, you can create a custom css for the interface and tell fog to use it
FOG Configuration > Web Server > FOG_THEME
you’ll want to keep a backup copy of it, in case it get’s removed during an upgrade.

@george1421 it sounds like the fog server would be exclusively for the lab, so the list of images available shouldn’t be an issue, and they could even set the default iPXE menu item to “deploy image”

@dwagner sounds like you need to recreate the /images/dev/postinitscripts directory, and it’s contents, a single file named “fog.postinit” with the contents

#!/bin/bash
## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post init scripts are
#. ${postinitpath}<SCRIPTNAME>

permissions 777
also, you’ll need to create an empty file named “.mntcheck” in /images/dev too, if you haven’t

@Sebastian-Roth i understand the reasoning for not updating it. i’m hoping to have a chance to help with testing by the end of the week.

@FeasiblePear the boot menus are ipxe based. updating those files may solve your problem. i recommend updating to the latest stable, or latest RC release for the lastest bug fixes, feature additions, and improvements. (the new zstd compression alone is probably worth the update for a lot of people)

log4j is a java library that is sometimes packaged with a program without it being installed on it’s own, so it doesn’t have to show up in the apt list to be present. that said, george is right that fog doesn’t use java, so you don’t have to worry about it there.

@george1421 or, he could temporarily attach a keyboard

i keep my ISO files in a separate folder from www/fog, and it works fine and my permissions are set to 644.
have you tried testing the location you put into the “advanced” menu in a browser? it should ask if you want to download the file.

that guide is from fog 0.27
it is no longer accurate
the places you will likely need to change the IP address are
in web interface

    Fog Configuration>FOG Settings>General Settings>FOG_WOL_HOST
    Fog Configuration>FOG Settings>TFTP Server>FOG_TFTP_HOST
    Fog Configuration>FOG Settings>Web Server>FOG_WEB_HOST
    Storage Management>DefaultMember> IP Address

in files

    /tftpboot/default.ipxe
    /opt/fog/.fogsettings

and, of course, your option 66 in your dhcp server settings

testing with the available pre-release versions of Windows 10 have at this time had no issue with compatibility with fog.

why not use a VM to create your master image, and use the laptop to remote into it? then you get the performance of your server with raid instead of the laptop for uploads?

[quote=“Tom Elliott, post: 38404, member: 7271”]To be legit some environments actually require what’s known as a department of defense white that’s what his menu system does the current Whitecastle it’s in fog is not right every bit with random characters[/quote]

this has got to look strange to anyone who doesn’t know you’re using voice to text right now, lol

translation:
To be legit some environments actually require what’s known as a Department of Defense wipe, that’s what this menu system does. the current wipe that’s in fog does not write every bit with random characters

you can find the password used for that account in the storage management page of your fog server’s web gui. “Management Password”
this is the account fog uses for ftp access to the images

in order to explore the files for recovery, all you’ll need to do is decompress the partition images and then mount them on a Linux computer. i’ve never done it myself because of how long it takes to decompress the files and how quickly i can just deploy the image and recover the files i need