Same here. 30+ PC, not domain joined due to this issue. 

It has to be fixed immediately!

I already posted in another thread: the situation is getting worse...

https://www.dell.com/community/Windows-10/What-exact-files-and-registry-entries-has-SupportAssist-deleted/m-p/6104390/highlight/false

Hi,

it doesn't seem to be solved !

Dell ?

This issue came up before and we reached out to the Optimize team, there response was...

"This is by design as SRE is designed specifically for consumer. Netlogon gets modified to Manual as most home/consumer users never use domain controllers and the service can be safely modified to Manual startup ( not stopped). This  way if there is an application or request to use this service it will be able to function. ( we do not disable it but only change the Startup Type to manual)." 

Our team did raise an enhancement request for a future release.

Thank you for the return.

But this answer from Dell is not acceptable.
Purchased PCs are enterprise-class PCs with Windows 10 Pro.
If SupportAssist is only for the general public, it should not be installed on client Windows that can join a domain.
Or modify it to check if the PC is on domain or not and do not modify the system in the same way.

Thanks for the reply jblinski

"This is by design as SRE is designed specifically for consumer."

I do not believe this is true. See: https://www.dell.com/support/contents/en/us/sebsdt1/article/product-support/self-support-knowledgebase/software-and-downloads/supportassist?lwp=rt

See: Managing Business Device

Dell supportassistant also comes pre-installed on Business Latitude laptops.

I have to agree with JGDUBOIS that it is not an acceptable answer. Besides the Netlogon service will NOT start ever on itself (no application request) and should ALWAYS be in automatic mode so users are able to login on domain joined computer. Also domain joined computers are able to verify to the domain and retrieve and apply Group Policies.

I urge you to leave the Netlogon service to automatic since the optimization only saves around 10 MB in RAM which is negligible for what kind of problems might occur on domain joined computers.

I copied both client feedback to the current enhancement we have.  I'm hoping this will be addressed in an upcoming release.  When I get an update on this enhancement I will post to this thread.

While this is appalling from Dell from a deployed piece of software on Business machines, the workaround we've employed is to add this to the computer object of our default domain policy. We don't apply this to servers, but as all Domain Joined machines will run it - it's a safeguard. 

Computer Configuration Object >> Preferences >> Windows Settings >> Registry

This step is unnecessary if this sets, but to ensure it's running, we follow with a logon script with "sc start netlogon"

Please fix. 

This is absolutely unacceptable to disable NetLogon on domain computers !!! Please change this behavior and reenable disabled services !!!

With NetLogon disabled on domain computer, group policy and time synchronization doesn't work !!