Hi,
I’m using FOG to deploy an Ubuntu image to several machines, I’m looking for a way to encrypt the hard drive during the deployment (something like BitLocker on Windows).
Have anyone ever done this or has an idea, on how to implement something like this? even a post installation encryption of the hard drive would do, but an encryption during the deployment of the image would be awesome! Obviously, the most important thing, is that every hard drive has its own encryption password at the end …

Thanks

Hello,

So I’m using FOG to deploy an Ubuntu image, of course the image I’m deploying is not ‘syspreped’, that means it already has some specific settings (like users etc …) belonging to the machine I captured it from, this is because it is not possible to sysprep an Ubuntu image like in Windows, and also it is harder because FOG Client does not support Ubuntu.
So to solve this problem, I tried writing a post download script fog.dothings I saved it to /images/postdownloadscripts so it could run after the image is deployed to the new machine and try to get rid of some of these specific settings, the script looks like this:

#!/bin/bash

apt update
apt upgrade
apt install --force-yes whois traceroute ntpdate net-tools sysstat iptables ethtool 
ufw --force-yes disable
apt purge --force-yes ufw
timedatectl set-timezone Europe/Berlin
cd /etc/systemd/
rm -f timesyncd.conf
killall -u FogMaster && deluser --remove-home -f FogMaster

I’m trying to do some simple things like installing some packages, resetting the time zone, and deleting a user called FogMaster from the deployed image and its home directory.
The script is not working, I’m getting a bunch of command not founds errors when the post download script tries to run.
Here is how my fog.postdownload looks like:

#!/bin/bash
# This file serves as a starting point to call your custom postimaging scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post download scripts are
#. ${postdownpath}<SCRIPTNAME>
. ${postdownpath}/fog.dothings

@george1421 Let’s say when I installed Ubuntu, during the installation a user ‘X’ was created with a specific password. Now let’s say I captured that image with FOG and deployed it to another machine then that other machine would have a user ‘X’ on it with the same password, that’s the problem I’m facing. A perfect scenario would be that this image that I captured, when deployed on another machine would ask the user to create a new account, or at least to login with his account present on an active directory (adding the deployed Ubuntu image to the active directory is a problem I’m gonna deal with later)
I managed to handle the host name change with a post install script, that was easy to do.
As for the booting from an ISO image using FOG, I followed your tutorial here which was pretty clear, but sadly I’m stuck in this loop after trying to boot from the ISO

after a quick google search, it seems to me this is not possible anymore in the latest version of Ubuntu …

@george1421 Thanks for the reply!
I’m trying to capture an Ubuntu image and deploy it to other computers using FOG.
The problem I’m facing is when I install Ubuntu on a machine and then capture it, when deployed on other machines, it is 100% identical to the captured image, which is obviously not good, as every machine should have its own hostname, user names and password should not carry on from the captured image to the deployed image etc …
I understand this is easily done on Windows using the FOG client (does not work on Linux) or Sysprep (not available for Linux).
I just thought of a work-around: As an image I can use an raw ISO Ubuntu image (which I can customize with software, configs etc … using Cubic for example) and then deploy this image with PXE using FOG, this would solve 95% of my problems, only if I knew how to configure FOG in such a way to boot from ISO …

Hello,

Is there a way to make a capture-ready Ubuntu image? something like Sysprep for Windows, where you remove all the user-specific data from the image (like user accounts, passwords, etc …) to make a ‘golden’ universal image ready to be capture by FOG and then deployed on other computers.

Hi,
I’m using FOG to exclusively capture and deploy Ubuntu images (no Windows is involved), everything is working fine but I have 2 customization issues:

• The computer name (and user name), and passwords are always the same as the captured original image, is there a way (or workaround) to customize this, so that every machine gets at least its own name after deployment?

• Is there a way to automatically join the deployed machine to an AD? I know this is easily done with FOG in the case of a Windows installation, but is there a workaround to make this happen on Ubuntu?

For both issues, I thought about writing a BASH script and running it as a Snapin with the deployment, but how could I write such scripts? or does anyone have working scripts that do this?

Thank you

@george1421 I found this tutorial on the wiki page, this is what I want to do, but I don’t know if this is up to date and if it’s going to work on my pure Ubuntu capturing/deploying process.

@george1421 This seems pretty awesome! thank you.
One last question: Can I configure my Ubuntu golden image to automatically join an Active Directory when deployed on a new machine using FOG? in other words: can FOG automatically add my new hosts to the active directory? if yes, how to configure this?

@george1421 Thank you for your response!

What about software? let’s say I have LibreOffice installed on the Ubuntu I’m about to clone, will this be also imaged and deployed to my other clients? or should I reinstall all the software afterwards using snapins?

Hello,

I have a working FOG Server (latest version), I want to use it to capture and deploy Ubuntu images. Is there something I should reconfigure in my FOG? or in my Ubuntu installation that I’m going to capture? how do I set up my DHCP server for this? or should I go ahead normally like I’m working with Windows images?

Thank you