What does this solve?
When running ADMU as NT Authority\System account, the ADMU tool failed to migrate accounts when the system account didn't have the right permissions to remove the blank profile created during migration.
Is there anything particularly tricky?
Not particularly tricky but testing is tedious to spin up a AD bound system which also has a broken secure channel. The JC agent can then run remote commands and migrate accounts.
Issues SA-1892 - Remote Invoke Work & ADMU
What does this solve? When running ADMU as NT Authority\System account, the ADMU tool failed to migrate accounts when the system account didn't have the right permissions to remove the blank profile created during migration.
Is there anything particularly tricky? Not particularly tricky but testing is tedious to spin up a AD bound system which also has a broken secure channel. The JC agent can then run remote commands and migrate accounts.