@sebastian-roth Yes, I was able to capture and deploy to a smaller disk but it was Windows 10 20H2, the newest version, that I used.
I am currently building a 2004 master machine though as we are having issues with our exchange server on the new 20H2 build. I will be capturing and deploying that image today. I’ll let you know the results.
@sebastian-roth Great, that seemed to have worked perfectly. I was able to capture and deploy my image now and confirmed that it used the new init-201114.xz. Thank you very much.
@sebastian-roth Sebastian, I’m having this same issue and would like to try with the init.xz. How would I go about doing so?
Good afternoon all, is it possible to change the FTP service used by FOG (vsftpd.service) to an SFTP service? Thank you in advance.
@george1421 cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)
VERSION_ID=10
@george1421 uname -a
“Linux raspberrypi 4.19.97-v7- #1294” … “armv7l GNU/Linux”
@Sebastian-Roth I’m using Raspbian on a Raspberry PI 3B+ … FOG 1.5.8
@george1421 I’m using Raspbian on a Raspberry PI 3B+ … Let me know if you need any more info/error logs
I was able to replace “libcurl3” with 'libcurl4" in the config.sh file and that seems to be working.
Good afternoon, I am trying to install the newest fog version but it is failing at the same spot each time. It goes through the installation prompts then starts installing packages, when it gets through the packages to the step “Installing now everything is updated” it is failing. The only package I see that failed install is libcurl3. I tried to install this package manually but it says “Package libcurl3 is not available but is referred to by another package” and prompts me to install libcurl4 which I already have…
I have never had this issue installing fog in the past on this same device. I have tried multiple devices on multiple networks but am getting the same error each time. Can anyone lend a minute? Thanks.
@george1421 Looked into this and it is exactly what I am looking for. Thank you very much George.
@Sebastian-Roth Yeah after writing this I’ve found a few computers where it launches the OS after failing the PXE boot and others it just gets stuck on PXE boot. I’ll have to further research. Thank you for the reply!
Hey, yes they are all differing Dell OptiPlex models. Mostly OptiPlex 5050 and 790s
Good afternoon all, I am trying to set up a fog server to remotely image computers to deploy Windows 10 to my company without having to visit every store.
In order to do this, I need to set the Onboard NIC as the first boot option so if I reboot a computer it will automatically launch into PXE boot. However, after I change the boot options while onsite, I will not be imaging the computers until a later date. So I need to keep Onboard NIC as the first boot option until after imaging is completed.
The issue is if Onboard NIC is the first boot option and the computer is restarted for some reason, it will boot into PXE boot and continue to fail since there are no TFTP offers. The employees that are onsite at each store generally have very little technical knowledge so I’d like to avoid having to have them F12 into the boot options and choose the hard drive each time a computer is restarted or turned back on.
What I’d like to know is if there is a way to make it so the computer tries to PXE boot, then if that fails it moves to the next boot option and boots to the hard drive instead of just PXE booting, failing, rebooting then going back into PXE boot.
Or, alternatively, is there a way to initiate PXE boot into FOG imaging without booting to the Onboard NIC?
As always, thank you in advance for the support and the opensource software.
Next Server IP address was wrong on DHCP server. TFTP is working now! Thank you @george1421
@george1421 Also, this was run on the client with IP 10.99.98.51. I believe it is event number 2 on the file in wireshark
@george1421 Sorry for the delay, you can find the output.pcap file at the following link: https://we.tl/t-rfJtwU2wsu
Let me know if this is not correct and I can try again.
@george1421 The DHCP server is actually set up on the switch itself. Sorry for the confusion. Let me get that capture for you now. And yeah I had an issue previously where I tried to switch the IP and found that in some places the new IP took and in others it was still trying to use the old IP. Since I’ve set up the RPi with a fresh install of Raspbian the IP of the fog server has not changed from 10.99.98.50.
Good afternoon good people,
I’ve set up a few fog servers in the past few months on a couple of Raspberry Pi 3 B+ and have had few to no issues for the most part. The company I work for however is in the process of a network equipment infrastructure upgrade. We are moving to Fortinet switches and firewalls. I am working on testing the fog server on this new equipment but I am running into an issue:
The Raspberry Pi is pulling IP 10.99.98.50 from our DHCP server at 10.99.98.1. During setup I’m using:
Network Adapter: Eth0
DHCP Server: 10.99.98.1
DNS: 10.20.8.74
Use FOG as DHCP: No
I’ve had our infra team set option 66 to 10.99.98.50 and option 67 to undionly.kpxe.
The setup works well, no issues getting into the management console. I added the client I am testing with. Now, when I go to capture an image, the Computer PXE boots, searches for DHCP, shows that it found the DHCP server then searches for TFTP and fails.
It searches for a few seconds for TFTP requests then says PXE-E32: TFTP open timeout
I’ve tried restarting the tftpd-hpa service, status says its ok. Tried reinstalling FOG multiple times, tried wiping my RPi and reinstalling the OS fresh and reinstalling FOG fresh. I’m not too terribly experienced with this so could somebody help me to determine where I’m going wrong? Could it be a firewall issue maybe?
Thank you in advance!
