@Cris13 From the things you posted it seems you have the exact same issue than others using the same NIC model. The issue is specific to that NIC. I have spend hours of work over weeks to look into this and digging through the iPXE and Linux kernel code - source code of both drivers are very similar to some extend but only the iPXE code seems to have the issue.
I was unable to work on this in the last weeks but I still hope we can somehow figure this out and make it work again. It’s just a matter of finding the right needle in the hay stack (more than 8500 lines of C code). Are you keen to get into this. I can give you instructions on how to compile and debug iPXE.
Did you copy&paste the filename into the Unifi DHCP settings page? Maybe just clear the setting and re-type by hand to make sure there is no hidden character in that filename field. I can clearly see 0xff in the PCAP file… So either the Unifi DHCP is doing something really weird or there is a character in that field.
@veresh The commit says the packages were added to enable compilation of iPXE binaries. As far as I understand the compiled iPXE binaries are (still?) pulled from the repository anyway, so I guess it’s to allow for updating (or modifying) the binaries manually without updating FOG
so we can install all the required software from our file servers
I would challenge you, that you don’t “need” to connect to the domain to map a drive to your file server to install software. If there are applications that require AD credentials to install, then those should be installed post imaging via a snapin or some other software deployment tool like PDQ Deploy.
The only software that I “must” install after imaging is our antivirus software because that application creates a unique GUID when its installed to identify the machine to the AV console. its not possible to clone a system after AV is installed because of this. But most all other applications can be installed before imaging without AD rights.
I would think that’s up to the software drivers themselves. Simply doing “IP Printer” would not be sufficient. For this I’d recommend installing the printer fully (via IP_port as possible) and seeing that the driver is likely not pre-installed on all the machines, I’m not sure that you’ll be able to regain the functionality (Maybe if you inject the driver before imaging?). Once you’ve installed the printer and can validate it has printing and scanning capabilities download the PrinterManagerHelper.exe
This should give the exact config you would use for configuring your printer in fog.
The blue part clone does show up on the client and does act like it went through on the client …
What do you mean by “does act like”. Does it actually read data from the drive. I mean do you see the byte count go up at reasonable speed or does that jump as well? Sorry if this sounds stupid but I just haven’t got an idea yet. Maybe you can take a video of the client screen while this is going on. Possibly there is something that jumps at us.
@Greg-Plamondon The new video is interesting as is seems to show that it finds the interface eth0 but is not able to bring it up within 35 seconds. What kind of client model is this? Are you able to FOS boot this very same machine at a different location? I kind of doubt but what do I know.
@itcc I do – please send me yours. I’ve done million tests, I’ve had MS case open (we have EA with unlimited cases but you get what you pay for - shit) and the issue with windows.immersivecontrolpanel is plaguing us. If you don’t know about this in 1709 it has to do with search not working and from there IE and ton of other crap. The lousy fix is to copy windows.immersivecontrolpanel to each future user c:\users\xxx profile. As I said a lousy fix.
If anyone can share their working xml that would be awesome!
Look in the fogsettings file: cat /opt/fog/.fogsettings and look for the field called username. What is it set to?
This username is the only account that FOG will set the password for. The default is fog.
Generally, users of FOG are quite notorious for setting up the OS with an account called ‘fog’ even though every relevant wiki article and every thread on the topic advises against it. Don’t know why really, I guess the universe wants it that way.
@george1421 It is that model. And I am using 1.4.4 Fog (noticed there is 1.5) I honestly spaced checking the firmware I did see a 2013 date for it though which might be the issue. I work for a small company it is just a clients computer so I may see one again I may not kind of thing. If I get another one I will have to check the firmware I think you probably on to something. Thanks for the help again @george1421
@chris-whiteley Why not just put a fog storage node on the other side of the link. Then you wouldn’t run the risk of over committing your WAN. You can define a specific replication bandwidth. That IS something that fog can manage. You could even use an older dual core desktop computer as a FOG storage node. FOG Servers don’t need a lot of resources.