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

Problems deploying/managing new windows host...

Scheduled Pinned Locked Moved
General Problems
3
26
4.5k
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.
  • B
    bogle @george1421
    last edited by Aug 13, 2019, 8:14 PM

    @george1421 Ok I got that correct.

    G 1 Reply Last reply Aug 13, 2019, 8:16 PM Reply Quote 0
    • G
      george1421 Moderator @bogle
      last edited by Aug 13, 2019, 8:16 PM

      @bogle So from the linux command prompt on your FOG server can you ping the devices by their windows host names? Not the FQDN name?

      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!

      B 1 Reply Last reply Aug 15, 2019, 6:17 PM Reply Quote 0
      • B
        bogle @george1421
        last edited by Aug 15, 2019, 6:17 PM

        @george1421 yes

        B 1 Reply Last reply Aug 15, 2019, 6:43 PM Reply Quote 0
        • B
          bogle @bogle
          last edited by Aug 15, 2019, 6:43 PM

          @bogle Even though windows firewall was disabled for domain, I added fog client to exclusion list for all network profiles, then opened inbound/outbound traffic on port 445. Can see the newly deployed computer now.

          I had to do a “reset this pc” after deployment to fix make the computer run right though…

          B 1 Reply Last reply Aug 15, 2019, 11:27 PM Reply Quote 0
          • B
            bogle @bogle
            last edited by Aug 15, 2019, 11:27 PM

            @bogle I did a “reset this pc” and can see the host online. I created a task to reboot the computer and it didn’t do anything.

            G 1 Reply Last reply Aug 15, 2019, 11:39 PM Reply Quote 0
            • G
              george1421 Moderator @bogle
              last edited by Aug 15, 2019, 11:39 PM

              @bogle The FOG server talks to the target computer via the FOG Client/service. That service has a check in interval that is set in the fog settings. So the default may be 5 minutes (300 seconds), so if you issue a task to the target computer it could take up to 5 minutes before the target system reacts.

              Also on the fog up/down indicator it doesn’t use a ping, but a connect to port 445 to confirm the system is up or not. If your windows firewall is blocking connections to port 445 then fog will assume its down.

              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 0
              • 1
              • 2
              • 2 / 2
              2 / 2
              • First post
                24/26
                Last post

              223

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project