@phil-dosi You are right. There seems to be a difference between 1.5.5 and 1.5.6 in that it does not see the partition 2 as re-sizable. I am not sure why that is. The only way to find out I suppose is that you schedule a debug capture task. Boot the client machine up and step through the whole capture process and take pictures of the messages on screen. Especially at the point where it does the resize stuff before the blue partclone screens!

@Tony-Fiorentino Ok now the next steps is to make that dhcp option 67 dynamic. You would typically do this by following the instructions I provided about uefi bios coexistence. But since your dhcp server is older than windows 2012 you still have options without touching your primary dhcp server. You would do this by installing dnsmasq on your FOG server, and then let dnsmasq provide the proper pxe boot information based on the pxe booting client. If you have a single subnet, where your fog server and pxe booting clients are on the same subnet you just need to install dnsmasq and your’d done. If your clients are on a different subnet than your fog/dnsmasq server you need to add the fog server’s IP address in the last position of your dhcp-helper/dhcp-relay service on your subnet router, just like your main dhcp server. Once that is done your FOG server will issue pxe boot information for all subnets.

Setting up dnsmasq literally takes about 10 minutes with my tutorial. It is the way to go when your dhcp server doesn’t support dynamic boot files.

@blainey While reading through the whole topic again and again I get the impression that it might be easier than expected. I think Eduardo is right about what he calls “hairpin NAT” but I think the term might be a bit missleading. When you use 10.10.1.4 as storage node IP the clients within the 192.168.1.x network try to contact their default gatway to reach out to that. Those requests come into your gateway on the wrong interface and usually get dropped.

On the other hand. I can tell the Master server the node ip is 192.168.1.2.
This results in replication not working but imaging via the local node is successful.

What if we tackle it from this side. I guess it still won’t be easy but can give it a try. Set the storage node IP in the web UI storage node settings to 192.168.1.2. Now with that you “only” need to make sure two things:

the Linux OS on your main FOG server needs to know how to reach 192.168.1.2 -> ip route add 192.168.1.0/24 via 10.10.1.4 dev eth0 (probably you need to set a different network interface than eth0 - just the one where 10.10.1.3 is configured to) you have port forwards and rules on the gatway to allow FTP traffic through -> this might be a bit of an issue because FTP uses random ports as well as connections going both ways depending on the FTP mode used (active or passive - not sure which one we do really)

This setup will only work if the gateway doesn’t do NATing. If it does we need to find a different solution.

@Sebastian-Roth

it worked ! Many thanks I did not even noticed this tab!

@george1421

Hi,

My skills in english are fair but that’s all, that’s may be why my message was not clear enough.

To resume :

-We had a NAS LUN linked to the legacy FOG Server
-We rarely do unicast deploy, 95% are multicast.
-Running 3 or more multicasts start causing slowdowns on the WebUI.
-Sometimes we have up to 10 simultaneous multicasts. Very have rarely more, even
with 23 classrooms on the main site.

As the nic used to access the WebUI is the same as the one that flood the images through the network we thought that we could mitigate this phenomenon using storage node.

We are note stuck to a model or another, we are still searching for the best compromise.

Now we have/had a second issue it’s image export/Import. We plan to use replication at the end but for the first load which represent several TB sync through a wan link is not possible.

It seems this issue is now solved, the remaining “problem” is only cosmetic, but may be I did something wrong, it was the first time I moved images from storage to another and tried the export/import.

@Sebastian-Roth

Full rebuild on dev-branch works.

Thanks for looking into this so deeply!

I figured it out with your help. Thank you for your help.

I am not sure why the code changed after I changed the AD username/password in fog settings, because it seems the host continued to use the original. This was seen under the host->active directory. I added all 50 computers to a group and changed the setting for the group which changed the settings for all 50 hosts. It seems like the global setting should have done this, but it didn’t.

@ddenney0004 What exactly happens when you schedule a task from a storage node?

@Deimos From what you are saying I am wonder if you aware of the fact that FOG does not have persistent group settings. It’s more or less just a tool to push a setting to several hosts at once but it does not stick to the group itself.

@Nabeel Did you configure your dhcp server to supply dhcp options 66 and 67? For dhcp option 66 that needs to be the IP address of your fog server. For dhcp option 67 that should be undionly.kpxe for bios based computers and ipxe.efi for UEFI based systems.

If you need to support both systems in your environment then once you prove that the above options work you can review this article: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

@george1421

Sooooo as stupid as this sounds but I have a solution / workaround.

Reduce the number of CPU’s on the VM to 1
Enable migrate to a physical computer with a different processor version

Changing either of these setting causes the speed to bottom out at 21mb/m leaving the setting at this results in 230mb/m capture speed.

OK, thought it might be possible…appreciate the reply.

@EAHarvey Can you post the content of the three text files d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions from this image you deployed here. We’ll see if there is something specific in the partition layout that might cause the problem.

bcdboot D:\windows /s Z: /f ALL

I have not used bcdboot too much but I kind of wonder about the drive letters…

@0juke Guess there is some useful information for you here: https://wiki.fogproject.org/wiki/index.php?title=Add_%26_Extend_a_2nd_Virtual_HDD

Other than that we need more specific information on what exactly you did so far (“So I would like to expand the space of the server uses . I’ve done this on the VM but…”). Only when we know what exactly you did and what system/software you use we will be able to help properly.

@bigjim Are there any news on this? I am marking this solved for now as no reply within a week kind of sounds like you were able to fix this.

@im-pearce Any news on this? Is there something we can do for you to solve this?

It’s done …I have completely installed the virtual machine but also the fog server with the latest version, at the moment it seems that everything works just fine, I managed to capture the image of windows 10 with MBR, also did a full inventory of the work station , i deployed it on another workstation … momentarily I’m with kernel 4.19.36 … I’m thinking to update it at 4.19.48 … but I doubt it will not come up with the same problem … however i will try anyway 🙂
10x for the help ! …specialy @george1421 but also @Tom-Elliott ( apparently the problem started from the location where my images are saved…bad cfg )

@bartont126 Well unfortunately we need to see what the partclone error is. Partclone doesn’t give a good quality error message back to fog, other than the copy failed. FOG ties to make a good guess to why the copy didn’t happen but misses some times. If you setup a debug capture then single step through the deployment you can capture what is on the partclone screen.

@Sebastian-Roth

Updating the FOG server to the latest image appears to have resolved the issues. Good thing is did not have to modify anything after the update all models appear to be imaging successfully. 🙂