• Booting pxe problem

    6
    0 Votes
    6 Posts
    974 Views
    B

    ok thank i actually install newer version of ubuntu not 20.04 but 19.10 cause i already have this iso,

    i install again and i change the dhcp conf with filename “ipxe.efi” and i give you new later.

  • Updated Ubuntu/Fog

    14
    0 Votes
    14 Posts
    3k Views
    D

    did as you instructed and seems to be working now thanks 🙂

  • Unable to locate image store

    10
    0 Votes
    10 Posts
    3k Views
    Tom ElliottT

    @Jim-Holcomb I still don’t fully understand. The database is just a point to store and pull the data from. Nothing more.

    If you manually rename the folder in Linux, would you expect the database to automatically update when now it has no reference point? It’s the same reason in reverse. Why allow the folder to be renamed in the terminal if it won’t update the database that may be referencing it?

    The folder doesn’t get automatically created when you define a new image. This only happens after the image is defined and captured. The pieces handling it are all after the database information is pulled. The GUI is not creating the folder. FTP is.

    If you manually change the folder name in the terminal, you will still need to change the folder in the GUI. It’s the same for updating the path in the GUI. While you could temporarily store the change, but what about you are changing the path when the image hasn’t been captured yet?

  • Access denied on WinSCP

    2
    0 Votes
    2 Posts
    680 Views
    Z

    Disregard - some how the SSH service was offline.

  • Please add ability to renumber images via the GUI

    Moved
    7
    0 Votes
    7 Posts
    1k Views
    Tom ElliottT

    @JDnoble18 download it to the fog server. Run it. That’s it.

    How you run is up to you. But I’d say do sh ./renumberImageIDs.sh once it’s on the fog server.

  • PXE-E18: Server response timeout

    3
    0 Votes
    3 Posts
    2k Views
    S

    @Pyrol said in PXE-E18: Server response timeout:

    I reinstalled FOG and PFSense and it’s still the same.

    You are using pfSense as DHCP server. Please share the settings you have in there (picture) as well as the information requested by George.

  • Host and Mac Passthrough with USB C Dock

    10
    0 Votes
    10 Posts
    3k Views
    O

    @Sebastian-Roth Just replaced a mobo on a failed 3500, and it came with latest bios, which now acts the same as the 3510 😞

    So it seems my work flow with imaging 3500 only worked due a bug in the firmware on the 3500s.

    Going to either set the bios to pass-through disabled on unboxing or put together a new imaging work flow.

  • Database update failure after image capture

    Solved
    18
    0 Votes
    18 Posts
    3k Views
    M

    @george1421 Thank you. I will delete them shortly to avoid any further issues.

  • Fresh Install of 1.5.9 with CentOS 7 issues

    35
    0 Votes
    35 Posts
    9k Views
    Chris WhiteleyC

    @Sebastian-Roth This is not a new branch, just an upgrade and move from Ubuntu to Centos 7 as it is more stable when upgrading. The only thing I can do as far as getting closer is to move this computer into the server room, but since it is a desktop that would be a little cumbersome. These are juniper switches.

    For creating the schools’ base image, I use this same machine to do the work for all of them since it is pretty close to the “golden image” for each one. I am using this Dell Optiplex 7040. I create a legacy image (have some more impoverished districts with old machines) and a UEFI image.

    I have not tried different iPXE binaries and I wasn’t aware that you guys wanted me to do a mirror port. I will try and work on this today if I get some time.

    Thanks for the guidance.

  • Perform full inventory returns debug menu

    7
    0 Votes
    7 Posts
    2k Views
    Matthieu JacquartM

    @george1421 Works great, thanks !

  • new setup in vitual box Node Offline Node is unavailable

    11
    0 Votes
    11 Posts
    2k Views
    george1421G

    @Sebastian-Roth I chatted with the OP last night and got things worked out. There was a number of things wrong with the setup. We got them worked out one by one.

    The IP address for the fog server was incorrect in dhcp In the end FOG wasn’t installed completely on the FOG server. Something happened during the install because the .fogsettings file was missing (not very common so it took us a bit to narrow down).
  • Shutdown host after deploy, change BIOS time?

    3
    0 Votes
    3 Posts
    585 Views
    george1421G

    now with that said linux has a command hwclock that can set the hardware clock to local time. That command does exist in FOS Linux, but it appears to have a dependency that is not met. The other missing command is ntpdate to set the FOS Linux clock to some ntp server on your network.

    So in theory we can get to where you need with a little black magic.

    ref: https://docs.fedoraproject.org/en-US/Fedora/26/html/System_Administrators_Guide/sect4-synchronizing-date-time-hwclock.html

  • Auto registration on boot

    2
    0 Votes
    2 Posts
    372 Views
    Goll420G

    Never mind, found the option in settings. Now working fine and just have to change the boot device before letting the client do it’s thing.

  • Skip Bitlocker detection?

    26
    0 Votes
    26 Posts
    9k Views
    george1421G

    @gwhiteia Well I can either walk you through updating what you need or you can wait until this feature is available in the dev branch. It should take about 15 minutes of hands on time to setup the patch. You will just have to remember to remove it (one line of code) when 1.5.10 is released later this year.

    The decision is yours.

  • could not install PciConfig hanler

    8
    0 Votes
    8 Posts
    2k Views
    george1421G

    @cicero ok two things.

    The PciConfig handlers is just a spurious warning message. You can safely ignore this warning. If FOS Linux hits a critical warning it will stop booting.

    What is more interesting is what I can’t read in the picture. It looks like /images are being redirected somewhere. What is going on with that link? I think I can make out you have the virtual raid adapter md127 is mounted on /raid/fog/images and then you have a symlink mapping /images to that sub directory. NFS doesn’t follow symlinks.

    There is a few ways to fix this, but I would have to ask why the logic of /raid/fog/images? A quick way to fix is to mount /dev/md127 over /images (directly) and then rerun the fog installer to fix the reset of the bits.

  • Visual Studio activation snapin

    Solved
    4
    0 Votes
    4 Posts
    861 Views
    EruthonE

    Great, it works 🙂 sorry for the bother

  • Getting stuck at /ipxe/boot.php

    9
    0 Votes
    9 Posts
    2k Views
    V

    @Sebastian-Roth It’s works thanks you ! 🙂

    Try with ipxe.kpxe !

    With “kk” SAN boot image don’t work.

  • How to PXE boot from master node in location/storage group

    10
    0 Votes
    10 Posts
    1k Views
    S

    @dopyrory3 said in How to PXE boot from master node in location/storage group:

    so the imaging actions of other admins in other countries can be monitored for usage, issues, and consistency.

    You can do this by logging into the web UIs of the FOG master nodes at each location or even easier write a little “tool” to or manually pull that information from the location (master) nodes. From my point of view there is no point in making the overall FOG setup decision depend on the reporting you want to get from the system. This should have way less priority than actual imaging and transfer of stuff over the VPN as this will cause you and your team way more issues and headaches when the initial setup decision is not ideal.

    I’m intending to disable the storage node features of the Central Master server so it’s not assigned to any Storage group, and let storage nodes take up the responsibility of deploy/capture for their respective countries.

    As mentioned before, capture can only be done to a master node. There is no way (other than really hacking a fair bit of the code) to get a machine to capture an image to a storage node.

    using the AccessControl plugin to restrict them somewhat

    Another plugin that does not belong to the core code (as all plugins do). While they are part of the official code they don’t get as much attention as the core code does. Not because we don’t like those but because we hardly have enough people to work on the core and can’t afford to put in as much energy into the plugins as we do in the core. What that means is that most plugins have been added by vigorous FOG users and we don’t have anyone to improve those as much as we work on the FOG core. When people report a bug we try to fix though. I think you get what I mean. The access control plugin is one of the most overrated in the FOG world I reckon. People hope to get a full blown access control to restrict people from anything they want them from doing but in reality FOG was not build with layers of access in mind and this plugin won’t solve it properly.

    I want to have nodes for countries, but centralise the management aspect.

    I think it’s really good you start looking into FOG and asking in the forums because we are keen to set you on the “right way” to enjoy using FOG a way it can really make your life a lot easier. But there are tripping hazards that we can try to rule out beforehand. So again, centralizing the management in a single Central-Master will leave you with some big hurdles to cope with. Let’s re-think that design I’d offer.

  • DHCP-Server is not fog, so how..

    10
    0 Votes
    10 Posts
    2k Views
    S

    Hi, sorry for the long time without response.
    I checked a WDS and this server couldn’t serve too,
    Than I put one client in my other dhcp config and tada, it works.
    So it’s with the shared-network settings, that at least pxe won’t work. I have this config for now 2 Years an most of the time myself is in “the other net” so i don’t have seen this behavior.

    My work around is to put my cloning Pc in the “working” net, image them and than change it to the other net.

  • Kernel update to 18.04 -- image deployment now taking 4x the time

    Solved
    3
    0 Votes
    3 Posts
    429 Views
    Z

    This can be disregarded – and marked as solved - the underlying VM infrastrcture was having an issue - we didn’t catch it as we of course thought it was due to the upgrade.

192

Online

12.5k

Users

17.5k

Topics

156.1k

Posts