• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. networkguy
    3. Topics
    N
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 41
    • Groups 0

    Topics

    • N

      Problem adding hosts to a group

      Watching Ignoring Scheduled Pinned Locked Moved Solved Bug Reports
      10
      0 Votes
      10 Posts
      3k Views
      N

      @Tom-Elliott Sounds good. I seem to have lost the ability to close the bug threads I’ve created. Call this one closed and thanks again!

    • N

      Fog Client - Snapins run after computer rename/domain join

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      8
      0 Votes
      8 Posts
      4k Views
      T

      We’re having the same issue as well. Imaging Windows 10 machines. The snapins are trying to deploy before the hostname change / active directory join has taken place.

      Fog server is SVN version 7909.
      Client is 0.10.6

    • N

      ipxe dhcp timeout

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      22
      0 Votes
      22 Posts
      13k Views
      george1421G

      @Wayne-Workman AND/OR post the image a google drive so the OP has total control of the image after the need is gone. Then just IM the link to the specific person(s) for review.

    • N

      Boot loop

      Watching Ignoring Scheduled Pinned Locked Moved Solved Bug Reports
      7
      1 Votes
      7 Posts
      3k Views
      Tom ElliottT

      @george1421 Found, confirmed, fixed, tested, and pushed.

    • N

      Host Screen Resolution

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      16
      0 Votes
      16 Posts
      7k Views
      I

      Please note that it’s been said that the DisplayManager has been built back into the client.

      https://forums.fogproject.org/topic/8383/svn-5949-screenres-manager/8?loggedin

      @Joe-Schmitt said in Host Screen Resolution:

      @networkguy 0.10.0+ removed DisplayManager from the client. As @Sebastian-Roth pointed at, its a very “Windows only” thing and never received much use compared to how much effort went into maintaining it. @Tom-Elliott, perhaps we can add some kind of “warning” next to display manager stating it isn’t present in 0.10.0+ ?

      Obviously if there is enough support for it, we can add back display manager, but we won’t be porting it to OSX or Linux.

    • N

      FOGService errors for all modules

      Watching Ignoring Scheduled Pinned Locked Moved Solved Bug Reports
      22
      0 Votes
      22 Posts
      8k Views
      Roger SaffleR

      a reboot of the PC seems to fix it on the two test machines.

    • 1 / 1