@64bitfury Eventuelly found the time to proceed on the wiki article. Find information on your question here: https://wiki.fogproject.org/wiki/index.php?title=HTTPS#Custom_CA_and_certificates Please let us know if the instructions are clear (and do work)! We can only improve things as much as we get feedback from users. :-)

@Sebastian-Roth https://imgur.com/a/j0WJInw

@Magiq Well if RAW works then you might try non-resizable image type as well. Suppose you have used resizable from the beginning?

We have another report on this: https://forums.fogproject.org/topic/14249/image-size-of-the-client-in-fog-does-not-match-the-size-of-the-capture-in-hard-drive @Ben-Acheff Still waiting for you to provide the contents of d1.minimum.partitions from your image.

@rmishra1004 Thanks for reporting. We have another user but I wasn’t able to replicate the issue yet and didn’t get the information needed to find what is causing this. Cross linking the topics so we keep track of this: https://forums.fogproject.org/topic/14160/image-size-on-client-incorrect Can you please post the contents of the text file d1.minimum.partitions here in the forums. You find that on your FOG server in /images/Win10LTS/ folder.

@TaTa said in Download speeds slow after upgrading to 1.5.8: On the web UI at the login window it says Latest Version:1.5.7, Latest Development Version:1.5.7.120 and on FOG Configuration page says “You’re running the latest alpha-branch version: 1.5.7.958”. Should all be 1.5.8 or later? Sorry for that. There were some minor issues in the version checking on our webserver. Fixed that just now. Thanks for letting us know. Ok, back to the issue. So turns out the slowdown is not between 1.5.7 and 1.5.8 but has been there with FOG 1.5.7 but only in UEFI mode. That an interesting one because at that stage I would expect there to be no real difference between UEFI and legacy boot. The Linux kernel uses a so call EFI stub for it to be loaded in UEFI mode but as far as I know should behave more or less the same after bootup either way. Sure there are differences like EFI VARs (/sys/firmware/efi/efivars) only being accessible in UEFI mode but I would think that most drivers should not see the difference. Please make absolutely sure this is happening on the very same machine (not just same model) and confirm.

Update: It works. The file ending was the problem.

Perhaps share how the custom task was created, what you’re trying to achieve etc so others can weigh in with suggestions? Above is not really much to go on. regards Tom

@Sebastian-Roth Also I just updated to 1.58 it went smoothly. I was worried when it forced a password on mysql, I screen capped it and so far everything is working. This kind of thing is so much more fun compared to Windows stuff.

@tech49 Let’s try to break this down to what is actually causing this. Is the image resizable or non-resizable? What size is the source disk and what size the destination? If destination is same size or larger I might suggest you try capturing a RAW image and deploy this just for testing.

@astrugatch Good to know this was caused by browser caching. I can imagine more people running into this. Thanks!

@dmoseley Can you verify the behaviour is different depending on the image you deploy to the exact same machine? I would expect BIOS version and/or settings to make the different. Or it’s model specific.

@AlexPDX You can ignore or disable the replication service on the storage node. It’s not really doing much.

@AlexPDX Those topics might help you: https://forums.fogproject.org/post/125438 https://forums.fogproject.org/topic/13486/fog-1-5-6-pushbullet-plugin-not-functioning (not a bug but a network issue)

@Mark-Shelton Thanks for the information. Please let us know if compilation works fine adding the wget commands as mentioned below. We shall add this as a bug fix soon.

Here’s the news https://news.fogproject.org/fog-1-5-8-officially-released/

@Skeer FOG 1.5.8 is out now: https://github.com/FOGProject/fogproject/releases/tag/1.5.8

@sokrina We updated the official kernel to allow for more than 8 CPUs. So you might just use the latest (version 4.9.101) or update your FOG server to 1.5.8 which was just released.

@cbittencourt So just for clarity you had secure boot enabled and you turned it off to resolve the issue?

@Sebastian-Roth Thank you for all you and everyone does. I agree with you this was a good choice to make a second topic out of. This is working well now and I greatly appreciate all the assistance!