FOG Project

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

    Solved Fog Client doesn't update (no rename, ad join)

    FOG Problems
    2
    4
    622
    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.
    • x23piracy
      x23piracy last edited by

      Server
      • FOG Version RC9
      • OS:
      Client
      • Service Version: 11.4
      • OS: Win10
      Description

      Hi,

      i’ve updated today to RC9 and had some deployments, my image contains fog client 11.4. The client doesn’t update the fog client, therefore no renaming and domain join and or snapins.

      Here is the fog client log: http://pastebin.com/VdVBNw4F

      @tom-elliott @joe-schmitt

      Help please.

      Regards X23

      ║▌║█║▌│║▌║▌█

      1 Reply Last reply Reply Quote 0
      • J
        Joe Schmitt Senior Developer last edited by

        @x23piracy when you update, the keys the client uses to authenticate are also regenerated. So even if there was a time difference of even a minute or a few seconds could cause this issue. But as you stated, it fixes itself after the client catches up in time.

        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        1 Reply Last reply Reply Quote 0
        • x23piracy
          x23piracy last edited by

          to solve this in future i will add a “net time…” command to my first logged on user.

          ║▌║█║▌│║▌║▌█

          1 Reply Last reply Reply Quote 0
          • J
            Joe Schmitt Senior Developer last edited by

            @x23piracy when you update, the keys the client uses to authenticate are also regenerated. So even if there was a time difference of even a minute or a few seconds could cause this issue. But as you stated, it fixes itself after the client catches up in time.

            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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            1 Reply Last reply Reply Quote 0
            • x23piracy
              x23piracy last edited by x23piracy

              This is strange, after letting some time go (10-15 minutes) the clients did their reboots and ad join’s after some minutes even when the inital error occour in the fog client log.

              FYI Server and Client time was correct.

              Regards X23

              ║▌║█║▌│║▌║▌█

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

              168
              Online

              10.2k
              Users

              16.3k
              Topics

              149.9k
              Posts

              Copyright © 2012-2020 FOG Project