Issue:
When performing an offline domain join for Windows 10 machine, after the machine completed the cutover process, the user will get a brand new user profile upon login. The original profile was not preserved.
Cause:
This is due to Windows 10 user profile was not ReACLed during the offline domain job cutover. For Windows 10, the user profiles are ReACLed at the time of cutover and this is done via a built-in process during online cutover. In the event of an offline domain join, the user profile ReACL was not triggered.
Solution:
A custom offline domain join action should be configured to include the Windows 10 User Profile cutover command, this can be configured via AD Pro’s action command menu option.
