[1709, fcu] System cannot contact a domain controller

[jmak]

Hi

 

I have a clean Win 10 Edu installation which is failing to contact the domain controller. I used the celebrated Candy Crusher script to strip out unwanted apps and then deployed with MDT/WDS. I added it to the domain and moved it to my deploy container and the software install GPOs ran - so it clearly worked properly the first time. On next boot, the login script didn't run and network shares aren't available. I can ping them by ip address or name.

 

I found that the Netlogon service and it's dependency Workstation weren't running (they're set to auto). Workstation service could not start with error 1705: "The dependency service does not exist or has been marked for deletion." I found a solution for that by deleting a reg key:

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation

 

Delete "DependOnService"

 

After rebooting, I was able to start Workstation service and then Netlogon. I could then navigate to network shares. However, on rebooting, the services don't start again.

 

This works a few times and then I need to delete the registry entry again.

 

I've tried removing from the domain - I had to manually start the Workstation service to rename it and then after a re-start, manually start the Workstation service to allow me to re-join the domain. I also had to add the ".LOCAL" to the domain name for it to find the DC to join.

 

Any ideas? Please?

[jmak]

Any ideas please?

 

Thanks

[Michael]

You do have to specify the FQDN in your answer file if that helps!

[jmak]

You do have to specify the FQDN in your answer file if that helps!

Thanks for replying.

 

I added to the domain manually after deployment, so I don't think it's too do with the answer file?

[Michael]

Do you think the Candy Crush script has anything to do with it possibly? It doesn't sound right, or ready to deploy, so you're right to question it.

[jmak]

I'll try deploying the same image to a different PC. Just seems weird that it joined and then stayed working long enough to install the software that I deploy by Group Policy...

 

Thanks for your thoughts.

[jmak]

Well this is embarrassing....

 

I had a GPO set to (re-)enable SMB1 (which I temporarily disabled to protect against WannaCry until I was sure all the clients were patched). As 1709 doesn't have SMB1, the GPO was breaking connection to the domain.

 

Totally self inflicted, but at least I worked it out....

[Michael]

You'd think it would have no negative influence not supporting SMB1, but glad you sussed it!