You must have the required knowledge in SQL Server, your Windows Server environments and of course some AX 2012 architecture understanding, before, migrate make sure you have the separate environment on new-domain.
Identify separate environments for Pre and Post Migration environments to carry out any verification that is required as part of migration.
1- Copy production database from one Active Directory domain to different production Active Directory domain environment.
2- Restore the Prod-database and set proper SQL permissions on destination.
Changing the Microsoft Dynamics AX users account to new Domain Account information.
4- In the SQL management studio run the following queries on the BusinessData Database (AXProdNEW):
DELETE FROM SYSSERVERCONFIG
DELETE FROM SYSSERVERCONFIG
5 Find out user information: select SID, Networkdomain, networkalias from userinfo
where networkalias = ‘useralias’
6- Open CMD with “Run as admin” and type:
wmic useraccount where (name='your_windows_username' and domain='your_domain') get name,sid
Example: wmic useraccount where (name='administrator' and domain='contoso') get name,sid
7-Copy the SID to notepad.
8- In the SQL management studio run the following query on the BusinessData Database (AXProd_New):
UPDATE USERINFO
SET SID='your_sid', NETWORKALIAS='your_windows_username', NETWORKDOMAIN='your_domain', NAME='your_name'
WHERE ID = 'Admin'
Ex:
UPDATE USERINFO
SET SID='S-1-5-xx-xxxxx-xxxxxxxx-xxxxxx-xxxx', NETWORKALIAS='administrator', NETWORKDOMAIN='contoso', NAME='ABC'
WHERE ID = 'Admin'
Note: Please always think about Rollback Plan, In case of any issues while carrying out the migration or if there is a migration failure at any point of time during migration, then it should be possible for the system to roll back.
