Mieliśmy ostatnio taki komunikaty na nowych instalacjach i próbach uruchomienia maszyn wirtualnych na komputerach Dell GX755 wyposażonych w procesory Intel Core 2 Duo E6550:
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 2009-02-14 23:46:11
Event ID: 3112
Task Category: None
Level: Error
Keywords:
User: NETWORK SERVICE
Computer: Comp.DOMAIN.LOCAL
Description:
The virtual machine could not be started because the hypervisor is not running. The following actions may help you resolve the problem:
1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.
2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)
3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.
Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
Source: Microsoft-Windows-Hyper-V-Worker
Date: 2009-02-14 23:46:11
Event ID: 3040
Task Category: None
Level: Error
Keywords:
User: NETWORK SERVICE
Computer: Comp.DOMAIN.LOCAL
Description:
’test’ failed to initialize. (Virtual machine 68DFD7B9-4411-4F66-B111-32BF010025F5)
I tu zagwozdka – VT włączone, wszystkie ficzery też, cold boot zrobiony. W końcu kfaz znalazł – trzeba wyłączyć Trusted Execution – nie mylić z Hardware Data Exectution Prevention.
WSUS – Self-update is not working event id 13042
od paru tygodni na serwerze aktualizacyjnym co jakiis czas pojawial sie nam blad
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Clients
Event ID: 13042
Date: 2008-02-26
Time: 16:57:22
User: N/A
Computer: XXX
Description:
Self-update is not working.
po wygooglowaniu roznego rodzaju rozwiazan i sprawdzeniu ich (doszedlem nawet do uzywania skryptu adsutil.vbs) nic nie znalazlem, az mnei w koncu natchnelo – WSUS stoi na bazie danych, a sam web service korzysta z Anonymus logon na IIS. "sprawdze, czy IUSR_XXX ma uprawnien na baze SUS" TADA! dziala. uruchomienie wsusutil checkhealth i 0 (slownie zero) bledow w eventlogu :)