@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.

@novice83 Ok good deal. I need to see the contents of a grub.conf file or grub.cfg.

I need to see the contents of isolinux.cfg from the loader directory.

One of those contain the key to booting it. It will list the kernel and the file system (virtual hard drive). Its probably that active_liveCD-readonly.sqsh (squash file system) file. But the config files will point to it.

There is still a risk because of the drm key (bootdisk.key I suspect) to be able to locate that in memory.

Hi Sebastian,
It’s OK, i do update (after to distupgrade to 10.9) and i doing upgrade fog directly to 1.5.9.
thank’you for your reply.

@dinesh_fog said in Storage node for third party vendor to reimage the system:

Fog 1.5.5 Ubuntu 16.04 servers

Both versions are really old. Just want to mention that we don’t support such old version. We’ll still answer questions about this but not fix issues.

@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.

@tenorio-leandro How do you shutdown the machine before capturing?

@tenorio-leandro said in could not verify verify mount:

I mounted a space nfs in my server /mnt/vol_fog/

So just to be clear the actual disk volume where the bits will be stored are on a different computer than your FOG server? If yes then that will not work. Its equivelent to in windows mounting a remote directory on your windows server as the W drive, then trying to share the W: drive out so that a 3rd computer can mount it. It doesn’t work that way.

Back to your FOG server, the nfs share needs to be a block device or NFS won’t share it. An iSCSI LUN is allowed since its a block level device. I have not personally done this, but it should work.

What is your end goal here?

What device is your fog server connected to?

@leocataorr Please post the contents of C:\fog.log from the newly imaged computer.

@jra correct

@tenorio-leandro See my post here: https://forums.fogproject.org/post/147487

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

@tenorio-leandro As far as I remember these two “profiles” are relicts from the days when FOG had a so called mobile user interface as well. This has been removed some years ago.

You can still try to add different access profiles to FOG using the access control plugin. Though understand this is not part of the core code and we are currently not able to support this in case it needs fixing. As well you need to know the mentioned plugin only hides certain menu items but is not properly restricting access.

@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)

@tenorio-leandro

Hi Leandro,
So what you mean is you have nothing on the “Group Base DN” field?
Ok, I just tested with that setting, but it failed the same. I also tested unticking the “Use Group Matching” both with an empty and filled “Group Base DN” but both failed anyway.

When I untick the “Use Group Matching” option I get an error saying “All methods of binding failed”.

I’m not sure what you meant by your last sentence? Is it like, all users are admins?

Oh I also tried putting the “Group Base DN” line into “Admin Group” but also gives me an error:

[16-Feb-2022 13:30:25 UTC] Plugin LDAP::_result(). Search Method: search; Filter: (&(|(name=cn=admins)(name=cn=groups)(name=cn=accounts)(name=dc=domain)(name=dc=io))(memberof=uid=admin_user,cn=users,cn=accounts,dc=domain,dc=io)); Result: 0 [16-Feb-2022 13:30:25 UTC] Plugin LDAP::_result(). Search Method: search; Filter: (&(|(name=))(memberof=uid=admin_user,cn=users,cn=accounts,dc=domain,dc=io)); Result: 0 [16-Feb-2022 13:30:25 UTC] Plugin LDAP::authLDAP() Access level is still 0 or false. No access is allowed!

Obrigado! 😉

Thank you very much.
I had already found and configured it. Sorry for the oversight

@sebastian-roth Thanks a lot, I followed you answer, thats right now. Thanks a lot.

@tenorio-leandro said in Problema https:

But I want change these certificate :
SSLCertificateFile /var/www/fog//management/other/ssl/srvpublic.crt
SSLCertificateKeyFile /opt/fog/snapins/ssl//.srvprivate.key
I want put my certificate in virtual host, but when the boot via pxe stop.
Because this certificate .pem I dont want change in this moment.

Well, if you swap out this certificate and key with your custom files then PXE boot won’t work anymore because iPXE does not know your CA (certificate authority). If you want to fix PXE booting you need to compile fresh iPXE binaries that have your custom CA included.

You might look over the wiki articles on the topic.
https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples
https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

@wayne-workman thanks for your info