Missing @adParams for Rename-ADObject and Move-ADObject about microsoft.ad

[kmschl2]

Ran into yet another problem, module is not using the same DC, when deleting ous. Get-ADObject is not using the proper params, subsequent calls to Set-ADObject or Remove-ADObject will fail.

It is really important to always use the same domain controller, when talking to AD. If not you will get "strange" unexpected results, because of replication delays.

[jborean93]

Thanks for the bug report and sorry for the delay, the PR #61 should fix up this issue.

Ran into yet another problem, module is not using the same DC, when deleting ous. Get-ADObject is not using the proper params, subsequent calls to Set-ADObject or Remove-ADObject will fail.

Is this related to the same missing splatted variables here or is it for something else? I just want to check if there is more that can be done here.

[kmschl2]

Thanks for your answer. This is all related to the same missing splatted variables.
In the second case it is missing too, I think.

PR #61 fixes the Move-ADObject stuff, I guess, but I think you missed the one, where Get-ADObject is called before removing AccidentalDeletion when state is absent.

[jborean93]

PR #61 fixes the Move-ADObject stuff, I guess, but I think you missed the one, where Get-ADObject is called before removing AccidentalDeletion when state is absent.

Thanks for the pickup, just pushed a commit that adds that one.