@unknownhost99 Could be as Wayne said, a rogue DHCP server or could be a dozen other things. There is no reason to hide internal network IPs. More often than not we see things on the screen that you don’t see. So you might post a full picture and tell us which IPs your DHCP server and which your FOG server has.

By the way, what is serving DHCP in your network? Has your setup ever worked or is it a fresh install? Which version of FOG?

Beside that you can take a look at the files in the TFTP directory on your FOG server to see if they do exist: ls -al /tftpboot

As well see if the TFTP server is running on your FOG server: netstat -antup | grep 69

Post the output of both commands here.

@unknownhost99 What was wrong? How did you fix it? These are things that future readers will wish you shared.

@breit said in Expanded Virtual Disk but FOG doesn’t see the change:

Ubuntu sees it just fine but I’m not able to get FOG to see the newly added space.

What do you mean by “Ubuntu sees it”? We need more details to help. So far you haven’t told us anything about what steps you made (details!) to expand virtual disk, LVM, partition, filesystem and how your setup looks like.

@george1421 said in Unable to UEFI boot to Fog Server:

If Windows 2008 DHCP doesn’t support automatic uefi/bios (I know it doesn’t)

If it does, I cannot figure it out. I spent days trying. One would think it can given the available GUI options in 2008 DHCP, but configuration of it is just way too complicated. 2012 R1 and above handles it nicely though.

@sebastian-roth

ok, thanks for the help

@junkhacker Not invalid password but ACCESS DENIED

@dylan123 I think this is very hard to debug not sitting right in front of the machines myself. You need to know that everything is this chain could be the bottle neck. So the best you can do is cross test things to hopefully nail it down. That means testing at least on three different clients in the exact same scenario (same network switch, no other things running over the network or on the FOG server at the same time). See if they all behave the same. If so, then you need to look into network or FOG server to find the issue. If they all go different speeds, then note down the numbers (start, end, average speed), redo the test again and see what you get. Possibly you can nail down one host that is different than the other two. Do a badblocks and memtest on that machine. As well see if that one has slightly different hardware.

@wayne-workman yes i saw thanks

@dpotesta50 I wanted to add to Wayne’s very important questions that we also need to know what exactly you see before the screen you posted the picture of. It surely is a blue partclone screen and it has the actual error printed. You need to take a picture of that!

@george1421 ah, yes I see it does say that in the Windows 7 guide… i didn’t look at it as i was trying windows 10 first. many thanks

You may have to do this by sql commands since that function is not supported by the GUI, even the latest version. Plus your version of FOG is about 5 years old (if not longer). It is difficult to provide support by the developers for something that old.

Is this thread asking if FOG can automatically assign a name to a host? Yes. It’s call quick registration auto population.

@meki333 If you cannot connect via the computers FQDN, then you have a DNS problem (or are lacking a DNS implementation altogether).

@mdean You should upgrade to RC 10 - lots of bug fixes in it. For the menu, you can always go view it through here: Web GUI -> Reports -> Pending Mac List

@cmurray139 First thing that comes to my mind is SELinux possibly not being disabled in CentOS. Please follow instructions here: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

About the blank page. It’s probably easier to take a look at the apache error logs (see my signature on where to find those)!

If you still want to check the packages then take a look at the FOG installation logs. Those are placed in the same directory where the ./installfog.sh script’s been run. As well you can check /var/log/yum.log for a list of packages.

By the way, which version of FOG do you use?

@jacky94 Thank you for sharing!!

Driver injection is always been an issue, especially hardware that is hidden behind other hardware. Some times it take 3 passes to get all of the hardware identified and the drivers loaded.

@astrugatch You’ve probably read through this?! Fairly easy to setup. Though if you really only need UEFI then you can go ipxe.efi “single handed” and you should be all fine.

@sebastian-roth, sure!

alt text

@joe-schmitt said in Service Fog Client:

when client installs, it sets the service to auto on boot, but does not start.

I guess what needs to be turned into a feature request is a msi install command line switch to alter this behavior. This switch would install and set the service to disabled. Or alter the process to require a command line switch to set the service to auto and the default would be disabled. Either way would work. Probably the command line switch to disable the service would cause the least amount of pain for already installed environments.

Most of the time the fog client is being installed before the system is sysprepped, which is causing us the most problems. So if the client installs but doesn’t start until the FOG Admins wants it to, that would eliminate that source of imaging pain. Also if we can keep the fog client from starting during reference image development, we can keep the fog client from tattooing to the defined FOG server until after OOBE is run (I’m not sure if there is a benefit there).

On the back end to turn the auto start service back on we could have a command line option for the fog client to start the client and enable the service that can be called from the setupcomplete.cmd file. Something like “c:\program files\fog\fogclient.exe /autostart” (I just made up the path and file name just as an example)

@george1421

yes!