Windows 10 Hostname changer failed

[Joe Schmitt]

Can anyone else confirm this bug?

[Wayne Workman]

@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.

[ch3i]

@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
------------------------------------------------------------------------------

[Joe Schmitt]

@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.

[Claude Girard]

@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 ?

[Matthieu Jacquart]

@Claude-Girard Hi Claude

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

[ch3i]

@Matthieu-Jacquart said:

@Claude-Girard Hi Claude

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

Hi, json error ?

[Matthieu Jacquart]

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

[ch3i]

@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.

[Joe Schmitt]

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.

[Matthieu Jacquart]

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

[Matthieu Jacquart]

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.

[Joe Schmitt]

@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?

[Matthieu Jacquart]

@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…

[Wayne Workman]

@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.

[Tom Elliott]

@Wayne-Workman @Jbob

Push set for updated Client Version.