@mmoore5553 Hi,

I create my golden images using VMWare Workstation Pro, so unsure if this is applicable. I have found the network settings on the virtual machine to be very important in this process.

Firstly, NAT just doesn’t work for capturing the image so ensure your connection is bridged.

Secondly I have found if you have multiple network connections (VPN, WIFI, Ethernet etc.) it will randomly pick which one to PXE boot via. I have found the “Replicate physical network connection state” setting is also required.

For safety I would suggest the host machine only has one network available (ie. temporarily disable WIFI and VPN) while using a bridged connection.

The other thought would be to check if there’s any network monitoring you can look at so diagnosis may be easier.

@chevengur there is not enough information to help you in that picture. If we could see more of the error message that partclone threw (i.e. just above the top of your picture) we would know what happened. At the point in the script all we know is that partclone wasn’t happy.

Thank you!

@george1421 noted. When I was initially testing, I did not know this and it took some digging in the forums to find this tidbit of knowledge. Given that having separate storage groups stops replication between the nodes in my mind it makes most sense to have a more distributed setup of normal servers at each site to handle all of my requirements. Thanks for the input!

@Tom-Elliott Cheers, works as expected now!

@george1421

Ok so the system in question has an on board nic (enp128s31f6), 1 single port Intel PCI-E Gigabit NIC (enp5s0), and 1 dual port Intel PCI-E Gigabit NIC (enp3s0 and enp4s0).

So I booted the system with a Linux system rescue USB key. The network cable is plugged into the single port nic. You can see that it has the IP address 172.16.57.22 was fetched. Without any issues. The mac addresses on the identified nics are:

enp128s31f6 - d4:a2:cd:b7:17:f2 enp3s0 - 00:13:3b:50:b2:b0 enp4s0 - 00:13:3b:50:b2:b1 enp5s0 - ec:08:6b:04:f9:d9 (the one that is attached to the network cable)

SysResecue-Image.jpg

Now when I boot the system up into debug mode with FOG into the FOS environment it seems whatever port is pluged into the lan it adopts another NIC’s mac address as shown below:

FogClient-Image.jpg

Now you can see when the fog client boots the mac address changes on the port that is connected to the LAN as:

enp128s31f6 - d4:a2:cd:b7:17:f2 enp3s0 - 00:13:3b:50:b2:b0 enp4s0 - 00:13:3b:50:b2:b1 enp5s0 - ec:08:6b:04:f9:d9 --> Changed to 00:13:3b:50:b2:b0 (the one that is attached to the network cable)

Now I’ve plugged the cable into enp128s31f6 and setup dhcp on that port as well and tested it. When the fog client starts all of sudden the enp128s31f6 has another NIC’s mac address…

Just a re-cap if I pull the two network cards, and do the re-image on the system I have no issues. It only occurs when I put an additional nic into the system… Any suggestions?

@Tom-Elliott Thank you so much Tom, as always I appreciate your support and guidance.

@Tom-Elliott thx👍

Hi everyone, and thanks for your answers.

Good news! If FOG works for you, it’ll work for me too (comming soon).

@mashina said in Issue when I tried to make Windows 11 gold image:

I am not aware of any completion message on the server. As far as I know, once the progress bar in the Task tab reaches 100%, the image has been fully cloned to the computer. Can you confirm if that is what you are seeing?

In the PC client, yes it’s exactly this message appears

@mashina said in Issue when I tried to make Windows 11 gold image:

Based on your description, it sounds like your configuration is not capturing the boot partition. As a result, when the image finishes deploying, the system cannot find a valid boot mechanism and falls back to network boot.

I’m looking at the clone I made on a test PC, and I can see using diskpart that the BCD was created correctly.

The files are there.

I tried rebuilding the BCD using the commands.

509 / 5000
Hi everyone, and thanks for your replies.

Good news! If FOG works for you, it’ll work for me too (eventually).

I’m looking at the clone I made on a test PC, and I can see using diskpart that the BCD was created correctly.

The files are there.

I tried rebuilding the BCD using the commands. The output is correct, but Windows won’t boot.

boot C:\Windows /l es-es /s X: /f UEFI

@pilipp_edv said in Issue when I tried to make Windows 11 gold image:

d8eb6692-2fff-4250-9ce8-9bf34f1e1183-image.png

I have the same configuration in my server.
But i tested the others options (im not used DD)

I don’t know what other options I have to check.
Do you know of any logs where I can find more information?

Regards

@Tom-Elliott What’s the difference between the full and quick registration processes then? because AD join exists in full, but not in quick…

Ok, nevermind, did the git thing, got it working, cheers 🙂

@Tom-Elliott Hi Tom,

Thank you, that clarifies a lot. I now understand that hostSecTime represents the expiration time, not the creation time, which fully explains the consistent +30 minute offset I was seeing. That part now makes sense and resolves my question.

The only remaining actual issue I’m trying to understand is the snapin behavior: in several cases, snapins did not execute on some hosts. I don’t see any errors in the logs. Only that the snap-in task doesn’t start, but I will work on this and gather some more data. Thank you!

@Tom-Elliott Yep, I caught that workaround in the earlier post. I moved the image folder from /images/dev to /images, but still resulted in the same error.

One thing I noticed this morning, is that the image capture process is hanging at 99% on the task page, as in for at least 45 minutes. Not sure if that is a symptom or the cause.

The previous post was suspect of a very recent init version – but i’m on the most recent dev-branch.

Thank you!

Thank you george1421 that 's was the solution.
I was troubleshooting remotely, and the technician on site insisted that images had already been downloaded onto it.

I understand your point of view, but I also have to remain anonymous to my colleagues.

Solved !

I am confident I have ruled out NFS. I can now connect to the NFS from localhost and Ubuntu to /images & /images/dev without issue and all the permissions that come with it. The only thing failing now is FOG, any guidance would be great!

@rodluz
Problem solved - the disk with the image was damaged

@romprager The simple answer is depends on the iso image and what OS will boot from the ISO image.

I do have several how tos in the forum that shows how to net boot several different installers.

https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

@rodluz I know you were talking to the other person, but if you like you can send me the kernels for testing.

@Sebastian-Roth Can I bother you with this quick question ^^^

@lmoysidis I’m not using fortigate but check out the following article: https://docs.fogproject.org/en/latest/installation/network-setup/proxy-dhcp/?h=
I needed to dynamically assign a boot file based on vendor class and dnsmasq did the trick!