Client 11-12 not registering correctly with server running 1.4.2

  • Client has been installed both via gpo and manually on machines, but when booted to pxe the screen states that client is not registered. The machine shows in database and in every aspect via FOG GUI correctly, but pxe screen not so much making it impossible to have the machines task from pxe boot. Please help

    Fog running on Fedora 25
    Clients have Win 7 pro installed.

  • @Tom-Elliott The client is what I suspect is different as I haven’t actually been pushing the client for the last 3 months as I was instructed to remove the client from all but a couple labs. So this is the first attempt for a couple months to have the clients pushed to computers before we image them in order to take full advantage of multicasting from the local nodes. Now it seems that the process used before isn’t working completely together. If I push a client to a computer, it registers with fog, and I see the machine, I suppose (as I haven’t tested) that the snapins and power management will work on these hosts just as they always have. The problem is when I pxe boot the laptops, they show as not registered.

    Now I have been running this system here for a couple years since trunk became available so it’s possible I have junk clients registered already, but I didn’t see these machines as I deleted them after removing the clients (at least not in the gui). I can verify this issue does not arise on desktop machines. I just don’t understand why the client would think it wasn’t registered.

    I have no idea how any macs could be shared, as we haven’t done anything to initiate that. All clients are currently running Windows 7 so the “randomizing” of any wireless nics isn’t the issue here, but rather in the manner the client registers the hosts.

    Quickreg works flawlessly, but it uses different mechanisms to register the nics I’m assuming since it’s still in a pre-boot environment.

  • Senior Developer

    @Hanz I’m not understanding what you’re saying @Hanz. FOG hasn’t changed how it handles devices. Only if your device’s mac is shared on other machines it could cause problems as you can only register a mac to a single host.

    The primary mac address is not what is used as basis of ensuring the host is registered. Any mac address that checks in and is registered to the host will associate to that host (so long as the mac isn’t being shared across multiple systems.)

  • @Avaryan Apparently that used to be the case, but now if the client registers the laptop with the wrong primary device, it shows as unregistered when pxe booting…so if you were to deploy an image to said laptop, it would bypass the task altogether since it believes the host is not registered. That is a huge issue, at least in reference to imaging.

  • @Hanz I’m not really sure how it determines which is the primary when it enrolls using the client. Maybe just whatever it finds first. It shouldn’t matter which is primary anyway, at least not for imaging or snapin deployment purposes.

  • @Avaryan @Developers What is the process for the client to register the nics on the machines, and can it be made/forced to choose the onboard lan as the primary by default ( for laptops) ?

  • @Avaryan Thanks for that, I’ll look to see which one it is allocating as the primary…will post back soon. Quick reg seems to work fine, but I don’t know how the client actually chooses which nic should be primary (these are laptops) I’ll also double to check to see if they are the only ones affected.

  • FOG uses the MAC of the NIC to identify. Check to make sure they match. You could manually add the MAC to FOG if it’s not doing it right, although I don’t know why it wouldn’t be doing it right.