@tandersb said in Cannot capture image- fails at 'Saving original partition table':

Is there a mailing list I should be on to get notified of new releases?

Release Candidates and Releases are in the Announcements area:
https://forums.fogproject.org/category/22/announcements

But currently news.fogproject.org is not working.

Latest version is also shown right on the FOG login screen, and in FOG Configuration area too.

This has been fixed.

Thank you so much, I made the changes I needed in the bootmenu.class.php file (line 528) and now the prompt is in french !

$Send['chainhide'] = array( 'cpuid --ext 29 && set arch x86_64 || set arch i386', "iseq \${platform} efi && set key 0x1b || set key $KSKey", "iseq \${platform} efi && set keyName ESC || " . "set keyName $KSName", "prompt --key \${key} --timeout $this->_timeout " . "Demarrage en cours... (Presser la touche \${keyName} pour acceder au menu) && " . "goto menuAccess || $this->_bootexittype",

I know it might sound trivial, but I would like to insert some kind of ascii logo to warn my users that it’s time to press the escape button. I can’t figure out how to insert a line break in the line of code below without breaking things… I would like to display someting like :

. "Demarrage en cours... "line break" _____ "line break" / __ \ "line break" | / \/ ___ _ __ _ __ "line break" | | / _ \| '__| '_ \ "line break" | \__/\ (_) | | | |_) |"line break" \____/\___/|_| | .__/ "line break" | | "line break" |_| "line break" (Presser la touche \${keyName} pour acceder au menu) && "

Thank you again for your time !

Regards,

Frederic

Hi guys, first I would like to say thanks for all of you that help me here on this amazing tools that is FOG.

Special thanks for @Tom-Elliott @george1421 @Sebastian-Roth

Unnfortunately I can’t share more info about the AD for policy of the company that I work, I check out about the AD tables directory parents and even like that I couldn’t establish integration.

So I use the plugin of Access Control Manager , and create local users.

Looks great, you can make the filter of what the users can see it, but these bunch of users also can see the images of others users when list the images and the hosts as well. It is not a problem for me now.

Thanks a lot guys you are amazing.

Jacob.

@sebastian-roth That worked I have no idea how those rules got loaded onto the firewall however…

@cml Changing DocumentRoot did not help but changing the folder from which the content is served, did. Thanks.

@louislagad OK lets see what the pcap is telling us. That will give us a better picture of what the client is seeing.

Just wondering, is the dhcp server configured for some other imaging solution?

The command to do such a thing would be:

snmysqlhost=10.10.10.10 snmysqluser='root' snmysqluser='passwordforcentralsql' ./installfog.sh -y

@Sebastian-Roth That worked! Thanks so much!

Can you explain more to me why I can’t browse to x.x.x.x/dban and see the about.txt?

@george1421 said in dhcpd and known/registred hosts in fog:

select hostName,hmMAC,hmPrimary from hosts left join hostMAC on hosts.hostID=hostMAC.hmHostID where hostMAC.hmPrimary<>1;

Works perfect. Thank you again!
Cheers

Rainer

@george1421 Yes it is, thanks.

@george1421 Sorry for the delayed reply, been SWAMPED. Anyway, so far it’s working with no issues, basically plug and play since I configured it here and had it delivered. Setup a bash to send me an email when it came online. As soon as it came up, I added it the console and replication took off… by the way, forgetting to limit bandwidth before replication start upsets a lot of users LOL. Now if I can figure out why these new Dell Latitude 3570’s will let me register them but not load the menu after I will be all set.

Note: No the firewall only filters external traffic, sorry I meant to start off with that.

This is true. In the current release of FOG NFS is used to transfer the images from the fog server to the target computers. This needs to be open for the target computers to be able to read the images. You can restrict mounting the nfs share to a specific subnet, but that is it as of now.

While this version is still a years off, FOG 2.0 will have security built in from the start. But that isn’t here today.

@brooksbrown I think the terms are being mixed up here so I am trying to set this right. When installing FOG there are two different modes you can choose from, either master OR storage node (there is nothing called “master storage node”!). From your description it sounds as if you installed all your FOG servers as master nodes and therefore you have separate DBs and hosts being registered to one node won’t show up in the other node unless you register each and every client with every FOG server you have. On the other hand if you do the usual setup you’d have ONE master node (where the DB and web UI is) and several storage nodes.

The “failover setup” you intent to build is not as easy to handle I am afraid. There is a lot involved in PXE booting clients - 1st DHCP handshake from the PXE ROM, TFTP to load iPXE binary, 2nd DHCP handshake from the iPXE binary, TFTP and then HTTP request to load iPXE config, HTTP request to load kernel and initrd, 3rd DHCP handshake from the linux kernel. It might sound as if this is pretty straight forward. But if the FOG server for a particular bench fails (or is too busy) the client will get his first DHCP answer from another FOG server. For example if the 1st DHCP handshake is answered by lets say NODE 2 (as the client is on bench 2). Then the client will download the iPXE binary from NODE 2 as well. But the 2nd DHCP handshake might be answered by NODE 3 (cause NODE 2 is not fast enough this time). Still fine if they all share the same DB (which would be on the one single master node) and the client gets a consistent iPXE config (e.g. FOG menu or task).

In theory this all works but all servers kind of need to be in sync, TFTP files, kernels/initrds, FOG web UI. If you alter the kernel on one server you might see clients from a different bench booting that kernel at random.

That all said there is another reason why I think this setup is not great. For every DHCP broadcast a client sends it gets up to eight answers from all the DHCP servers. Finding an issue and keeping this all setup properly will be a nightmare I suppose! What if there is just one single setting different on NODE 6? Some clients will boot properly but others will fail randomly because of that.

I reckon one could be keen enough to set this up all in one broadcasting domain using two or three servers at the most. But definitely not eight. This will cause you so much headache I suspect. Just don’t do it if you and the rest of your team are no real network wizards who love to use tcpdump for analysing network packet dumps to figure out what’s going on.

If you intend to use the fog-client the whole idea of failover is buried alive anyway. Sure, fog-clients not reaching their particular server is not as problematic as the other stuff can be. But failover is just not possible.

I bet you better take some more time to think about the network setup now and have a lot less issues later on…

@Sebastian-Roth said in FOG 1.4.2 TFTP Open Timeout:

@cassie_280 There is one step in the installer where it tells you to go to the web interface. This is not the end. You need to hit enter after that to proceed. Not to sound rude just wanted to make sure…

I don’t know how many times I’ve reached that step and when to copy the url and hit ctrl-c to copy the url, which then aborted the install. So it does create a botched install. It does happen.

In terms of single disk productivity is the best option because the clone of this image was on average 30 minutes in multicast mode, when I used multiple partition the time to clone the image was in 2 hours and 30 minutes.

@Sebastian-Roth Yea, I’m good now, actually got it to work with a Windows DHCP server as I was hoping.

Thanks for all your help!!

@hancocza Ok, so I got this. I am looking into the building process of the FOG client right now as our client developer is absent right now. I might come up with a description of how to custom build the client (e.g. for custom SSL cert). I am still trying to get things sorted with the building tools. Let’s hope I get this fixed soon.

@Tom-Elliott using KMS server, if I leave blank will that work?