@george1421 said in Possible to secure /var/www/* ipxe boot contents?:

apache stop file browsing

Yes I will place this here to save a search for anyone who stumbles upon this post.
https://www.vultr.com/docs/how-to-disable-directory-browsing-on-apache/

@sebastian-roth Where do I “use –recreate-CA and –recreate-keys keys” switches? Like this?
.\installfog.sh --recreate-CA --recreate-keys?

@george1421 the good thing is, you only need to do the reg hack and app removal on the GI, once you sysprep the GI and capture it, when you deploy it, you have to do nothing and you can deploy to multiple laptops, vms etc

the pic i shows you shows a laptop with TPM enabled, using the deployed image
20220414_181954.jpg

@jack-mills Thank you. This is the solution.

In short, during the installation process, the installer will ask for server address with the default to ‘fogserver’. You will need to replace ‘fogserver’ with the IP address of your FOG server (i.e. the http://<FOG_ADDRESS>/fog/management).

If you’ve already installed FOG client, in order to change the ‘fogserver’ variable, you need to remove then reinstall FOG to get the window prompt asking for the server address.

I’m not sure how I missed that in my notes. Thanks again.

That is all I need to know. Thank you all

@Sebastian-Roth actually I didn’t touch anything anymore. It suddenly started to work. Very strange.

@sebastian-roth @george1421 Solved! Thank you for your time!
There is no firewall between the host and storage node. There is a firewall between the storage node and the master but is correctly configured.

The problem was that the storage node is registered at the master with his dns name and this was somehow deleted from the domain.

I have restored the dns record for the storage node and now all is functions correctly except “Storage Node Disk Usage” from the dashboard (it shows nothing), but this is not a big problem.

@cdutko The simplest way to do it is via this wiki page.

https://docs.fogproject.org/en/latest/installation/install_fog_server.html

Using the git method is real easy. Performing upgrades are even easier. But lets get things setup on the 20.04 server first then you can follow this wiki page: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

The migration will leave the existing fog server in place but migrate (copy) the data over.

@george1421 said in FOG Capturing Entire SSD:

manage-bde -status 😄

After using the command you suggested, it is working and capturing as NTFS. The new image size is 40GB.

Thanks

@WT_101 Hook events are called by the FOG code. Don’t think this is what can help you with activating plugins. Did you look into directly updating the database tables as mentioned in your other topic yet?

@george1421 Thanks I will try this on Monday and get back to you.

FOG currently does not support imaging over wifi. You need to use a cabled ethernet solution.

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