Deployed Image does not join Domain or change hostname
-
Hello,
I and my colleague have been at this for a couple days and read several other posts regarding this issue but have not had any luck so far. No matter what we try, we cannot get hosts to automatically change hostnames and join our domain. I have followed all the instructions on how to do this several times without success.
After a first boot after deployment, our unattend.xml file does its tasks and, after a reboot, I can see the FOG client is running and is set to auto-run but subsequent reboots make no difference; the host name remains unchanged and the machine is not added to the domain. The desired hostname and MAC address are in the host list and “Join Domain after deploy” and “Name Change/AD Join Forced Reboot” are both enabled for the host. We’ve also confirmed that the AD info is correct.
I’ve attached a log file from our latest test.
Full disclosure: we are inheriting this system from someone who left our organization so we are still trying to get up to speed with FOG as quickly as we can.
One question we have (which may or may not matter) is: Should the computer object already exist in AD or should we delete it if it’s already there. We are re-imaging machines. We’ve also tried this both ways with no luck.
Thank you in advance for any help you can provide!
-
have you looked into:
Response Error multiple hosts returned for list of mac addressesin the host search box you can put the mac address to lookup the host (or many hosts)
There should be only one per MAC access (careful when imaging from docks or usb NICS) Fog does protect against this action but you never know.
-
I’m not sure if this is exactly what you’re driving at but we had a similar problem imaging our HP 705’s. The sysprepped image would install fine and everything worked fine but it wouldn’t allow FOG to rename the host. Here’s how we fixed it:
- In FOG select one of your Host PC’s.
- In the host screen click the Active Directory option near the top of the screen.
- Find the option that says: Name Change/AD Join Forced Reboot? Turn this option on and save the update for your host.
According to the FOG wiki documentation:
Setting this check box will configure the client to enforce the hostname / AD setting regardless of if a user is logged in.So if enabled, the client will restart the computer to update the hostname even when a user is logged in. If unchecked, the client will wait until no one is using the computer before restarting to
apply the hostname / AD.If this works for you, you can apply it to all of the hosts at once by using the Groups option. Just open your group, click Active Directory, Turn on the Name Change/AD Join Forced Reboot settings and save.
-
@JeremyBrown said in Deployed Image does not join Domain or change hostnameQuick Draw:
Hello,
I and my colleague have been at this for a couple days and read several other posts regarding this issue but have not had any luck so far. No matter what we try, we cannot get hosts to automatically change hostnames and join our domain. I have followed all the instructions on how to do this several times without success.
After a first boot after deployment, our unattend.xml file does its tasks and, after a reboot, I can see the FOG client is running and is set to auto-run but subsequent reboots make no difference; the host name remains unchanged and the machine is not added to the domain. The desired hostname and MAC address are in the host list and “Join Domain after deploy” and “Name Change/AD Join Forced Reboot” are both enabled for the host. We’ve also confirmed that the AD info is correct.
I’ve attached a log file from our latest test.
Full disclosure: we are inheriting this system from someone who left our organization so we are still trying to get up to speed with FOG as quickly as we can.
One question we have (which may or may not matter) is: Should the computer object already exist in AD or should we delete it if it’s already there. We are re-imaging machines. We’ve also tried this both ways with no luck.
Thank you in advance for any help you can provide!
I have heard about this machine before. I think you should consider carefully before deciding to delete it
-
@JeremyBrown You may want to filter out any Tunnel MAC’s that come with the computer. You can do this via the Fog Configuration -> Fog Client - Host Register and putting in the first 6 of the MAC to eliminate certain manufacturers MACs from populating the host registration. The only way I’ve seen this cleared is either re-naming the Primary MAC in the Host’s page, or deleting the host and letting it re-register via the smart client.
v/r,
WC. -
@JeremyBrown Are you still having this issue?
The fog log is saying that the host has multiple macsIf it’s still happening I will gladly help you use the fogApi powershell module to find the duplicate macs and how to fix it from there.
