Topics created by bmick10

@steveballantyne Did you also update the Kernel and Init? What version fo FOG are you on?

@bmick10 said in Renaming Windows10 Device with Secure Boot:

So I can ping from Windows computer but not our fog server.

One final check is to use the windows computer to get the IP address of that registered computer. Ensure you can ping the IP address of that computer. If you can then the issue is…

You need to setup DNS resolution on the FOG server so that it resolves the computer name correctly. You do this through the /etc/resolve.conf file OR for the linux distro that you use, if you have the gui for the FOG server linux OS, then use the network manager to set the DNS server to the IP address of your Windows DNS server (typically your AD DC). Make sure the search domain is set to your AD domain (i.e. ad.bigco.com)

As far as Fog changing settings for UEFI may I ask how that could happen

FOG will not do that. It doesn’t touch UEFI settings. I’m just saying that is only one of the few ways to upset secure boot, well actually bit locker. Secure boot only deals with the OS starting up.

@bmick10 said in Deleting Hosts:

If I delete a device that is still in production on the network. It will not remove from domain or lose connection?

Correct. The only impact to the target computer is that if the fog client is installed on the target computer it will no longer get instructions from the FOG server. The FOG Client will be abandoned with no instructions.

If I have a machine named ittech20 and remove that from database when I restart in pxe will the computer still be named ittech20.

Yes the computer will remain untouched. The only thing you will notice is that in the fog iPXE menu the computer will appear as unregistered.

So if I delete all of them since the machine still has service running on will it talk back to server and sync to database?

If the FOG Client is installed on the machine but they are no longer in the database the FOG Client should reregister the computer. Now that I think about it. BUT they will be registered in a pending state and must be approved before you can work with them in the FOG Gui. Its been a while since I did this part so its not as clear in my mind. But they should go into the database again in a pending state.

@adukes40 said in UEFI boot Instead of Bios boot:

@george1421 you doing that for every single uefi machine, or just the problem child’s?

We do it for every machine that won’t init using iPXE in uefi mode. Which is only the o7010 so far.

We also don’t pxe boot through fog to the hard drive. This is to avoid accidental reimaging systems. We always require a tech to sit in front of the system they are imaging and use the F12 boot menu to select pxe boot. Once a tech accidentally remotely deployed an image to the controllers laptop, that was enough motivation to change our workflow.

@bmick10 So now that you have it configured to not restart when the system is that’s good. Now just make sure the settings are correct in your .fogsettings file so that the dhcp server isn’t reenabled when you update FOG.

@bmick10 said in DHCP Server Change:

I think I have tried to get in by clicking on and said I didn’t have access even though I am administrator.

Linux doesn’t have the concept of ‘Administrator’, that’s a Windows thing. Linux has users, and root. And sometimes users are allowed sudo privileges for some or all commands. Really, you need to be root to edit the file. Usually, that’s done via CLI.

I can’t envision this is a FOG related issue. But, if you sysprep an image and then reboot it on the same machine (removing fog from the picture) do you still have keyboard and mouse function?

I would tend to think its a driver issue where you started with an earlier release of windows and its drivers, upgraded to 1803. Maybe the earlier windows drivers were still intact and then when you sysprep all of those drivers are reset to 1803. Understand this is just a guess. Also watch the revisions of your firmware to see if there is an update that solves your issue.

@bmick10 said in Updating Fog to newer version and Pending Mac Addresses:

just wondering if it is always something that breaks locally or if things can be affected by developers or fog employees.

We aren’t employees, FOG is supported entirely by a community of volunteers that help out at their own discretion, of their own accord. There’s no money involved besides donations - which are never expected but always appreciated. You can help out too, just by answering questions you can answer or writing tutorials or documentation, videos, etc. You’ll find that you will learn a ton just by reading the stuff that’s posted here.

As for if things are affected or not by the devs - if you re-run the fog installer, it would get the latest kernel and init in order to support the latest hardware - but no web-core changes or DB changes are made unless you actually go get the latest version of FOG. As for your OS, when you re-run the installer it makes sure it has the latest version of the packages it needs, everything else is left unchanged. Ubuntu is notorious for resetting customized configuration files during updates, which in turn cause problems - this is of course compounded because Ubuntu by default automatically updates and most people aren’t knowledgeable enough about Linux to rip out that functionality.

@grant1842 said in Your database connection appears to be invalid.:

I had to re run the installer as well as remake my dnsmasq 2.76. … but my dnsmasq reverted back to 2.75 which was causing the boot file to not be received correctly.

This is only speculation, but I’m guessing that the linux distro you use updated dnsmasq from (2.72 or 2.73) to 2.75, thus overwriting your compiled 2.76. As wayne said the package manager only knows about what it does. Hopefully the next time it happens is when your distribution updates to 2.76 or newer. Then it won’t matter at all.

On the plus side you were able to discover and fix the problem pretty quickly. So good job there.

Thank You!

@bmick10 yes. I’ve been working pretty hard on the units lately I’ll try to figure this out tonight.