6311 - AD legacy password blank for existing hosts

[Tom Elliott]

I suspect you’re lying.

It appears to work fine. (I do believe you but just like to say you lied lol).

I just registered a host and told it to join the domain. It saved the info (all of it – legacy password included).

[Tom Elliott]

ON existing hosts, the ad legacy field was likely added after the switch was made. This is why they are blank. I can’t guess what was what, so I had to leave some work.

[Tom Elliott]

I don’t think this is a bug report. While I can agree it may have been unexpected. Do you mind if I solve the thread?

[Wayne Workman]

@Tom-Elliott said:

I suspect you’re lying.

[MRCUR]

@Tom-Elliott It works fine if you register a new host. Just like it works fine if you go to an existing host, uncheck the box and check it again.

But for existing hosts that were previously registered, the field is blank. If you go do a quickimage on them, they won’t join AD.

For us this is absolutely a bug and an issue (we have 100% old clients in use).

[MRCUR]

@Tom-Elliott (I would love to be lying about this one.)

[Tom Elliott]

@MRCUR THe only fix I can give for this. Put all the hosts into a group, update the hosts with the ADPassLegacy Field updated within the group, save. It should happen really fast anyway.

[MRCUR]

@Tom-Elliott You’re killing me Tom.

[Tom Elliott]

@MRCUR ??? Are you serious or joking? My method will work, and it is pretty fast.

I know it’s not perfect but I had to make a choice in the past, and maybe I chose wrong? Either way, this is the fastest way to fix the issue. I can’t do it automagically now.

[MRCUR]

@Tom-Elliott I’m kidding. I’ll use the group method to get them all set correctly again. Automagic would be nice huh