The same problem here.
Hi,
I am migrating Exchange accounts between forests from one Exchange environment to another using the Exchange native scripts alongside ADMT. However, I encounter the error below when migrating Active Directory users via ADMT's command line to merge passwords, SIDs, and ADUser. Strangely, using the graphical interface (GUI) does not produce any errors, and the SID and password are copied correctly.
<#
2024-11-13 18:31:33 ERR2:7615 SID History cannot be updated for TESTEuser1. You must be an administrator in the source domain.
2024-11-13 18:31:33 WRN1:7392 SIDHistory could not be updated due to a configuration or permissions problem. The Active Directory Migration Tool will not attempt to migrate the remaining objects.
2024-11-13 18:31:33 Operation Aborted.
#>
I followed all the steps in the two links below in a lab environment, and everything worked perfectly. However, in production, I am encountering issues. I would appreciate guidance on how to resolve this.
ADMT 3.2 Interforest Migration - Part 2
https://social.technet.microsoft.com/wiki/contents/articles/16208.admt-3-2-interforest-migration-part-2.aspx
ADMT 3.2 Interforest Migration - Part 3
https://learn.microsoft.com/en-us/archive/technet-wiki/16621.admt-3-2-interforest-migration-part-3
I am using this script, which worked flawlessly in the lab environment, but in production, it fails with errors only via the command line, while the ADMT console works fine:
PowerShell ADMT Script
https://github.com/duffney/PowerShell/blob/master/ActiveDirectory/Migrate-ADMTUserCLI.ps1
To isolate the issue, I tested using direct commands on the ADMT server, but the same problem occurred.
Test Without Script
admt user /N "TESTEuser1" /SD:"SOURCEDOMAIN.LOCAL" /SDC:"DC01.SOURCEDOMAIN.LOCAL" /TD:"TARGETDOMAIN.LOCAL" /TDC:"AD01.TARGETDOMAIN.LOCAL" /TO:"Hosting/0123456789" /UGR:YES /FGM:YES /CO:MERGE /MSS:YES /PS:"MTDC07.SOURCEDOMAIN.LOCAL" /PO:"COPY" /UX "HomeMDB,HomeMTA,showInAddressBook,msExchHomeServerName,mail,msExchRBACPolicyLink,msExch*,msRTCSIP*,msOnlineSIP*" /UMO:YES
PS: The problem only occurs when copying SIDHistory via power shell. Perform a migration without SIDHistory, removing the /MSS:YES parameter, it works, except that the graphical interface goes without problems.