Joining a Target to a Domain through OSIM Job fails. The OS installation completes successfully but the target is not joined to a Domain
 
Domain parameters in the OSIM Job:
 

<Please see attached file for image>

In Windows 10 Fall Creators Update and Windows Server, version 1709 (RS3) and later versions, the Server Message Block version 1 (SMBv1) network protocol is no
longer installed by default. It was superseded by SMBv2 and later protocols starting in 2007. Microsoft publicly deprecated the SMBv1 protocol in 2014.
 
More Information can be found at

• https://social.technet.microsoft.com/Forums/en-US/59183715-0c04-44f7-b5ea-bb37da4125a5/unable-to-join-domain-with-new-windows-10-computers-build-1803?forum=win10itpronetworking
• https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows
• https://support.microsoft.com/en-us/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

CA Client Automation R14 SP2 and newer

Latest Windows 10 and Windows Server 2016 Operating Systems

During the OS installation, SMBv1 can be temporarily enabled on the target for joining it to a domain.
Reset the value , once the operation is finished.
 
Steps to Enable SMBv1 during OSIM Job:
 

1. If you are creating the OS Image the file can be changed in  DSM\osimips\os-template\images\<WINDOWS OS TYPE>\oeminst
2. If the OS image already exists , change the file from the location: DSM\Server\SDBS\var\managedpc\images\<ImageName>\<ImageName>\oeminst

 

<Please see attached file for image>

1. If you are creating the OS Image the file can be changed in  DSM\osimips\os-template\images\<WINDOWS OS TYPE>\oeminst
2. If the OS image already exists , change the file from the location: DSM\Server\SDBS\var\managedpc\images\<ImageName>\<ImageName>\oeminst

<Please see attached file for image>