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

    After Imaging Windows Setup error on Fog Build 7709

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    5
    1.1k
    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.
    • C
      chetansays
      last edited by

      Since yesterday when i updated fog to latest build, I am not able to successfully install windows on any new machines. I am getting error as seen in screensshot. It was working absolutely fine on same hardware before updating the fog to this latest build.0_1463676748226_IMG_6335.JPG

      fry_pF 1 Reply Last reply Reply Quote 0
      • fry_pF
        fry_p Moderator @chetansays
        last edited by

        @chetansays What FOG client are you using? 0.10.6 goes too fast for sysprep. I recently learned it was best practice to disable the FOG service on your image and re-enable after sysprep using the setupcomplete.cmd script. Here is the Wiki page on it: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

        Like open source community computing? Why not do it for a good cause?
        Use your computer/server for humanitarian projects when it is idle!
        https://join.worldcommunitygrid.org?recruiterId=1026912

        george1421G 1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator @fry_p
          last edited by

          @fry_p It does sounds like the fog client IS changing the system while its still in the initial startup stages.

          This is just me thinking out loud: but what would happen if you disabled all of the fog client functions in the FOG webgui so there was nothing for the fog client to do. If the client was at fault, then there would be nothing to do. Understand the client won’t connect to the domain or rename itself but the idea is to try to isolate the fog client actions out of the picture.

          If you don’t have the fog client installed on the target computer then I’m doubting that updating FOG caused this specific error.

          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!

          C 1 Reply Last reply Reply Quote 0
          • C
            chetansays @george1421
            last edited by

            @george1421 Sorry to ask this but how do i disable fog client through webgui just to isolate the issue.

            george1421G 1 Reply Last reply Reply Quote 0
            • george1421G
              george1421 Moderator @chetansays
              last edited by george1421

              @chetansays

              If you want to disable globally
              FOG Configurations->FOG Settings->FOG Client - XXXXXXX
              For now just disable all FOG Client sections individually

              Or you can do on a host by host basis (probably what you want for this test)
              Host Management -> List all Hosts -> {Select your host}
              Then from the left menu select Service Settings and then uncheck all under service configuraiton.

              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 1
              • 1 / 1
              • First post
                Last post

              182

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project