Topics created by anisgh

@anisgh Don’t think there is any way you can automate this using FOG as it is right now.

It might be possible to use pre-deployment scripting to setup LUKS encryption on the device and then deploy the image to the encrypted LUKS containers on disk. But I am sure there is a lot you need to fiddle with to get this going. Give it a try and keep us posted.

Post deployment encryption is not that much an option I find. While this can be done on Windows (VeraCrypt or Bitlocker) I have not found a good way to do this on an already installed Linux system yet.

@george1421 said in Post install script not running:

You need to use the FOG Postinstall script to drop the files or leave settings behind so that your first run program in the target OS will find the values and use them. Just like if your target OS is windows, FOS Linux can not change the target OS internal settings.

That is surely one way of doing it but there is another way. You could mount the newly imaged drive and chroot into it to to those things on the destination Linux OS.

@anisgh Ok so lets follow that sysprep concept. The easiest solution is to not create the user when you build the golden image. I don’t use ubuntu so I don’t know if that’s an option. But lets say its not. So lets create a script called sysprep, and you would run that on your ubuntu golden image. Within that sysprep script you could execute a series of commands and then call a system shutdown (just like sysprep does). Now you need to decide what this sysprep script will do before shutting down ubuntu.

You might have it reset the hostname back to some generic name, and then remove the default added user with something like deluser --remove-home username The last thing you will need to setup is a first run script (akin to windows setupcomplete.cmd batch file) https://askubuntu.com/questions/156771/run-a-script-only-at-the-very-first-boot This will let you do some customization on first boot of the computer (like creating new use and such). You would do this with the unattend.xml file or the setupcomplete.cmd in windows anyway.

Now that you have the ubuntu image cleaned up shutdown the computer.

To extend this a bit more, in your post install script that renames the computer. You could access FOG fields like other1, other2, and (assigned user, don’t remember the actual field name). You use one of those fields to hold the name of the user account to create on the computer. You will write that user name to a text file that your first run script will find and create the user. When you create the user account with a generic password (like Password-1) use this to expire the account so they would be forced to reset the password on first login passwd --expire <username>

The point is to use FOG to leave bread crumbs in the target system based on deployment time values, then use a first run script in the target OS to pickup the crumbs and do something with them. This is the same for windows as well as linux. While FOS is linux, its not the target system linux so it can’t do much more than leave bread crumbs behind for the target OS to find.

@anisgh said in customizing Ubuntu deployed images:

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?

While the fog-client is designed to run on Linux and also rename computers I am not sure this is working at the moment. Very few people seem to use the fog-client software on Linux and there are not enough people to work on the code either. Here you see rumors on it not working but I am not sure this is true for all distros: https://forums.fogproject.org/topic/15903/linux-fog-client-hostname-changer-not-working

The other way is using so called a post download script:
https://forums.fogproject.org/topic/4510/scripts-customization-of-ubuntu-fog-service-for-ubuntu
https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

Is there a way to automatically join the deployed machine to an AD?

This is discussed here using fog-client snapins: https://forums.fogproject.org/topic/9638/join-active-directory-using-fog-on-ubuntu-linux (pretty old topic, no idea if this is of much help)

@anisgh Find some more information here: https://forums.fogproject.org/topic/16057/customizing-ubuntu-deployed-images

@anisgh Which version of Debian did you try to install FOG on? I am really wondering what’s going on because the error we see in the output posted doesn’t make sense to me. The package named mariadb-client is available in all current versios of Debian: https://packages.debian.org/search?keywords=mariadb-client&searchon=names&suite=stable&section=all (for stretch, buster, bullseye, even bookworm and sid!)

Please try installing it manually via apt-get install mariadb-client and see what error you get.

So either you try to install on Debian 11 - then follow what George posted. Or you are using a really old version of Debian and need to update to a later one first.