• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Epsilon52
    3. Topics
    E
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 22
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by Epsilon52

    • E

      Surface Pro 7

      FOG Problems
      • • • Epsilon52
      14
      0
      Votes
      14
      Posts
      950
      Views

      S

      @Epsilon52 Thanks for the update and good to know. Maybe it just needed a cold boot or something like that.

    • E

      I think i may be just dumb

      FOG Problems
      • • • Epsilon52
      26
      0
      Votes
      26
      Posts
      4.1k
      Views

      george1421G

      @epsilon52 First let me say that I 100% agree with Sebastian, but I also know a secret for the Dells.

      Using the Dell CCTK (Command and configure tool) you can instruct the bios to pxe boot on the next boot up. This is totally outside the scope of FOG and not something that FOG is capable of, but the cctk tool has the ability to update/change bios settings from inside windows. So using that thought one could create a snapin (FOG deployable program) to run the preinstalled cctk command with the proper parameters to pxe boot on the next reboot only then instruct the computer to reboot. You would deploy that task after you have created an imaging task. I have not personally do this on my campus because I have other rules, but it should be totally possible with snapins and the fog client (I don’t use either in my environment).

      As I said before I require the Imaging Tech to sit in front of the computer being imaged so they are 100% certain on what computer they are imaging. Because once in the past with the fully automated process we had an Imaging Tech pick the wrong computer and reimaged (i.e. erased) a VIP’s computer.

    • E

      Selected boot device failed - possible dupe

      FOG Problems
      • • • Epsilon52
      5
      0
      Votes
      5
      Posts
      552
      Views

      S

      Turns out the install was corrupted with TFTP files in /srv/tftp (as for ARCH installs. Re-running the installer fixed it all up.

    • 1 / 1