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

    Fog Client - 0.10.3 issues after update on host from previous version.

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    17
    5.4k
    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.
    • Wayne WorkmanW
      Wayne Workman @RipAU
      last edited by

      @RipAU Reset the encryption for this host, see what happens. This is in the host’s general area.

      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

        What client version were you on before the auto upgrade?

        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
        • R
          RipAU
          last edited by

          Thanks for the quick response 🙂

          I was on version v.0.10.0

          I just rolled back my personal workstation to the previous version I had and let it update to get more from the logs:

          ------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 3/05/2016 10:32 AM Client-Info Client Version: 0.10.0
 3/05/2016 10:32 AM Client-Info Client OS:      Windows
 3/05/2016 10:32 AM Client-Info Server Version: 7452
 3/05/2016 10:32 AM Middleware::Response Success
 3/05/2016 10:32 AM Middleware::Communication Download: http://fog2/fog/client/SmartInstaller.exe
 3/05/2016 10:32 AM Data::RSA FOG Project cert found
 3/05/2016 10:32 AM ClientUpdater Update file is authentic
------------------------------------------------------------------------------

 3/05/2016 10:32 AM Bus {
  "self": true,
  "channel": "Update",
  "data": "{\r\n  \"action\": \"start\"\r\n}"
}
 3/05/2016 10:32 AM Bus Emmiting message on channel: Update
 3/05/2016 10:32 AM Service-Update Spawning update helper
 3/05/2016 10:32 AM UpdaterHelper Shutting down service...
 3/05/2016 10:32 AM UpdaterHelper Killing remaining processes...
 3/05/2016 10:32 AM UpdaterHelper Applying update...
 3/05/2016 10:32 AM UpdaterHelper Starting service...
 3/05/2016 10:32 AM Main Overriding exception handling
 3/05/2016 10:32 AM Main Bootstrapping Zazzles
 3/05/2016 10:32 AM Controller Initialize
 3/05/2016 10:32 AM entry Creating obj
 3/05/2016 10:32 AM Controller Start

 3/05/2016 10:32 AM Service Starting service
 3/05/2016 10:32 AM Service ERROR: Could not clear last session data
 3/05/2016 10:32 AM Service ERROR: Access to the path 'FOGUpdateHelper.exe' is denied.
 3/05/2016 10:32 AM Bus Became bus server
 3/05/2016 10:32 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 3/05/2016 10:32 AM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/05/2016 10:32 AM Client-Info Version: 0.10.3
 3/05/2016 10:32 AM Client-Info OS:      Windows
 3/05/2016 10:32 AM Middleware::Authentication Waiting for authentication timeout to pass
 3/05/2016 10:32 AM Middleware::Communication Download: http://fog2/fog/management/other/ssl/srvpublic.crt
 3/05/2016 10:32 AM Middleware::Authentication ERROR: Could not authenticate
 3/05/2016 10:32 AM Middleware::Authentication ERROR: Value cannot be null.
Parameter name: authority

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/05/2016 10:32 AM Client-Info Version: 0.10.3
 3/05/2016 10:32 AM Client-Info OS:      Windows
 3/05/2016 10:32 AM Middleware::Authentication Waiting for authentication timeout to pass
 3/05/2016 10:34 AM Middleware::Communication Download: http://fog2/fog/management/other/ssl/srvpublic.crt
 3/05/2016 10:34 AM Middleware::Authentication ERROR: Could not authenticate
 3/05/2016 10:34 AM Middleware::Authentication ERROR: Value cannot be null.
Parameter name: authority

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/05/2016 10:34 AM Client-Info Version: 0.10.3
 3/05/2016 10:34 AM Client-Info OS:      Windows
 3/05/2016 10:34 AM Middleware::Authentication Waiting for authentication timeout to pass

          Resetting the encryption data doesn’t seem to help at all.

          1 Reply Last reply Reply Quote 0
          • J
            Joe Schmitt Senior Developer
            last edited by Joe Schmitt

            Can you rolllback your workstation to
            https://github.com/FOGProject/fog-client/releases/download/0.9.12/FOGService.msi
            And let it auto update? (You will need to clear encryption data before installing). It may just be an issue with 0.10.0 to 0.10.2 MSIs.

            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.

            R 1 Reply Last reply Reply Quote 0
            • R
              RipAU @Joe Schmitt
              last edited by RipAU

              @Jbob

              Just rolled back to 0.9.12 and cleared the encryption data.

              It seemed to work that time on my work station.
              I’ve attached the log from the 0.9.12 to 0.10.3.

               3/05/2016 11:09 AM RegistryHandler 64 bit registry detected
 3/05/2016 11:09 AM Middleware::Communication URL: http://fog2/fog/management/other/ca.cert.der
 3/05/2016 11:09 AM Bus Became bus server
 3/05/2016 11:09 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 3/05/2016 11:09 AM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/05/2016 11:09 AM Client-Info Version: 0.9.12
 3/05/2016 11:09 AM Middleware::Communication URL: http://fog2/fog/management/other/ssl/srvpublic.crt
 3/05/2016 11:09 AM Data::RSA FOG Server CA cert found
 3/05/2016 11:09 AM Middleware::Authentication Cert OK
 3/05/2016 11:09 AM Middleware::Communication POST URL: http://fog2/fog/management/index.php?sub=authorize
 3/05/2016 11:09 AM Middleware::Communication Response: Invalid security token
 3/05/2016 11:09 AM Service Sleeping for 120 seconds
 3/05/2016 11:10 AM Service Stop requested
 3/05/2016 11:10 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 3/05/2016 11:10 AM Bus Emmiting message on channel: Status
 3/05/2016 11:10 AM Bus Became bus server
 3/05/2016 11:10 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 3/05/2016 11:10 AM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/05/2016 11:10 AM Client-Info Version: 0.9.12
 3/05/2016 11:10 AM Middleware::Communication URL: http://fog2/fog/management/other/ssl/srvpublic.crt
 3/05/2016 11:10 AM Data::RSA FOG Server CA cert found
 3/05/2016 11:10 AM Middleware::Authentication Cert OK
 3/05/2016 11:10 AM Middleware::Communication POST URL: http://fog2/fog/management/index.php?sub=authorize
 3/05/2016 11:10 AM Middleware::Communication Response: Success
 3/05/2016 11:10 AM Middleware::Authentication Authenticated

 3/05/2016 11:10 AM Bus Registering ParseBus in channel Power

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 3/05/2016 11:10 AM Client-Info Version: 0.9.12
 3/05/2016 11:10 AM ClientUpdater Running...
 3/05/2016 11:10 AM Middleware::Communication URL: http://fog2/fog/service/servicemodule-active.php?moduleid=clientupdater&mac=98:90:96:B3:A6:5D||00:00:00:00:00:00:00:E0&newService=1
 3/05/2016 11:10 AM Middleware::Communication Response: Success
 3/05/2016 11:10 AM Middleware::Communication URL: http://fog2/fog/service/getversion.php?client&newService=1
 3/05/2016 11:10 AM Middleware::Communication URL: http://fog2/fog/client/FOGService.msi
 3/05/2016 11:10 AM Data::RSA FOG Project cert found
 3/05/2016 11:10 AM ClientUpdater Update file is authentic
------------------------------------------------------------------------------

 3/05/2016 11:10 AM Bus {
  "channel": "Update",
  "data": "{\r\n  \"action\": \"start\"\r\n}"
}
 3/05/2016 11:10 AM Bus Emmiting message on channel: Update
 3/05/2016 11:10 AM Service-Update Spawning update helper
 3/05/2016 11:10 AM Bus Registering ParseBus in channel Power
 3/05/2016 11:10 AM Update Helper Shutting down service...
 3/05/2016 11:10 AM Service Stop requested
 3/05/2016 11:10 AM Bus {
  "channel": "Status",
  "data": "{\r\n  \"action\": \"unload\"\r\n}"
}
 3/05/2016 11:10 AM Bus Emmiting message on channel: Status
 3/05/2016 11:10 AM Update Helper Killing remaining FOG processes...
 3/05/2016 11:10 AM Update Helper Applying MSI...
 3/05/2016 11:10 AM Update Helper --> msiexec /i "C:\Program Files (x86)\FOG\tmp\FOGService.msi" /quiet USETRAY="1" HTTPS="0" WEBADDRESS="fog2" WEBROOT="/fog" ROOTLOG="1"
 3/05/2016 11:10 AM Update Helper Starting service...
 3/05/2016 11:10 AM Main Overriding exception handling
 3/05/2016 11:10 AM Main Bootstrapping Zazzles
 3/05/2016 11:10 AM Controller Initialize
 3/05/2016 11:10 AM entry Creating obj
 3/05/2016 11:10 AM Controller Start

 3/05/2016 11:10 AM Service Starting service
 3/05/2016 11:10 AM Service ERROR: Could not clear last session data
 3/05/2016 11:10 AM Service ERROR: Access to the path 'FOGUpdateHelper.exe' is denied.
 3/05/2016 11:10 AM Bus Became bus server
 3/05/2016 11:10 AM Bus {
  "self": true,
  "channel": "Status",
  "data": "{\r\n  \"action\": \"load\"\r\n}"
}
 3/05/2016 11:10 AM Bus Emmiting message on channel: Status

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/05/2016 11:10 AM Client-Info Version: 0.10.3
 3/05/2016 11:10 AM Client-Info OS:      Windows
 3/05/2016 11:10 AM Middleware::Authentication Waiting for authentication timeout to pass
 3/05/2016 11:10 AM Middleware::Communication Download: http://fog2/fog/management/other/ssl/srvpublic.crt
 3/05/2016 11:10 AM Data::RSA FOG Server CA cert found
 3/05/2016 11:10 AM Middleware::Authentication Cert OK
 3/05/2016 11:10 AM Middleware::Communication POST URL: http://fog2/fog/management/index.php?sub=requestClientInfo&authorize&newService
 3/05/2016 11:10 AM Middleware::Response Invalid security token

------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
 3/05/2016 11:10 AM Client-Info Version: 0.10.3
 3/05/2016 11:10 AM Client-Info OS:      Windows
 3/05/2016 11:10 AM Middleware::Authentication Waiting for authentication timeout to pass
 3/05/2016 11:12 AM Middleware::Communication Download: http://fog2/fog/management/other/ssl/srvpublic.crt
 3/05/2016 11:12 AM Data::RSA FOG Server CA cert found
 3/05/2016 11:12 AM Middleware::Authentication Cert OK
 3/05/2016 11:12 AM Middleware::Communication POST URL: http://fog2/fog/management/index.php?sub=requestClientInfo&authorize&newService
 3/05/2016 11:12 AM Middleware::Response Success
 3/05/2016 11:12 AM Middleware::Authentication Authenticated


 3/05/2016 11:12 AM Bus Registering ParseBus in channel Power
 3/05/2016 11:12 AM Middleware::Communication URL: http://fog2/fog/management/index.php?sub=requestClientInfo&mac=98:90:96:B3:A6:5D||00:00:00:00:00:00:00:E0&newService&json
 3/05/2016 11:12 AM Middleware::Response Success
 3/05/2016 11:12 AM Middleware::Communication URL: http://fog2/fog/service/getversion.php?clientver&newService&json
 3/05/2016 11:12 AM Middleware::Communication URL: http://fog2/fog/service/getversion.php?newService&json

 3/05/2016 11:12 AM Service Creating user agent cache
 3/05/2016 11:12 AM Middleware::Response Module is disabled globally on the FOG server
 3/05/2016 11:12 AM Middleware::Response Success

------------------------------------------------------------------------------
---------------------------------ClientUpdater--------------------------------
------------------------------------------------------------------------------
 3/05/2016 11:12 AM Client-Info Client Version: 0.10.3
 3/05/2016 11:12 AM Client-Info Client OS:      Windows
 3/05/2016 11:12 AM Client-Info Server Version: 7452
 3/05/2016 11:12 AM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
----------------------------------TaskReboot----------------------------------
------------------------------------------------------------------------------
 3/05/2016 11:12 AM Client-Info Client Version: 0.10.3
 3/05/2016 11:12 AM Client-Info Client OS:      Windows
 3/05/2016 11:12 AM Client-Info Server Version: 7452
 3/05/2016 11:12 AM Middleware::Response Success
------------------------------------------------------------------------------


------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 3/05/2016 11:12 AM Client-Info Client Version: 0.10.3
 3/05/2016 11:12 AM Client-Info Client OS:      Windows
 3/05/2016 11:12 AM Client-Info Server Version: 7452
 3/05/2016 11:12 AM Middleware::Response Success
 3/05/2016 11:12 AM HostnameChanger Checking Hostname
 3/05/2016 11:12 AM HostnameChanger Hostname is correct
 3/05/2016 11:12 AM HostnameChanger Host is already joined to target domain
------------------------------------------------------------------------------
              1 Reply Last reply Reply Quote 0
              • J
                Joe Schmitt Senior Developer
                last edited by Joe Schmitt

                Thanks for checking. Whats happening is because of the pre 0.10.3 MSI issues, your FOG server is becoming unpinned during upgrade.
                If you have pdq deploy or GPO you can either re-deploy the client or manually pin the server (harder).

                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.

                R 1 Reply Last reply Reply Quote 0
                • R
                  RipAU @Joe Schmitt
                  last edited by RipAU

                  @Jbob

                  We don’t actually have access to the deployment via GPO as that is controlled by externally but we can install what we need manually or via login scripts.
                  So just re-reinstalling with the MSI over top the existing install should fix this?

                  e.g.

                  FOGService.msi" /quiet USETRAY="1" HTTPS="0" WEBADDRESS="fog2" WEBROOT="/fog" ROOTLOG="1"

                  Thanks 🙂

                  1 Reply Last reply Reply Quote 0
                  • J
                    Joe Schmitt Senior Developer
                    last edited by Joe Schmitt

                    Unfortunately no. You’d need to do an msiexec /x .....(uninstall), then install it, and either restart or do a net start FOGService

                    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.

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      RipAU @Joe Schmitt
                      last edited by

                      @Jbob

                      No worries, I’ll have a check on how I can do this easily 🙂

                      Thanks again.
                      Cheers.

                      1 Reply Last reply Reply Quote 0
                      • J
                        Joe Schmitt Senior Developer
                        last edited by Joe Schmitt

                        I have confirmed and isolated the source of this issue. It will only affect 0.10.0 to 0.10.2 auto upgrades. 0.10.3 will operate normally when auto updating in the future. Sorry about the oversight.

                        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
                          Joe Schmitt Senior Developer
                          last edited by Joe Schmitt

                          If you can wait until Tom gets around to pushing 0.10.4, it should auto repair all of hosts when you upgrade. (Keyword being should. It depends how damaged the 0.10.3 install is)

                          We designed the auto update system to be completely independent of server authentication in 0.10.X for scenarios just like this. Even though the client won’t take commands from your server, it will still process FOG Project update requests.

                          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.

                          R 1 Reply Last reply Reply Quote 1
                          • R
                            RipAU @Joe Schmitt
                            last edited by

                            @Jbob Awesome.

                            Thanks, Happy to wait and test it out 🙂

                            1 Reply Last reply Reply Quote 0
                            • J
                              Joe Schmitt Senior Developer
                              last edited by Joe Schmitt

                              @RipAU v0.10.5 is released. As long as your “broken” clients still have our FOG Project certificate installed, they should repair themselves. If they do not, you can simply run the v0.10.5 msi via a script and it will manually upgrade the broken installation that is running (you’ll still want to either restart or manually start the service when done). No need to first uninstall v0.10.3 now.

                              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.

                              R 1 Reply Last reply Reply Quote 1
                              • R
                                RipAU @Joe Schmitt
                                last edited by

                                @Jbob

                                Perfect 🙂 I’ll update the server and test 🙂

                                Thanks for the quick response guys.

                                1 Reply Last reply Reply Quote 0
                                • R
                                  RipAU
                                  last edited by

                                  Yep, looks like the problem clients have updated themselves. 🙂 All working it seems.

                                  Cheers.

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

                                  234

                                  Online

                                  11.7k

                                  Users

                                  17.2k

                                  Topics

                                  154.7k

                                  Posts
                                  Copyright © 2012-2024 FOG Project