SmartDeploy - Join Network

[Mikules]

Seems no matter what I do SmartDeploy answer file will not join my machines to the network using Client deployment abilities. Have to manually go over to the machines and join them. Typed in everything right, domain\AdminUser and password. Nothing

 

Anyone else finding this to be an issue too ?

[SmartDeploySupport]

Hi there,

Domain joining failures can occur for a variety of reasons relating to network connectivity, syntax, or user permissions. On a target device that has experienced this issue, boot to SmartDeploy media and click the Collect logs button. Save the resulting zip file to an external location, and send it to support (at) smartdeploy.com. Once we have your logs in hand, we can advise further.

SmartDeploy Support Team

 

TECH RESOURCES

SmartDeploy User Guides

DeployCentral Forum

Platform Pack RSS

 

SOCIAL

 

[Mikules]

Sorry for the delayed responses! I'm going to try this again today and post an update with logs

[Mike Grills]

Having the same problem.  Would love to see the answers to some of these related domain joining topics in the forum once they are resolved.  Would be a tremendous help.  Thank you.

[Jeff Harris]

The place to look for information is C:\Windows\Debug\NetSetup.log. If this file isn't present, it's possible that the sysprep mini-setup is crashing, which means we'd want to look at the image source. 

[wsova]

Any further information on this? We are running into a similar situation where joining the domain fails. Our internal domain name is "companyname.local"

 

Any help would be appreciated.

[SmartDeploySupport]

Hi wsova,

We'll want to see a complete logset to troubleshoot this further, and I've opened a support ticket with you to troubleshoot this further.

Unfortunately, there is no single, specific answer to domain join failure, but broadly speaking, the failures tend to occur due to bad credentials, a bad FQDN for the domain, a bad Distinguished Name for a specified OU, or a failure to connect to a domain controller during the SPECIALIZE phase (which can occur with certain network adapters that fail to initialize without a reboot).

The logs can usually tell us where to look, so that's where we'd need to start.

Glenn
SmartDeploy Support

[Ian Zavardino]

Hey All,

 

We've had similar issues and this is what we found.  So lets you have a Golden Image with V1903.  And you update it to V2004.  It will not join the domain.  From what I've learned is that you cannot do a Feature update to your Golden Image.   Essentially Every time there is a Feature update to Windows. You'll have to re-create your Golden Image.  This is what I've been told by Smart Deploy. 

[Jeff Harris]

1 hour ago, Ian Zavardino said:

Hey All,

 

We've had similar issues and this is what we found.  So lets you have a Golden Image with V1903.  And you update it to V2004.  It will not join the domain.  From what I've learned is that you cannot do a Feature update to your Golden Image.   Essentially Every time there is a Feature update to Windows. You'll have to re-create your Golden Image.  This is what I've been told by Smart Deploy. 

Correct; there is a specific bug in Windows/Sysprep following an in-place upgrade to v2004. You always want to create a new VM, installing the new version of Windows you want to deploy from ISO.