Best posts made by Wayne Workman

@zpoling For an image to be resizable, it has to be captured as resizable. Also, the used space on the resizable image must be able to fit on any disk it is deployed to.

@jfulton Try putting a dumb switch (unmanaged mini-switch) between the target host you’re working with and the rest of the network, see if it makes a difference or not. If there’s a difference, we have additional steps for you on how to fix it.

@dpotesta50 In the hosts’s general area, you can input the key that belongs to it. The FOG Client will use this key to activate Windows.
Be aware, you are not allowed to deploy Windows OEM copies in any other way than original installation media. If your licenses really are Pro licenses, you are in the clear. Beware of audits - they do happen and people do get fired over them.

@bigchief said in Enter FTP Server issue:

when I do any network boot to FOG, it always makes me type our FOG server IP address.
I checked to make sure I don’t have 2 DHCP servers already and wireshark is showing only 1.

I’d say check again because that has only ever happened when there are two DHCP servers on the same broadcast domain (and the two also don’t agree on options 66 and 67, typically the rogue one simply not having them). I can probably find a dozen threads where this has been the cause of the problem you describe.

@dclark If DHCP options 66 and 67 were not set on at least one DHCP server, network booting wouldn’t even happen.

@george1421 Wouldn’t downgrading the kernel work in this case?

@msi said in Can't login to FOG web Interface:

When asks to change the directory to Git environment, do you mean where the fog installation file is located?

Yes. Typically it’s at /root/fogproject or /root/git/fogproject if you’ve followed instructions from the wiki.

@msi You can use git like this: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG

When you switch branches, use the branch in Tom’s post, which is working-1.5.1 The article covers switching branches.

@jherron Yep, use these commands: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

@sadowsky80 I’m unsure at this point if it’s something wrong with your new setup or if it’s something wrong with 1.5.1 which was released within the last 24 hours. When I get home I’ll try to replicate your problem to see if creating image definitions works. Unless one of the @moderators or @testers can test creating a new image definition on 1.5.1 before then.

@tiagoluz If you intend to have 54 storage nodes, you’ll likely need to disable the graphs on them all. The graphs cause problems when there are several storage nodes. This is a setting on each storage node in Storage Management.

@nt_tech said in FOG Down today, no GUI and all PXE boots failed:

/var/log/apache2/error.log and the error log is below. I could rerun the install but am concerned that I may loose all my hosts. Any suggestions would be

Check free space: df -h look for partitions with 100% used.

@zer0cool Check permissions on the path /centos7/images There needs to be permissions for the whole path including centos7 and images individually. Although I don’t think this is causing your problem, it’s something else.

@zer0cool Read over this, it might help you: https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu

@zer0cool said in New iPXE Entries Not Showing:

Does the host need to be registered prior to seeing this menu entry?

There should be a setting when editing the entry to allow it to be seen by registered only, non-registered only, or both.

@zer0cool said in New iPXE Entries Not Showing:

Is that the “Menu Show With”?

That’s the one.

Let’s back up a moment and start troubleshooting this. We need to figure out where the problem is and where it isn’t. Are you trying to boot an un-registered host? If not, try it. Are you trying to boot a registered host? If not, try it. Also try to add other menu entries - exact copies of what others have used - don’t worry about setting up the files on the server, we just want to see if the menu will display a known-good item or not.

Also, do you have two FOG Servers by chance, and these hosts are booting to the other one you didn’t modify? Just a thought.

@zer0cool There is an advanced menu item if I recall, best to try that too. At this point, I’m going to ask the @developers and @moderators to take a look at this because I’m stumped.

@ravigon Thank you very much for reporting this. Most definitely this difference is due to Microsoft changing something through a patch made public after our wiki article was initially published. I will get this updated photo into the wiki and again thanks for this! #wiki worthy.

Just wanted to add my experience about OS upgrading with FOG already installed.

My advice: Don’t do it.

Why? I’ve been active on these forums for about 3 years. I’ve helped several people with FOG since 1.2.x through to 1.5.x concerning OS upgrading. I’ve watched other community members help even more with this. More often than not, it does not go well. There are cases I remember where everything went fine. But there are more cases where things go wrong. When things go wrong - often the community has tried to help the person get things going. From what I can remember, this has taken days to weeks - sometimes these efforts do not result in the repair of the existing installation. I don’t think it’s worth the effort or risk. We have no way to tell you if your OS upgrade would work or not. If things go wrong, you’ll be stuck without a FOG Server, you may not be able to image, and if all of your hosts are setup to network-boot first, that’d be worse still.

What I would recommend: Migrate to a newly built box or VM.

Why? There’s lots of reasons here.

1. Your existing FOG Box will remain unaltered - and not be put at any risk. This is a major safety net. If you are not able to timely build the new box, if the new box has a problem, or any other issue - you still have that old box that is exactly as it was before.
2. We know the exact steps involved for migrating a FOG Server from an old box to a new box - regardless of the OS on either. These are all outlined here: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
3. I test clean installations of the major branches of FOG on several different Linux distributions daily. These tests are automated and the results are available to the general public. The link to the results is in my signature. With these tests, everyone is able to know ‘with a lot of sureness’ if the latest version of FOG will install successfully on whatever Linux distribution - or not.
4. A clean & fresh OS is easier to maintain, has less problems, and is a more ‘known’ state than an upgraded OS where you may or may not have any idea about what’s unique on it.

@gtx

• test.pxe is not a real file, please follow these instructions: https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG
• Is 10.0.2.4 your fog server?
• What OS is your FOG server running?
• What version of FOG?

@imagingmaster21 You’ll want to run through this: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS