Hello,

excuse-me for awakening a quite old post, I’m not asking for help but adding some contribution in case of someone else has same problem. I also had yesterday the same message when trying to capture a syspreped Windows 10 pro 1709 image (with Virtual Box)

0_1524123955382_Capture6.PNG

I tried several basic steps suggested in this post, but the thing that simply worked for me was tu upgrade fog server… (It was not updated since two or three months)

I can’t reproduce the issue, but it can be a step to try before recreating a new Windows sysprep image 🙂

@Quazz True, but I wan’t to see what can be done with UEFI. In the future I will make almost all my deployment by UEFI boot. So I hop it will work find, I see than UEFI is not standardize as Legacy. So it was to understand.

what device is providing your dhcp or proxydhcp services?

@zeltron80 said in Storage Node different for capture and deploy:

Could you explain me if it’s normal operation or it’s a bug?

It’s normal operation. FOG uses the first server it finds that has available slots - unless you’re using the location plugin which changes this behavior.

I have try to skip this problem to set Max Clients to 0 on my default Node it’s work but when i want to see my Nodes on the Storage Management web page i have a blank page…

This is a known bug in 1.5.1 and 1.5.2 where if the max clients is set to 0, it causes a problem. This will be fixed in the next release candidate.

@tom-elliott sorry about that!

0_1523945512782_9e3dcf56-182d-47e1-937a-824dd9f19c3a-grafik.png

So only to get it right, the id i want to get here is 2 on this host.
I’m getting the same result as the last time:

0_1523945594808_21b5b555-73b6-45f0-b8f2-2c64bbc261b4-grafik.png

Ok, I figured it out. Turns out the mysql db wasn’t properly setup. Deleting the old files, reinstall and re-setting up did the trick!

I remoted in and helped identify the problematic adapter.

I’m currently working on a way for the client to automatically filter out virtual interfaces to help prevent these kinds of issues in the future.

So obvious when you see it !
Thanks all for your responses.
Have a nice day

@jmercier When you try to add a key, most likely there are some apache errors being written to your server’s apache error log. If you could supply those, that would help the developers. Also - this plugin is not necessary but makes things easier as far as applying keys to different hosts/groups. You can still use groups to apply a MAC key to a group via group management, and you can still apply a key to an individual host via host management.

@towndrunk Understand that I’m talking about the Veeam backup agent not Veeam B&R. These are two different products, But they can work together very well. The FOG backup agent is used to backup physical machines to a local disk, CIFS share, or to your Veeam B&R server. It works much like any normal backup tool. From the local machine you can launch a backup or restore a file.

If you want to go the raid imaging route we can do that too. For YOUR raid system you will follow pretty much the raid document I create… 2 years ago (dang) for the intel built in fake-raid controller.
https://forums.fogproject.org/topic/7882/capture-deploy-to-target-computers-using-intel-rapid-storage-onboard-raid

Before I start this, I do have to say that FOG has not been tested to see if it can backup, or even restore a windows 2016 OS. I suppose I could test that in my home lab, but at this point I don’t know if the following process will be able to produce a viable system upon restore.

What you will do is this:

Register that server with FOG. Go into the host properties for this 2016 server and add in these kernel properies: mdraid=true Now schedule a capture or deploy (does not matter, we are going to do neither), but before you hit the schedule task button, tick the checkbox to debug. PXE boot the target system. After a few key presses you will be dropped to a linux command prompt (FOS) on the target computer. Kind of follow part 3 of the document I linked to find out if mdraid can see your array and what its called. It probably won’t be called md126

I’m aware of this issue, just haven’t gotten to look at it yet sorry.

Thanks for your advice. Will try on monday.

OK thank you my prblem is solved now i will post another problem now with license key plugins x)

There are a few things here.

Upgrade to 1.5.2 because it addresses a few issues. The 780s did have an issue with pxe booting and picking up an IP address. I don’t feel that is the issue here, but just be aware. Can you post a clean picture of the actual error so we can see the context of the error? When pxe booting happens and then we see random issues with dhcp, that is typically related to having a network switch with spanning tree enabled (a good thing), but the switch is not using one of the fast spanning tree protocols (not such a good thing). As Wayne said, put an unmanaged (dumb) switch between the building switch and the pxe booting computer. If the computer boots and runs through FOG OK, then your building switch does have STP enabled instead of RSTP or what ever your switch vendor calls it.

@sebastian-roth It’s possible, but that can be done right in the gui.

@joe-schmitt said in FOG 1.5.1 ~ Unable to create image:

@Sadowsky80 1.5.2 was just released due to the list of bugs in 1.5.1.

https://fogproject.org/download has been updated with the 1.5.2 instructions.

Awesome! Thanks for the quick fix

@flareimp It should not. I’m about to release 1.5.2 (considering the bugs listed) which means you’ll have to edit the file again on install.

You can help simplify this by doing:

mv /var/www/fog{,_back} ln -s /var/www/html/fog /var/www/fog

@mz3bel said in Can't add new hosts:

PS: What i’m trying to do is to implimenting 4 Laptops with same image pré installed softwares. Is there any way that i can do that with rj45 cables no network? so that i can just deploy the machine when i need to ? and take them off, so the students could use them

FOG needs certain network resources to work. You must have DHCP setup to supply the network booting configurations to the pxe target computers. You can have FOG do this for you, or you can use an existing network infrastructure. You can setup fog on an isolated imaging network, or you can setup fog on your existing business network. You must have some kind of network, even a 5 port small switch will work. It is technically possible to setup FOG to image a single computer at a time by just using a cross over network cable, I’m not sure you really want to go that path.

@kmstuartjackson Hey, just letting you know that 1.5.1 was released overnight. If you used the git method to download the FOG installer all you need to do is change to the fogproject folder and download the latest installer by issuing a sudo git pull request then change to the bin directory and issue a sudo installfog.sh command again to rerun the installer. Your fog install will be updated to 1.5.1.

@Taspharel Client version 0.11.16 (included in the FOG 1.5.1 release) features the new Snapin messages (currently only for English, other translations will follow in future releases).

Thanks for suggesting this change!