Navigation

    FOG Project

    • Register
    • Login
    • Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. jflippen
    J
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    jflippen

    @jflippen

    10
    Reputation
    72
    Posts
    405
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    jflippen Follow

    Posts made by jflippen

    • RE: Windows 10 Error on deployment only on 1st attempts...

      @Sebastian-Roth That’s fine. Things have been pretty swamped over here so I had to put the issue on the back burner. The issue doesn’t always show up, so troubleshooting has been time consuming.

      posted in FOG Problems
      J
      jflippen
    • RE: Windows 10 Error on deployment only on 1st attempts...

      @george1421 Here is what shows up as mounted on the storage node:
      10.59.181.12 mounts.png

      Firewalld stopped and disabled.
      sestatus is in permissive mode.

      posted in FOG Problems
      J
      jflippen
    • RE: Windows 10 Error on deployment only on 1st attempts...

      @george1421 I had a meeting this afternoon and will be off the next few days, so I won’t be able to test this until Monday. I will post results when I get in.

      posted in FOG Problems
      J
      jflippen
    • RE: Windows 10 Error on deployment only on 1st attempts...

      @george1421 Okay. I was issuing the debug task from the web GUI instead of deploying an image with debugging.
      So, when I try mounting the volume before running the fog command, I get denied:
      IMG_20190710_143326.jpg

      However when I then run the FOG command the imaging goes without a hitch:
      IMG_20190710_143412.jpg

      After the imaging completes the share is mapped no problem.

      posted in FOG Problems
      J
      jflippen
    • RE: Windows 10 Error on deployment only on 1st attempts...

      @george1421 Here is a pic of the first command… the 2nd command brought back an empty result on the surface:
      IMG_20190710_135458.jpg

      The storage node IP is 10.59.181.12.

      posted in FOG Problems
      J
      jflippen
    • RE: Windows 10 Error on deployment only on 1st attempts...

      @george1421 They are just load sharing. The devices being imaged are on a different subnet than the storage nodes and fog server. Network team said there should be no blocking between sites on the firewall or the switch configs.

      posted in FOG Problems
      J
      jflippen
    • RE: Windows 10 Error on deployment only on 1st attempts...

      @Sebastian-Roth Here’s what I get when trying to debug on my surface when I try to run the fog command on the debug. It doesn’t even make it past the first step.
      IMG_20190709_160009.jpg
      IMG_20190709_160126.jpg

      posted in FOG Problems
      J
      jflippen
    • RE: Windows 10 Error on deployment only on 1st attempts...

      @Sebastian-Roth maybe… I know our network team has been tightening up security. Our main FOG server and our storage nodes are all set up with link aggregation (NIC teaming with LACP) with dual Gigabit ports. However the LAG setup didn’t seem to have issues previous to the 1.5.6 update.

      posted in FOG Problems
      J
      jflippen
    • Windows 10 Error on deployment only on 1st attempts...

      So I have had the following issue for the last few months and haven’t been able to figure out what’s going on. The issue seems to only be with any of my windows 10 images, including ones I have just created… and only on the 1st attempt FOG takes to image the machine. After the client machine reboots from the error it images just fine. The error is that it is unable to locate the image store (/bin/fog.download).

      imaging_error_edit.jpg

      Based on searches it seems to be an issue with FTP… I did notice that somehow my deployment server now has both a “fog” and a “fogproject” user account that it uses. I have to use one for my storage node settings and the other for the FTP username and password under the TFTP settings. If I try to use one account or the other for both I can no longer update my kernel and other functions break.

      The only thing I can think of is that somehow things got screwy when I went from being on some test builds for troubleshooting last year back to a stable build when 1.5.6 came out.

      Any suggestions for fixing this is greatly appreciated.

      posted in FOG Problems
      J
      jflippen
    • RE: New latitude E7400. No internal NIC, Boot to USB-C Puck NIC. Gets IP from DHCP but does not connect to Fog.

      @buercky Awesome! Glad to hear it’s working now.

      posted in General Problems
      J
      jflippen
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 8
    • 1 / 8