@Sebastian-Roth The latest build worked. I’ll try and put this in a new thread later today.

@Sebastian-Roth Just for reference: I could never make that work correctly on 2008. I may have missed something or two, but I messed with trying to get it to work for a day or so and gave up. Maybe someone else better than me can get it working.

@Quazz @george1421
Thank you both for your answers, appreciate it. I started with the easy solution suggested by Quazz, and it fixed it!
Now running trunk 6677 and the registration just works fine!
Thanks a lot.
Next time I have a problem, I’ll update first, then post on the forum 🙂

@Sebastian-Roth Doing my best. 😉

Marking this solved as I am absolutely sure that using newer kernels will make this Intel i210 NIC work!

I am solving this as others were able to capture and deploy on those HP stream 11 gadgets with the most current version of FOG trunk!

Ok, marked as solved for now. People who want to keep following, see here (mind this is about PXE booting a Surface 4 now).

Thanks for reporting back. Moved to “Hardware Compatibility” section and marking it solved.

@Psycholiquid Oh, ok. I think I might suggest trying to capture your image using different OS types - specifically Linux. See if that works.

Thank you guys! It seems to be that GPT Problem. After doing the fixparts command and deleting the GPT entries now I can upload the machine 🙂

Hopefully deploying them will work in the usual way 😉

THANK YOU!

Sort of a side note but advanced task debug download/upload should also now work properly.

@Aaron-Kearns said:

However, that SOMETIMES works and other times does not.

What exactly does that mean? Can you please take a picture when things go wrong andupload it to the forums. There is no chance we can help you if we don’t know exactly what goes on.

So SSD does not want to play with FOG from what I get. Please try booting any kind of live linux DVD (e.g. ubuntu) on the 3020 with SSD installed. If this comes up please run commands lsblk and cat /proc/partitions - take a picture for us.

Upgrading to trunk might fix this for you but I can’t tell for sure.

@Wayne-Workman I believe that would be a right thing to do.

@george1421 @jloke

Here’s a DHCP class example I just made up to match the example I posted below.

class "Legacy-Specific" { match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00000:UNDI:002001"; filename "undionly.kkpxe"; }

Of course, the ending bits will be different for others, and you’d want to set this class above the other legacy class so that this matches first and the more generic one matches second, then you’d set the filename you want.

Thanks for letting us know! I am so glad that this has been fixed now.

@Tom-Elliott Yes, I just did. I marked it as unsolved when it broke again.

As Tom already asked: Where do you want to see those drivers being added to? Is this nexcom thing your FOG server? Then you need to see how to add the drivers in Ubuntu. This does not have to do anything with FOG.

While this doesn’t appear to be a FOG problem I did a quick google-fu search (as I’m sure you did).

I did find this article. https://forum.acronis.com/forum/70905#comment-252812

Can you confirm that post deployment the dell utility partition is marked as active as listed in the above post?

As always, its helpful to know what OS you are trying to deploy and what version of FOG you are running (the numbers in the cloud on the FOG management page will tell us a bit more than just 1.2.0 or such)

@Tom-Elliott
I know that.
I am just irritated that the network card seems to work with the same kernel version on one server and not on the other. and coming down to wich arch it uses seems kind of strange to me.

Are there any information or screenshot i could provide that could help to further look into that?

thanks a lot.

Sounds a bit like you have two DHCP servers answering clients’ discovery requests in your network. Sometimes they pick up IP and PXE information from FOG and sometimes they pick up whatever the other DHCP server provides (probably only IP without PXE info)??? Just a wild guess…