Only forty days to go for the next Experts Live event! This year we have an amazing line up again with tracks about:
- Windows Server
- System Center
- Office 365
More than forty sessions! This time the event will be hosted in Cinemec in Ede.
We from Hyper-V.nu may give away two tickets that gives you free entrance to this event. If you want to win one of these tickets you have to write a tweet explaining why anyone should attend Experts Live using the hashtag #Hypervnu #ExpertsLive. The tweet must be posted between October 8th and 15th.
Blog by Ben Gelens who blogs at http://mssecbyben.wordpress.com
SMA Runbooks can be triggered by Windows Azure Pack events like VM Role creation. You can configure this by going to the VM Cloud automation tab and linking a runbook to an Azure Pack known object like “Microsoft VMRole“.
The objects have actionable event like Create, Scale, Repair and Delete. You can link one runbook per actionable event per object.
A runbook is only available to linkup with an event if it is configured with the SPF tag.
When taking this information in mind, you can see that if you are going to build a dependency between actionable events and SMA runbooks you need to develop and commit to some standards. In this blog post I’ll show you some examples of what you could think off while developing your SMA Windows Azure Pack integration strategy for VM Roles.
In my daily job I see VM Roles being used by enterprise customers as a replacement for SCVMM service templates and VM templates. Although the VM Role is meant to be disposable, scalable, recyclable and easily replaceable, they are actually being used for VMs which will have long life spans and take advantage of some of the VM Role benefits like scaling and resource extension configuration.
READ MORE »
Guest blog by Mark Scholman
I have been working on a new script project to configure Hyper-V hosts. Every time I deploy new Hyper-V servers in a new customer environment, there are many things that require configuration. Also little things that are easily forgotten. Let’s see how we can automate that process. Of course I realize that Bare Metal Deployment is an available functionality in VMM. But with the chicken and egg story or customers who cannot use Bare Metal Deployment, I decided to create this tool. It is using the converged network setup as described in this blog post. What it does is the following:
- Rename Adapters
- Create Teams
- Create Team Nics (tNics)
- Set Network Configuration (MGT,LM,CSV)
- Join Server to the Domain
- Create a server-local administrators group in the domain
- Allows you to create a new or join an existing cluster
- Configure Cluster network names
- Configure Cluster Live Migration subnet
On the to-do list is the following and will be added with upcoming releases:
- Configure Storage network (iSCSI & SMB3)
- Use of different topologies for converged networking as described here
- Using JEA (Just Enough Admin) or PSCustomSessionConfiguration for deployment of Hyper-V hosts
How to use the toolkit
Download the latest version from the Technet Gallery. If you feel like to help me optimize and extend the tool fork it on github.
On the newly provisioned Hyper-V Server start the Deploy-HyperVHost.ps1. On the Configure Nic’s tab select the adapters you want to use for Management (MGT / LM / CSV) and click Set Management Adapters:
Notice the list box will refresh with the new names for the adapters. Next select the adapters you want to use for VM Network and click Set VMNet Adapters
READ MORE »
This blog is written by Mark Scholman (@markscholman).
This post will explain the do’s and don’ts of Hyper-V Network virtualization. Especially on the topic where we want to bring our next solution / example to Microsoft Azure Pack and / or System Center Virtual Machine Manager. First things first. For those who need to understand the basics on Hyper-V Network Virtualization I recommend to start reading the article here.
This blogpost is based on the following use case:
A customer wants to host their infrastructure at a Service Provider. The Service Provider utilizes Hyper-V Network virtualization, management with System Center Virtual Machine Manager and optionally Windows Azure Pack. The customer currently has the following networks:
- Production Network
- DMZ Network
The customer prefers to bring their own Linux firewall and use it as the default gateway for their networks. The customer network consists of the following subnets:
Production subnet: 10.10.0.0/24
DMZ Network 10.11.0.0/24
As for each subnet the first possible IP address (normally x.x.x.1) is automatically provisioned as the default gateway. The FW/Gateway (MS-TEST-A01) is configured with x.x.x.254 for each NIC. The default gateway in the firewall is set to 10.10.0.1 and this VNet is enabled with Internet connection and NAT.
Not really an exciting network configuration you might think. We will change the default gateway in each machine to the x.x.x.254 (ip of the virtual fw).
The following image displays two provisioned virtual networks. VNET-A is configured with a gateway:
The virtual machines use the following IP configuration:
READ MORE »
Two months ago I published a blog on the Windows Azure Pack Tenant Public API. This API allows you to interact with your cloud services using PowerShell over the internet and certificate authentication. The Microsoft Azure PowerShell module provided cmdlets for Windows Azure Pack as well. As you might remember from that blog was the lack of VM Role cmdlets. There was a workaround that worked but was somewhat complex to configure and maintain.
A new version of the Microsoft Azure PowerShell module has been released. This new version also contains various new cmdlets for Windows Azure Pack.
As you can see it also contains new cmdlets for interacting with cloud services and the VM Role.
You can download Microsoft Azure PowerShell module 0.8.6 through the Web Platform Installer with this link.
The VM Role is a custom configuration that can consist of many required and optional fields. As with the GUI wizard some values must be provided for the PowerShell cmdlet. Creating a new VM Role with the New-WAPackVMRole cmdlet requires some input.
If we take a look at the ResourceDefinition of an existing VM Role there is still some configuration requirement, but it is a huge improvement compared the previous procedure.