Thank you so much for your reply, I have seen your name dozens of times while researching various issues. It is a pleasure to speak with you.
Can you be more specific on when this started? Did it work without issues before? Just wondering if it could be Windows or .NET updates or something else that brought this issue up.
This issue was discovered on 1/28/2021 in our organization. We had new PCs to deploy and some technicians discovered the issue, but I am unsure how long it would have existed before we discovered the issue. AD Join / Hostname Changer did work perfectly fine before this issue was discovered.
It is quite possible that this issue is because of a newer .NET issue or similar, it is hard to say with all the changes MS is implementing! We did have a new image created, Version 20H2, but our old image is experiencing issues as well, Version 2004. I can troubleshoot whatever you need though!
None of those things would play a role in this case. Not the kernel used and there have not been changes in how FOG handles hostname changes between 1.5.9 and 18.104.22.168. As well, the fog-client being involved a lot has not been updated.
Did you update from an earlier version to 1.5.9 when this started to happen?
I didn’t think these would play a role in Hostname Changer, but I figured I would give it a try just in the off chance that there was a difference. We upgraded from v1.5.8 to v1.5.9. From my memory, we didn’t have any issues after the upgrade. But see if anyone else noticed anything.
If the fog-client version used has not changed I can only see other components (Windows build version, Windows Updates, .NET Updates, AD server Updates, GPO, …) causing this.
Don’t get me wrong. I am not saying this is non of our business. What I am asking for is a detailed description of components that changed since it worked last. Otherwise this won’t get us anywhere I suppose.
I can certainly see how that could affect the system as well. Give me some time to try and curate a list of these changes, although the issue has appeared on our known good image as well. But I can still compile a list.
Which Windows 10 build version do you use?
Previously we were utilizing 2004, then we moved to 20H2. We always keep one known good version in the event there are issue with the new image.
Which AD server version?
AD Server version is Server 2012 R2
All current updates installed on the systems?
At the time of creation all updates were installed on the image, but i can update a PC after imaging or update the image if you’d like.
Just to clarify what this option really does is that it edits the Windows registry files after deploying the image to disk (before the very first reboot!) to change the computer name. This has worked with Windows 7 in the past and I have tested this with Windows 10 not long ago. Though I did not test this in a setup with AD integration. So I can’t say if this would cause any side effects.
That’s an interesting point! From my point of view there is no need to have CHANGE HOSTNAME EARLY enabled if you use the fog-client doing the renaming for you. As you say it shows less issues, just leave that switched off.
Thank you so much for the information on this setting! I wasn’t sure exactly how it functioned. Unfortunately for me, today it made me a liar, in my testing it isn’t wanting to add the PC to AD even with this setting unchecked. We are just experiencing very very strange issues. It also acts like the PC is on the domain, I can log in with my network account, but the PC is nowhere on the domain and will eventually encounter a Trust Relationship issue.
Let me know if there is anything at all you would be interested in seeing. I can recreate the images, grab logs, test whatever you may need.
One thought I had, is it possible to downgrade from version 1.5.9 to 1.5.8 for testing purposes?