Retour
-
Titre
ReACL is ok. cutover fails Result code: 32768 Domain join failed with error: 1332 -
Description
Attempting to cutover a windows server 2016 standard edition device and ReACL is successful. However, cutover job fails with the following error.Result code: 32768Domain join failed with error: 1332Also in log is:Cannot validate argument on parameter 'ComputerName'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.We can manually join the server to the target domain without any issues using the same credentials we use in ODM. -
Cause
POSSIBLE CAUSE 1"Cannot validate argument on parameter 'ComputerName'. The argument is null or empty.”--This error is indicating that the Target OU you are trying to create computer objects in cannot be validated. This can happen if OU path is incorrect or was renamed. Or if your profile’s credentials are incorrectPOSSIBLE CAUSE 2The network profile wants the DNS suffixes
(more likely when investigating 'possible cause 1' the below was discovered)a. Before raising this service request, I validated the target OU as well as tried using the default Computers OU (CN=Computers,DC=A,DC=Corp,DC=Com) but the same error.b. Profile credentials are validated and there is no error there.c. I am not using Credential Cache profiled. I have validated the Network profile and DNS settings both on current NIC and in the profile are set to use static IPs.
-
Résolution
RESOLUTION FOR POSSIBLE CAUSE 1
Validate that the OU path is correct and has the correct name. Confirm the Dirsync workflow is setting the Device OU correcting and device is still in scope and has not been moved to an OU which is outside the scope of Dirsync.Validate that the target IP is set in the credential cache profile If yes, confirm you can open Windows Power Shell from the AD Pro server and execute the following:Test-Connection -<ComputerName>Note: for *ComputerName *plug in the IP address of the Target DC as you have defined within Credential cache profile.Additionally, you will need to evaluate your network profile configuration. You want to ensure your network profile configuration under ADM settings > Network Profiles does align with your network adapter of the device. For example in past similar tickets, we have seen this error when within the network profile "obtain DNS server via DHCP” is set to true however the network adapter on the device is set to use Static IPs instead.
RESOLUTION FOR POSSIBLE CAUSE 2
Tweak network profile by adding the required DNS suffixes manually