Group Details Private

Senior Developers

  • RE: All new Dell laptops stuck on Bios Splash screen

    @Alk I myself have not seen this happening myself but we had someone else describing an issue that sounds pretty similar to me.

    Good to know you got this fixed by “formating” the drive. What did you use to format? Did you just recreate the partition table or overwrite that part of the disk with zeros or used sgdisk -Z?? We’ll need to gather more information to be able to figure this out.

    Would it be possible the new laptops are UEFI only and the firmware has some kind of really weird bug causing it to hang if there is a boot loader installed to the MBR??

    posted in FOG Problems
  • RE: Fog V1.5.9.29 Active Directory Defaults for OU not populating Database

    Found and fixed in 1.5.9.34

    Thank you,

    posted in Bug Reports
  • RE: Fog V1.5.9.29 Active Directory Defaults for OU not populating Database

    I have not forgotten about this, just am busy with work and trying to stand up an instance where I can test and apply the issue.

    Hopefully will get to it sometime today.

    posted in Bug Reports
  • RE: Feature request for FOG 1.6.x - Support GRUB as UEFI exit mode

    @george1421 Sounds pretty good to me so far.

    As long as we are talking about exit modes, it would be interesting to have an iPXE exit mode too. […]

    chain -ar ${boot-url}/service/ipxe/ipxe_efi.ipxe || goto MENU
    

    Not sure what you want to achieve with this? FOG’s exit types are all meant to chainload the installed OS from the local disk. Because there are many different systems with firmware not behaving all the same we provide different exit types. iPXE itself has a pretty “basic” exit type itself, the iPXE command exit (ref). A fair amount of legacy BIOS systems are able to go back and load the OS from disk after that. But the iPXE are also aware of their exit not working in all cases and propose to use GRUB4DOS (possibly why earlier FOG devs decided to use it in the first place).

    So back to my point: Why would you chainload to another iPXE binary again for exiting?

    posted in Feature Request
  • RE: Deployed imaged failed with blue screen (error 0xc0000225 or "NTFS file system")

    @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. 😉

    posted in FOG Problems
  • RE: Smart Installer caching credentials causing AD lockouts - maybe?

    @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.

    posted in Windows Problems
  • RE: FOG Automation

    @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.

    posted in FOG Problems
  • RE: refind not working properly

    @Huecuva said in refind not working properly:

    there was no /var/www/fog/html/service/ipxe

    I guess there is a typo in this. It should really be /var/www/html/fog/service/ipxe

    Please run the following commands on your FOG server and post output here:

    ls -al /var/www/
    ls -al /var/www/fog/
    ls -al /var/www/html/
    
    posted in FOG Problems
  • RE: FOG not updating Active Directory Users and Computers

    @zaccx32 Which version of FOG and the fog-client do you use? When this happens what so you get in the fog.log file on the client machine? Is this a Windows AD (domain controller version?) or Samba server setup as AD controller?

    Have you searched the forums for this kind of issue yet?

    posted in FOG Problems
  • RE: Feature request for FOG 1.6.x - Support GRUB as UEFI exit mode

    @george1421 While I like the idea of not having to embed the grub.cfg file into the binary - for users’ convenience to be able to edit the file - I would like to have the grub modules within the actual binary (its memdisk). It’s just my guts saying this might be more reliable if modules don’t need to be loaded separately.

    posted in Feature Request