Hyper-V Resolving Event ID 4096

re: Hyper-V Resolving Event ID 4096

Andy Stumph — Mon, 05 Jan 2009 20:47:32 GMT

Hey John,

I ran into this a while back and I wrote a little powershell script to delete the broken links.

It uses James O'Neill's Hyper-V library on codeplex http://www.codeplex.com/PSHyperv, so you will need that loaded into your shell.

-Andy

-------

. .\Hyperv.ps1

$VMPath = "C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines"

$FileNames = Get-ChildItem $VMPath | select Name

$VMs = Get-VM | Select Name

foreach ($FileName in $Filenames)

{

foreach ($VM in $VMs)

{

#$VM.Name

if ($FileName.Name.split(".")[0] -match $VM.Name)

{

$Match = "True"

}

if (-not $Match)

{

Write-Host "Deleting $($FileName.Name)" -foregroundcolor Red

Remove-Item "$($VMPath)\$($FileName.Name)"

}

else

{

Write-Host "$($FileName.Name) is Good!" -foregroundcolor Green

}

$Match = $Null

}

re: Hyper-V Resolving Event ID 4096

rajeev — Tue, 13 Jan 2009 06:34:39 GMT

This is a great post and was really helpful! If only the Hyper-V team decided to add this event ID to their online help documentation.

And I would assume that the UI would expose these stray hyper v configs and let the user delete them without messing with the config files. Alas, Wishful thinking???

re: Hyper-V Resolving Event ID 4096

Chris — Tue, 10 Mar 2009 03:56:34 GMT

Argh. I admit, I am completely stuck. I've managed to make the Hyper-V MMC Manager work in Windows7 32bit; but in 64 bit, I'm now getting a goofball issue.. I can connect and see the VMs, but when I try to start any of them, I get an error..

"Your system adminstrator does not allow the use of default credentionals to log on to the remote computer HYPERV because it's identity is not fully verified."

So, hell, I go ahead and add the certificate as a trusted publisher.. it makes absolutely NO difference,

"The certificate is not from a trusted certifying entity"

(I think).

Works beautiful in Win7 32bit.. but damn, I'm stuck.. anyone seen this ???

re: Hyper-V Resolving Event ID 4096

jhoward — Tue, 10 Mar 2009 05:12:39 GMT

Chris - what build number of Windows 7, and are you logging on with a smartcard? (I assume you are also remotely managing a server.....? If so, what is the server build - 2008, or R2, and if R2, which build number?)

Thanks,

John.

re: Hyper-V Resolving Event ID 4096

Chris — Tue, 10 Mar 2009 16:24:09 GMT

John-

I'm using 7000 X64 build; I probably should log into my MSDN account and see if there is a new one out there for me to grab, but haven't had a chance, I will try to do that today.

On our HyperV, I have these servers:

Windows 2008 (stand alone)

Windows 2003 SBS (setup, virtualized from dead hardware)

And here's a bit of a gasp, but wanted to try it, a Windows NT 3.1 Server.. just wanted to try this, still had the floppy discs, so what the hell :) :)

The thing is, it doesn't matter which VM I try to connect to, the Windows7 box won't let me get remotely that far, saying the certificate for the box I'm connecting to (HYPERV, a box running Hyper-V 2008 Server, ie core) has a certificate published by a non-authenticated server. I've added the certificate to the trusted publishers, etc. still no-go.

Blah!

I'm wondering whether or not turning on the Win2k3 SBS, which is setup as an AD, whereas everything else in this test environment is stand-alone is part of the issue. I've debated giving the SBS an IP outside of the local range and creating a virtual IP-network to keep it off the same subnet as the HyperV server, just in case I"m running into something that way.

But the Win7 x32 build can open up a window on all of these.

That's the weird part. On the x64 build, the manager opens, it sees the server, I can even create new VMs.. at least build the HDD, change settings, etc. all of that works. I can even get the thumbnail view of what's going on.. but when I try to connect to them, bammo.. the certificate/publisher stuff shows up :(

re: Hyper-V Resolving Event ID 4096

Chris — Tue, 10 Mar 2009 18:50:07 GMT

Never mind. In WIndows 7 X32, "Install Certificate" works fine.. but it doesn't in x64. Using the certificates MMC plugin, I was able to add the certificate to the local computer and that fixed it.

re: Hyper-V Resolving Event ID 4096

jhoward — Tue, 10 Mar 2009 18:56:44 GMT

Chris - is it possible you are hitting http://support.microsoft.com/default.aspx?scid=kb;EN-US;967902? Alternately, under Hyper-V Settings in Hyper-V Manager, have you flipped the "Use default credentials..." checkbox? It shouldn't be necessary to import a certificate from the server into the Win7 client....

Thanks,

John.

re: Hyper-V Resolving Event ID 4096

Chris — Tue, 10 Mar 2009 20:33:39 GMT

Nope, not running into expired certificate; using a Hyper-V Server R2 (Beta) candidate for testing purposes only; certificate is valid through 3/10 or something. It just doesn't like publisher. I ran the HVRemote script to reset; I've replicated this, it only seems to occur within the x64 version, this never happens in x32.. so, I'll submit it in as a bug for now.. :) But it's fixed after an import.