Network Technician at Cayuga Community College
Found the issue! After some research and discussion with Cisco, we had to add “PIM” to the vlan on our core, even though both the server and client are both on the same vlan!
Used the command - ip pim sparse-dense-mode on vlan 1 interface and it started working like a charm! I really appreciate everyone’s assistance here. This will help our institution so very much.
As always, the community comes through! Not sure how this got askew, but following these directions I was able to fix the issues. The image pulled correctly and at the end updated the database info. The image is good, I am all set. Thank you again this was awesome!
@Tom-Elliott Good thinking, I just attempted that but it seemed to make no difference. My clients still seem to hang on the partclone screen. I did reach out to Cisco to check to see if my 6509E core switch has all the correct settings on it for multicasting. I also made sure the port the server was on is using “port-fast”. It worked like a charm the moment I plugged it into the edge switch. I will do some more testing while I wait for Cisco to answer me back. Sorry for all the back and forth with this, I really do appreciate this product, it’s developers, and the dedicated community behind it.
@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.
@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.
@george1421 I will certainly never try to upgrade CentOS forklift style again. You were correct I upgraded Centos from version 7 to 8. After the mess it created I took your advice and ran the FOG installer using “GIT” and it cleaned up a bunch of the issues. A BOAT LOAD of things were missing after the upgrade but now they are functional. Thank you for all the assistance, FOG’s community and dev team is top notch.
Finally finished a brand new image this morning where we started from a fresh Windows install. The image captured without an issue. I suspect the age of our previous image was to blame for the issues with the capture. I think recent Windows updates by Microsoft to the recovery partition may have modified the size or something else in those recovery partitions.
New image pulled using the 6.6.34 Kernel, and then deployed successfully as well. If anyone is having issues related to the errors I posted above, I would try the CHKDSK + defrag/trim, and if that doesn’t work I recommend rebuilding your image from a clean Windows install with the absolute latest Windows enterprise installer.
Thank you Tom and crew for all the excellent technical assistance!
Simply Installing “Postfix” on Alma Linux and rebooting the server did the trick. After the server came back up, I successfully deployed an image, and afterwards the email came through without an issue. Had all the information filled out appropriately as well. Thank you very much Tom!
Requesting a feature addition in the “FOG Settings > FOG Email Settings” section that would allow an admin to test whether or not email is working. This would be similar to other programs that have a “test email” button with a box of who to send the test email to.
Or perhaps some built in logic to test if postfix or other email prereqs that FOG needs to send email post image deployment.
@Tom-Elliott As usual Tom you are a genius. I had forgotten to add the individual search domains for our active directory domains. Once I added those, and waited the requisite amount of time you mentioned, the machines that are on came back and now I can see them in the interface. This was super helpufl and I sincerely appreciate all the effort and insight you folks give into this great product.
For those experiencing the same issue on mainstream linux distros, navigate to your “resolv.conf” config file located in /etc/resolv.conf and add your individual search domains. Test a ping to a DNS name via command line on the box itself, then check your GUI again. Took about 2 minutes for it to reflect and show for me.
I thought FOG used “sendmail” so I installed that on the box. I am working on FOG version 1.6, and i copied over the settings from my previous working FOG install, but I suspect the email software on linux itself not being configured is where the issue is.
We do have an internal SMTP server that I could relay to, if that is a possibility. I would just need to know where in linux to configure that relay. I guess what I need is where to start looking for email config using sendmail, or some other built in linux mail program.
Version 1.5.10.1629
Environment - Dell Poweredge server running Alma Linux 9.5
FOG client 0.13
We recently migrated to a new FOG server (Wanted newer/better hardware). While FOG installed, and is functioning when capturing and deploying images, the “OS Details” feature on the “Hosts” screen shows a red exclamation mark for all new hosts we attach. Previously on the old server, it would sometimes glitch and show the exclamation mark. Now ALL of them show this. Am I missing a setting in the FOG client or Windows firewall setting on the host PC? While the feature isn’t critical, it was nice to see all green across the board. Thanks everyone!
Version 1.5.10.1629
Environment - Dell Poweredge server running Alma Linux 9.5
We recently migrated to a new FOG server (Wanted newer/better hardware). While FOG installed, and is functioning, the email function that occurs post successful image deploy no longer works.
I installed sendmail on the linux server, and set the settings in FOG Configuration > FOG Settings > FOG Email Settings to match the settings on our old server. Is there something I am missing? Did I have to modify a config somewhere or something? Or add in settings to sendmail to get this to work? Any assistance would be appreciated as this was a nice feature we enjoyed.
Version 1.5.10.1629
Environment - Dell Poweredge server running Alma Linux 9.5
Not to dredge up an old forum post, but I experienced this same error after migrating from an old CentOS server to newer hardware and Alma Linux. (What apparently many are moving to now).
For me the issue seemed to be related to trying to pull an image from a laptop that had the previous client on it. I have 2 computers that I use as dedicated imaging devices, 1 laptop and 1 desktop. I uninstalled the old FOG client, but when installing the new client and attempting to point it to the server, I got the CA Certificate error mentioned on the “Pinning” stage of the install. I tried to find an old cert on the device itself, with no luck.
What I ended up attempting after doing a little digging was to add back the following Windows firewall rules. I did that, and it seemed to kick over immediately and installed on the very next try. I am unsure if this is coincidence or if the firewall rules truly needed to be on the device before installing. But it worked after that and I now have a successfully pulled base image like I utilized on the previous server. The rules I used in an elevated command prompt are below. Perhaps someone from the FOG community can comment on the accuracy of my firewall rules? Good luck and hope this helps someone in need!
netsh advfirewall firewall add rule name=“Fog Client” dir=in action=allow program=“%ProgramFiles(x86)%\FOG\FOGService.exe”
netsh advfirewall firewall add rule name=“Fog Shutdown” dir=in action=allow program=“%ProgramFiles(x86)%\FOG\FOGShutdownGUI.exe”
netsh advfirewall firewall add rule name=“Fog Tray” dir=in action=allow program=“%ProgramFiles(x86)%\FOG\FOGTray.exe”
netsh advfirewall firewall add rule name=“Fog Update Helper” dir=in action=allow program=“%ProgramFiles(x86)%\FOG\FOGUpdateHelper.exe”
netsh advfirewall firewall add rule name=“Fog Update Waiter” dir=in action=allow program=“%ProgramFiles(x86)%\FOG\FOGUpdateWaiter.exe”
netsh advfirewall firewall add rule name=“Fog User Service” dir=in action=allow program=“%ProgramFiles(x86)%\FOG\FOGUserService.exe”
UPDATE
After some investigation, I found that if I connect to FOG using the FQDN, the Kernel versions show. If I connect via IP address, which I had been previously, it doesn’t show. This was on a machine with our Endpoint protection enabled. On a machine without any endpoint protection, both IP and FQDN show the Kernel versions. Strange, must be some sort of overzealous web protection on the part of our endpoint software. Thanks for your help @Tom-Elliott !!!
@Tom-Elliott Correct, in yours you see the bzImage and arm_image, but in mine it is totally blank for some reason. Been like this for quite a while and I have no clue what I did to cause it. Unless it is potentially just a browser issue or something with my PC only?
Current version - 1.5.10.1598
Several versions ago, I found t hat under the “Kernel Update” tab, it no longer shows me which Kernel versions I have installed. If I clicked on “Default Member FOG Version: ()” it would list what versions of the kernel were installed. It stopped working some time ago, and I didn’t mess with it. Is there an easy fix for this? I have tried updating and a few small changes but no luck. Not a huge deal, but would like it back if I can. Thanks everyone!
