You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a technical constraint that doesn't allow computers to join the domain with the hostname they are currently using? Would it be possible to add a feature that allows hosts to join the domain using the same hostname they currently have?
==> wef: "Running Windows Domain Provisioner"
VERBOSE: Performing the operation "Join in domain 'windomain.local'" on target "wef".
Add-Computer : Skip computer 'wef' with new name 'wef' because the new name is the same as the current name.
The text was updated successfully, but these errors were encountered:
I'm not 100% sure, but judging by the message Add-Computer : Skip computer 'wef' with new name 'wef' because the new name is the same as the current name. titat looks like the Windows ecosystem is rejecting it. The plugin is definitely trying to join the domain. It's been a while since I wrote this code, so things may have moved on.
@alexisrosano89 I'm not actively maintaining this plugin I'm afraid, as I have no access to modern Windows machines to test this on. I'm openly accepting PRs and changes should they come through.
Unfortunately domain policy and a bunch of other things can also affect how this plugin works, but in most cases you should be able to test joining the domain using Powershell with a variety of CLI commands and if that sorts it out, it's fairly easy to translate into logic in this plugin.
Is there a technical constraint that doesn't allow computers to join the domain with the hostname they are currently using? Would it be possible to add a feature that allows hosts to join the domain using the same hostname they currently have?
The text was updated successfully, but these errors were encountered: