If any network device is connected, this will result in a forever spinning login screen. This is platform independent and happens on both our Dell's and Lenovo's. I was able to determine this using Process Explorer for sysinternals. The behavior that happens after a domain join computer is freshly imaged with 2004 or is updated from a previous version is that if there is any network connectivity, lsass.exe will spike all cores to 100% CPU usage while trying to call dnsapi.dll and it will use multiple threads to attempt to execute. We have an issue (possibly specific to a GPO in our environment) that causes issues with the dnsapi.dll library in build 2004.
0 kommentar(er)
