Best posts made by Wayne Workman

Moved to feature requests.

@george1421 said in [SOLVED] PXE boot fails on a WIN10 based Lenovo (USB Ethernet) - FOG TRUNK:

@arnaudrigole If your dhcp server is a windows 2012 server you can add a filter to send the uefi boot file to uefi device and the bios boot file to bios devices automatically. That way you don’t need to manage two different scopes. Unfortunately this filter is not available for windows 2008 dhcp server.

Here’s our article on this process: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@Arrowhead-IT He’s working on making a storage node work on Windows.

Can you post the output of this?

On your FOG server:
[CODE]ls -laR /images/Win7Prox64[/CODE]

@george1421 That’s pretty sweet looking. I didn’t know about triggers till this thread, actually.

@mandrade said in Make new bzImage...:

would FOG handle USB NIC’s differently perhaps?

Yes,
in the host’s kernel arguments, you would put has_usb_nic=1

@Quazz I’d actually recommend @jbob 's firewalld configuration. I’ve had zero issues with it.

https://forums.fogproject.org/topic/6162/firewall-configuration

for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp samba; do firewall-cmd --permanent --zone=public --add-service=$service; done
systemctl restart firewalld.service

but yes, SELinux needs set to permissive, instead of being enforcing.
vi /etc/selinux/config
Instructions on using Vi:
https://wiki.fogproject.org/wiki/index.php?title=Vi

Change enforcing to permissive in that file.
Then to change the live setting, issue: setenforce 0

FOG Trunk has features that allow easily adding items to the menu via the Web UI…

Read through this article (especially at the bottom): https://wiki.fogproject.org/wiki/index.php/SVN

I just dealt with a full root partition due to the web folder backups that go into /home They were using about 16GB of my 20GB / directory.

I’m requesting that these backups instead go into /opt/fog somewhere and I can then update documentation to make a partition for /opt.

@mandrade You could try to register it manually with just a name and MAC.

Also - not sure how possible this might be but you may try @george1421 's USB tutorial.

He wrote a tutorial that was put in the wiki, it outlines how to create a bootable flash drive with FOS on it, that will allow you to image. I’m not sure how you’d incorporate it into the Lenovo Thinkpad x1 Carbon, perhaps a MicroSD card, perhaps a USB Hub…

Basically, this process removes iPXE and PXE from the equation totally. You still use the FOG server, but you’re booting from removable media.

Read through it here:
https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media

Some have said that dnsmasq’s 066 and 067 offers override DHCP’s 66 and 67 offers - while others have reported that things changed and their setup no longer worked with dnsmasq.

I’d say just try it and see how it goes. There is a good example of how to configure it here: https://wiki.fogproject.org/wiki/index.php?title=Fedora_21_Server#dnsmasq_.28if_using_ProxyDHCP.29_setup
I know that’s from a Fedora article, but the configuration for dnsmasq is the same across distributions.

@rothrock88 That’s an FTP issue.

Check this out: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

Give ya a hint… credentials.

This is a good idea - however - the client and the server are being developed simultaneously.

updates to the server may break older clients… or cause weird things to happen.

I might even suggest sticking with the legacy client until 1.3 in your case.

@the_great_heed Network boot, and it’ll either be right there in front of you or in the advanced menu.

There is also:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
and
https://wiki.fogproject.org/wiki/index.php?title=Fedora_21_Server#Verify_Fedora_DHCP_config_.28if_using_DHCP.29

Also, if you just install FOG with DHCP, it will build the dhcpd.conf file you need, and then you can edit /opt/fog/.fogsettings to disable DHCP on future installations, and then disable dhcp at the OS level as well.

Tomorrow, I’m going to quickly build up a new Fedora 21 box and put an older Trunk version of FOG on it. I know for sure it was working at r2922, so that’s what I’ll try to use and then I can test it.

If it’s successful, I’ll iterate up by 100 revisions at a time (snap-shoting each one), and when it breaks, I’ll roll back and iterate up by 10, till it breaks, then iterate up by 1 and find EXACTLY where things went wrong.

@Jbob said in Disable Client Auto-update:

Unfortunately it wouldn’t be that easy. Auto updating is a 100% isolated system. The server doesn’t even need to have a host registered for its client to update.

I feel I should add that any update is first verified for authenticity, too.
@jbob did it right.

Clearing gunk from the DB, plus numerous other helpful things about fog multicast can be found here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_Downloading_-_Multicast

@Sebastian-Roth A strong FOG Wiki is needed for a strong FOG. The moderators/developers would just be killing themselves if they answered things over and over in the forums. While the forums is also a critical component and a means of documentation - the Wiki should also be of equal concern - and the Wiki should be the first-stop-shop for people trying to do things and figure things out. If the Wiki is sound and solid, then people shouldn’t have so many issues.

Up to this point - i’ve only very generically covered 1.3.0 in the wiki because things change so fast. I’ve focused more on the Linux stuff and troubleshooting techniques. Once 1.3.0 is released - I plan on doing more basic stuff, how to do this, how to do that, best practices, and videos - a lot of videos.

@My-Sanity Sorry, I meant single disk - resizeable.

The only one that is resizeable lol.