Respectfully requesting a modification to the data “Image Completion Task” emails contain. The feature is excellent, one small request would be to add the following lines in the email sent:

Image Duration (in other words, how long the task took to complete)
IP Address of the host that was imaged

The image duration is the most important as sometimes we start images before leaving for the day, or sometimes our supervisor requests that sort of information about an image task. Thank you for your consideration!

@Sebastian-Roth

I suspect this already had the fog client at some point. We image the same machines over and over for various reasons in our labs and in our classrooms. Is this not supported by FOG? Is there some procedure I should be running before we image the machines or something?

From the GUI is there any way to search via mac address?

Thank you Wayne, I use a deployment program to install the client so I figured it should work just like the others in the lab did. It is odd, like 25 will work, and 4 will fail in one room. By “fail” I mean not show up in the client. Attached is the log. I notice the response module fails but I don’t know what that means.

fog.log

I have several hosts in several computer labs that don’t show up in the console when we install the FOG client. They just never show up in pending hosts or in “hosts”. It is possible we have installed the client on them previously and maybe that is the issue? I tried resetting the encryption data on all of the hosts but it didn’t change anything.

In any event, is there a way I can globally fix this? I considered that 1.5.9 might fix this issue as every update seems to fix problems all over the place but I was curious what the community thought.

I realize this post is a bit old, but I wanted to thank everyone for their suggestions and give our experience to back up what has been said in this topic already. We experienced an image that should have been about 120gb, but was showing in FOG as the full 500GB hard drive. After referencing this thread, it fixed the issue. The steps we took are below in order:

Verified that the PC didn’t have a second drive or second large partition it was capturing
Verified that bitlocker encryption was OFF using the command prompt command “manage-bde -off C:”
Ran Disk Cleanup (to get rid of old unused files)
Ran Tools > Check to scan for hard drive errors (may require reboot to fix)
Ran Tools > Tools > Optimize and defagment
Capture Image again

Once we did those steps, the newly captured image only takes up the actual amount used on the hard drive.

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

@Sebastian-Roth Testing with newer init with partclone 0.3.13 and kernel 4.19.101 seems to fix my slowness in deployment of images. I am seeing speeds of 9GB or more in my testing now. I am guessing it is the partclone that is causing the slowness in some environments. Will continue to test and utilize 0.3.13 partclone to verify theory.

@Sebastian-Roth Can confirm that after testing this in my environment with the new init (partclone 0.3.13) and the latest dev Kernel specified, things are back to fast again. Average in my environment was somewhere around 9/GB per minute.

@Sebastian-Roth My apologies if this is too forward, but would the latest build with 0.3.13 be able to be installed by myself as well? I would love to test 0.3.13 to see if it fixes my slowness issue as well. I would gladly report back my findings.

@64bitfury We only did the web UI. We ended up giving it a DNS entry, getting our commercial certificate, and then installing the cert in Apache on the server. It wasn’t FOG specific, it was more installing a cert on Apache that you have to go through. Have you had much experience in commercial certificates?

Do you mean just securing the web UI with a certificate? Or do you mean securing the client communication between the server and the client with a cert? I have done the former.

@Tom-Elliott I tried some newer kernels like 5.3.3 as well as what shipped with 1.5.7 (kernel version 4.19.48). I tried using the original version of init.xz but it claimed my memory was too low or something of that nature so I switched it back. The speed didn’t seem to change at all on any of the different kernels, almost like the speed wasn’t related to those kernels. Also as another piece of information I am using UEFI pxe booting with ipxe.efi as the boot file.

I just updated to 1.5.7.115 but no change at all. Just for full disclosure.

@Tom-Elliott It is possible it is something in my environment. Typically it is a single machine (imaged either via the console, or directly from the machine itself by a member of our desktop support team). It seemed related to the version because I first noticed it after I upgraded from 1.5.7 to the dev version of 1.5.8 and then later the dev version of 1.5.7.102. It went from like 12GB/min to 4GB/min or 1GB/min. The servers are production boxes so I can’t make too many changes without potentially affecting others but it still seems like it is related to the update I did. Perhaps the update of partclone? Also I noticed that when I pulled an image today for testing, the capture was super quick at 10GB/min but the deploys to the same machine and others like it were 4GB or less. I feel like I am missing something extremely mundane and obvious.

@Sebastian-Roth They are normal SSD sata drives for the most part. I was told by a member of the desktop team today though that they tried to image an Optiplex 7070 with an M2 solid state drive (the ram style drives) and it was around 1.4gb per minute.

I will certainly try to make some changes, but the fixes that came with the dev version far outweigh the speed issues I am having at the moment. Hoping some bug fixes in the 1.5.8 version will do the trick. I will keep testing as I can. Thank you all for your help for now!

@Sebastian-Roth said in Slowness after upgrade to 1.5.7.102 (dev branch):

file /var/www/html/fog/service/ipxe/bzImage533

Good catch, found the typo and got it to deploy. The speed is the exact same however. I stepped through all the steps, verified the 5.5.3 Kernel and the speed is around 950mb per minute. Way slower than my usual. Part Clone is .3.12, I tried using the old init.xy file from 1.5.7 but it claimed I didn’t have enough memory. Very very odd. Do I just deal with it until stable version of 1.5.8 comes out maybe?

@george1421 Tried the debug method, it booted from bzImage533 but it failed to start. Below is the error I recieved while attempting to boot using that bzImage:

@george1421 Oddly, when I deploy it doesn’t show any screen that mentions bzimage or xy.init.xz at all. Is this because I am deploying using ipex.efi for booting? I am actually a bit ignorant to what these files actually do? Does the kernel boot the host client, or does ipxe.efi boot the client?

@george1421 I watched during the deploy but didn’t see anything relating to which bzimage version it is using. Odd. I have a feeling it is still using the other bzimage. I am going to test by backing up the current 4.19.101 bzimage and renaming the bzimage533 to “bzimage”. Just a temporary test.

@george1421 said in Slowness after upgrade to 1.5.7.102 (dev branch):

/var/www/html/fog/service/ipxe

Just tried the new Kernel, I moved it to: /var/www/html/fog/service/ipxe and for the Optiplex 7050 in question I changed “Host Kernel” to “bzImage533”. Is that all I had to do to make that machine image using that 5.3.3 kernel? I didn’t see a way for me to know if I was using the right kernel or not.

@george1421 Thank you for these great instructions. I am going to try it now. I did see that the partclone version that was on the screen was 0.3.12 and the image pushed at about half the speed it did previously. I am going to try this new Kernel as I haven’t tested it yet, and will report back.