Issues with Automatic Domain Join and name change

[fry_p]

Hello all,
I am having some strange issues that have appeared recently. I am running 8413 with client 11.2. This issue is also hard to describe so bear with me. From what I gather, this is happening to newly registered and re-imaged existing hosts. When I register new hosts, I go through full registration and choose “y” for domain join. They image and come out of sysprep and sit. It looks like it checks in fine and does not receive all of the info and credentials from the server

------------------------------------------------------------------------------
--------------------------------HostnameChanger-------------------------------
------------------------------------------------------------------------------
 7/6/2016 6:44 AM Client-Info Client Version: 0.11.2
 7/6/2016 6:44 AM Client-Info Client OS:      Windows
 7/6/2016 6:44 AM Client-Info Server Version: 8413
 7/6/2016 6:44 AM Middleware::Response Success
 7/6/2016 6:44 AM HostnameChanger Checking Hostname
 7/6/2016 6:44 AM HostnameChanger Hostname is correct
 7/6/2016 6:44 AM HostnameChanger ERROR: Required ADDom Joining information is missing

So I look at the AD settings on the host in the GUI and see this:

I figured it could be a defaults setting but it appears everything is set properly.

The only workaround I found for this is to either add all of the needed hosts to a group, go to the AD option, uncheck the Join box, recheck the join box (it then populates the missing fields), and hit save (or do the same thing for specific hosts).

Also, under service settings, hostname changer is enabled and set to default.

Thanks!
Paul

[Tom Elliott]

This happens every time you register?

[fry_p]

@Tom-Elliott said in Issues with Automatic Domain Join and name change:

This happens every time you register?

Yes sir. New hosts and old hosts that re-image both have this issue.

[Tom Elliott]

So I am unable to replicate the issue. I’ve created a tasking, after setting the host information up. I told it to join to domain and all that jazz. I Checked in and Checked out the tasking and the AD Settings remained.

Registered a host and asked it to enable AD Joining during the process. I asked it to perform the image task when done registering. I then deployed it and watched it and all stayed in place.

[fry_p]

@Tom-Elliott I just added everything to a group (1700 or so hosts) and checked the box for AD. I hope this will fix existing hosts, but FYI this is what I see after I hit “Update”

It populates when I hit the tick box, but as soon as it reloads, everything is gone.

[Tom Elliott]

@fry_p The group page is not an accurate indicator. This is because each host has a unique password defined for it, or at least should. Do the hosts maintain their new settings when you apply from a group?

[fry_p]

@Tom-Elliott They seem to. I spot checked some random hosts and it seems to all be populated. So that should take care of that part of the problem. I am registering and imaging a new host right now to see what it does.

[Tom Elliott]

Updated the code base. The only one that will likely be problematic will be product keys and active directory keys. This is because hosts store this data encrypted and that encryption information get’s changed.

[fry_p]

@Tom-Elliott I don’t know what happened, but due to another issue, I updated to 8440 and the new host joined with no issue. So adding all of the existing hosts to a group and applying AD changes to them took care of those, and the patch to 8440 seems to have changed something that was keeping my defaults from populating on new hosts. Thanks!