If it helps to identify anything, the following are the results: Diagnostic Report (.0): - Windows Validation Data-> Validation Code: 0 Cached Online Validation Code: N/A, hr = 0xc004f012 Windows Product Key: *****-*****-V9488-FGM44-2C9T3 Windows Product Key Hash: rmk1OjF0iZq7gQoRmEcpnJHr0oc= Windows Product ID: 0042662-00010 Windows Product ID Type: 2 Windows License Type: OEM SLP Windows OS version: 00.1.0.001 ID. Since I have not been able to get this to join the domain, NetLogon would not be running.įor the MCDiag link, it would appear that I do not have a msdn copy but an OEM copy which would be expected with this HP machine. NetLogon doesn't actually start running until the machine can actually join a domain. However, from what I have read, this is expected. When I attempt to start it, it begins then quickly stops with a message that dependent services are not running. I have tried with the IPv4 settings as both DHCP and static ip no change.
0 Comments
Leave a Reply. |