@Gerrit-Anderson Thanks for this – fixed this issue for me! I used to get stuck on Init, but can get further now into the actual boot menu like you. I too have lost my custom background but really that’s a non-issue.

However, when I try to deploy an image, it asks me for a password (which is the FOG webUI username & password of course). I don’t recall this happening with my old TFTP boot files – I guess they must have had the password embedded in there somehow? Anyone know how I can fix this?

Copy and pasted for the Chocolatey wrapper ChocolatePy
Pretty much same same. Just Chocolatey won’t neccessarily give an error on the exit code on failure if a program is already installed.

https://github.com/mediocreatmybest/FOG-O-Matic/blob/main/FOG-Snapins/ChocolatePy.py

@mmw_canada lspci and lsusb is already built into the FOS Linux image. You should only need to patch fog.auto.reg if you need extra stuff. There is no need to unpack and repack init.xz unless you really want you. I have a tutorial on dynamically patching the init.xz file here: https://forums.fogproject.org/topic/14278/creating-custom-hostname-default-for-fog-man-reg

@gafferwiles When you use a NAS as a storage node there are a few things that happens.

FOS Linux (the OS that runs on the target computer) loads the image from the target computer onto the storage node (FOG or NAS) using NFS. The files are uploaded using NFS to /images/dev directory which is read write access. Now the user ID and password comes into play. The management user ID and password is used because the FOS Linux OS connects to the storage node using FTP to move the raw data files from /images/dev/<mac_address> to /images<image_name> directory. So you need to make sure the management user ID and password has rights on the NAS to login via FTP and can execute the mv command to move the files.

@jamaal said in Powershell and fog:

. I’m not sure on how to check the apache error logs.

You need console access (e.g. SSH) to your FOG server. See my signature on where to find the logs files.

@sebastian-roth thx for ur info

I use WAPT to deploy softwares but i don’t understand your use case.
Why not just deploy WAPT agent and use command like “wapt-get install tis-yourPackage” ?

@george1421 Thanks for the tutorial, i’ll try it.. .

@fog_newb Thanks a lot,

@george1421

Huh, your Google-fu is stronger than mine. I searched on google but didn’t find the link you provided. Thank you for the quick reply 🙂

Forget about it. It seems there is no easy way to do it and it’s not a big deal even if this kind of boot menu isn’t set up.
Thanks for your guidance.

@george1421 Ah ok I misread the OP. Well last time I checked, True Image can still create a boot image ISO with Windows kernels in addition to Linux kernels. If I’m not mistaken I believe you need to have the Windows ADK suite installed in order to create a WinPE boot ISO.

@Pitohui
How big is the ISO file? Perhaps you can try the sanboot or memdisk methods?

@andreluciano2 https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

The move is 2 steps. One to move the raw data files from /images. The second step is to copy the database to the new server.