• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. sgoodman
    3. Topics
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 13
    • Best 1
    • Controversial 0
    • Groups 0

    Topics created by sgoodman

    • S

      PHP 7.4 released

      General
      • • • sgoodman
      4
      0
      Votes
      4
      Posts
      689
      Views

      Q

      A quick look at https://www.php.net/manual/en/migration74.php makes me think there shouldn’t be too many issues, though without a code evaluation I can’t say for certain.

    • S

      Solved rEFId (feature request)

      FOG Problems
      • • • sgoodman
      7
      0
      Votes
      7
      Posts
      797
      Views

      S

      @sgoodman Bump…

    • S

      Unsolved Clean Up

      FOG Problems
      • • • sgoodman
      3
      0
      Votes
      3
      Posts
      402
      Views

      S

      @sgoodman Reviving this topic as I think this would be good to get done for the next 1.5.x release.

    • S

      Solved FOG Service and interventions

      FOG Problems
      • • • sgoodman
      16
      0
      Votes
      16
      Posts
      1.0k
      Views

      S

      @sgoodman @Daniel-Miller @Greg-Plamondon @george1421 Has anyone run into this issue (again)? I’d think this might have been caused by a major .NET framework update which we can’t do much about.

      In case people have PCs running for a long time without restart they might consider setting the service to auto-restart.

      I am marking this solved now. Feel free to post if you think it’s not.

      Cross reference to another topic: https://forums.fogproject.org/topic/13704/fog-service-quits-running

    • S

      Solved FOG Encryption Problem / AD Domain Joins failing

      FOG Problems
      • • • sgoodman
      6
      0
      Votes
      6
      Posts
      469
      Views

      S

      @sgoodman said:

      I have been updating FOG on a regular basis and never changed the encrypted string to clear text and it always worked.

      There was no change of that code since Feb 1, 2018.

      Was an encrypted string “semi-supported” for some time after the commit? Did a recent update nullify that?

      From what I understand about the code it seems to try both ways - un-encrypted and encrypted - line 40ff. This has not changed since Feb 1, 2018. Neither hast the fog-client code changed since Apr 10, 2018 (0.11.16 released together with 1.5.1). Is it possible you changed your AD logon credentials in the last weeks and somehow hit some kind of special case with character encoding that we were not aware of? Just guessing here.

      I use “technicians” to help me deploy (students) and they are not normally given this credential as it could create a security concern.

      We are working on this - see github issue. Tom added it to the working-1.6 branch already and I will adapt this to dev-branch today.

    • 1 / 1