@cizio said in Centos7 - default.ipxe no such file or directory:

What are you doing wrong?

Not sure who you mean?

Did some mess with your installer directory in /root/git/fogproject, maybe? If it’s git-based (as the name suggests) then just do a git pull. If it’s an extracted archive, then I suggest downloading and extracting it again.

@cr17373 Any update on this topic?

@davido38 have tried but the program is not able to find PE file. but nice trick

@sebastian-roth HI Sabastian, sorry buddy the answer is staring me in the face, the domain password appears to be missing.

@george1421 said in postinit script changing kernel parameter "fdrive":

AFAK you can’t edit the kernel invocation line.

@WT_101 While I think George is right on this part I can still see how you might achieve what you want to do by overwriting the fdrive variable within a postinit script. The postinit script is being sourced (ref) instead of called (subshell).

This is just from brain to keyboard and I have not done any testing. Give it a try and see…

@sebastian-roth I appreciate the response. Unfortunately none of those options resolved the issue.

I spent some time reading through those articles you linked, and I saw a lot of suggestions for disabling DMA protection. I tried it out, and that fixed it for me!

@sebastian-roth said in /bin/fog.upload doesn't exist:

mkdir /fogserver/images/dev
chmod 777 /fogserver/images/dev/
touch /fogserver/images/dev/.mntcheck
exportfs -r -v

Thanks for the help on this @Sebastian-Roth this was the fix. I also 777 .mntcheck but not sure if this is/was necessary.

@sebastian-roth
ok, add another menuentry to /tftpboot/boot/grub/grub.cfg
and add an timeout worked. But there will be a second menu to select one of the two menuentry. Not so nice, but it works.
I could not find a working chain-syntax for the grub.exe.
Embedding a grub.cfg into your core.0 binary I didnt test yet.

@fog_newb said in Strange formatting when selecting host. Dev Branch1.5.9.207 Ubuntu 22.04.1 LTS:

I saw Partclone 3.20

Yes that is the version that contains the updated code for apfs support. So it should clone apple based computers beyond getting access for the T2 chip.

Transferred to github to we don’t loose track of it: https://github.com/FOGProject/fos/issues/48

@danboid said in Removing MACs from multicast task without starting over:

I also seem to be having an issue with machines not changing their hostname to match what they’re known as to the FOG server. We’re using Windows 10 on the clients. I’ve installed the FOG client, set the address of the FOG server for the client and it has worked for most of the machines but not all. They’re all on the same network / switch but there are two types of PC with different network adapters if that could make a difference?

Just figured this part of your request is still open. Not a great idea to ask for several different things in one topic. As Wayne said early on we need the fog-client log (usually in C:\fog.log) to be able to help. Probably best if you open a new topic if this is still an issue for you - and post fog-client logs as well.

Cross linking the GitHub issue: https://github.com/FOGProject/fog-client/issues/72

@sebastian-roth Ok i test again with [] for mac but yesterday i probably write mac nots mac. Thx for help it’s working

@YaidenCR Which version of FOG do you use (lower right corner on the FOG web UI when being logged in)?

@george1421 Really appreciate the help, so turns out it was secure boot, after turning it off everything worked great.

In case anyone else has this question, the Reports tab serves this purpose. Once an AD user logs into FOG and starts doing things, the history report will log it.

@WT_101 Currently FOG does neither store the error message nor does it stop the task in case of a failure. Probably a nice feature to add if you are keen to get into it.

You wanna start by looking at the FOS script code. Pretty much all errors cause a single function to be called: handleError() in /usr/share/fog/lib/funcs.sh (code reference). This function could be extended to report back to the FOG server and even cancel the task.

@kureebow in windows, once the fog client is installed AND you have the correct AD settings in fog:
d308c21c-4d1f-4814-9db8-d0d82b071ccf-image.png

it should work without issues. Correct settings are make sure “join domain after deploy” as well as "name change(ad join forced reboot) are selected,as well as a domain username credentials with privilege to join the domain. You may have to “reset encryption data” for fog to get the correct token, that is if you keep getting the below errors over and over:
9/27/2022 10:48:41 AM Middleware::Authentication ERROR: Could not get security token
9/27/2022 10:48:41 AM Middleware::Authentication ERROR: Could not find file ‘C:\Program Files (x86)\FOG\token.dat’.

@Greg-Plamondon Sorry for the really long delay. Hope you got this solved!

Just for the record, fog-client auto registration currently works (FOG 1.5.9.200 - fog-client 0.12.2) and I don’t think it was broken in the versions you have.

Found a bit of time to look into this. Just in case anyone comes across the Middleware::Response Invalid MAC address format on unregistered clients again. This happens when a MAC address filter (FOG Configuration -> FOG Settings -> FOG Client - Host Register -> QUICKREG PENDING MAC FILTER) is defined so that a newly registering client’s MAC matches the filter.

Just for the record, fog-client auto registration currently works (FOG 1.5.9.200 - fog-client 0.12.2).