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

Did the hostname changer change how it works?

Scheduled Pinned Locked Moved
General
5
9
2.8k
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.
  • J
    jamesb
    last edited by Apr 1, 2015, 4:02 PM

    I wasn’t sure where to put this since it isn’t broken and this isn’t exactly a feature request. Before the new client version of FOG the hostname changer would change the hostname even if a user was logged in. However now in the log file I get a message that says a user is logged in and will rename it later after the user logs out. Could possibly have an option or something to let us rename even if a user is logged in? Or would that cause issues with how the hostname changer acts now?

    1 Reply Last reply Reply Quote 0
    • W
      Wayne Workman
      last edited by Apr 1, 2015, 4:25 PM

      IMO, it’s safer to wait until the computer is not in use…

      Changing a computer name and forcing a reboot in the middle of someone getting work done will cause MUCH more than just I.T. problems…

      I.T. maintenance should be transparent, even totally invisible to the end users… and should never prevent or disrupt productivity.

      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!
      Daily Clean Installation Results:
      https://fogtesting.fogproject.us/
      FOG Reporting:
      https://fog-external-reporting-results.fogproject.us/

      1 Reply Last reply Reply Quote 0
      • J
        Joe Schmitt Senior Developer
        last edited by Apr 1, 2015, 4:33 PM

        The shutdown will occur even when a user is logged in if you set the “force” setting on your FOG server. (I’m not sure where it is off the top of my head)

        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        1 Reply Last reply Reply Quote 0
        • J
          jamesb
          last edited by Apr 1, 2015, 4:53 PM

          That option is for the task reboot service but not the hostname changer service. So unfortunately that won’t force the pc to reboot and change it’s name.

          1 Reply Last reply Reply Quote 0
          • W
            Wayne Workman
            last edited by Apr 1, 2015, 4:59 PM

            Powershell from a domain controller can immediately force computers to shutdown / restart / etc.

            It’s incredibly powerful… let me dig up the script I use…

            here:

            [CODE]stop-computer -computername FirstCompName, SecondCompName -force
            stop-computer -computername ThirdCompName -force[/CODE]

            You can also call a powershell script to run with admin rights using a batch file, like this:

            [CODE]PowerShell -NoProfile -ExecutionPolicy Bypass -Command “& {Start-Process PowerShell -ArgumentList ‘-NoProfile -ExecutionPolicy Bypass -File "“C:\Remote_Shutdown.ps1"”’ -Verb RunAs}”[/CODE]

            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!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            1 Reply Last reply Reply Quote 0
            • J
              Junkhacker Developer
              last edited by Apr 2, 2015, 1:48 PM

              [quote=“Wayne Workman, post: 44840, member: 28155”]IMO, it’s safer to wait until the computer is not in use…

              Changing a computer name and forcing a reboot in the middle of someone getting work done will cause MUCH more than just I.T. problems…

              I.T. maintenance should be transparent, even totally invisible to the end users… and should never prevent or disrupt productivity.[/quote]

              for some computers, there is no time when they’re not “in use” as far as the computer understands. kiosks for example autologon and stay on 24/7

              signature:
              Junkhacker
              We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

              1 Reply Last reply Reply Quote 0
              • J
                jamesb
                last edited by Apr 2, 2015, 1:54 PM

                I only brought this up because it used to work like that a some revisions ago. The old client would reboot the machine to change the hostname even if the computer was logged in. Then the first few revisions of the new client would have a pop up box saying the computer needs to rename and reboot and once you hit the ok button it would then restart and change the hostname. However these latest revisions seemed to have taken away that function.

                1 Reply Last reply Reply Quote 0
                • T
                  Tom Elliott
                  last edited by Apr 2, 2015, 2:16 PM

                  The client hasn’t changed. However I think the “model” behind it was a little broken because of the “randomly disappearing systems” setup.

                  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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                  Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                  Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                  1 Reply Last reply Reply Quote 0
                  • J
                    Joe Schmitt Senior Developer
                    last edited by Apr 2, 2015, 4:58 PM

                    The notification GUI your are referring to was not ready for the initial public beta. See [url]http://portal.fogproject.org/work_packages/24[/url] for the workpackage.

                    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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    1 / 1
                    • First post
                      9/9
                      Last post

                    256

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project