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

Surface Laptop 3 - All devices show as registered with the same host name

Scheduled Pinned Locked Moved Solved
FOG Problems
2
3
301
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.
  • A
    argylega
    last edited by Mar 27, 2024, 3:59 PM

    Last year I ran into an issue when attempting to register & image a batch of Surface Pro 9’s. After completing the first one, the rest showed that they were already registered as the same host name as the first - basically, it was as if FOG thought they were all the same device. After some digging, I discovered a firmware update from Microsoft resolved this issue.

    Fast forward to now, I’m having the exact same issue with a batch of Surface Laptop 3’s. Found the update file from Microsoft & installed, but this time it doesn’t seem to be fixing the problem. Has anyone else run into this? Any recommendations for a fix?

    1 Reply Last reply Reply Quote 0
    • M
      mttpr1
      last edited by Apr 8, 2024, 3:29 PM

      I’ve had this issue before. I’m guessing a lot about your setup so correct me if I’m wrong.

      I’m guessing you’re using a usb to ethernet adapter to pxeboot? FOG is reading the MAC address of the usb adapter instead of the internal NIC.

      I’m not sure if there’s a better solution but - we added the device onto fog as normal. Imaged it then deregistered the device from FOG for the next one. Obviously - not really a solution if you’re relying on fog for asset management.

      A 1 Reply Last reply Apr 16, 2024, 9:36 PM Reply Quote 1
      • A
        argylega @mttpr1
        last edited by Apr 16, 2024, 9:36 PM

        @mttpr1 Thanks, that was basically it - apparently the Surface dock itself has a MAC address, so that’s what was causing the issue. No way around it really, but at least I know what the problem was. Thanks for pointing me in the right direction!

        1 Reply Last reply Reply Quote 0
        • [[undefined-on, A argylega, Apr 16, 2024, 9:36 PM]]
        • 1 / 1
        • First post
          Last post

        204

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project