Some registry keys may no longer be set after computer is moved to the target domain. Is it possible that RUM (Resource Updating Manager) deleted them during resource updating or computer move cycles?
RUM (Resource Updating Manager) scans through the registry when performing resource updating on the computer in order to replace/append source SIDs with the corresponding target values. During the computer move process some keys that are responsible for the domain membership are modified. However no registry keys that are critical for the computer functionalities are deleted in any way. Please refer to the resolution section to review some possible scenarios.
When a computer joins a target domain and reboots, its local Group Policy Settings (GPO) are refreshed based on the settings in the target environment. As a result, many registry values are modified or removed.
Before the migration:
HKLM\Software\Policies\Microsoft\Windows NT\Current Version\Winlogon
contains one DWORD value - SyncForegroundPolicy set to 1
After the migration:
The entire HKLM\Software\Policies\Microsoft\Windows NT\Current Version\Winlogon key is not present.
This is a result of "Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer start up and logon " GPO setting not being configured in the target environment.