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.
I’m using the following. . .
FOG version 1.5.2
bzImage Version: 4.15.2
bzImage32 Version: 4.15.2
When I looked at the images, there are some in both locations, /images/ as well as /images/dev. The last two that I tried to do are in the the /images/dev folder, which I believe is incorrect?
I started the process and let it capture, however I wasn’t around at the end of the process either time to see if there was a message on the screen of the PC being captured.
We created all of our images about two years ago, and haven’t had the need to create anything new. Yesterday, we needed to create a new image, but I’m having issues. I created an image just like I always have, and when I captured the image from the host it worked as it should. The issue is that I still see the task in Task Management, and the status is In Progress. It has been like that since I left it yesterday afternoon.
When I go and look at Image Management, it shows that the Image Size is 465.87 GiB, but the Captured date says Invalid Date. I’m not sure if there is something I am overlooking, or if I have done something wrong. Thanks for any advice you may be able to give.
@george1421 We currently use Veeam Backup, and I was going to make another backup with that later. It is just that the other employees in the office understand how to use FOG, where they don’t necessarily understand Veeam the same way. I was just trying to make it easier for them.
@george1421 We are making an image of the server in case of hard drive or software failure. It took us, working with the Vendor for the application this is going to support, about 2-3 weeks to get it all up and working. If something we to fail, we would like to have an image to restore to similar hardware. The only portion of the hardware that I don’t currently have is the RAID card. If I had another, I could test the restore process. I’m not willing to try it on the current install, just to see if it works.
It has RAID, and I believe we had it configured for a RAID 1. If I do Windows 10, Multiple Partition image, single disk (not resizable), you think it may cause issues? Of course I don’t have another box with the same hardware to restore it to and test. Even if worse case scenario was to restore this image to a single disk, I would be happy. That I can test though.
I wanted to see if anyone has had any experience using FOG to image Server 2016. I looked at Operating Systems that can be imaged with FOG at the link below, but I didn’t see any reference to 2016. I saw some for 2003 and 2008, so I was assuming I could just choose a Windows 10 image, and should be good from there? Just wanted to see if will work. Thanks.
https://wiki.fogproject.org/wiki/index.php?title=What_Operating_Systems_can_be_imaged_with_FOG%3F
I applied the most recent update, and I am now able to register and multicast again.
Is there any benefit to updating all the time if there is also the potential to have things not work? Maybe I will just leave it how it is for now until our computer roll out is done.
@Wayne-Workman was able to do some testing, and after forcing it to use port 9000, we could get it to work. For some reason over the last few days it has now stopped working. I’m not sure if it has something to do with an update or not? We have made no changes to the network, and it was working while imaging the last 100 computers are so. We have just been using the deploy option, but with multiple computers at the same time it can cause a lot of latency on the network.
We have been working through it, however for some reason we can’t register hosts now either. Every time I go in and register a host it shows up in Host Management, but it is named the MAC Address and isn’t assigning the image or the group. I’m going to perform another update now since it shows that I’m out of date and try it again.
@Wayne-Workman it isn’t working. The thing is, that once I set it up on the server by using the information on the troubleshooting page I get this information.
Udp-sender 20120424
Using full duplex mode
Using mcast address 234.15.31.20
UDP sender for /opt/fog.fogsettings at 10.15.31.20 on eth0
Broadcasting control to 10.15.31.255
Why is the mcast address 234.15.30.20 when the IP of my server is 10.15.31.20? The server and the test device aren’t talking at all right now.
@Wayne-Workman the settings for the network are correct in the Interface setting for the Storage Management. I do not have another Linux machine running at this time to perform the test. I will have to get a live-boot going and perform the test. I’ll let you know the results once I’m done.