@sunks if it happens again like this, come back and tell us, try to use this same thread.

OK. Will do. Thanks!

Typical newbie mistake. I’ve done my best to spread this knowledge all over the wiki:
https://wiki.fogproject.org/wiki/index.php?title=Ubuntu_16.04_Server#Settings

set a username, recommended name is YOUR first name, or “admin”. Do not use “fog”!

And
https://wiki.fogproject.org/wiki/index.php?title=Password_Central#Local_.22fog.22_user

Please do not use the local “fog” user account on the server to do back-end work. Create another account and use that.

It’s other places too. I don’t know what it’s about but I think the force compels the human soul to set the local account name as fog

@sebastian-roth I never had the option to reset encryption on this host and it wasn’t working for all hosts.

@arkhad said in Failed to get an IP via DHCP!:

I installed 1.44 again and tried to register a host and it worked this time.

Because reinstalling fog 1.4.4 replaced the kernel and inits with the correct versions for 1.4.4

Ok I solved it.
Yes, that is when I let the menu timeout.
In my host the : FOG_EFI_BOOT_EXIT_TYPE and FOG_BOOT_EXIT_TYPE were both set to EXIT, Ichanged them back to the default setting (‘Please select an option’) and set those parameter to SANBOOT in the fog settings.

Thank you for your help 😄

Solved!

How I said in before posts, the problem was the different states of the network card. After working hardly with the network guys and talking with @Sebastian-Roth, we solved the problem using the undionly.kpxe file that is in the folder 10seconddelay.

This file adds a little delay in the DHCP request after power on the network card.

The FOGScheduler logs just show my 7 scheduled cron wake up jobs. I have disabled all of the FOG services and they still started up. Thus it does not appear to be FOG. I am trying to get a hold of a network analyzer to trace who is really sending this signal. Thanks for your help in understanding how FOG works, it has helped me narrow down who is causing the problem.

I know it is a WOL being sent as my boot is SSD, then IP/PXE and it is PXE booting. Also, it is only happening in one of my three buildings. And only about 1/3 to 1/2 of the computers that I have in that building. So it looks like I have a rogue server somewhere in that building.

@zingaro said:

There are the difference with VM Machine ?

Well, VM is not hardware and vice versa and also hardware is not equal to all other hardware. We do see many issues related to slight differences in the UEFI firmware and such things. Causing a lot of trouble sometimes. There is no easy answer to your question. You’d need to get into debugging the problem on your VMware to see why it doesn’t work.

@lpetelik said in Login takes 5minutes+:

following for more solutions.

I wanted to tell you that you can disable the graph for all of the storage nodes, and this really does make login pretty snappy, but of course with this you no longer have graphs for all the nodes on the dashboard. With graphs disabled, you can still see tasks in Task Management.

@coxm said in Image Replication Across Storage Groups:

should i image a pc in that remote site which is made part of that remote site storage group it will pull the image from that node, not the master Fog server on my local site.

Not necessarily. Without the location plugin, fog just picks whatever server that has empty slots.

You should look at the location plugin (link posted earlier), I think that’s what you need. The location plugin allows you to assign storage groups and storage nodes a physical location, and allows you to set physical location on hosts. If host A is assigned location A, and a storage node is assigned location A, then all imaging on host A would only use node A.

@lebrun78 said in Manage scheduled task:

May be examples are lacking in the documentation ?

Help us write examples? Post them here.

@marcolefo Ok, thanks for letting us know. Marking this solved now. If you have issues again, just let us know.

@sebastian-roth Yeah, my supervisor is satisfied with the process. It is working. Thanks so much for your help guys!

@quinniedid OK in my test lab I’m running the build listed in my post. That is with 6.5u1 and the Oct 2017 patch. Point being if I can get a few minutes of time I want to see if I can duplicate what you are seeing to see if VMWare addressed/changed/fixed the issue with a vSphere update. I don’t know one way or the other, but this sounds like a uefi firmware issue to me.

@NateCCC Do you have any custom scripts, post-init or post-deploy?

To me it seems you have a similar but still different issue. Better open a new thread and describe your setup in detail: FOG version, picture of any messages on screen at the end of deploy on the client, even better take a video of pre and post imaging screens…

@sjensen said in Issues with disk in an unsafe state:

I got the update installed and i am uploading an image from the Samsung laptop now.

Great to see that you’re up and running. I’ll mark this solved then. Please open new threads (yes several if you like) in case you hit another problem. It’s best to not mix up a dozen or so questions in one thread.

Cheers,

Yes that work around worked.

Cheers!

@Tywyn Great to hear you could make it work again. I have no idea what was wrong before. I have looked through the code many times and don’t know what could have gone wrong. Marking this solved now. Let us know if you see this again.

@BardWood Bump… 🙂 Any news on this?