Computers Join Domain before Hostname Changes

zpoling

Alrighty, I’ll enable that and see if it resolves the issue.

george1421

I would have to ask the question what is attaching the workstation to the domain? Do you have this set in your unattend.xml file to connect to the domain or are you letting FOG do everything?

zpoling

@george1421 Fog is doing all of the work as far as Active Directory.

george1421

@zpoling OK then you want to set the early hostname change as Quazz mentioned. If your system names are still coming out the windows default then you may need to look into your unattend,xml file.

Wayne Workman

@joe-schmitt should domain joining be happening before a pending name change is completed?

zpoling

@Quazz Enabling that feature did not fix this issue.

Wayne Workman

@zpoling Doing more thinking on this issue, and to more completely explain what I think might be happening…

This line in your unattend.xml file would change the hostname.
<ComputerName>*</ComputerName>

The early hostname changer works, so too does the hostname changing of the client. Another thing to remember is the fog client is fast, very fast.

Tying all these pieces together, if the Early Hostname Changer sets the correct name, that sysprep line will un-do that work, every time. Also, if the fog client changes the name before the sysprep post-deployment process gets to that line, then too is the fog client’s work undone.

There’s a way around this. Disable the fog service on your reference image, and place a setupcomplete.cmd file to re-enable the service and start it at the very end of the post-sysprep process.

Details on this are in the wiki, at the bottom of the fog client article here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client

This issue is consistent with what you were saying about the issue happening sometimes. If the hardware is slow, the issue might be more prevalent. Faster hardware may not be affected as often. Either way, you’re playing with fire when you don’t disable the fog service on the reference image before capture, as outlined in the wiki.

zpoling

@Wayne-Workman The fog service is disabled on startup until the setupcomplete.cmd is called for. That was actually my thread where you created the Wiki post about it

I just checked through our unattend file and I cannot find <ComputerName>*</ComputerName>.

Quazz

As far as I know <ComputerName> doesn’t work in unattend on Windows 10 anwyay.

Wayne Workman

@zpoling something has to be causing the naming issue. Is it possible that two hosts in host management exist for the computers? Like one for wifi mac and one for Lan mac? If you search fog for some of those names showing in AD, what are the results?

zpoling

@Wayne-Workman Non of them appear in Fog with the default name or MAC, and they never have. We have a small scale setup with Fog, so it’s easy to keep track of that sort of thing.

Wayne Workman

@zpoling can you image one of the problem computers and after all reboots and joining is done, get the log for us from the computer?

zpoling

@Wayne-Workman

Here’s all the hostname data from the log.

 6/8/2016 10:36 AM Client-Info Client Version: 0.10.6
 6/8/2016 10:36 AM Client-Info Client OS:      Windows
 6/8/2016 10:36 AM Client-Info Server Version: 7541
 6/8/2016 10:36 AM Middleware::Response Success
 6/8/2016 10:36 AM HostnameChanger Checking Hostname
 6/8/2016 10:36 AM HostnameChanger Removing host from active directory
 6/8/2016 10:36 AM HostnameChanger The machine is not currently joined to a domain, code =  2692
 6/8/2016 10:36 AM HostnameChanger Renaming host to DIESEL-1
 6/8/2016 10:36 AM Power Creating shutdown request
 6/8/2016 10:36 AM Power Parameters: /r /c "FOG needs to rename your computer" /t 0
 6/8/2016 10:36 AM HostnameChanger Success, code =  0
 6/8/2016 10:36 AM Power Creating shutdown request
 6/8/2016 10:36 AM Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
 6/8/2016 10:39 AM Client-Info Client Version: 0.10.6
 6/8/2016 10:39 AM Client-Info Client OS:      Windows
 6/8/2016 10:39 AM Client-Info Server Version: 7541
 6/8/2016 10:39 AM Middleware::Response Success
 6/8/2016 10:39 AM HostnameChanger Checking Hostname
 6/8/2016 10:39 AM HostnameChanger Removing host from active directory
 6/8/2016 10:39 AM HostnameChanger Success, code =  0
 6/8/2016 10:39 AM Power Creating shutdown request
 6/8/2016 10:39 AM Power Parameters: /r /c "Host left active directory, restart needed" /t 0
 6/8/2016 10:39 AM HostnameChanger Renaming host to DIESEL-1
 6/8/2016 10:39 AM Power Creating shutdown request
 6/8/2016 10:39 AM Power Parameters: /r /c "FOG needs to rename your computer" /t 0
 6/8/2016 10:39 AM HostnameChanger Success, code =  0
 6/8/2016 10:39 AM Power Creating shutdown request
 6/8/2016 10:39 AM Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
 6/8/2016 10:41 AM Client-Info Client Version: 0.10.6
 6/8/2016 10:41 AM Client-Info Client OS:      Windows
 6/8/2016 10:41 AM Client-Info Server Version: 7541
 6/8/2016 10:41 AM Middleware::Response Success
 6/8/2016 10:41 AM HostnameChanger Checking Hostname
 6/8/2016 10:41 AM HostnameChanger Removing host from active directory
 6/8/2016 10:41 AM HostnameChanger Success, code =  0
 6/8/2016 10:41 AM Power Creating shutdown request
 6/8/2016 10:41 AM Power Parameters: /r /c "Host left active directory, restart needed" /t 0
 6/8/2016 10:41 AM HostnameChanger Renaming host to DIESEL-1
 6/8/2016 10:41 AM Power Creating shutdown request
 6/8/2016 10:41 AM Power Parameters: /r /c "FOG needs to rename your computer" /t 0
 6/8/2016 10:41 AM HostnameChanger Success, code =  0
 6/8/2016 10:41 AM Power Creating shutdown request
 6/8/2016 10:41 AM Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
 6/8/2016 10:44 AM Client-Info Client Version: 0.10.6
 6/8/2016 10:44 AM Client-Info Client OS:      Windows
 6/8/2016 10:44 AM Client-Info Server Version: 7541
 6/8/2016 10:44 AM Middleware::Response Success
 6/8/2016 10:44 AM HostnameChanger Checking Hostname
 6/8/2016 10:44 AM HostnameChanger Removing host from active directory
 6/8/2016 10:44 AM HostnameChanger Success, code =  0
 6/8/2016 10:44 AM Power Creating shutdown request
 6/8/2016 10:44 AM Power Parameters: /r /c "Host left active directory, restart needed" /t 0
 6/8/2016 10:44 AM HostnameChanger Renaming host to DIESEL-1
 6/8/2016 10:44 AM Power Creating shutdown request
 6/8/2016 10:44 AM Power Parameters: /r /c "FOG needs to rename your computer" /t 0
 6/8/2016 10:44 AM HostnameChanger Unknown Return Code:  1364
 6/8/2016 10:46 AM Client-Info Client Version: 0.10.6
 6/8/2016 10:46 AM Client-Info Client OS:      Windows
 6/8/2016 10:46 AM Client-Info Server Version: 7541
 6/8/2016 10:46 AM Middleware::Response Success
 6/8/2016 10:46 AM HostnameChanger Checking Hostname
 6/8/2016 10:46 AM HostnameChanger Hostname is correct
 6/8/2016 10:47 AM HostnameChanger Success, code =  0
 6/8/2016 10:47 AM Power Creating shutdown request
 6/8/2016 10:47 AM Power Parameters: /r /c "Host joined to Active Directory, restart required" /t 0
 6/8/2016 10:49 AM Client-Info Client Version: 0.10.6
 6/8/2016 10:49 AM Client-Info Client OS:      Windows
 6/8/2016 10:49 AM Client-Info Server Version: 7541
 6/8/2016 10:49 AM Middleware::Response Success
 6/8/2016 10:49 AM HostnameChanger Checking Hostname
 6/8/2016 10:49 AM HostnameChanger Hostname is correct
 6/8/2016 10:49 AM HostnameChanger Host is already joined to target domain

Wayne Workman

@zpoling is it possible that you have group policy pushing out an older client? On this computer you just imaged, check if there is just one fog client installed, and if there is just one fog service in services.

zpoling

@Wayne-Workman We never push out the client. There is only one installed, as well as only one service running.

Wayne Workman

@zpoling we need @joe-schmitt to look at it and comment. Without hands on the problem, I am unsure where to go from here.

What is unique about the problem hosts? What is different?

george1421

@Quazz said in Computers Join Domain before Hostname Changes:

As far as I know <ComputerName> doesn’t work in unattend on Windows 10 anwyay.

It works the same in win10 as in Win7. In my setup I don’t have the FOG client connect the computer to the domain or set the system name. I do that with a postinstall script because I need to control where the device connects in AD depending on the target location and image being deployed. Because of the dynamic nature of this OU placement it was just easier to calculate the values, update the unattend.xml file and let Windows OOBE setup do the rest.

zpoling

@Wayne-Workman The problem has been happening to all machines indiscriminately. Each image is made on that respective model of computer, so the only thing different would be drivers installed on each image. We use the same unattend file for each image.

Wayne Workman

@zpoling can you disable domain joining on a computer and image it? And then observe it’s renaming? Provide the log for that too? This is to eliminate variables and try to isolate what’s happening.

george1421

For clarity, will you confirm that you DO NOT have the following section in your unattend.xml file? The reason why I ask is that I could see a potential for a race condition between the unattend.xml connecting the device to the domain and then the fog client doing its bit since the fog client does have a check in interval that also impacts timing of when things happen.

<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

Computers Join Domain before Hostname Changes

174

11.6k

17.1k

154.6k