Tag: windows 2012

Infrastructure-as-a-Service Technical Guidance for Hosting Service Providers

Microsoft published a guide for Hosting Service Providers that use or will use System Center and Windows Server. The guide just gives an overview from which you will be able to get the big picture on where to start but it is useful for starters. Download this document from here.

Advertisements

Microsoft Virtual Academy: Migration to Windows Server 2012

If you are in the path to Windows Server 2012 migration MVA just published videos for you. The course is still not available on MVA site but you can watch the videos:

Infrastructure-as-a-Service Product Line Architecture Fabric Architecture Guide and Management Architecture Guide

If you are working in one of those companies that are building IaaS there are two guides from Microsoft to help you with the basics. Check them out:

Book Review: Windows Server 2012 Hyper-V: Deploying Hyper-V Enterprise Server Virtualization Platform

These days I’ve managed to get my hands on another Hyper-V book and review it. These book reviews aim to give you more insight so you can make your mind if this book is for you.

The books starts at a very basic level by explaining what is Virtualization and the basic concepts of Hyper-V. After that as usual there is a chapter for planning, designing and implementing so you can  get a grasp on the basic features of Hyper-V. The third chapter is for Hyper-V Replica which is a very popular feature since the release of Hyper-V 3.0. Network and Storage have their own chapters as there are a lot of improvements there. Unfortunately in the Network chapter there is not detailed information about Network Virtualization (NVGRE) which is becoming very popular topic. PowerShell is implemented in every enterprise Microsoft product and because of that the author of the book hasn’t missed to place a chapter about automation with PowerShell. The next three chapters include more advanced content. You can find a chapter on how to use VMM 2012 to manage Hyper-V, a chapter on how to achieve high availability with Hyper-V and a chapter with best practices for securing Hyper-V. The last chapter that you will find in the book is about Backup and Recovery. It is interesting how in real world topic like Backup and Recover is also left last Smile. It may not be the most attractive part of Hyper-V and servers in general but it is something that we should take care good.

As a summary the book aims not so much to show you how to configure a certain feature but more to explain you the capabilities of Hyper-V in order to get most of them in your specific environment. I would recommend the book to engineers who just start to work with Hyper-V 3.0, to engineers who had little experience with Hyper-V 2.0 and now are facing the challenge to migrate to 3.0 and at last but not least to engineers who have been working with “the other guys” and now are converting to Hyper-V 3.0. If you think this book is for you can find in one of the following stores:

Network Virtualization (NVGRE) in Windows Server 2012 May Not work if You Do Not Have Update KB2779768 Installed

Two of my colleagues were testing Network Virtualization these days and stumbled on some strange issue. They’ve setup two standalone Hyper-V hosts, installed System Center 2012 Virtual Machine Manager SP1 and added the two hosts to be managed by VMM. They’ve created two networks with network virtualization in VMM. The first network was for customer A the second was for custom B. You can see a demo here how to setup Network Virtualization in VMM. After this 4 virtual machines were installed:

  • 2 for customer A. One (VMA1) located on Host1 and second (VMA2) located on Host 2.
  • 2 for customer B. One (VMB1) located on Host 1 and second (VMB2) located on Host 2.

Then they’ve started to ping VMA2 from VMA1 an vice versa but no replies were received.

It was time for some hard troubleshooting on network level with Wireshark. They’ve started to analyze the packets and compare them also to the RFC of the NVGRE. They were seeing this icmpType3Code10(Destination host administratively prohibited)upon inspection. They’ve searched over Internet and found this presentation Satoshi GOTO who is Microsoft MVP. The presentation is written in Japanese and provides information for our issue and why it was happening.

When Microsoft release Windows Server 2012 RTM Network Virtualization was included but it was based on the initial version of NVGRE RFC. So let’s compare the initial and the latest version of  NVGRE’s RFC:

In the initial version we have the following diagram for GRE Encapsulation Frame Format:

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   Outer Ethernet Header:             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                (Outer) Destination MAC Address                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |(Outer)Destination MAC Address |  (Outer)Source MAC Address    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  (Outer) Source MAC Address                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Optional Ethertype=C-Tag 802.1Q| Outer VLAN Tag Information    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Ethertype 0x0800        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   Outer IPv4 Header:
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Version|  IHL  |Type of Service|          Total Length         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Identification        |Flags|      Fragment Offset    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Time to Live | Protocol 0x2F |         Header Checksum       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      (Outer) Source Address                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  (Outer) Destination Address                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   GRE Header:
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |0| |1|0| Reserved0       | Ver |   Protocol Type 0x6558        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                        Tenant Network ID (TNI)|   Reserved    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   Inner Ethernet Header
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                (Inner) Destination MAC Address                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |(Inner)Destination MAC Address |  (Inner)Source MAC Address    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  (Inner) Source MAC Address                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Optional Ethertype=C-Tag 802.1Q| PCP |0| VID set to 0          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Ethertype 0x0800        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   Inner IPv4 Header:

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Version|  IHL  |Type of Service|          Total Length         |


Sridharan et al             Informational                      [Page 7]

Internet-Draft NVGRE September 2011 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Identification |Flags| Fragment Offset | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Time to Live | Protocol | Header Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Options | Padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Original IP Payload | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

In the latest version we have the following diagram for GRE Encapsulation Frame Format:

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   Outer Ethernet Header:             |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                (Outer) Destination MAC Address                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |(Outer)Destination MAC Address |  (Outer)Source MAC Address    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  (Outer) Source MAC Address                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Optional Ethertype=C-Tag 802.1Q| Outer VLAN Tag Information    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Ethertype 0x0800        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   Outer IPv4 Header:
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Version|  IHL  |Type of Service|          Total Length         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Identification        |Flags|      Fragment Offset    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Time to Live | Protocol 0x2F |         Header Checksum       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      (Outer) Source Address                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  (Outer) Destination Address                  |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   GRE Header:
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |0| |1|0| Reserved0       | Ver |   Protocol Type 0x6558        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               Virtual Subnet ID (VSID)        |   Reserved    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   Inner Ethernet Header
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                (Inner) Destination MAC Address                |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |(Inner)Destination MAC Address |  (Inner)Source MAC Address    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  (Inner) Source MAC Address                   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Optional Ethertype=C-Tag 802.1Q| PCP |0| VID set to 0          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |       Ethertype 0x0800        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   (Continued on the next page)




Sridharan et al             Informational                      [Page 6]
 
Internet-Draft                  NVGRE                     February 2013


   Inner IPv4 Header:
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Version|  IHL  |Type of Service|          Total Length         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Identification        |Flags|      Fragment Offset    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Time to Live |    Protocol   |         Header Checksum       |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                       Source Address                          |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Destination Address                        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                    Options                    |    Padding    |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                      Original IP Payload                      |
   |                                                               |
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

On first sight there are no significant differences. I’ve highlighted with yellow the area where you need to focus your attention. You can see that the only difference is that the term Tenant Network ID (TNI) was replaced with Virtual Subnet ID (VSID). but let’s look closer at the explanation in the RFC.

Initial version:

  • The Key field in the GRE header is used to carry the Tenant Network Identifier. Key field is 32 bits long of which the lower 24 bits are used for TNI. The Key Present (bit 2 in the GRE header) is always set to 1.
  • The upper 8 bits of the Key field are reserved for use by NVGRE endpoints and are not part of the TNI space. NVGRE endpoints MUST set this value to zero.

 

Latest version:

  • Virtual Subnet ID (VSID): The first 24 bits are used for VSID as shown in Figure 1.
  • FlowID: The last 8 bits of the Key field are (optional) FlowID, which can be used to add per-flow entropy within the same VSID, where the entire Key field (32-bit) is used for ECMP purposes by switches or routers in the physical network infrastructure. If a FlowID is not generated, the FlowID field MUST be set to all zero.

 

So if you are reading right in initial version VSID 32 bits were looking like this:

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-

| 8 bits FlowID |                          32 bits VSID                         |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-

and in the latest version we have this:

-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-

|                   32 bits VSID                                 | 8 bits FlowID |

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-

Format was changed.

Even it was not stated nowhere update KB2779768 was changing this format from the initial version to the format of the latest version. If you see in the description of the update you will find that only these issues are fixed in it:

  • Improves the speed of text input in some Windows Store apps.
  • Resolves an issue that prevents some users who have Windows Display Driver Model (WDDM) 1.0-based devices from using mirror drivers.
  • Resolves an issue that may prevent some games from being updated.
  • Resolves an issue that may cause blips in audio playback when a computer is running in "Connected Standby" mode.
  • Resolves an issue in which Windows Store apps do not obtain data when they connect to Windows Store through a cellular network.

But this update has another web page where are listed which files will be changed after the update is applied. An there you can see these files are changed:

  • Wnv.sys
  • Wnvapi.dll

Both files define Network Virtualization in Windows Server 2012.

In our case Host1 was having update KB2779768 and Host2 didn’t had it. This is like the two hosts are speaking in different languages for Network Virtualization.

You should install KB2779768 on all your Hyper-V hosts if you plan to implement Network Virtualization because every network device that will be NVGRE aware will follow the latest NVGRE format.

This issue is widely spread over Internet but only in Japanese web sites.

All credits for these findings go to my colleagues Yordan Dimov and Kiril Tsvetanov for tracing and resolving this issue and to Satoshi GOTO who detailed it in his presentation.

Book Review: Windows Server 2012 Unified Remote Access Planning and Deployment

This is another book review. Windows Server 2012 Unified Remote Access Planning and Deployment book is about technologies I do not have so much experience with – DirectAccess and VPN. Even though I specializing in System Center and Hyper-V it is good to have broader knowledge at least on some basic level. Technologies like DirectAccess and VPN are deployed event in the Cloud.

First I will start that is a small book but it understandable that it covers only one feature in Windows Server 2012. Before starting to read this book I recommend to have basic knowledge on Windows Server, Active Directory, Certificate Services and Networking. The book starts by introducing you to DirectAccess, how it works on general level and what are the requirements for it. It doesn’t rush you directly in the technology instead it explains very well every technology that is built into DIrectAccess. This very good if you have only some basic knowledge on Windows Server, Active Directory, Certificates services and Networking because explains you technologies like IPv6, DNS, ISATAP, DNS64, NAT64, 6to4, Teredo, IP-HTTPS, Group policy and PKI. In next chapters the book continues by introducing you to the architecture of DirectAccess and how to prepare your environment for implementing it. This is followed by installation and configuration of Unified Remote Access role. The last chapters cover some advanced scenarios as well as troubleshooting tips.

In summary the book is very easy to read and provides very good picture of Unified Remote Access role in Windows Server 2012. I recommend this book for engineers who have the task or consider deployment of DirectAccess in their environments. The book is suitable reading for those who have implemented Direct Access in Windows Server 2008 R2 in the past and want to know what have changed in 2012 and how they can migrate to the new version. If you think that this book is for you can grab it on one of these stores:

New Version: Insight Control for Microsoft System Center 7.2

Insight Control for Microsoft System Center is a package of integration kits that aim to integrate HP Hardware and Software with Microsoft System Center. Here is the description of these integration kits taken from the HP site:

System Center Operations Manager (SCOM) support:

  • The HP ProLiant and BladeSystem Management Packs expose the native capabilities of ProLiant and BladeSystem servers and enclosures to help prevent problems from occurring by proactively monitoring and managing hardware health and intelligently responding to hardware events on servers running Windows.
  • The HP ProLiant Agentless Management Pack manages the health of ProLiant Gen8 servers without the need for loading OS-based SNMP agents or WBEM providers. It can also be used to monitor the health of servers that do not have an OS yet loaded, as well as ProLiant Gen8 servers running any operating system that has a supported Agentless Monitoring Service (such as VMware ESXi).
  • The HP ProLiant Linux and VMware Management Packs provide the ability to monitor hardware health and configuration, as well as to receive HP hardware alerts, on ProLiant servers running Linux and VMware ESX.
  • Supports SCOM 2007 and SCOM 2012 (including SP1) for all HP SCOM management packs.

 

System Center Virtual Machine Manager (SCVMM) support:

  • The HP Performance Resource Optimization (PRO) Management Pack reduces unplanned downtime by proactively automating live migration of Hyper-V virtual machines based upon HP pre-failure and predictive hardware alerts from ProLiant servers. Supports SCVMM 2008.
  • HP SCVMM 2012 Integration Kit provides HP WinPE and production drivers for ProLiant servers to assist with OS deployment via SCVMM 2012 (including SP1).
  • The HP ProLiant Updates Catalog can be used by SCVMM 2012 (including SP1) to provide simplified Windows driver and firmware updates via a rotating, automated workflow for Hyper-V clusters.

 

System Center Configuration Manager (SCCM) support:

  • The HP ProLiant Server Operating System Deployment (OSD) feature provides quick and reliable Windows deployment to bare metal HP servers, including pre-deployment hardware and BIOS configuration, and post-OS HP driver and agent installation.
  • The HP ProLiant Updates Catalog ensures consistency and maximizes uptime with simplified Windows driver and firmware updates using the HP Service Pack for ProLiant.
  • The HP ProLiant Hardware Inventory Tool provides detailed component level inventory of every managed HP Windows server.
  • Supports SCCM 2007 and SCCM 2012 (including SP1).

 

Let’s look what has changed from 7.1 version:

Support for Microsoft System Center Operations Manager (SCOM) 2012 SP1

  • Management packs certified with SCOM 2012 SP1
  • Support for Windows Server 2012 monitoring

 

System Center Operations Manager (SCOM) Management Pack Updates

  • Updated system discovery rule for BladeSystem Management Pack
  • Updated WMI Provider for ProLiant DL980

 

Support for Microsoft System Center Configuration Manager (SCCM) 2012 SP1

  • Updated SCCM 2012 Integration Kit to support SCCM 2012 SP1 (supported only when SCCM 2012 SP1 is installed on Windows Server 2012)
  • Updated HP ProLiant Updates Catalog to support SCCM 2012 SP1
  • Support for Windows Server 2012 deployment and updates
  • Note: The HP SCCM 2012 Integration Kit is only supported on SCCM 2012 SP1 installed on Windows Server 2012
  • Note: OS deployments to Windows Server 2008 R2 Core are not supported

 

Support for Microsoft System Center Virtual Machine Manager (SCCM) 2012 SP1

  • Updated SCVMM 2012 Integration Kit to support SCVMM 2012 SP1
  • Updated HP ProLiant Updates Catalog to support SCVMM 2012 SP1
  • Support for Windows Server 2012 deployment and updates

 

Updates to support HP Service Pack for ProLiant (SPP)

  • Updated SCVMM 2012 & SCCM 2007/2012 Integration Kits
  • New Drivers and firmware from SPP 2013.02.0
  • New software bundles included in the HP ProLiant Updates Catalog to support Windows Server 2012

 

So we now have full SC 2012 SP1 and Windows Server 2012 support. This is great job of HP releasing support so soon after GA of SC 2012 SP1.

If you are wondering what have changed like versions on the SCOM management packs look here:

image

Keep in mind that new versions of the management pack for HP servers and blades will come only in this bundle Insight Control for Microsoft System Center. No separate downloads will be released. HP Storage Management Pack for now stays separate download and it is not provided in this package.

To download this new version go here. You only need to download Insight Control for System Center 7.2 DVD ISO – Mar 2013 for the System Center integration kits.