Additional Microsoft Entra services and features related to identity, access, and network security
Based on the error, I would focus first on the Cloud Sync provisioning agent and its gMSA configuration rather than the AD Connect configuration itself.
Although the agent shows as Active in Entra, this only confirms that the agent is registered and communicating. The two required jobs (AD2AADProvisioning and AD2AADPasswordHash) are still not starting.
Since you mentioned seeing an initial gMSA-related error during installation, I would investigate that first:
On AD1, verify that the Microsoft Entra Provisioning Agent and Agent Updater services are running.
Verify the gMSA account and test it using PowerShell: Test-ADServiceAccount -Identity "provAgentgMSA" (Replace with the actual gMSA name.)
If the test returns False, investigate KDS configuration, gMSA permissions and replication between DC1 and DC2.
Check Windows Event Viewer, particularly System logs and Service Control Manager events. Event ID 7041 is worth checking because it can indicate missing service logon rights.
Review the provisioning agent trace logs under: C:\ProgramData\Microsoft\Azure AD Connect Provisioning Agent\Trace
If all these checks pass, I would export the migration wizard diagnostics and investigate the activation failure with Microsoft Support.
I would also avoid manually deleting or modifying the Cloud Sync configurations created by the migration wizard, as this could interfere with its recovery mechanism.
My first suspicion would be something related to the gMSA/service initialization, given the initial installation error you mentioned.