Windows 10 Hostname changer failed



  • Hi

    I don’t know if it’s a fog / client / Widnows 10 bug, but I try to deploy some windows 10 computers, tested with or wihtout sysprep, and I have the same problem, Ad joining is working but not hostname changer. it reboots all the time, for nothing…

    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     11/01/2016 16:21 Client-Info Version: 0.9.10
     11/01/2016 16:21 HostnameChanger Running...
     11/01/2016 16:21 Middleware::Communication URL: http://192.168.10.60/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=B0:83:FE:B7:B2:CD|&newService=1
     11/01/2016 16:21 Middleware::Communication Response: Success
     11/01/2016 16:21 Middleware::Communication URL: http://192.168.10.60/fog/service/hostname.php?moduleid=hostnamechanger&mac=B0:83:FE:B7:B2:CD|&newService=1
     11/01/2016 16:21 Middleware::Communication Response: Success
     11/01/2016 16:21 HostnameChanger Checking Hostname
     11/01/2016 16:21 HostnameChanger Renaming host to S081PROF
     11/01/2016 16:21 HostnameChanger Unregistering computer
     11/01/2016 16:21 HostnameChanger Removing host from active directory
     11/01/2016 16:21 HostnameChanger Unknown Return Code:  1332
     11/01/2016 16:21 HostnameChanger Updating registry
     11/01/2016 16:21 RegistryHandler ERROR: Could not set SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerNameComputerName
     11/01/2016 16:21 RegistryHandler ERROR: Impossible de créer une sous-clé stable sous une clé parente volatile.
    
     11/01/2016 16:21 Power Creating shutdown request
     11/01/2016 16:21 Power Parameters: /r /c "FOG needs to rename your computer" /t 0
     11/01/2016 16:21 HostnameChanger Registering host with active directory
     11/01/2016 16:21 HostnameChanger The machine is already joined to the domain, code =  2691
    ------------------------------------------------------------------------------
    
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     11/01/2016 16:21 Client-Info Version: 0.9.10
     11/01/2016 16:21 Middleware::Communication URL: http://192.168.10.60/fog/management/other/ssl/srvpublic.crt
     11/01/2016 16:21 Middleware::Communication ERROR: Could not download file
     11/01/2016 16:21 Middleware::Communication ERROR: Impossible de se connecter au serveur distant
     11/01/2016 16:21 Middleware::Authentication ERROR: Could not authenticate
     11/01/2016 16:21 Middleware::Authentication ERROR: Le fichier spécifié est introuvable.
    
     11/01/2016 16:21 Service Sleeping for 120 seconds
    
    ------------------------------------------------------------------------------
    
    

    Thanks for help
    Matthieu


  • Senior Developer

    @Wayne-Workman @Jbob

    Push set for updated Client Version.



  • @Matthieu-Jacquart It is normal. Just delete them. I’ve already made a feature request for the new client to be able to clean these up.



  • @Jbob Is this normal to have original hostname (before renaming with fog hostname changer) on AD ?
    It seems that just after sysprep and deploy, computer is first integrated in AD, and then renaming, but older name remains in AD…
    Not a big deal, but I have to clean AD each time I deployed computers…

    0_1454517461668_Capture.JPG


  • Senior Developer

    @Matthieu-Jacquart @ch3i @Claude-Girard

    v0.9.11 is currently in the process of being released, and should properly address this issue.

    @Tom-Elliott, can you post here when you update the fogproject repo with 0.9.11?



  • I’ve just deployed 20 Win7 computers, and 2 of them had same error (AD integration was good but not hostname changer)
    After upgrading to last client, it works fine.



  • Thanks to Jbob, with last executable everything works fine with Win 10 computers !


  • Senior Developer

    I’m currently quite busy, but I’ll update the patch when I get a chance. The patched build had a bad installer. @Claude-Girard , the registry alterations are correct, the problem lies with my power interface.


  • Moderator

    @Matthieu-Jacquart Same here. I’ve deploy it and was sure that was ok, but I’ve tested a standalone installation today on my computer and I’ve that error.



  • @ch3i Yep : Unable to install CA certificate, le fichier c:\Windows\TEMP\session.jession est introuvable


  • Moderator

    @Matthieu-Jacquart said:

    @Claude-Girard Hi Claude

    I couldn’t test the patch, error during installation…

    Hi, json error ?



  • @Claude-Girard Hi Claude

    I couldn’t test the patch, error during installation…



  • @Jbob said:

    @ch3i @Matthieu-Jacquart
    I have a potential patch made. If either you are willing to try it, send me a chat message and I’ll send you the nightly installer.

    Same bug win 8.1:
    Client 0.9.10

    01/02/2016 10:48 RegistryHandler ERROR: Could not set SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerNameComputerName
    01/02/2016 10:48 RegistryHandler ERROR: Impossible de créer une sous-clé stable sous une clé parente volatile.

    Maybe missing antislash between ActiveComputerName and ComputerName ?
    Does the patch solve the issue ?


  • Senior Developer

    @ch3i @Matthieu-Jacquart
    I have a potential patch made. If either you are willing to try it, send me a chat message and I’ll send you the nightly installer.


  • Moderator

    @Jbob Hi, same bug on Windows 7 here :

    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     15/01/2016 09:55 Client-Info Version: 0.9.10
     15/01/2016 09:55 HostnameChanger Running...
     15/01/2016 09:55 Middleware::Communication URL: http://fog.eseo.fr/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=E0:69:95:C0:A6:21|0A:00:27:00:00:00|00:50:56:C0:00:01|00:50:56:C0:00:08||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
     15/01/2016 09:55 Middleware::Communication Response: Success
     15/01/2016 09:55 Middleware::Communication URL: http://fog.eseo.fr/fog/service/hostname.php?moduleid=hostnamechanger&mac=E0:69:95:C0:A6:21|0A:00:27:00:00:00|00:50:56:C0:00:01|00:50:56:C0:00:08||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0&newService=1
     15/01/2016 09:55 Middleware::Communication Response: Success
     15/01/2016 09:55 HostnameChanger Checking Hostname
     15/01/2016 09:55 HostnameChanger Renaming host to MARCONI04
     15/01/2016 09:55 HostnameChanger Unregistering computer
     15/01/2016 09:55 HostnameChanger Removing host from active directory
     15/01/2016 09:55 HostnameChanger Success, code =  0
     15/01/2016 09:55 Power Creating shutdown request
     15/01/2016 09:55 Power Parameters: /r /c "Host left active directory, restart needed" /t 0
     15/01/2016 09:55 HostnameChanger Updating registry
     15/01/2016 09:55 RegistryHandler ERROR: Could not set SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerNameComputerName
     15/01/2016 09:55 RegistryHandler ERROR: Impossible de créer une sous-clé stable sous une clé parente volatile.
    
     15/01/2016 09:55 Power Creating shutdown request
     15/01/2016 09:55 Power Parameters: /r /c "FOG needs to rename your computer" /t 0
     15/01/2016 09:55 HostnameChanger Registering host with active directory
     15/01/2016 09:55 HostnameChanger Success, code =  0
     15/01/2016 09:55 Power Creating shutdown request
     15/01/2016 09:55 Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
    ------------------------------------------------------------------------------
    


  • @Jbob We’ve been working on building a Win10 image for testing purposes - we are not totally done yet - but will test when it’s time.


  • Senior Developer

    Can anyone else confirm this bug?



  • No, it didn’t work, same error

    This problem occurs for all windows 10 client, not for windows 7

    ------------------------------------------------------------------------------
    --------------------------------HostnameChanger-------------------------------
    ------------------------------------------------------------------------------
     12/01/2016 13:23 Client-Info Version: 0.9.10
     12/01/2016 13:23 HostnameChanger Running...
     12/01/2016 13:23 Middleware::Communication URL: http://192.168.10.60/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=74:27:EA:6C:AA:6F|&newService=1
     12/01/2016 13:23 Middleware::Communication Response: Success
     12/01/2016 13:23 Middleware::Communication URL: http://192.168.10.60/fog/service/hostname.php?moduleid=hostnamechanger&mac=74:27:EA:6C:AA:6F|&newService=1
     12/01/2016 13:23 Middleware::Communication Response: Success
     12/01/2016 13:23 HostnameChanger Checking Hostname
     12/01/2016 13:23 HostnameChanger Renaming host to RAPH
     12/01/2016 13:23 HostnameChanger Unregistering computer
     12/01/2016 13:23 HostnameChanger Removing host from active directory
     12/01/2016 13:23 HostnameChanger Success, code =  0
     12/01/2016 13:23 Power Creating shutdown request
     12/01/2016 13:23 Power Parameters: /r /c "Host left active directory, restart needed" /t 0
     12/01/2016 13:23 HostnameChanger Updating registry
     12/01/2016 13:23 RegistryHandler ERROR: Could not set SYSTEM\CurrentControlSet\Control\ComputerName\ActiveComputerNameComputerName
     12/01/2016 13:23 RegistryHandler ERROR: Impossible de créer une sous-clé stable sous une clé parente volatile.
    
     12/01/2016 13:23 Power Creating shutdown request
     12/01/2016 13:23 Power Parameters: /r /c "FOG needs to rename your computer" /t 0
     12/01/2016 13:23 HostnameChanger Registering host with active directory
     12/01/2016 13:23 HostnameChanger Success, code =  0
     12/01/2016 13:23 Power Creating shutdown request
     12/01/2016 13:23 Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
    ------------------------------------------------------------------------------
    
    ------------------------------------------------------------------------------
    --------------------------------Authentication--------------------------------
    ------------------------------------------------------------------------------
     12/01/2016 13:24 Client-Info Version: 0.9.10
     12/01/2016 13:24 Middleware::Communication URL: http://192.168.10.60/fog/management/other/ssl/srvpublic.crt
     12/01/2016 13:24 Middleware::Communication ERROR: Could not download file
     12/01/2016 13:24 Middleware::Communication ERROR: Impossible de se connecter au serveur distant
     12/01/2016 13:24 Middleware::Authentication ERROR: Could not authenticate
     12/01/2016 13:24 Middleware::Authentication ERROR: Le fichier spécifié est introuvable.
    

  • Senior Developer

    If you are logged into a computer, and then change the hostname on FOG, does it operate properly?


 

398
Online

41.5k
Users

12.0k
Topics

113.5k
Posts