If I migrate computer account using RUM, which DC it creates computer objects in target Domain?

Normally one close to the workstation.

Out of the box it will use the closest DC that it finds, as Jeff mentioned below.

Hi Chris, it is not getting created in my case. We have RUM in AWS, we have Domain controllers (GCs) in AWS as well. now when we move computer(in client network on-prem) using RUM, computer account is created in DC which is in AWS and not in workstation's nearest. Because of this, when move getting completed and system reboot it couldn't find computer account in nearest DC ( as replication interval is 15 mins) and user don't get authenticated in first reboot. we have to wait for account to get replicate from AWS DC to computer's nearest Dc and then only user get authenticated.
Is there any settings need to be changed , please suggest.

We don't currently support any part of the tool being deployed in AWS. The way the tool is written is that it issue's netdom /join to the workstation and from there the rest is up to Windows AD. So why the workstation is joining the DC in AWS would be a question for Microsoft in why it's not following AD site orders perhaps.

You have a few options.

1. The move task should be Agent based. The default is Remote. Uncheck that box. This will drive the whole task from the workstations.
1. Pre create the computer accounts. Then in the RUM task, omit the Target OU. You can't do both, join an existing computer object AND move the workstation.

Thanks Jeff this will help us.