I had the clients in a group and when I managed the group to have the Host Name Changer Service run for some reason that didn’t take. Issue Resolved though
and Joining Domain I was using “Domain Name\Administrator” instead of just the username Oddly enough It automatically joined the workgroup “Domain Name” instead of just an error

Never Mind Don’t know how to delete

Fog Gives the Correct name but seems to auto join the work group instead of the domain.

Ideas?

Alright Thanks Junk

Does the Fog Service need to be updated on Master Images for the newer version of fog?
Or is it the same file?

I’m in process to see if I can disable but They have it bios locked.

I do not. The HVAC Technician uses PXE to boot to the device when making a trouble call.

The Controller needs the PXE boot enabled. It is undesirable to have the fog server communicate with it at all.

It is xp embedded but I don’t have a way to visually see the boot up.

I have an HVAC Controller on the Network that PXE boots. Recently had a power flicker, Controller reboots, The Device hangs. Pull the Controller off the network and reboot; Everything works fine. Repeat on the network; Hangs.

Can I have fog ignore a mac address or will this have to be done using an ACL over the network?

Wireless Fidelity? Wireless Network

Images created that had no issues with joining domain are deciding that they don’t want to join the domain at all or if they do want to try to join. They will try to join a workgroup using the domain name.

4 out of 5 computers will not automagically join the wifi

Thanks, Fog Server is imaging. Let’s see if the fog service works? will the images with .32 fog service work with the 1.x.x ???

Fog Server works great, then I upgraded to the 1.1.2 version. Initially could not retrieve my image from the tftp server. Solved, When I upgraded, fog renamed pxelinux.0 to pxelinux.0.old and was not able to locate it.

From the Clients: I can reach the fog boot menu to register hosts, quick image, etc. The Client successfully registers on fog, It creates an active task in the Fog Task Manager, Normally it would start receiving the image from the server immediately after. All I get is text stating “Task Completed, Rebooting”

Note that even if I deploy an image from fog it seems like the client doesn’t have a clue that the fog server is trying to reach it.

Did not realize a /tftpboot.old file would be created with the upgrade

Having a similar issue. Just upgraded from .32 to 1.1.2 and am receiving the tftp files not found

Edit: Note that everything worked prior to the upgrade

Running A PCI 10/100/1000/(125GigaBytes per second) NIC. Thank you guys. I believe I have my Solution!

I would Assume what ever is native to the fogging screen. I think its roughly 1.2 GigaBYTES per minute. It’s a single client or broken up into smaller chunks the more clients I add.
Pentium 4 4gb ram on ubuntu, download task

Running a 1gb network but the fog server is very sluggish. Version .32
it’s only using 20-25 mbps of the network. Any ideas?

Ya no fog service was running on this new image I created.

Brand New to fog and took a position that uses fog.

Troubles joining domain. How do I set Fog to Automatic Delayed?