SOLVED Win 10 New Client - Service Crashing after Imaging

  • Testers

    Hi all,

    Working with the new client (0.9.11) on Win 10 (Enterprise version 1511). I’m seeing an issue where after imaging is completed, sysprep is done, etc., the client service seems to crash and does not recover until the computer is restarted. This only happens intermittently, and nothing seems completely obvious to me in the client log file (excerpts below where a critical error is thrown). Once this happens, if I manually start the service again or restart the computer, it works fine and renames/joins AD.

    Any thoughts?

     2/9/2016 2:26 PM Client-Info Version: 0.9.11
     2/9/2016 2:26 PM HostnameChanger Running...
     2/9/2016 2:26 PM Middleware::Communication URL:|A0:A8:CD:35:BA:E3|C4:34:6B:07:09:AE|A0:A8:CD:35:BA:E6|&newService=1
     2/9/2016 2:26 PM Middleware::Communication Response: Success
     2/9/2016 2:26 PM Middleware::Communication URL:|A0:A8:CD:35:BA:E3|C4:34:6B:07:09:AE|A0:A8:CD:35:BA:E6|&newService=1
     2/9/2016 2:26 PM Middleware::Communication Response: Success
     2/9/2016 2:26 PM HostnameChanger Checking Hostname
     2/9/2016 2:26 PM HostnameChanger Renaming host to ADM-640-TEST2
     2/9/2016 2:26 PM HostnameChanger Unregistering computer
     2/9/2016 2:26 PM HostnameChanger Removing host from active directory
     2/9/2016 2:26 PM HostnameChanger The machine is not currently joined to a domain, code =  2692
     2/9/2016 2:26 PM HostnameChanger Updating registry
     2/9/2016 2:26 PM RegistryHandler ERROR: Could not set SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerNameComputerName
     2/9/2016 2:26 PM RegistryHandler ERROR: Cannot create a stable subkey under a volatile parent key.
     2/9/2016 2:26 PM Service ERROR: Critical error 
  • Testers

    @Tom-Elliott It is enabled, yes. We don’t do hardware independent images (ugh), so we haven’t run into any issues where the client interrupts sysprep. After talking to @Jbob a bit, I have a better understanding of what’s happening and a workaround to correct it.

  • @MRCUR Is the FOG Client service enabled in the image? With my images where i work, I have the FOG Client service disabled entirely to prevent the system changing/joining domain during the setupcomplete script running. Yes, SSD is faster, so what you state makes sense, though I don’t know if it’s a good thing either to have the client running as a service. For me, the disabling was required because my images are more or less independent of hardware. My setupcomplete script installs the systems drivers, and before it is finished, it enables the FOG Client service and restarts.

    This is specific to my school district as we are still using FOG 1.2.0 (Legacy client), but I imagine a similar issue may occur with the new clients.

  • Testers

    @Tom-S It seems to only happen immediately after imaging and sysprep is complete. I have noticed that the same model laptop with an SSD doesn’t exhibit this issue, which makes me think this is a service start timeout issue being hit that doesn’t occur on a sufficiently fast computer.

  • Developer

    Quick question:
    Does the service run fine after reboot and then from then on out? Meaning does this only happen directly after imaging and syspreping?

  • Testers

    @Jbob Looking through the system event log, it actually looks like the service is failing to start in the first place. After the computer imaged, it appears the name was updated successfully by the FOG service and the computer restarted. After that, the service failed to start.

    There are two event entries, one is event 7009 - A timeout was reached (30000 milliseconds) while waiting for the FOGService to connect. And then immediately after, event 7000 - The FOGService failed to start - the service did not respond to the start or control request in a timely fashion.

  • Testers

    @Tom-Elliott The image this is coming from was not joined to AD (it’s in audit mode with sysprep being run immediately before capture). I did wonder if perhaps something was going on because the name of the machine was not changing from the image but was being asked to join the domain, but I’ve had success and failures with both scenarios.

  • Senior Developer

    This is very concerning. There are safegaurds in place to prevent faulty modules from crashing the service. I’ll take a look at this as soon as I get a chance.

  • Based on the information here, is it possible the image was joined to the domain, but the hostname was changed, making it believe that the HOST as named is not joined to the domain?

  • Informing @jbob about this.