@alexvm said in Selecting which server to capture/deploy images on Fog:

is to select on which server I want the images to be captured first and which server to deploy them first.

There are some rules that you have to work with. Rule 1. Captures always, always, always go to the master of the storage-group the image is assigned to. This rule can’t be changed, it’s how fog works.

However, you can have many storage groups, and a storage node can belong to many groups. A storage node can be a master in one group, and a non-master in another - there’s a whole lot of ways to setup the nodes & groups & masters. Here’s more information on how replication works: https://wiki.fogproject.org/wiki/index.php?title=Replication

For the second part of your question, I think you might be looking for the Location plugin, here’s more details: https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin I think if you watch the video, a lot of your questions will be answered.

@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

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.

@ttellez Yep, steps here: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@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

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.

@caw001 You’ll want to read through this, it has the configuration steps you need: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@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

@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.

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

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

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.

@john-johnson Check that host with disk diagnostics and ram diagnostics. Often these tests are built into firmware and you can select them when the device is just powering on. Generally though, if the errors are not excessive it’s normally fine.

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

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

The only one that is resizeable lol.

In FOG Settings there are question marks with descriptions about things.
In a host’s “Service Settings” there are also question marks with descriptions.

Can we get question marks that show descriptions for a host’s “Active Directory” area?