I know it’s been a while since I posted this announcement, but I’ve been kind of keeping up with @Sebastian-Roth with his code changes with 1.5.5 and how they apply to 1.6 as well.
Remember, for the most part, the backend side of FOG is staying the same with as minimal of changes as I can. What this means, is many of things in terms of overall performance and functionality that has been going into 1.5.5 can be relatively simple to apply to 1.6.
There are some caveats to this though. But I think things are looking much better than they had from the initial posting of this.
I know it’s the holiday season and I hope everybody enjoys it. I think this is all the more reason to apply the post so it can be viewed a little more readily.
Thank you all.
Sorry to revive an old thread again, but like another person mentioned, I think it’s good to keep the knowledge combined into one thread. I understand that this thread was posted with the intention of supplementing an incomplete UEFI implementation on older computers that lacked UEFI PXE booting.
Is it possible to use this process for new devices (Microsoft Surface tablets, Lenovo Carbon X1 laptops, etc) that lack a built in Ethernet port? I understand that PXE requires drivers built into the computer’s firmware, which aren’t available for generic USB > Ethernet adapters. Is it possible to create the USB-booting PXE launcher, with a driver for a particular adapter wrapped into it?
Where I work, we have two network segments (build and production). Both have connection to the Internet, as well as basic communication between them (employees on the production network can connect remotely to a computer on the build network to QA the finished build, and computers on the build network have access to network shares on the production network).
However, I think when those built computers move to the production network, they lose touch with FOG. I really like the idea of using FOG’s inventory, snapin, and printer services, but those would be pretty limited if FOG can’t reach across. Is it possible to set something up so that I can push snapins, review login history, etc when the computers are on the prod network?
Then again, as I think about this post further, is that already possible / active? I haven’t specifically tested it, but on prod, the computers can ping the FOG server, so maybe the FOG client can still check in? I think PXE probably doesn’t work because of the different network segmentation, but that part may not matter as much. I’d like your thoughts on this. Thanks!
Certificate is not from FOG CA
Seeing this in the logs meant that you are probably using a different CA certificate on your FOG server. Is this correct? Did you manually install certificates?