@browolf Are you running into the CPU stall issue too?

@Sebastian-Roth Brilliant. Thank you so much!

@Sebastian-Roth
I have 70 same model PCs and same SSDs. The PCs were purchased at the same time and were configured on the same day.

@Sebastian-Roth said in Adding needed repository... Failed!:

@Wayne-Workman The installer test seems absolutely fine but possibly that’s because you have the package software-properties-common pre-installed? Can you check on that? I have had a look at the logs from your installer tests but the package is not mentioned and that’s why I guess you have it pre-installed…

Yes, it’s pre-installed. This is on Ubuntu 18.04 server, minimal installation.

root@ip-10-0-0-165:~# dpkg -l | grep software-properties-common ii software-properties-common 0.96.24.32.7 all manage the repositories that you install software from (common)

Will do.

@EricLA2K Thanks heaps for keeping us posted. I am fairly sure this will help other users as well!!

@jcabuco Yeah, in gernal that’s right. But switching forth and back is not very convenient. You might want to look into setting up dnsmasq as ProxyDHCP as George suggested at some point.

@nevinconstantin Please keep us posted on the issue and if and how you were able to solve this.

Resizing to a smaller disk does actually work in many cases. So it is not something FOG is unable to handle in general. But there are partition layouts where the later partition(s) prevent from a full resize.

@Sebastian-Roth
Yes, problem solved. The error is gone (sorry for the bad photo):
https://photos.app.goo.gl/ZhWkYuHLTwndZBZPA

Thanks!

@Quazz ok, then i keep my already downloaded kernels/inits, and wait for next release for further tests.

Hey,

Thanks again, it’s ok on both Vms and 3050 with “REFIND_EFI” Bios Exit Type.

We can pass this post in resolve state.

Have a good day.

Hei 🙂

As Sebastian stated, for a domain join to function the Host will have to have the client running.

Information here https://wiki.fogproject.org/wiki/index.php?title=FOG_Client

And for further questions, have a look around the wiki first, it will answer many questions. Anything not listed there people on the forum will be able to help you with. The Developers are VERY active and great 🙂

Sorry if me message there sounded short, that was not my intention. I simply wanted to inform you of the plugin that would do exactly what you were asking.

There is some documentation on how to use the location plugin too, for the future.

Mind you, you can do this is “Central GUI Server->Storage Nodes about” layout, or really however you feel appropriate for your environment.

Location plugin will likely get an overhaul in the next few years (yes years) with more automating of how to select which storage node’s based on subnets/ip ranges, but for now it’s completely manual (and thus extremely granular too).

https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

OK Well I solved my own issue. Had to retrace my steps and go all the way back to the beginning. When I set the IP and everything in the cfg file I had a dash instead of a equals sign next to the gateway.

My bad but glad I caught it. This only goes to show that you should not work in linux until the coffee has kicked in… So this is solved.

@clugoimx Feel free to ask questions so we can help you getting up to speed with your setup.

@Sebastian-Roth Sometime we have a problem before the PXE menu. The PXE boot is waiting for an IP, and don’t receive it. Or some time, PXE says to check cable… I have no idea else a bios or hardware problem, we do try by changing switch, and put directly the fog server and client on same switch no change… per ups we have some hardware series problem, but only on PXE it’s strange

Done testing and I can confirm that AOMEI Backupper causes the problem.

I re-captured the image using dism, injected the install.wim into the install media, installed from it (essentially allowing Windows installer to re-create the EFI and MS reserved partitions) and now the restore works perfectly.

This error still appears:
https://photos.app.goo.gl/7UWrM7y2dNgELa8E9

But it has no negative impact on capture or restore.

So, the bottom line is that, from now on, I won’t capture any drives that were restored with AOMEI.

AOMEI is a very good free tool, I’ll still use it but only for images that go to the final user, not images that are captured for deployment.

Had the same issue, reverting to 4.18 kernel solved it.

EDIT:

on debug mode the
ip addr show had network interface visible but without proper address
udhcpc failed to get addy
sorry no lspci was in a hurry

@Tom-Elliott Thanks!

For now, I have created a fog AD user that has rights to join the domain. the only issue with that is the helpdesk tech needs to have one of the domain admins remove the PC from AD if it’s preexisting.

I have since messed with my setup and no longer have the error. Sorry but I did not get a screenshot of the warning.