I believe this is the real problem here, this error no. The userenv.log yields following error: ProcessGPOs: GetNetworkName failed with 10013. It is interesting that at the time the error happens, the computer recieves and uses the correct connection-specific DNS suffix, but the registry key HKLM\SOFTWARE\Microsoft\Windows\Group Policy\Current Version\History\Network Name is empty!? What expains why the WF is using the standard profile, but it does not explain what leads to this behaviour, why is this empty? The computers are allways connected to the domain, they are never disconnected from it or used on an other domain. The problem in most cases occurs on machine startup and it goes away when the computer updates the GPO policy. Windows Firewall, which is configured from GPO is not detecting that the computer is on the domain and therefore it uses the standard profile instead of domain profile.
Hello, since some time now I investigate a strange thing happening on our network.
0 kommentar(er)
