• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Host registration failure with HP EliteDesk 800 G2 Desktop Mini

Scheduled Pinned Locked Moved Solved
Hardware Compatibility
3
5
2.0k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • O
    onepotato
    last edited by Mar 11, 2016, 10:50 AM

    Hi
    Whenever I try a quick or full host registration with a HP EliteDesk 800 G2 Desktop Mini, it fails with the following error:

    Attempting to register host…Failed
    An error has been detected!
    Cannot register host. (/bin/fog.auto.reg)
    Args Passed:
    Computer will reboot in 1 minute.

    I’m getting this on both Fog 1.2 and Trunk 6365.
    Other computers are working fine, it seems to be a problem specific to this model (product number: P1G15ET#ABU). Has anyone encountered the same issue or managed to get this model to work with Fog?
    I did try and change various BIOS settings to see if that makes a difference but nothing seems to work.

    Thanks!

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Mar 11, 2016, 5:30 AM Mar 11, 2016, 11:29 AM

      I was about to give out a collective groan 😱 because I thought this was another realtek issue. But in this case this workstation has an Intel I219-LM network adapter installed.

      If you select the compatibility test from the ipxe menu what does that produce?

      next step
      If you manually register this computer and then setup a debug deploy to this computer. Boot the computer into the ipxe menu the end results will be a command prompt on the target computer.

      Then issue the command ip addr show and post the results here.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 0
      • Q
        Quazz Moderator
        last edited by Mar 11, 2016, 11:52 AM

        I believe they fixed certain registration issues on trunk 6555+ or so, so it might be worth updating.

        G 1 Reply Last reply Mar 11, 2016, 12:34 PM Reply Quote 1
        • G
          george1421 Moderator @Quazz
          last edited by Mar 11, 2016, 12:34 PM

          @Quazz said:

          I believe they fixed certain registration issues on trunk 6555+ or so, so it might be worth updating.

          Very true!! I only looked at the last group of numbers and assumed 65 was greater than 55, no problem here… 😞

          ISO… 2nd cup of coffee now

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          1 Reply Last reply Reply Quote 0
          • O
            onepotato
            last edited by Mar 11, 2016, 12:35 PM

            @Quazz @george1421
            Thank you both for your answers, appreciate it. I started with the easy solution suggested by Quazz, and it fixed it!
            Now running trunk 6677 and the registration just works fine!
            Thanks a lot.
            Next time I have a problem, I’ll update first, then post on the forum 🙂

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            1 / 1
            • First post
              4/5
              Last post

            158

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project