SOLVED Hostnamechanger not working

  • FOG Trunk v7486, Ubuntu 14.0.4, client 10.5. This is a new FOG server, hasn’t seen production use yet other than to upload an image. Just updated server this morning to have latest everything as I’m working on creating a master Win 7 desktop image. Fog.log shows no errors I can see, hostnamechanger module says hostname correct and it’s not. It’s not changing the hostname, not sure where to look to correct this. I’ve seen a couple other articles but nothing that seems to be my particular problem.

  • @Wayne-Workman Thank you, I’ll post if I see anything else happening.

  • @gwhitfield There are some other issues going on, the issue is no longer present in the current FOG Client, they are server side issues at this point. Please follow this thread for updates:

  • @Jbob - sorry didn’t see this for so long. I will test as soon as I can but it may be several days yet due to other commitments. Hopefully someone else will give it a go much sooner if they haven’t already!

  • Senior Developer

    v0.10.6 should fix this issue. Can you verify?

  • Senior Developer

    Bug found, and patched. Long story short, Zazzles was killing the service right before it was about to run the shutdown command (a.k.a a race condition). See for the fix.

    I’ll post here when we release v0.10.6 (more work needs to be done to fix some of the MSI issues first). Thank you for reporting this.

  • Senior Developer

    Confirmed the bug exists. For some reason Windows isn’t receiving the client’s shutdown request.

  • No worries! I’m not complaining, FOG has never let us down!

  • Senior Developer

    @gwhitfield The old client has several security issues. You switched to the new client right after we did a major upgrade of it, so these kinds of bugs are to be expected. If you can wait until tommorow, I can take a look at this then.

  • I think the FOG gods are laughing at me. I uninstalled client v10.5 installed my oldest client back from 2010 with the encrypted password in hostnamechanger.dll and as soon as I started the service it renamed and restarted the host. I’m tempted to stay with it and use it for my master image - it works awesome like it always has. Not sure of the downside to staying with old client though… any thoughts?

  • Testers

    @gwhitfield Yeah that was the same issue I was having and had to deploy the disabled service and start after sysprep to overcome. Now I agree that the old server didnt do that and nor did mine, but once I went to using trunk I had to switch to this method.

  • @Psycholiquid - good question. I do not let my master image ever join the domain before sysprep. When I sysprepped my master image and deployed it last night, it didn’t rename or join domain on it’s own so I’m troubleshooting that issue. The client version was 7.2 which I am now attempting to bringing up to 10.5 to keep up with the latest server version.

    The server is new, this is the only image on it. The image was sysprepped and uploaded with no apparent problems yesterday, but obviously something is wrong when it’s deployed. I had hoped it was just a bad client but the new client isn’t working either.

    What I’m doing now is testing what will happen when the sysprepped image is deployed. Since all my fog servers (up til now) have made hostname and AD joins happen automatically with reboots, I’m hoping to get back to that. Unfortunately it looks like it’s needing a manual restart to complete the task which I’m sure isn’t right.

  • Testers

    @gwhitfield Small question why are you trying to rename the computer before sysprepping? Your master image should never join the domain. This can cause issues when you sysprep and that image still has some of the policies of your domain in the image.

    This can cause auto logon to not work along with a bunch of other issues. That being said I have done it to get some software to work then dropped it back, reset the Admin password to blank and it worked fine but I really don’t recommend it.

  • Yet another update. Now that my host has correct name to match what’s in FOG console, and the host is joined to the domain I decided to test to see what would happen if I rename it in the FOG console. Log is below. Host does not restart on it’s own:

     5/5/2016 2:33 PM Client-Info Client Version: 0.10.5
     5/5/2016 2:33 PM Client-Info Client OS:      Windows
     5/5/2016 2:33 PM Client-Info Server Version: 7488
     5/5/2016 2:33 PM Middleware::Response Success
     5/5/2016 2:33 PM HostnameChanger Checking Hostname
     5/5/2016 2:33 PM HostnameChanger Removing host from active directory
     5/5/2016 2:33 PM HostnameChanger ERROR: Required ADDom information is missing
     5/5/2016 2:33 PM HostnameChanger Renaming host to MOSSIMAGEVMTEST
     5/5/2016 2:33 PM Power Creating shutdown command in 60 seconds
     5/5/2016 2:33 PM Bus {
      "self": true,
      "channel": "Power",
      "data": "{\r\n  \"action\": \"request\",\r\n  \"period\": 60,\r\n  \"options\": 2,\r\n  \"command\": \"/r /c \\\"FOG needs to rename your computer\\\" /t 0\",\r\n  \"message\": \"This computer needs to perform maintenance.\"\r\n}"
     5/5/2016 2:33 PM Bus Emmiting message on channel: Power
     5/5/2016 2:33 PM Service Power operation being requested, checking back in 30 seconds
     5/5/2016 2:34 PM Service Power operation being requested, checking back in 30 seconds
     5/5/2016 2:34 PM Power Creating shutdown request
     5/5/2016 2:34 PM Power Parameters: /r /c "FOG needs to rename your computer" /t 0

  • @Tom-Elliott - Just to clarify what I’m seeing with my crazy machine - when host name is changed in FOG console, nothing happens on host (edit: even when manually restarted). When host is set in FOG console to join domain and is manually restarted, then both the machine name AND the domain join happen.

  • @Tom-Elliott - Yes, when I manually reboot the client the machine name changes and the AD join is done. It only takes the one reboot though, almost like it was all done in the background without any signs it was happening.

  • Testers

    @gwhitfield Also keep in mind I only see this reaction with Windows 7 after I applied some updates. So it could be a mix of things causing it.

  • Testers

    @gwhitfield There is an issue I have that if the service is running during sysprep is causes issue that mimic what you are seeing, So I just disabled it and then let the commands turn it back on and set it to start once sysprep is complete.

  • @Psycholiquid - I actually have that in my setupcomplete.cmd to stop FOG and then start it once completed. However, I have not sysprepped this host yet. I am still building the master image. I was expecting that as soon as the FOG client service started it would see the discrepancy in hostname and change it immediately, restarting the machine to complete the task I have only just in the last couple days started using the new client so I’m used to how the “old” ones act.

  • Testers

    @gwhitfield Try this, dis able the fog service in your pre sysrepped image and add these lines to your unattend.xml if you are using one:

                    <SynchronousCommand wcm:action="add">
                        <CommandLine>del /Q /F c:\windows\system32\sysprep\unattend.xml</CommandLine>
                        <Description>Deletes unattend.xml</Description>
                    <SynchronousCommand wcm:action="add">
                        <CommandLine>del /Q /F c:\windows\Panther\unattend.xml</CommandLine>
                        <Description>Deletes unattend.xml</Description>
                    <SynchronousCommand wcm:action="add">
                        <CommandLine>sc config FOGService start= auto</CommandLine>
                        <Description>Changes FOG server to Automatic</Description>
                    <SynchronousCommand wcm:action="add">
                        <CommandLine>net start FOGService</CommandLine>
                        <Description>Starts FOG service </Description>

    All this happens in the OOBE phase of the sysprep. If your not using unattend try this batch file to run after it comes up:

    sc config FOGService start= auto
    net start FOGService

    paste that into a text file and save as SetupComplete.cmd. Then place the file in the following area: %WINDIR%\Setup\Scripts\

    Then sysprep.