Cloud and Datacenter Management Blog

Microsoft Hybrid Cloud blogsite about Management

Leave a comment

NEW Website System Center User Group Netherlands SCUG.NL #sysctr #SCVMM #Cloud


Thank you Taco van Gerven for this Great Website !

I’m very Proud and honored to be an Member of the Dutch System Center User Group of the Netherlands for the community together with this Great Team :


  • Brenda Kager
  • Helmer Zandbergen
  • Robert Smit
  • Ronny de Jong
  • James van den Berg



Creating Virtual NICs on a Virtual Hyper-V 2012 R2 Switch for #Hyperv Cluster with #Powershell

Dell EnclosuresTwo Dell Enclosures with four Dell M620 Blades for Hyper-V 2012 R2 Cluster

Dell M620 Blade 384GB MemoryEach with 384GB internal Memory

We got four physical NICs in each blade server for the following configuration in Microsoft Windows Server 2012 R2 Datacenter :

Teaming IconeOn each NIC-Team we have made a Hyper-V Virtual Switch.

On each NIC-Team we have different VLANs from our Multi-Tenant Datacenter comming through.

For our Microsoft Hyper-V 2012 R2 Cluster we need more NIC’s for our Hyper-V Nodes and we make them virtual with Powershell 4.0 :

Powershell ISE 4

Open Powershell in Administrator modus.

vNIC Powershell CMD

Here we make two virtual NIC’s with Powershell connected to the virtual Management switch.

  • VMNetworkAdapter called HBVLAN1250 for Heartbeat
  • VMNetworkAdapter called CSVVLAN1251 for Live Migration

Each NIC in the right VLAN configured with Powershell After these Powershell commands you can configure the VNICs for the Microsoft Hyper-V 2012 R2 Cluster : Network Hyperv


From Microsoft Private #Cloud to Hybrid Cloud Services Part 1 of 5 #Hyperv Clustering

This is the first of five blog posts “From Microsoft Private Cloud to Hybrid Cloud Services”.
Here you can find our Configuration hardware on-premisses and the Start of this blog series.

PRIVATE CLOUD Infrastructure :

Before we start with installing Microsoft Windows Server 2012 R2 on our hardware, it is important to check your vendor support for Windows Server 2012 R2.
For production is vendor support very important ! (Check this for your own hardware configuration first)
Microsoft built a lot of drivers into Operating System W2012R2, we use DELL Power Edge Servers and found the following about support :

Dell PowerEdge R710 Support

CHECK For Windows Server 2012 R2 Hyper-V Node

LIST Built in Drivers Windows Server 2012 R2Here you can find more information on Dell Power Edge Servers

Our Dell Power Edge Servers (R410 – R610 – R710 – M620) hardware configuration drivers are in the box of Windows Server 2012 R2 🙂

We already had Microsoft Windows Server 2012 Datacenter edition installed in our forest called ICTCUMULUS, with the DELL management DVD for W2012.
Dell Support & Drivers for the Power Edge R710

We successfully upgraded all the Servers from Windows Server 2012 => Windows Server 2012 R2 and we raised domain and forest functional level to R2 :

Raise Forest Functional Level

Here you see the configuration step-by step guide for Microsoft Windows Server 2012 R2 Hyper-V Cluster :

Dell PowerEdge R710 Back Config networkDELL Power Edge R710 Hyper-V Node Back

We started with building the production Teams on each Hyper-V node with Microsoft Windows Server 2012 R2 NIC-Teaming :

Enable NIC Teaming

Enable NIC-Teaming on the local Server with Server Manager

NIC Teaming Productie Teaming Mode

NIC Teaming Productie LB mode

NIC Teaming Productie Standby Adapter

Our two 1 Gbit NICs are both active for the capacity

Productie Team StatusOn each Hyper-V node.

NIC Teaming ProductieNIC Productie Team Settings.

NIC Teaming Productie operationeelHyper-V Productie Team is Operational.

Network overzicht Hyper-V NodeWe configured all four Hyper-V nodes the same :

  • NIC 1+2 Production Team
  • NIC 3 CSV for Storage (I-SCSI Trafic)
  • NIC4 Heartbeat network for Cluster.

For more information about Microsoft Windows Server 2012 R2 NIC Teaming is on this WhitePaper

Now we have network configured we can attach the I-SCSI LUNS to the Server, with our Dell Powervault MD3200i storage box :

Dell PowerVault 3200i Storage LUN Config

With the Storage Manager of Dell we made a Host Group “Hyper-V_Cluster” with the four Hyper-V nodes.
There we provision 5 LUNS ( 4 x VDISK of 1TB and 1 x VDISK for QUORUM) for the Microsoft Windows Server 2012 R2 Hyper-V nodes.

ISCSI Initiator Icone

With iSCSI Initiator of Windows Server 2012 R2 we attach the storage which is provisioned with the Dell Storage Manager.

ISCSI Initiator Quick Connect

ISCSI Discovery Target Portal

ISCSI Volumes and DevicesHere you get your LUNS by clicking on Auto Configure.

Now we have the storage presented to the Hyper-V host and can we configure the LUNS with Diskmanagement :

Disk management Config 1Here we see the Disks in Disk Management.

Disk management Config 2

Disk management Config 3

Disk management Config 4

Disk management Config 5

Disk management Config 6

Disk management Config 7

Disk management Config 8

Disk management Config 9

Disk management Config 10

Do this with all the LUNS and give them the right Volume Label like for example CVS1, CSV2, CSV3, CSV4….

Disk management Config 11

Disk management Config 12From Server Manager you can see all the Hyper-V Nodes.

Now we Have Networking and Storage ready to go, we can install the Features Hyper-V and Failover Clustering of Windows Server 2012 R2.

Enabling Features with dism commando

Install prerequisite .net Framework 3.5 via de command prompt. Make sure you mount the Windows 2012 DVD in D:
Run as Administrator CMD.exe  and type the following commando : dism /online /enable-feature /all /featurename:NetFx3 /source:d:\sources\sxs

  1. Install the following features of Windows Server 2012 R2 : Hyper-V and Failovercluster
  2. Update Software via Windows Update.
  3. Open failover Cluster Manager


FailOverCluster 1


FailOverCluster 2

FailOverCluster 3

FailOverCluster 4

FailOverCluster 5

FailOverCluster 6

FailOverCluster 7

FailOverCluster 8

FailOverCluster 9

In our report we had a message about Gateway :

FailOverCluster 10FailOverCluster 11

FailOverCluster 12

Here we give the Cluster a name with IP-adres.

FailOverCluster 13

FailOverCluster 14

FailOverCluster 15After the Cluster is ready, we add the storage to Cluster Shared Volumes (CSV)

FailOverCluster 16 CSV

FailOverCluster 17

For Hyper-V we set the Storage path for the VM Configs and VHDx Disks in Hyper-V Settings for each host.

Virtual Hard Disks Cluster path

With these steps we checked our hardware that’s in the driver box of Microsoft Windows Server 2012 R2, we provisioned iSCSI Storage and made a Windows Server 2012 R2 Hyper-V Cluster.
My Next blog is all about Management with System Center 2012 R2 Virtual Machine Manager and App-Controller.


#Microsoft System Center 2012 R2 Evaluation VHDs available #sysctr #SCVMM #Hyperv

microsoft_system_center_2012_r2_VHDsThis VHDs enables System Center customers to jointly evaluate System Center 2012 R2 and Windows Server 2012 R2 . For detailed information about each component, see the component documentation included with these download files.
System Center 2012R2 components that ship Evaluation VHDs can be found at the following locations:



Starting : From Microsoft Private #Cloud to Hybrid Cloud Services Part 1 of 5 #SCVMM #WindowsAzure

Private Cloud Rack TestLAB

Windows Server 2012 R2 Logo

The Microsoft Cloud OS

Cloud computing is happening. It is being driven by the exponential growth in modern applications, data and devices. These trends require organizations to quickly scale and deliver continuous services. Simultaneously, innovation is happening across storage, network and compute technologies. With these new requirements and innovations, IT is under pressure to deliver capacity on demand, whether for short-term projects or longer-term initiatives. At the same time, organizations have higher expectations for service levels – services must be always up, always on, with no planned or unplanned downtime. To meet these challenges, a new modern platform is required. In the era of cloud computing, Microsoft delivers this with the Cloud OS. The Cloud OS takes on a broader role than just managing a server. Microsoft’s vision for the Cloud OS is focused on the transformation of the datacenter, enabling modern applications, unlocking insights on any data and empowering people-centric IT. The Cloud OS requires a comprehensive execution of vision crossing a wide range of enterprise technologies, including Windows Azure, SQL Server, System Center and Windows Server. Fundamental to the modern datacenter, is the ability to build private cloud infrastructures and quickly scale within the datacenter as well as agile and secure consumption of Windows Azure and service provider cloud capacity.

In the picture above you see our Testlab and all the Servers are installed with Microsoft Windows Server 2012 R2 in a forest.

Here we have the following configuration of our TestLAB :

  • The Domain Controller is an Dell Power Edge R410 Server Intel Xeon CPU E5520 @ 2,20Ghz 2,20Ghz and 4GB Memory installed with 2 x 144GB SAS HDD in RAID 1 set.
  • The SCVVM Server is an Dell Power Edge R610 with Intel Xeon CPU E5530 @ 2,40Ghze 2,40Ghz and 32GB Memory installed with 2 x 144GB SAS HDD in RAID 1 set and 300GB RAID 5 set
  • 4 x Hyper-V Node is an Dell Power Edge R710 with Intel Xeon CPU L5520 @ 2,20 Ghz 2,20Ghz and 48GB Memory installed with 2 x 144GB SAS HDD in RAID 1 set.
  • The RAS Server is an Dell Power Edge R710 with Intel Xeon CPU L5520 @ 2,20 Ghz 2,20 Ghz and 48GB Memory with 2 x 144GB SAS HDD in RAID 1 set.
  • I-SCSI Storage Box is an Dell Powervault MD3200i with 12 x 2TB SAS HDD

The Remote Access Server (RAS) is an Windows Server 2012 R2 with more features installed :

  • RAS feature installed for VPN and DirectAccess connections.
  • Hyper-V feature is installed for an Virtual Web Proxy Server ( Ubuntu 13.10 with Squid proxy )
  • WSUS Server
  • Virtual VPN Gate way site-to-site for Windows Azure.

In the next couple of blogs we will share the installations step by step on the following items :

  1. Installation of I-SCSI Storage for Hyper-V Nodes and Failover Clustering for Hyper-V with CSV
  2. Installation of SQL 2012 SP1 and System Center 2012 R2 Virtual Machine Manager | APP-Controller
  3. Installation of Microsoft Virtual Gateway for Site-To-Site VPN with Windows Azure.
  4. Private Cloud Computing – Services
  5. Hybrid Cloud Computing – Services


Leave a comment

UPDATE :Technical Documentation for Windows Azure Pack for Windows Server #WAP #WindowsAzure #Cloud


  • Deploy Windows Azure Pack for Windows Server, updated 10/17/13
  • Plan, Deploy, and Configure Windows Azure Pack: Web Sites, updated 10/17/13
  • Administer Windows Azure Pack for Windows Server, updated 10/17/13

Here you can download the Microsoft Technical documentation for Windows Azure Pack


Download the Microsoft User Guide to Windows Server 2012 R2 NIC Teaming (LBFO) #Winserv #Hyperv

NIC Teaming

NIC teaming, also known as Load Balancing/Failover (LBFO), allows multiple network adapters to be placed into a team for the purposes of

  • bandwidth aggregation, and/or
  • traffic failover to maintain connectivity in the event of a network component failure.

This feature has long been available from NIC vendors but until Windows Server 2012 NIC teaming was not included with Windows Server.

Here you can find the Microsoft User Guide to Windows Server 2012 R2 NIC Teaming (LBFO)