Windows 10 1709 and Client 11.14



  • FOG 1.4.4
    Ubuntu 16.04

    Got a change to test this client out on Window 10 1709 image. First test (We are also seeing high CPU issues at the time) on a HP Elitedesk 8300 the client did not start. It changed to automatic start but did not start after sysprep. Once manually starting the client or rebooting kicks off the client and it does work like it should. The other HP Elitebook 840 G1. The client did start and rename and join domain and snap ins BUT it did not reboot after rename and domain join. It stayed logged in as Admin. Our last snapin is Zenworks Agent and that does a reboot so it does technically work but its not working right for that model.



  • Hi,

    in normal you don’t need any autologons, i just use it because i am working with windows 10 pro oem where you cannot have setupcomplete.cmd executed automatically, therefore i used the autologon stuff with first logon commands in my unattend.xml.

    If you don’t need to do anything special remove autologons in your unattend.xml

    Regards X23


  • Senior Developer

    @UWPVIOLATOR I’m not really sure to be honest, it could also be that the client is performing the first restart before admin can even log-in.



  • @Joe-Schmitt @x23piracy With Windows 10 Fast Boot. If its enabled a reboot is not being registered so could that be why it keep logging back in? I know Fast Boot messes with run time as a reboot wont “reset” the counter but a shutdown will.



  • @joe-schmitt All we need is for FOGService to do its thing. So if that is not needed for it then I will remove it.


  • Senior Developer

    @UWPVIOLATOR I don’t really see a need for it with the client, unless you have some special steps your image takes during that period.



  • @joe-schmitt So question, Do we need Auto Login at all? I think it’s a legacy setting we had.


  • Senior Developer

    @UWPVIOLATOR - @x23piracy is correct, fog version v1.4.0 shipped with the client domain improvements. The fact that admin is staying logged in points to a simple unattend.xml configuration issue. I would assume that if you manually restarted, OR even just examine the computer while admin is logged in, you’d see the computer is domain joined.

    I can’t speak to why its happening, but this is definitly outside the scope of the client’s responsibility.



  • @x23piracy Yeah I do see a AutoLogon but its at 1. This was never an issue on previous FOG Clients. After the rename reboot it would put you back to lock screen.



  • @uwpviolator is it possible that you have a autologon in your unattend.xml? If so i had two autologons in the past until the client doesnt needed reboots twice anymore, since that point i reduced auto logons to 1 instead of 2.

    I am not sure but i think it was 11.12…

    https://news.fogproject.org/fog-1-4-0-officially-released/

    New Features

    New languages: es-ES, eu, no
    Renaming a Windows computer and then joining a domain is now 2 times faster
    Renaming a Windows computer inside a domain is now 3 times faster



  • @joe-schmitt At what version did Rename and Join domain become one task? So I get a reboot but it doesn’t go back to the Lock Screen for Windows 10. After the 1 reboot it goes back in as admin. Is that how this new client is supposed to act?

    Edit: I tested again without our Zen Snapin. The system stays logged in as Admin without intervention. It should be at the Lock Screen when its finished imaging, joining domain, and apply snapins.


  • Senior Developer

    @UWPVIOLATOR it does:

     2/20/2018 10:24 AM Power --> API call returned 1, will re-attempt in 5 minutes
     2/20/2018 10:26 AM Main Overriding exception handling
    

    This reboot (which you said was successful) corresponds to these changes:

     2/20/2018 10:23 AM HostnameChanger Renaming host to MMSD-LPT-119719
     2/20/2018 10:23 AM HostnameChanger Joining domain
     2/20/2018 10:23 AM HostnameChanger Success, code =  0
    

    The 0.11.X series performs all domain changes in a single reboot, whereas old versions required multiple reboots.

    When the client starts back up after the single reboot, we can see that the name is correct, and the domain is joined:

     2/20/2018 10:26 AM HostnameChanger Checking Hostname
     2/20/2018 10:26 AM HostnameChanger Hostname is correct
     2/20/2018 10:26 AM HostnameChanger Attempting to join domain
     2/20/2018 10:26 AM HostnameChanger Host already joined to target domain
    

    If there is an issue here, its not with reboots. Is there some extra information I’m unaware of? For example is the client reporting that its joined to the domain, but in reality its not?



  • @joe-schmitt Correct but it should be rebooting after joining domain.


  • Senior Developer

    @UWPVIOLATOR I see no indication of a second reboot even being scheduled or attempted in the logs. There is only the single reboot done to rename and join AD:

    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:23 AM Client-Info Client OS:      Windows
     2/20/2018 10:23 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:23 AM Middleware::Response Success
     2/20/2018 10:23 AM HostnameChanger Checking Hostname
     2/20/2018 10:23 AM HostnameChanger Renaming host to MMSD-LPT-119719
     2/20/2018 10:23 AM HostnameChanger Joining domain
     2/20/2018 10:23 AM HostnameChanger Success, code =  0
     2/20/2018 10:23 AM Power Creating shutdown command in 60 seconds
     2/20/2018 10:23 AM Bus Emmiting message on channel: Power
    ------------------------------------------------------------------------------
    

    Did not reboot after Joining Domain

    I am not seeing any place where the client even should have done a reboot besides the one instance it did (which is the exact same as in the other logs you posted), and so by all accounts 0.11.14 seems to be operating exactly as expected.

    If there is some shutdown the snapin you run should do, then that is a problem with the snapin, not the client. (As a note, the snapin you run seems to be exiting early, while spawning some kind of new process that retains a file lock on the installer, so something is definitely strange with your snapin file)



  • @joe-schmitt HP Elitedesk 840 G1 FogService set to Delay Start.

    Service Started
    Renamed then rebooted
    Did not reboot after Joining Domain

    2/20/2018 10:23 AM Main Overriding exception handling
     2/20/2018 10:23 AM Main Bootstrapping Zazzles
     2/20/2018 10:23 AM Controller Initialize
     2/20/2018 10:23 AM Controller Start
    
     2/20/2018 10:23 AM Service Starting service
     2/20/2018 10:23 AM Bus Became bus server
     2/20/2018 10:23 AM Bus Emmiting message on channel: Status
     2/20/2018 10:23 AM Service Invoking early JIT compilation on needed binaries
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Version: 0.11.14
     2/20/2018 10:23 AM Client-Info OS:      Windows
     2/20/2018 10:23 AM Middleware::Authentication Waiting for authentication timeout to pass
     2/20/2018 10:23 AM Middleware::Communication Download: http://fogserver/fog/management/other/ssl/srvpublic.crt
     2/20/2018 10:23 AM Data::RSA FOG Server CA cert found
     2/20/2018 10:23 AM Middleware::Authentication Cert OK
     2/20/2018 10:23 AM Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
     2/20/2018 10:23 AM Middleware::Authentication ERROR: Could not get security token
     2/20/2018 10:23 AM Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'.
     2/20/2018 10:23 AM Middleware::Communication POST URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&authorize&newService
     2/20/2018 10:23 AM Middleware::Response Success
     2/20/2018 10:23 AM Middleware::Authentication Authenticated
    
    
     2/20/2018 10:23 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&configure&newService&json
     2/20/2018 10:23 AM Middleware::Response Success
     2/20/2018 10:23 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14|A0:A8:CD:EA:A2:17&newService&json
     2/20/2018 10:23 AM Middleware::Response Success
     2/20/2018 10:23 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?clientver&newService&json
     2/20/2018 10:23 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?newService&json
    
     2/20/2018 10:23 AM Service Creating user agent cache
     2/20/2018 10:23 AM Middleware::Response Module is disabled globally on the FOG server
     2/20/2018 10:23 AM Middleware::Response Module is disabled on the host
     2/20/2018 10:23 AM Middleware::Response Module is disabled globally on the FOG server
     2/20/2018 10:23 AM Service Initializing modules
    
    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:23 AM Client-Info Client OS:      Windows
     2/20/2018 10:23 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:23 AM Middleware::Response Success
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ----------------------------------TaskReboot----------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:23 AM Client-Info Client OS:      Windows
     2/20/2018 10:23 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:23 AM Middleware::Response Module is disabled globally on the FOG server
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:23 AM Client-Info Client OS:      Windows
     2/20/2018 10:23 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:23 AM Middleware::Response Success
     2/20/2018 10:23 AM HostnameChanger Checking Hostname
     2/20/2018 10:23 AM HostnameChanger Renaming host to MMSD-LPT-119719
     2/20/2018 10:23 AM HostnameChanger Joining domain
     2/20/2018 10:23 AM HostnameChanger Success, code =  0
     2/20/2018 10:23 AM Power Creating shutdown command in 60 seconds
     2/20/2018 10:23 AM Bus Emmiting message on channel: Power
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:23 AM Client-Info Client OS:      Windows
     2/20/2018 10:23 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:23 AM Middleware::Response Success
     2/20/2018 10:23 AM SnapinClient A power operation is pending, aborting module
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:23 AM Client-Info Client OS:      Windows
     2/20/2018 10:23 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:23 AM Middleware::Response Module is disabled on the host
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------PowerManagement-------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:23 AM Client-Info Client OS:      Windows
     2/20/2018 10:23 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:23 AM Middleware::Response Success
     2/20/2018 10:23 AM PowerManagement Calculating tasks to unschedule
     2/20/2018 10:23 AM PowerManagement Calculating tasks to schedule
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ----------------------------------UserTracker---------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:23 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:23 AM Client-Info Client OS:      Windows
     2/20/2018 10:23 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:23 AM Middleware::Response Success
     2/20/2018 10:23 AM Middleware::Communication URL: http://fogserver/fog/service/usertracking.report.php?action=login&user=XXX-XXX-XXXXX\Administrator&mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14|A0:A8:CD:EA:A2:17&newService&json
    ------------------------------------------------------------------------------
    
     2/20/2018 10:23 AM Service Sleeping for 926 seconds
     2/20/2018 10:24 AM Power Creating shutdown request
     2/20/2018 10:24 AM Power Parameters: /r /c "FOG needs to rename your computer" /t 0
     2/20/2018 10:24 AM Bus Emmiting message on channel: Power
     2/20/2018 10:24 AM Power Attempt 1/6 to shutdown computer
     2/20/2018 10:24 AM Power --> API call returned 1, will re-attempt in 5 minutes
     2/20/2018 10:26 AM Main Overriding exception handling
     2/20/2018 10:26 AM Main Bootstrapping Zazzles
     2/20/2018 10:26 AM Controller Initialize
     2/20/2018 10:26 AM Controller Start
    
     2/20/2018 10:26 AM Service Starting service
     2/20/2018 10:26 AM Bus Became bus server
     2/20/2018 10:26 AM Bus Emmiting message on channel: Status
     2/20/2018 10:26 AM Service Invoking early JIT compilation on needed binaries
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:26 AM Client-Info Version: 0.11.14
     2/20/2018 10:26 AM Client-Info OS:      Windows
     2/20/2018 10:26 AM Middleware::Authentication Waiting for authentication timeout to pass
     2/20/2018 10:26 AM Middleware::Communication Download: http://fogserver/fog/management/other/ssl/srvpublic.crt
     2/20/2018 10:26 AM Data::RSA FOG Server CA cert found
     2/20/2018 10:26 AM Middleware::Authentication Cert OK
     2/20/2018 10:26 AM Middleware::Communication POST URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&authorize&newService
     2/20/2018 10:26 AM Middleware::Response Success
     2/20/2018 10:26 AM Middleware::Authentication Authenticated
    
    
     2/20/2018 10:26 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&configure&newService&json
     2/20/2018 10:26 AM Middleware::Response Success
     2/20/2018 10:26 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14|A0:A8:CD:EA:A2:17&newService&json
     2/20/2018 10:26 AM Middleware::Response Success
     2/20/2018 10:26 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?clientver&newService&json
     2/20/2018 10:26 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?newService&json
    
     2/20/2018 10:26 AM Service Creating user agent cache
     2/20/2018 10:26 AM Middleware::Response Module is disabled globally on the FOG server
     2/20/2018 10:26 AM Middleware::Response Module is disabled on the host
     2/20/2018 10:26 AM Middleware::Response Module is disabled globally on the FOG server
     2/20/2018 10:26 AM Service Initializing modules
    
    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:26 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:26 AM Client-Info Client OS:      Windows
     2/20/2018 10:26 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:26 AM Middleware::Response Success
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ----------------------------------TaskReboot----------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:26 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:26 AM Client-Info Client OS:      Windows
     2/20/2018 10:26 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:26 AM Middleware::Response Module is disabled globally on the FOG server
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:26 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:26 AM Client-Info Client OS:      Windows
     2/20/2018 10:26 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:26 AM Middleware::Response Success
     2/20/2018 10:26 AM HostnameChanger Checking Hostname
     2/20/2018 10:26 AM HostnameChanger Hostname is correct
     2/20/2018 10:26 AM HostnameChanger Attempting to join domain
     2/20/2018 10:26 AM HostnameChanger Host already joined to target domain
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:26 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:26 AM Client-Info Client OS:      Windows
     2/20/2018 10:26 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:26 AM Middleware::Response Success
     2/20/2018 10:26 AM SnapinClient Running snapin Windows_10_and_Office_Activate
     2/20/2018 10:26 AM Middleware::Communication Download: http://fogserver/fog/service/snapins.file.php?mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14|A0:A8:CD:EA:A2:17&taskid=152045
     2/20/2018 10:26 AM SnapinClient C:\Program Files (x86)\FOG\tmp\Activate_For_Windows_10.bat
     2/20/2018 10:26 AM Bus Emmiting message on channel: Notification
     2/20/2018 10:26 AM SnapinClient Starting snapin
     2/20/2018 10:27 AM SnapinClient Snapin finished
     2/20/2018 10:27 AM SnapinClient Return Code: 1
     2/20/2018 10:27 AM Bus Emmiting message on channel: Notification
     2/20/2018 10:27 AM Middleware::Communication URL: http://fogserver/fog/service/snapins.checkin.php?taskid=152045&exitcode=1&mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14|A0:A8:CD:EA:A2:17&newService&json
     2/20/2018 10:27 AM SnapinClient Running snapin ZenAgent 11.4.3 x64
     2/20/2018 10:27 AM Middleware::Communication Download: http://fogserver/fog/service/snapins.file.php?mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14|A0:A8:CD:EA:A2:17&taskid=152046
     2/20/2018 10:27 AM SnapinClient C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe
     2/20/2018 10:27 AM Bus Emmiting message on channel: Notification
     2/20/2018 10:27 AM SnapinClient Starting snapin
     2/20/2018 10:27 AM SnapinClient Snapin finished
     2/20/2018 10:27 AM SnapinClient Return Code: 0
     2/20/2018 10:27 AM Bus Emmiting message on channel: Notification
     2/20/2018 10:27 AM SnapinClient ERROR: Unable to clean up snapin file
     2/20/2018 10:27 AM SnapinClient ERROR: The process cannot access the file 'C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe' because it is being used by another process.
     2/20/2018 10:27 AM Middleware::Communication URL: http://fogserver/fog/service/snapins.checkin.php?taskid=152046&exitcode=0&mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14|A0:A8:CD:EA:A2:17&newService&json
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:27 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:27 AM Client-Info Client OS:      Windows
     2/20/2018 10:27 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:27 AM Middleware::Response Module is disabled on the host
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------PowerManagement-------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:27 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:27 AM Client-Info Client OS:      Windows
     2/20/2018 10:27 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:27 AM Middleware::Response Success
     2/20/2018 10:27 AM PowerManagement Calculating tasks to unschedule
     2/20/2018 10:27 AM PowerManagement Calculating tasks to schedule
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ----------------------------------UserTracker---------------------------------
    ------------------------------------------------------------------------------
     2/20/2018 10:27 AM Client-Info Client Version: 0.11.14
     2/20/2018 10:27 AM Client-Info Client OS:      Windows
     2/20/2018 10:27 AM Client-Info Server Version: 1.4.4
     2/20/2018 10:27 AM Middleware::Response Success
     2/20/2018 10:27 AM Middleware::Communication URL: http://fogserver/fog/service/usertracking.report.php?action=login&user=MMSD-LPT-119719\Administrator&mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14|A0:A8:CD:EA:A2:17&newService&json
    ------------------------------------------------------------------------------
    
     2/20/2018 10:27 AM Service Sleeping for 938 seconds
    

  • Senior Developer

    @x23piracy unfortunately it’s more than just the network not being up. The client interfaces with several different win32 api and depends on several other Windows services to even function. If the client starts up too early, it can actually start before those apis are ready, or those dependent services aren’t running. This causes a whole series of issues like failed runtime bindings.

    The “big” thing here is that when the client starts too early, it can’t even log. It just fails to start, which means there’s a fundamental dependency missing, to the point where the client can’t even do basic things like logging. 0.11.13 was supposed to make the clients dependencies explicitly defined so this can’t happen, but evidently I missed a couple.



  • Hi,

    using auto-delayed was a recommedation a long time in the wiki, then i don’t remember with which client version that should be solved and delayed was gone in the wiki.

    I never changed it away from delayed because if this can prevent errors with the client why not stick with auto-delayed?
    @Joe-Schmitt why is the client such petulant when there is no network when the service came up? Why can’t it just try and try again until network is working?

    Regards X23



  • @joe-schmitt Here is the FOG log for a HP Elitedesk 840 G1

    Its never reboots. Stays logged in as admin until our last snapin installs which has a reboot in it.

     2/19/2018 8:37 AM Main Overriding exception handling
     2/19/2018 8:37 AM Main Bootstrapping Zazzles
     2/19/2018 8:37 AM Controller Initialize
     2/19/2018 8:37 AM Controller Start
    
     2/19/2018 8:37 AM Service Starting service
     2/19/2018 8:37 AM Bus Became bus server
     2/19/2018 8:37 AM Bus Emmiting message on channel: Status
     2/19/2018 8:37 AM Service Invoking early JIT compilation on needed binaries
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     2/19/2018 8:37 AM Client-Info Version: 0.11.14
     2/19/2018 8:37 AM Client-Info OS:      Windows
     2/19/2018 8:37 AM Middleware::Authentication Waiting for authentication timeout to pass
     2/19/2018 8:37 AM Middleware::Communication Download: http://fogserver/fog/management/other/ssl/srvpublic.crt
     2/19/2018 8:37 AM Data::RSA FOG Server CA cert found
     2/19/2018 8:37 AM Middleware::Authentication Cert OK
     2/19/2018 8:37 AM Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
     2/19/2018 8:37 AM Middleware::Authentication ERROR: Could not get security token
     2/19/2018 8:37 AM Middleware::Authentication ERROR: Could not find file 'C:\Program Files (x86)\FOG\token.dat'.
     2/19/2018 8:37 AM Middleware::Communication POST URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&authorize&newService
     2/19/2018 8:37 AM Middleware::Response Success
     2/19/2018 8:37 AM Middleware::Authentication Authenticated
    
    
     2/19/2018 8:37 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&configure&newService&json
     2/19/2018 8:37 AM Middleware::Response Success
     2/19/2018 8:37 AM Middleware::Communication URL: http://fogserver/fog/management/index.php?sub=requestClientInfo&mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14&newService&json
     2/19/2018 8:37 AM Middleware::Response Success
     2/19/2018 8:37 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?clientver&newService&json
     2/19/2018 8:37 AM Middleware::Communication URL: http://fogserver/fog/service/getversion.php?newService&json
    
     2/19/2018 8:38 AM Service Creating user agent cache
     2/19/2018 8:38 AM Middleware::Response Module is disabled globally on the FOG server
     2/19/2018 8:38 AM Middleware::Response Module is disabled on the host
     2/19/2018 8:38 AM Middleware::Response Module is disabled globally on the FOG server
     2/19/2018 8:38 AM Service Initializing modules
    
    ------------------------------------------------------------------------------
    ---------------------------------ClientUpdater--------------------------------
    ------------------------------------------------------------------------------
     2/19/2018 8:38 AM Client-Info Client Version: 0.11.14
     2/19/2018 8:38 AM Client-Info Client OS:      Windows
     2/19/2018 8:38 AM Client-Info Server Version: 1.4.4
     2/19/2018 8:38 AM Middleware::Response Success
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ----------------------------------TaskReboot----------------------------------
    ------------------------------------------------------------------------------
     2/19/2018 8:38 AM Client-Info Client Version: 0.11.14
     2/19/2018 8:38 AM Client-Info Client OS:      Windows
     2/19/2018 8:38 AM Client-Info Server Version: 1.4.4
     2/19/2018 8:38 AM Middleware::Response Module is disabled globally on the FOG server
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     2/19/2018 8:38 AM Client-Info Client Version: 0.11.14
     2/19/2018 8:38 AM Client-Info Client OS:      Windows
     2/19/2018 8:38 AM Client-Info Server Version: 1.4.4
     2/19/2018 8:38 AM Middleware::Response Success
     2/19/2018 8:38 AM HostnameChanger Checking Hostname
     2/19/2018 8:38 AM HostnameChanger Renaming host to MMSD-LPT-119719
     2/19/2018 8:38 AM HostnameChanger Joining domain
     2/19/2018 8:38 AM HostnameChanger Success, code =  0
     2/19/2018 8:38 AM Power Creating shutdown command in 60 seconds
     2/19/2018 8:38 AM Bus Emmiting message on channel: Power
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ---------------------------------SnapinClient---------------------------------
    ------------------------------------------------------------------------------
     2/19/2018 8:38 AM Client-Info Client Version: 0.11.14
     2/19/2018 8:38 AM Client-Info Client OS:      Windows
     2/19/2018 8:38 AM Client-Info Server Version: 1.4.4
     2/19/2018 8:38 AM Middleware::Response Success
     2/19/2018 8:38 AM SnapinClient A power operation is pending, aborting module
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------PrinterManager--------------------------------
    ------------------------------------------------------------------------------
     2/19/2018 8:38 AM Client-Info Client Version: 0.11.14
     2/19/2018 8:38 AM Client-Info Client OS:      Windows
     2/19/2018 8:38 AM Client-Info Server Version: 1.4.4
     2/19/2018 8:38 AM Middleware::Response Module is disabled on the host
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------PowerManagement-------------------------------
    ------------------------------------------------------------------------------
     2/19/2018 8:38 AM Client-Info Client Version: 0.11.14
     2/19/2018 8:38 AM Client-Info Client OS:      Windows
     2/19/2018 8:38 AM Client-Info Server Version: 1.4.4
     2/19/2018 8:38 AM Middleware::Response Success
     2/19/2018 8:38 AM PowerManagement Calculating tasks to unschedule
     2/19/2018 8:38 AM PowerManagement Calculating tasks to schedule
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    ----------------------------------UserTracker---------------------------------
    ------------------------------------------------------------------------------
     2/19/2018 8:38 AM Client-Info Client Version: 0.11.14
     2/19/2018 8:38 AM Client-Info Client OS:      Windows
     2/19/2018 8:38 AM Client-Info Server Version: 1.4.4
     2/19/2018 8:38 AM Middleware::Response Success
     2/19/2018 8:38 AM Middleware::Communication URL: http://fogserver/fog/service/usertracking.report.php?action=login&user=XXX-XXX-XXXXX\defaultuser0&mac=64:51:06:A1:44:1D|A0:A8:CD:EA:A2:13|A0:A8:CD:EA:A2:14&newService&json
    ------------------------------------------------------------------------------
    
     2/19/2018 8:38 AM Service Sleeping for 1269 seconds
     2/19/2018 8:39 AM Power Creating shutdown request
     2/19/2018 8:39 AM Power Parameters: /r /c "FOG needs to rename your computer" /t 0
     2/19/2018 8:39 AM Bus Emmiting message on channel: Power
     2/19/2018 8:39 AM Power Attempt 1/6 to shutdown computer
     2/19/2018 8:39 AM Power --> API call returned 1, will re-attempt in 5 minutes
     2/19/2018 8:39 AM Main Overriding exception handling
     2/19/2018 8:39 AM Main Bootstrapping Zazzles
     2/19/2018 8:39 AM Controller Initialize
     2/19/2018 8:39 AM Controller Start
    
     2/19/2018 8:39 AM Service Starting service
     2/19/2018 8:39 AM Bus Became bus server
     2/19/2018 8:39 AM Bus Emmiting message on channel: Status
     2/19/2018 8:39 AM Service Invoking early JIT compilation on needed binaries
    


  • @joe-schmitt So you want Automatic (Delayed Start) ?


  • Senior Developer

    @UWPVIOLATOR So that power API actually has a non-zero return code on success, it’s a bit different.

    And for the failed startup, I’m assuming a delayed start fixes it?


 

319
Online

41.6k
Users

12.1k
Topics

114.4k
Posts