@Tom-Elliott, thanks. I believe we can close this thread. Things are working now as far as a Capture/Deploy aspect goes. I’m having issues with my images not joining the domain. I have done some reading here and all of my settings appear to be correct. If I can’t get it working, I can start another thread.

Thanks for all of the help. There is no way that I would have got this working without you guys. Thanks.

I was using the Factory image that came on the device from Lenovo. It was Win 10 and I updated it to Win 11 and we were getting the issues.

I wiped it clean, and loaded a new instance of Win 11, and everything worked fine afterwards. Looks like after disabling Secure Boot, all other issue were with the device. We now have a working images. Thank you for all the help.

I disabled Secure Boot and it did allow me to register the computer in FOG. I created a new image so I could Capture a new image, but I don’t see an option for Windows 11 in the images. Should I use Windows Other, Other, or do I need an update?

I created a new Windows 10 Image as a test, and when I try and run a Capture it starts, but doesn’t complete. I need to investigate the error. BitLocker Signature in partition, need to disable BITLOCKER. This is a new computer to us with the default image, so I wasn’t aware it had BitLocker on it.

Your version of FOG is up to date.
You’re running the latest dev-branch version: 1.5.10.15

We are in the process of replacing all the computers for our organization. We are using Lenovo Win 10 machines that we deployed using FOG, and we are replacing them with a newer version of the same PC.

I have updated the computer and we are looking to create a base image for the computer. Every time I try and boot to the network I get a Secure Boot Violation. Invalid signature detected. Check Secure Boot Policy in Setup.

I have went through all the settings, and I can’t seem to get it to boot to FOG. I have a new Desktop, Laptop, and Tiny that we are attempting to image, and they all have the same issue. I’m not sure if it is the PC or FOG at this moment, so I came here looking for advice.

I thought I found my mistake, but it didn’t help. While updating the www.conf file, I made a change to one of the values, but didn’t remove the ; at the beginning

;php_admin_value[memory_limit] = 256M

is now 

php_admin_value[memory_limit] = 256M

Here is a list of all the settings I have enabled in the www.conf file I have.

[www]
user = www-data
group = www-data
listen = 127.0.0.1:9000
listen.owner = www-data
listen.group = www-data
pm = dynamic
pm.max_children = 35
pm.start_servers = 5
pm.min_spare_servers = 5
pm.max_spare_servers = 3
pm.max_requests = 2000
php_admin_value[memory_limit] = 256M

sudo systemctl start php7.1-fpm.service
Job for php7.1-fpm.service failed because the control process exited with error code. See "systemctl status php7.1-fpm.service" and "journalctl -xe" for details.

I ended up updating the /etc/php/7.1/fpm/pool.d/www.conf file. The values below are what I currently have.

php_admin_value[memory_limit] = 256M
pm.max_requests = 2000
pm.max_children = 35
pm.min_spare_servers = 5
pm.start_servers = 5

sudo systemctl restart php-fpm
Failed to restart php-fpm.service: Unit php-fpm.service not found.

When I went in to edit the www.conf file and searched for it there was a single result the first time. I opened it and made the changes you requested, and the
php_admin_value[memory_limit] = 256M was already in there. The value was 32M, but it was there.

Now when I do the same search, there are multiple responses.

find /etc -name www.conf
find: ‘/etc/cups/ssl’: Permission denied
find: ‘/etc/ssl/private’: Permission denied
find: ‘/etc/vmware-tools/GuestProxyData/trusted’: Permission denied
find: ‘/etc/polkit-1/localauthority’: Permission denied
/etc/php/7.1/fpm/pool.d/www.conf

I made these changes, and performed a reboot. . . and now FOG will not start. I ran through the install again thinking it may correct the service, but that didn’t help either. When trying to go to the FOG address in a web browser, I’m just getting Service Unavailable.

When I did the search for the www.conf file, there was only one. So I’m sure that I was editing the correct file. I just wish I would have written down the original values now.

I have a default image that I use for a majority of my computers, and everything has worked great in the past. I have deployed the image, updated it as needed, and captured an updated copy multiple times. For some reason this is no longer working.

I just updated one of our Windows 10 images to 1803, added an application, and updated all the runtimes. Afterwards I shut the computer down, then set up FOG to capture the image.

The computer will boot, act as if it is sending the images to FOG, however it never finishes. I can watch the status in FOG on the Task Management, and it progresses as it should. After some time the computer finishes, and reboots. I’m able to log into the computer with no issues, and everything looks fine. After checking FOG, the Task Management shows the image sitting at 79% and does not move any more. I have left it for an hour or so just to be sure and there is no change.

I have tried multiple times now with different images, and I get the same indication on all of them. I’m currently using FOG version 1.5.4 and we are trying to image our Lenovo m900 Tiny computers running Windows 10 x64.

I’m not sure if I should delete the information in the /images/dev/ or if I just need to change a setting somewhere.