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

Snapins failing due to hostname not changing

Scheduled Pinned Locked Moved Solved
Bug Reports
3
8
2.6k
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.
  • T
    theWizard
    last edited by Wayne Workman Aug 17, 2016, 6:27 AM Aug 17, 2016, 12:20 PM

    I have not seen it mentioned in recent posts so hope this is not a repeat post but i have an issue currently where i deploy an image, everything seems to be going ok i see in the log file fog auto updates the client to latest one included with rc8 but then it goes on to the hostname changer section where it should rename the machine but instead declares there is someone logged in ( except there 100% is not i sat and watched the machine myself so i know no one is logged on ) so cancels that action and begins the snapins but unfortunately our default snapin script relies on the name of the machine being correct which it is not.

    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     17/08/2016 12:44 Client-Info Version: 0.9.12
     17/08/2016 12:44 ClientUpdater Running...
     17/08/2016 12:44 Middleware::Communication URL: http://135.100.5.9/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=E8:40:F2:D1:EB:60||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
     17/08/2016 12:44 Middleware::Communication Response: Success
     17/08/2016 12:44 Middleware::Communication URL: http://135.100.5.9/fog/service/getversion.php?client&newService=1
     17/08/2016 12:44 Middleware::Communication URL: http://135.100.5.9/fog/client/FOGService.msi
     17/08/2016 12:44 Data::RSA FOG Project cert found
     17/08/2016 12:44 ClientUpdater Update file is authentic
    ------------------------------------------------------------------------------
    
     17/08/2016 12:44 Bus {
      "channel": "Update",
      "data": "{\r\n  \"action\": \"start\"\r\n}"
    }
     17/08/2016 12:44 Bus Emmiting message on channel: Update
     17/08/2016 12:44 Service-Update Spawning update helper
     17/08/2016 12:44 Bus Registering ParseBus in channel Power
     17/08/2016 12:44 Update Helper Shutting down service...
     17/08/2016 12:44 Service Stop requested
     17/08/2016 12:44 Bus {
      "channel": "Status",
      "data": "{\r\n  \"action\": \"unload\"\r\n}"
    }
     17/08/2016 12:44 Bus Emmiting message on channel: Status
     17/08/2016 12:44 Update Helper Killing remaining FOG processes...
     17/08/2016 12:44 Update Helper Applying MSI...
     17/08/2016 12:44 Update Helper --> msiexec /i "C:\Program Files (x86)\FOG\tmp\FOGService.msi" /quiet USETRAY="" HTTPS="0" WEBADDRESS="135.100.5.9" WEBROOT="/fog" ROOTLOG="1"
     17/08/2016 12:44 Update Helper Starting service...
     17/08/2016 12:44 Main Overriding exception handling
     17/08/2016 12:44 Main Bootstrapping Zazzles
     17/08/2016 12:44 Controller Initialize
     17/08/2016 12:44 Zazzles Creating main thread
     17/08/2016 12:44 Zazzles Service construction complete
     17/08/2016 12:44 Controller Start
    
     17/08/2016 12:44 Service Starting service
     17/08/2016 12:44 Bus Became bus server
     17/08/2016 12:44 Bus {
      "self": true,
      "channel": "Status",
      "data": "{\r\n  \"action\": \"load\"\r\n}"
    }
     17/08/2016 12:44 Bus Emmiting message on channel: Status
     17/08/2016 12:44 Service ERROR: Could not clear last session data
     17/08/2016 12:44 Service ERROR: The directory is not empty.
    
     17/08/2016 12:44 Service Invoking early JIT compilation on needed binaries
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     17/08/2016 12:44 Client-Info Version: 0.11.5
     17/08/2016 12:44 Client-Info OS:      Windows
     17/08/2016 12:44 Middleware::Authentication Waiting for authentication timeout to pass
     17/08/2016 12:44 Middleware::Communication Download: http://135.100.5.9/fog/management/other/ssl/srvpublic.crt
     17/08/2016 12:44 Data::RSA FOG Server CA cert found
     17/08/2016 12:44 Middleware::Authentication Cert OK
     17/08/2016 12:44 Middleware::Communication POST URL: http://135.100.5.9/fog/management/index.php?sub=requestClientInfo&authorize&newService
     17/08/2016 12:44 Middleware::Response Success
     17/08/2016 12:44 Middleware::Authentication Authenticated
    
    
     17/08/2016 12:44 Bus Registering ParseBus in channel Power
     17/08/2016 12:44 Middleware::Communication URL: http://135.100.5.9/fog/management/index.php?sub=requestClientInfo&mac=E8:40:F2:D1:EB:60||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
     17/08/2016 12:44 Middleware::Response Success
     17/08/2016 12:44 Middleware::Communication URL: http://135.100.5.9/fog/service/getversion.php?clientver&newService&json
     17/08/2016 12:44 Middleware::Communication URL: http://135.100.5.9/fog/service/getversion.php?newService&json
    
     17/08/2016 12:44 Service Creating user agent cache
     17/08/2016 12:44 Middleware::Response Module is disabled globally on the FOG server
     17/08/2016 12:44 Middleware::Response Module is disabled globally on the FOG server
     17/08/2016 12:44 Middleware::Response Module is disabled globally on the FOG server
     17/08/2016 12:44 Service Initializing modules
    
    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     17/08/2016 12:44 Client-Info Client Version: 0.11.5
     17/08/2016 12:44 Client-Info Client OS:      Windows
     17/08/2016 12:44 Client-Info Server Version: 1.3.0-RC-8
     17/08/2016 12:44 Middleware::Response Success
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ----------------------------------TaskReboot----------------------------------
    ------------------------------------------------------------------------------
     17/08/2016 12:44 Client-Info Client Version: 0.11.5
     17/08/2016 12:44 Client-Info Client OS:      Windows
     17/08/2016 12:44 Client-Info Server Version: 1.3.0-RC-8
     17/08/2016 12:44 Middleware::Response Success
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     17/08/2016 12:44 Client-Info Client Version: 0.11.5
     17/08/2016 12:44 Client-Info Client OS:      Windows
     17/08/2016 12:44 Client-Info Server Version: 1.3.0-RC-8
     17/08/2016 12:44 Middleware::Response Success
     17/08/2016 12:44 HostnameChanger Users still logged in and enforce is disabled, delaying any further actions
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     17/08/2016 12:44 Client-Info Client Version: 0.11.5
     17/08/2016 12:44 Client-Info Client OS:      Windows
     17/08/2016 12:44 Client-Info Server Version: 1.3.0-RC-8
     17/08/2016 12:44 Middleware::Response Success
     17/08/2016 12:44 SnapinClient Snapin Found:
     17/08/2016 12:44 SnapinClient     ID: 3808
     17/08/2016 12:44 SnapinClient     Name: Default Snapins
     17/08/2016 12:44 SnapinClient     Created: 2016-08-17 10:14:24
     17/08/2016 12:44 SnapinClient     Action: 
     17/08/2016 12:44 SnapinClient     Pack: False
     17/08/2016 12:44 SnapinClient     Hide: False
     17/08/2016 12:44 SnapinClient     Server: http://135.100.5.9/fog
     17/08/2016 12:44 SnapinClient     TimeOut: 0
     17/08/2016 12:44 SnapinClient     RunWith: 
     17/08/2016 12:44 SnapinClient     RunWithArgs: 
     17/08/2016 12:44 SnapinClient     Args: 
     17/08/2016 12:44 SnapinClient     File: DefaultSnapins17082016.exe
     17/08/2016 12:44 Middleware::Communication Download: http://135.100.5.9/fog/service/snapins.file.php?mac=E8:40:F2:D1:EB:60||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&taskid=3808
     17/08/2016 12:44 SnapinClient C:\Program Files (x86)\FOG\tmp\DefaultSnapins17082016.exe
     17/08/2016 12:44 Bus {
      "self": true,
      "channel": "Notification",
      "data": "{\r\n  \"title\": \"Installing Default Snapins\",\r\n  \"message\": \"Please do not shutdown until this is completed\"\r\n}"
    }
     17/08/2016 12:44 Bus Emmiting message on channel: Notification
     17/08/2016 12:44 SnapinClient Starting snapin...
     17/08/2016 12:45 SnapinClient Snapin finished
     17/08/2016 12:45 SnapinClient Return Code: 0
     17/08/2016 12:45 Bus {
      "self": true,
      "channel": "Notification",
      "data": "{\r\n  \"title\": \"Default Snapins Installed\",\r\n  \"message\": \"Installation has finished and is now ready for use\"\r\n}"
    }
     17/08/2016 12:45 Bus Emmiting message on channel: Notification
     17/08/2016 12:45 Middleware::Communication URL: http://135.100.5.9/fog/service/snapins.checkin.php?taskid=3808&exitcode=0&mac=E8:40:F2:D1:EB:60||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService&json
    ------------------------------------------------------------------------------
    

    Mod edited to use code box.

    1 Reply Last reply Reply Quote 0
    • J
      Joe Schmitt Senior Developer
      last edited by Aug 20, 2016, 5:00 AM

      This is why the Debugger was made. Note that there is a bug in the Debugger starting at 0.11.0 with exiting so for the below instructions please use the one from 0.10.6 (https://github.com/FOGProject/fog-client/releases/download/0.10.6/Debugger.exe)

      Make a snapin with the following settings:

      • Snapin File: Debugger.exe
      • Snapin Arguments: user list > C:\user-dump.txt

      Deploy this snapin on a problematic host. A listing of the logged in users will be in C:\user-dump.txt.

      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 1
      • W
        Wayne Workman
        last edited by Aug 17, 2016, 12:30 PM

        Is the machine sys-prepped? What version of Windows?

        Pinging @Joe-Schmitt on this. The OP says nobody is logged in, but the hostname won’t change still.

        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/

        T 1 Reply Last reply Aug 17, 2016, 12:38 PM Reply Quote 0
        • T
          theWizard @Wayne Workman
          last edited by Aug 17, 2016, 12:38 PM

          @Wayne-Workman
          It is a sys-prepped image yes but the fog service is disabled until everything is complete and a reboot is complete, then it is enabled and as you can see starts the auto update of client but when the new client fires up it claims there is someone logged on but there definitely is not because we even have a script in the image which forces user logoff instantly until deployment is complete.

          Windows 7 currently
          We have the force task reboot disabled so we can queue stuff up for when it is rebooted ( always have done though )

          Thanks

          W 1 Reply Last reply Aug 17, 2016, 12:42 PM Reply Quote 0
          • W
            Wayne Workman @theWizard
            last edited by Aug 17, 2016, 12:42 PM

            @theWizard When it says it’s not doing anything while users are still logged in, it’s acting on the below pictured setting. The problem is you say that nobody is logged in - and that’s concerning - and we need to figure out why this is happening.

            0_1471437724823_upload-5242104b-5e73-476f-a8ba-44faa38fe8cd

            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/

            T 1 Reply Last reply Aug 17, 2016, 1:16 PM Reply Quote 0
            • T
              theWizard @Wayne Workman
              last edited by Aug 17, 2016, 1:16 PM

              @Wayne-Workman
              Ah i see thanks that makes more sense i forgot about that setting, true though there is no one logged on but it says there is which is where the problem lay.

              1 Reply Last reply Reply Quote 0
              • W
                Wayne Workman
                last edited by Aug 17, 2016, 1:19 PM

                @joe-schmitt I’m requesting in the next FOG Client version, that the client write in the logs who is logged in that is preventing the renaming/joining process from completing when the “Make changes even when users are logged on?” Setting is disabled.

                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
                • W
                  Wayne Workman
                  last edited by Aug 20, 2016, 3:36 AM

                  Things were crazy at work when this thread was opened. Three days ago, I did create a github issue about it - because I feel simply adding who’s logged in into the logs would help us solve this issue and future issues. here’s the issue:

                  https://github.com/FOGProject/fog-client/issues/71

                  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 Aug 20, 2016, 5:00 AM

                    This is why the Debugger was made. Note that there is a bug in the Debugger starting at 0.11.0 with exiting so for the below instructions please use the one from 0.10.6 (https://github.com/FOGProject/fog-client/releases/download/0.10.6/Debugger.exe)

                    Make a snapin with the following settings:

                    • Snapin File: Debugger.exe
                    • Snapin Arguments: user list > C:\user-dump.txt

                    Deploy this snapin on a problematic host. A listing of the logged in users will be in C:\user-dump.txt.

                    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 1
                    • 1 / 1
                    1 / 1
                    • First post
                      7/8
                      Last post

                    213

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project