I am having this issue where the a device that has previously been imaged and joined to the domain using Fog, will fail at joining the domain as a re-image. The hostname change will modify the name, but I get incorrect password on the domain join. If I delete the device from hosts, and let the service reconnect, as long as I have put it back in a group that has the AD join listed, it will re-join properly. Any thoughts as to what I might have screwed up.
Thanks,
Ryan
@george1421 yes it was. I also had to create the Scripts folder, it was not there by default. After adding that folder and the setupcomplete.cmd, I ran sysprep again with the unattend.xml file after adding the firstlogoncommand section to the file, deployed to my other test machine and everything worked according to plan.
@george1421 The setupcomplete.cmd worked like a champ. Thank you very much for your advice.
The full message is “Windows could not complete the installation. To install windows on this computer, restart the installation”.
Fresh install of Windows 10 1809
Newly built and validated answer file from Windows System Image Manager.
Original computer reboots after image upload and completes sysprep process as it should.
Cloned machine gets error.
Has anyone experienced this message before?
I have tried new install media, new sysprep file. Tried just installing windows without anything other than base install and updates. Any assistance would be appreciated.
Thanks,
Ryan
@Wayne-Workman said in Joining Domain before Hostname change:
If that’s the case, that’s an issue. We now need to know your exact FOG version so we can replicate & confirm this.
Yes, as far as I can tell this is still happening. And it may very well be something that I am doing wrong. I read in another post that to use groups and assign the machine to the group, and set the service settings on the group. However, what I am noticing is that if I set the service settings to the host itself they are blanked out. Also, if I assign to group, it will remove group membership. If I do the quick host delete, and then full registration and choose all the group membership and snapin options, domain join etc, it works like a champ.
@Wayne-Workman Yes, I realize that FOG can only manage registered machines. My question was in regards to just using the “deploy image” option that uses the image already attached to the registered host versus deleting the host and re adding with “full registration and inventory” and choosing associating the image, groups, and snapins again. So, in both instances the host will be registered. @Tom-Elliott pointed out that it was my sysprep answer file that is causing most of my problem. Although, the “deploy image” option still seems to blank out all the service settings to a host as far as host name changing and domain joining. I am also only on 1.4.0 so I will check again after I update.
@Tom-Elliott I I had to double check my answer file to make sure, but no it is not joining by sysprep.
Correction. Yes, the answer file does have a domain in it. My windows 10 images do not have the join domain in answer file, and they just don’t join because the service settings get blanked out.
I have a weird issues that seems to have popped up after one of the recent updates. If I pxe boot the machine, the boot menu identifies the machine as it is registered in Fog, I can then choose to deploy image and the image deploys, but after the images is finished the machine is joined as “randomcomputername” to our domain. Then while looking at the fog.log I can see that the hostname changer can’t find the name on the server. If I find the machine name on the server, the service settings are all blanked out. I can check the hostname settings and host name registration, or move the machine to a group with those options checked, then restart the fog service and it will attempt to restart the machine and rename it. If I bring a machine on for the first image on fog and do the full registration, it works perfectly each time. It only seems to happen on the deploy image which is what I am assuming is the same as the older quick image option. Any thoughts?
I just had a very similar problem yesterday. I had to use chkdsk /markclean on a system partition because it was being seen as dirty.
@george1421
from information on the other topics that match this new error that you showed me how to find, i was able to boot back into windows use diskpart and chkdsk to mark the hidden system drive as clean, sysprep again, and then the image capture went through. Thanks for the help. :)