Hi, thanks for your suggestions, i made another try i gave the first login more time, after 10 minutes the first login attempt worked, i maybe was to impatient usually a login doesnt take such long, every login attempt after that first one is working normally. Hmpf, i will try recreate the image from scratch to see if this impact occours again. Best Regards X23

@george1421 Thank you so much! It works now!

@george1421 I can almost guarantee that the problem would not move with the hardware. I have moved rigs from the secondary location to the primary before, as we are slowly downsizing this secondary site and moving stuff to the primary as we sell off video cards. I’ve used motherboard from here to replace boards at the primary location without any problems. I do have an empty rack at the primary location where I can move a couple of the rigs from secondary though and make sure it will work. I will have to do that at some point next week. I can’t have a rig dismantled over the weekend.

The figures seem much more stable now, much less fluctuations. Thank you @Quazz !

@zaccx32 said in Pxe-Boot gets hung up on TFTP: We do have two DHCP servers within the same scope that are for load balancing Make sure that both are setup to support pxe booting. We’ve see situations where one is configured and the other is not and the clients will get random pxe boots depending on which dhcp server responds first.

These laptops are coming with M2 Nvme disks, i used diskpart in windows 10 with “clean all” option to fix the problem. Yes all laptops are UEFI only I am building fresh windows 10 using one of the new Microsoft ISO files. I will try to capture an image from one of the laptops and try to deploy it to other. If this will not work we will raise a ticket with dell

Found and fixed in 1.5.9.34 Thank you,

@Sebastian-Roth @Jurgen-Goedbloed I have got the new theme working with scrolling toc and all. I think the top menu needs a little tlc https://fogproject.readthedocs.io Do we want to stick with this theme or revert back to the default theme, I know @Jurgen-Goedbloed mentioned he didn’t like it as much. I don’t want to go changing the readme with the structural changes if we’re not gonna stick with this theme. Personally I didn’t like it at first but it’s grown on me and it’s pretty easy to navigate.

@wmw509 Disabling CSM makes sense. I’ve seen a lot of bioses that if CSM is enabled it only lets you use the legacy/bios pxe boot. I’ve had that disabled on all my hardware for so long I forgot it was a thing.

@FOG38640 said in DHCP option 67: Is there an option for FOG to automatically choose between BIOS and UEFI? For what? For the network boot file? If so that is done by your dhcp server. What is your dhcp server? (its been a few days so I don’t remember, a quick scan of the thread didn’t answer that question either) Edit: found it way at the bottom Windows 2019 server. So there is instructions for windows 2012 and later. Hopefully it translates to 2019 dhcp servers. https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy

@Sebastian-Roth said in Feature request for FOG 1.6.x - Support GRUB as UEFI exit mode: So back to my point: Why would you chainload to another iPXE binary again for exiting? I don’t have a specific use case at the moment. So adding additional features without a specific reason may not be as valuable as I initially throught. Also I had a setback with grub. For some reason grub isn’t loading the config file that is uploaded, but using tftp to connect back to {next-server} (guess) and picking up the grub config file I had there. It is picking up the config file from there, I’m just not sure how it knows where to get the file from. Possibly from dhcp request. I’m still working with it, but grub isn’t quite as dynamic as I would have hoped to find uefi boot partitions.

@Matthieu-Jacquart Well that’s really interesting. It is known that Windows 2004 adds another revovery partition to the end of the disk. I have this on my list of things to work on for the next weeks. Though I cannot imagine how removing this partition can cause such issues you described here. It’s really over the top for a Windows installation to boot fine for a couple of times and then fail with such errors if it is for the missing recovery partition I would think. But well, I am a Linux guy and only scratch my head unable to understand the way MS is making up its world.

@altitudehack said in Smart Installer caching credentials causing AD lockouts - maybe?: It’s especially weird because I wouldn’t have been able to actually run the installer as a non-admin … Sorry for pointing the finger at FOG but it’s the only non-commercial software installed on this particular laptop that I installed under my non-admin account. Those two sentences don’t make sense to me. One is saying fog-client was installed using the non-admin account and the other says no. The fog-client installs a service that should run as local system account and not using AD-accounts at all. Though the fog-client is trying to join the domain on every cycle it runs. If your non-admin account is used as AD-credentials (FOG web UI -> host settings -> Active Directory) and the password was changed at some point I can imagine this to happen as described. But the AD-account would have to have rights to join a computer to the domain - don’t think a non-admin account can do this.

@eseelke While I do understand all of those topics are kind of related in your point of view they are actually not and I think it’s way better to open a new topic for each of them. Easier to follow and answer if things aren’t mixed up. I’ll quickly answer the questions for now but wait with the details until you opened those different topics. Give them names according to what each of them is really about! I have Quick Registration set to apply hostname, image, and group. It does all of this, but it will start pulling the image from the master host and not the local storage. Is there a way to force this? How did you make quick registration to apply the group setting to a host? Maybe this customization is preventing the location plugin to work properly. There is no other way to force this other than setting the correct location in the host’s settings. I have a small 1GB ISO for diagnostics in the menu. It works, but it always pulls it from the master host. I have it stored in each replicated storage. Is there a way to tell it to use local storage instead of master? This has been discussed recently. The FOG menu is mostly pulled from the master node. You need to tell it to load the ISO from storage nodes explicitly. For above ISO, is there a way to script it, so it pushes to each replication share at creation, rather than manually having to push it? Possibly, have it check the master and if file newer, push out to each? George answered this already. I have the FOG client installed on each system, but it doesn’t seem to check-in. I am only needing this in order to remotely shutdown or reboot systems. The log file on the client is blank. How can I troubleshoot this? If the fog.log file is empty the fog-client has never ever started on this machine. Windows XP is pretty old. Does it even have .NET Framework 4.5.2 (fog-client used 4.0 up until version 0.11.19 but we switched to 4.5.2 with release 0.12.0). Did the installation succeed? Is the service installed and enabled? As mentioned above I ask you to open different topics so we can discuss things in depth separately.

@Sebastian-Roth Hello, Sebastian, I believe the reason for why hostnames were not updating was due to the client not being up to date, however, after a name change, AD is still not updating, causing a trust relationship error when logging in and the domain does not change. Also, we a running 0.12.0 client version. Any other ideas on why AD is not communicating correctly? Thanks!

@george1421 said in Multicasting: @Goll420 bitlocker ref: https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/15 Very interesting, thank you. I imagine this was the problem for these machines.

The only way I was able to make it work was by loading the whole ISO file. :hbcd initrd http://${fog-ip}/images/tools/hbcd/HBCD_PE_x64.iso chain memdisk iso raw || boot || goto start by using the WinPE method I was able to boot but it couldnt find bootmgr in the wim file. I then tried to define the bootmgr and I was then getting errors regarding not being able to patch the wim file. in the end I just tried loading the whole Iso like with dban and lo and behold it worked, though it then limits you to a 2gb ram minimum setup.

@Tacolover99 said in New to this: Which I wanted but I notice that the internet was limited connected. So CMD, and found out the Thin Clint also inherited the IP Address from the other thin client. Check the original one and now that thin client is doing the same thing. Not to sure if it is DHCP problem when I cloned it. I think you need to explain this part in more depth. Probably best if you can post some pictures so we know what you mean by “limited connected”, “inherited the IP Address”, “doing the same thing”.

@dtkeith002 said in Acer Aspire A515-55 Connection Timed Out: Does FOG offer the ability to listen on multiple interfaces / ips at the same time? I haven’t dug into the config files to see. If so I can try a direct bridge to the server VM and bypass the network completely. Don’t think it’s worth going down that route. Testing on the same switch as the server should be enough to rule out most of the network related stuff. From the picture we see that it seems to be able to fully download the kernel (bzImage) file but times out on the initrd (init.xz). I would setup a mirror port on the switch and capture traffic on both ends - client port (using a notebook with Wireshark on the mirror port) and directly on the FOG server (e.g. using tcpdump). Use capture filters to restrict traffic to a particular MAC address (ether host aa:bb:cc:11:22:33). Please upload the PCAPs to a file share and post links here. If that doesn’t give us enough insights we might compile debug enabled iPXE binaries to analyze the TCP traffic - though this will a tough job! Have you tried using ipxe.efi yet?