Microsoft has updated the page that lists the hot fixes for Hyper-V. This now includes both Windows Server 2008 and Windows Server 2008 R2.
Microsoft updated this tool to include support for Windows Server 2008 R2 and VMM 2008 R2. What does it do?
What it does is allow you to update VM’s that are offline and stored in your VM library. A scheduled job runs, deploys the VM, updates it and stores it back in the library.
It does not work with templates unfortunately. I have no need to store VM’s in the library but I do have a tidy little collection of templates stored away (MS just refers to them as VHD’s, templates are a different thing altogether in VMM-speak) and I have no choice but to update them by hand.
Version 2.1 of the tool now works with System Center Virtual Machine Manager 2008 R2, System Center Configuration Manager 2007 SP2, and Windows Server Update Services 3.0 SP2. The tool also supports updating the Windows® 7 and Windows Server® 2008 R2 operating systems.
It was widely reported that a UK company was claiming that one of last weeks security updates by Microsoft was causing a “black screen of death” where Explorer would show nothing when you logged in. Microsoft responded overnight:
“While these reports weren’t brought to us directly, from our research into them, it appears they’re saying that our security updates are making permission changes in the registry to the value for the HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionWinlogonShell key.
We’ve conducted a comprehensive review of the November Security Updates, the Windows Malicious Software Removal Tool, and the non-security updates we released through Windows Update in November. That investigation has shown that none of these updates make any changes to the permissions in the registry. Thus, we don’t believe the updates are related to the “black screen” behavior described in these reports.
We’ve also checked with our worldwide Customer Service and Support organization, and they’ve told us they’re not seeing “black screen” behavior as a broad customer issue. Because these reports were not brought to us directly, it’s impossible to know conclusively what might be causing a “black screen” in those limited instances where customers have seen it”.
There you have it. Prevx didn’t do the responsible thing, i.e. contact Microsoft directly, and instead decided to generate some publicity for themselves. Their claims have been refuted so this leads me to wonder: are these developers more of the same who don’t comply with documented standards and just write rubbish code and to hell with their customers? I don’t know them, never dealt with them and certainly never heard of them before yesterday. You decide 🙂
I’ve read a few reports on this today. It’s being claimed by Prevx that one of Microsoft’s recent security updates causes issues on machines. The machine boots up OK, but you get nothing but a black screen when you log in. The have posted a “fix” (it’s not something MS has authorised). Note that this is an issue that can be caused by a lot of things. I’ve personally seen it a few times over the years.
Microsoft are reported to be investigating.