Windows Server team Blog

We wanted to make sure and remind the Microsoft Partner community that the Hyper-V Surge! program is happening right now.  This incentive program is for a limited time so don’t be late.  If you are wondering what the “Hyper-V Surge!” promotion is, here’s a great description:

If the Firewall service crashes a number of times within a short time period it does not automatically restart after the 4^th crash. If you review the Service Control Manager settings for the Firewall service appears to be configured to restart after all failures.

With server virtualization, you are able to decouple a compute instance from the underlying hardware.  That enables you to pool compute resources for greater flexibility. However, to truly transform your datacenter, you’ve also got to deliver your storage, compute, and networking resources as a shared, elastic resource pool for on-demand delivery of datacenter capacity. Indeed, this datacenter-level abstraction is a critical part of Microsoft’s Cloud OS vision.    

Organizations face many challenges when it comes to storage.  Data volumes are exploding, increasing the cost of storage and the headaches of storage management.  The rise of Big Data analytics means more data is being collected and mined than ever before – 90% of the world’s data has been created in the last two years.  Enterprise data is expanding at 20% per year or more. 

Autoruns v11.6: Autoruns is a utility for enumerating and disabling executables and DLLs configured to activate in dozens of autostart registration points.  This update fixes some minor bugs and adds Authenticode SHA1 and SHA256 hash reporting to Autorunsc output.

Just a quick FYI on a new Knowledge Base article we published today. This one talks about an issue where protection of virtual machines on a Windows Server 2008 R2 Hyper-V cluster host fails with error ID 30156 “The system cannot find the path specified (0x80070003).”

Just a quick FYI on a new Knowledge Base article we published today. This one talks about an issue where attempts to restore a SharePoint default.aspx file using DPM Item Level Recovery (ILR) fails with internal error code: 0x80990E14. This is a fairly unique situation that normally only comes up in testing but we thought it would be good to let you know about it just in case you happened to come across it. You can get all of the details here: