@Sebastian-Roth
No no, you’ve made clear that it is a lost cause trying to sort this out. If I had a clean capture and deploy on this version showing the system partition shrinking it would be different. Your comments made that clear. Thanks for the help.

@mig39 I would only turn off spanning tree on a switch where you have 100% control of the switch ports. If any of the switch ports are user facing I would not disable spanning tree. Your cisco switch should support rapid-stp or fast-stp. That is all that is needed. Then you don’t run the risk of a loopback taking down your network.

Can you upload the pcap of your pxe boot where PXE error T01 is thrown? I’d be interested in seeing why for my knowledge, especially if this is the only model giving this error?

@Hoghsfoot Search the forums for “persistant groups” to understand that FOG has a different concept of the group settings than you think.

Here are the screenshots your requested

Screenshot from 2019-03-21 10-21-20.png

Screenshot from 2019-03-21 10-23-22.png

I’ve changed fog user password to what was written at the bottom in web UI -> Storage -> DefaultMember as you just said, and it worked perfectly ! I just uploaded one more Image and no error - task complete and I am able to deploy it. Thanks a lot guys !! ISSUE SOLVED

@george1421
Increasing PHP-fpm memory did the trick.

Thx for the thinking together.

@nehsa said in Create scheduledtask via POST to API:

“minute”: “30”,
“hour”: “5”,
“dayOfMonth”: “",
“month”: "”,
“dayOfWeek”: “*”,

This all depends on the type of task this is to do:

The json elements that you can set:

{ "name": 'Some Name', // Optional "description": 'Some Description', // Optional "type": "C", // C = Cron, S = Single "taskType": 1, // ID of the task type, 1 = deploy, 2 = capture, 3 = debug do not use this one, 4 = memtest, 5 = test disk, 6 = disk surface test, 7 = recover, 8 = multicast, 10 = inventory, 11 = password reset, 12 = all snapins, 13 = single snapin, 14 = wake up, 15 = debug deploy, 16 = debug capture, 17 = deploy no snapins, 18 = fast wipe, 19 = normal wipe, 20 = full wipe "minute": 30, "hour": 5, "dayOfMonth": '*', "month": '*', "dayOfWeek": '*', "isGroupTask": 0, // 0 = host only, 1 = group task "hostID": 1, // If is grouptask is 1 this will be the group id, otherwise the relevant hostID "shutdown": 0, // 0 = restart, 1 = shutdown "other1": "", "other2": "-1", // Snapins either the id of the individual snapin, or -1 for all. "other3": "fog", // The username who created the task "other4": true, // Wake On Lan? "other5": "", "scheduleTime": "", // Only used for delayed time in which case you will need a valid unix timestamp in the future. "isActive": 1, // 0 or false would mean the task is not active currently. "imageID": 1 // The image ID in the case it's an imaging task. Can be any imageID you want. }

Much thanks, George and others for the help. As well as saving my company thousands of dollars! 🙂

@george1421 You are the man! That was it! I made the changes and the menu came up. It was the - before the Windows 10 1809 - Office 2013 image

@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!