Microsoft Azure Virtual Machine Readiness Assessment #azure #cloud   Leave a comment

Microsoft Azure Virtual Machine Readiness Assessments for Active Directory, SharePoint Server and SQL Server. Also available on Windows Azure Portal here: http://www.windowsazure.com/en-us/downloads/vm-readiness-assessment

Automated Assessment

  • This tool will provide a high level checklist and a detailed report.
  • The checklist outlines areas which are ready to move and areas which may need additional configuration or design changes.
  • The detailed report offers expert guidance and advice tailored to your environment.
Expert Advice
  • Your report shows areas that are ready to move and areas that need additional configuration or design changes.
  • Click into each area to get expert guidance and advice tailored to your specific situation.

 

The installation is real easy but I noticed that the discovery is not always working. In my case I did run this on the SQL server.

 

image

When the Installer is finished I ran the Assessment toolkit.

image

In this case I used SQL server the method is the same only the result is different.

 

imageimage

Two easy steps with some questions and basically there is no right and wrong ( I checked unsure )

 

image

Yes it is not the MAP toolkit just one server at the time.

Windows  Microsoft Assessment and Planning Toolkit

The Microsoft Assessment and Planning Toolkit makes it easy to assess your current IT infrastructure for a variety of technology migration projects. This Solution Accelerator provides a powerful inventory, assessment, and reporting tool to simplify the migration planning process.

image

after a little coffee break the scan is done and the report is ready. You can save and edit this as it is a Word file.

 

 

image

As I did the Next Next method I need some planning when I migrate this SQL server to Azure.

the report is in detail and 62 pages long. It could be handy if you don’t know anything about this server.

image

But if you want to test the migration and already running VMM and have a S2S VPN to Azure read my other blog post.

http://robertsmit.wordpress.com/2014/08/27/azure-site-recovery-service-asrs-hyper-v-to-azure-recovery-mvpbuzz/

Posted September 12, 2014 by Robert Smit [MVP] in Microsoft Azure

Tagged with

Azure Site Recovery Service #ASR #Hyper-v to #Azure #Recovery #mvpbuzz   3 comments

Azure Site Recovery can help you protect important services by coordinating the automated replication and recovery of System Center private clouds at a secondary location. The ongoing asynchronous replication of each VM is provided by Windows Server 2012 Hyper-V Replica and is monitored and coordinated by Azure Site Recovery. In the event of a site outage at the primary datacenter, VMs can be brought up in an orchestrated fashion to help restore service quickly. This process can also be used for testing recovery, or temporarily transferring services.

Now you can replicate virtual machines from your primary site directly to Azure, instead of your own secondary site. In the event of an outage at the primary site, the service orchestrates the recovery of virtual machines in Azure.

As there is already Azure Recovery manager using Azure to protect you VM between two VMM Servers. and now there is in a preview a new option Failover to Azure.

This is a great new option and will open the door to new options for your private cloud.

You can use Azure Site Recovery in the following scenarios:

  • On-premises to cloud: Replicate Hyper-V virtual machines on a source VMM server or cluster to another VMM server or cluster located in the same datacenter or in a different site. You can also replicate between clouds on a single physical or virtual VMM server.
  • On-premises to cloud: Replicate Hyper-V virtual machines on a source VMM server or cluster to Azure storage.

In this step by step I show you what steps to take for a working situation.

We need a VMM Server and An Azure Account with the Site Recovery Preview.

Azure Site Recovery - on-premises to Azure

When opening the ASR ( azure Site Recovery ) We can select the recovery option. Lets pick hyper-v to Azure Recovery.

image

If you do not have a Certificate in place already below is the line to create a Self signed certificate.

This Certificate us needed to talk to and from the VMM Server to Azure.

makecert.exe -r -pe -n CN=Certmvpvmm12 -ss my –sr localmachine -eku 1.3.6.1.5.5.7.3.2 -len 2048 -e 01/01/2016 c:\Certmvpvmm12.cer

Azure Site Recovery - on-premises to Azure

Now that we have created the Certificate We import this in the Azure portal , On manage Certificate we can import the Cer file

image

Import the Cer file

Azure Site Recovery - on-premises to Azure

I already did the Hyper-v vs Hyper-v See my blog post.

http://robertsmit.wordpress.com/2013/06/12/windowsazure-hyper-v-recovery-manager-azure-hyperv-recovery-msteched-tee13-draas/

but now we pick Hyper-v to Azure. In the Dashboard step 2 there is a link for downloading the Recovery Provider for VMM

Download Microsoft Azure Site Recovery Provider and install it on VMM servers

image

We are installing this on the VMM Server!

image

After downloading we kick the setup and as we do not read all the text, I need to stop the VMM services!

image

So there is downtime keep this in mind VMM can also takedown your Windows Azure Pack

imageimage

The setup does not need many words it is a basic next next finish setup.

imageimage

However we need to use the certificate that we created and imported in Azure in the first step. I have already multiple Certs in my VMM I just need to pick the right one. So naming convention is important!

image

After Selecting the Key we need a vault key ! this key is in Azure generated and can be copied from azure to the VMM server.

In the Azure portal in Step 1 there is a line get your vault key

image

We copy the Key and past the key in the setup an Next.

image

I pick enable encryption just to make sure I do have a secure line.

image

Pick the VMM server name in FQDN

imageimage

And your VMM server is ready make sure the services is started again.

The next step would be install the Microsoft Azure Recovery Services Agent on your Hyper-v Server

You can download this in step 3

Download the Microsoft Azure Recovery Services Agent, and install it on Hyper-V host servers.

image

The installation is just a quick install no screens to capture or things to do.

The next step is Configure a cloud that needs the protection Selecting the Vault and the Protection name as you can see the current status is not configured

image

Select Configure Protection

image

here we can select a target and we pick Microsoft Azure

image

A new screen with lots of settings opens

image

The copy Frequency is the Hyper-v Replica between Hyper-v and Azure In windows Server 2012R2 there is the option 30sec,5&15 minutes Azure is not changing this.  pick any option you want but In my case I use 15 min that is more enough for me.

one this is really nice that is the Replication time most thing are starting just wen you press enter ;-( but here you pick a scheduler.

image

Pick any time you want but I pick do this now, there is a 60GB VM that needs to get uploaded to Azure.

Then Click on Save! image ( replication will start immediately !!! )

the next step is wait for Azure to finish the settings  image This can take a few Minutes.

yes you can configure other steps but I like to make sure this step is successful.image

image

Now the Cloud is Configured We enable protection for My VM’s.

Select the Name and we pick enable protection in the Virtual Machines

image

When selecting this option and you will see no VM’s you did something wrong ! think…

Yes you are protecting a Cloud so your VM must be in a cloud on this VMM server I have only one cloud and in this cloud are 3 vm’s

image

and you can see this 3 vm’s here in azure

image

I’ll pick the MVPAZU2 VM and again I’ll wait until Azure is finishing it process.

After this the window will show you the VM and unprotected.

image

You can select more VM’s but for this demo I’ll use just one VM.

When selecting the VM we can adjust the CPU and Memory in Azure

imageimage

I’ll pick medium and hit the save button at the bottom!

In the Resources of the Vault we need to link the Networks. If you don’t have a network in azure you will need to create one.

Pick the VMM server as Source and the Target is Azure. The screen will list all your networks that are connected

image

Pick the network from the Protected network and link it to the Azure network. In my case the azure network is connected with a S2S VPN to my private network So I’ll use this network. the IP stack is showing.

image

As I picked Immediately as replication lets see Oh ok it is running

image

In the Hyper-v Manager you can see the progress. It would be nice to have it also in Azure.

image

image

My internet connection is a 1 GB but the internal routers and the networking on my Hyper-v Server needs some attention.

And if we are checking in VMM the Recovery Settings it is set to 15 minutes just as we set in Azure.

image

And we need to wait until the replication is done from Hyper-v To Azure this can take some time It all depends on your Internet connection

imageimage

After the Replication is ready You can see that there is one VM protected and we can create a recovery plan.

image

Now that we have created a recovery plan this is just a step to link the VM to a recovery plan from or to Azure and what VM.

image  image

Now that the Recovery Plan is is ready we can test this with a test failover.

image

As we check the test failover a popup ask me on witch network the VM should connect.

image  As this is a TEST you can not connect to the real network that is picked in the VM

image

In the VM you can see the test VM is build but you can’t connect to the VM. There is a DNS name  image

Azure Site Recovery - on-premises to Azure

In the Job status you can see a step by step overview and for completing you have to check the complete option on the bottom.

a Popup is shown where you can put in comments and set the checkbox complete. After this step the test will continue

Azure Site Recovery - on-premises to AzureAzure Site Recovery - on-premises to Azure

Azure Site Recovery - on-premises to Azure

With these Easy steps you can use Microsoft Azure As your failover DataCenter and even With One Hyper-v Server you can be always up.

If you need more info then go to the MSDN site see below for the URL

Azure Site Recovery - on-premises to Azure

The walkthrough consists of the following steps:

  1. Deployment prerequisites: On-premises to Azure. Check deployment requirements, and complete the planning steps before you begin deployment.
  2. Step 1: Create and configure an Azure Site Recovery vault: On-premises to Azure— Create a vault and specify a vault key. Upload a management certificate (.cer) to the vault.
  3. Step 2: Install the Azure Site Recovery Provider: On-premises to Azure— Install the Hyper-V Recovery Manager agent on the VMM servers you want to register in the vault.
  4. Step 3: Install the Azure Recovery Services Agent: On-premises to Azure— Install the Azure Recovery Services agent on Hyper-V host servers located in the VMM source clouds you’re protecting.
  5. Step 4: Configure protection settings for VMM clouds: On-premises to Azure— Specify protection settings for the cloud, including source and target settings, recovery points and snapshots, and initial replication settings.
  6. Step 5: Configure network mapping: On-premises to Azure—Create mappings between VM networks on the source VMM server and destination Azure networks.
  7. Step 6: Enable protection for virtual machines: On-premises to Azure— Enable protection for virtual machines.
  8. Step 7: Create and customize recovery plans: On-premises to Azure—Create and customize recovery plans that specify how virtual machines should be grouped and failed over.

Greetings,

Robert Smit

http://robertsmit.wordpress.com/

Posted August 27, 2014 by Robert Smit [MVP] in Microsoft Azure

Tagged with

StorScore A test framework to evaluate SSDs and HDDs #Cloud Server Infrastructure Engineering #CSI #ssd #winserv @microsoft   Leave a comment

StorScore is a component-level evaluation tool for testing storage devices.
When run with default settings it should give realistic metrics similar to
what can be expected by a Windows application developer.

image

You must download and install the following or StorScore will not work:

    A Windows Perl interpreter:
        ActiveState: http://www.activestate.com/activeperl
        Strawberry: http://strawberryperl.com/
   

Strawberry Perl is a perl environment for MS Windows containing all you need to run and develop perl applications. It is designed to be as close as possible to perl environment on UNIX systems.

http://www.microsoft.com/en-us/download/details.aspx?id=43739

imageimage

With the output you can create some pivot tables and get great output.

image

Posted August 21, 2014 by Robert Smit [MVP] in Windows Server 2012 R2

Tagged with

How to use VMM Network Builder #scvmm #azure #cloud #winserv #NBT   Leave a comment

 

Anjay Ajodha and Matt McGlynn are Program Manager Interns on the System Center VMM team.

They spent their summer analyzing customer pain points regarding networking in VMM and have developed a small tool that should help ease the frustration with setting up VLAN-isolated networks in VMM. To help you get started quickly with networking in VMM and to simplify the process of creating new networks, we have created a UI add-in.

An entire basic networking setup can be created with this tool that can either be applied to hosts directly or used as a generic networking object base to be modified for customization to your configuration. VMM Network Builder compresses the steps required to build a logical switch. This tool will create networks that utilize VLAN isolation and is not purposed for creating NVGRE networking configurations.

and this is to bad the creation of a NVGRE network is often not easy.

Download the VMM Network Builder tool here : http://www.microsoft.com/en-my/download/details.aspx?id=43975

An quick installer Takes you to the next step. You need to import the Console or just run this from the installation folder.

 

image  

image

import add in console in the settings you can pick the import console add in.

image

Normally you would go to the installer folder but now the .Zip is on your desktop odd place ( I was looking in the installed folder )

image

image

After the import there is an extra Icon in the title bar “ build a network “

 

image

Starting the VMM Network Builder

image

image

I already have a management Network and the VMM Network Builder won’t create a second one.

image

I’ll pick my creative name VMMBAD VMM Builder Address Device

 

image

Create a IP pool and a if you want a static pool.

 

image

then make a choice, I’ll pick to a host.

image

I pick a host for this network.

image

And in VMM you can see this network as created, with the vlan and the IP subnets

image

A lot more options are in the tool. Play with the tools and maybe it is the right thing for you.

Download the VMM Network Builder tool here : http://www.microsoft.com/en-my/download/details.aspx?id=43975

image

 

System Center All Up: http://blogs.technet.com/b/systemcenter/

System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager

System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/

WSUS Support Team blog: http://blogs.technet.com/sus/

The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/

MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Create a New Network Load Balancing NLB Cluster On Windows Server 2012 R2 #Winserv #nlb   Leave a comment

Still I thought NLB is so common that there is no point here to create a blog. but recently I see a lot of misconfigurations of NLB or people trying to do the easy way and not listen to the guidelines. So this blog is all about NLB only in the private cloud you can’t extend this to Azure even if you have a S2S.

So I have two servers in my private cloud.  MVPNLB001 and MVPNLB002 Both Machines have two NIC’s one for LAN and the other is for the NLB actions.

and yes it can be with one but with two is it much easier and fault tolerant. Less errors and less administration.

Both domain joined and ready for Setup of my basic IIS.

First we setup IIS with the Management tools

image

Install-WindowsFeature -Name Web-Server Or Add-WindowsFeature Web-WebServer –IncludeAllSubFeature to get all the features

Install-WindowsFeature -Name Web-Mgmt-Tools
Add-WindowsFeature NET-Framework-45-ASPNET

Get-WindowsFeature nlb*

 

image

add-WindowsFeature –Name NLB

add-WindowsFeature RSAT-NLB

Now we are ready to configure the NLB. We can do this With powershell but the GUI also Works.  ( I show both )

image 

 

The First Step will be Create a New NLB Cluster. As I do like things clear and therefor I start with rename the NIC names

Rename-NetAdapter -Name "Ethernet 2" -NewName "NLB"

Rename-NetAdapter -Name "Ethernet" -NewName "LAN"

imageimage

Open the NLB Manager and select Cluster NEW

imageimageimageimageimage

Or use powershell

Rename-NetAdapter -Name "Ethernet 2" -NewName "NLB"

New-NetIPAddress -IPAddress 10.255.255.93 -InterfaceAlias "NLB" -AddressFamily IPv4 -PrefixLength 24

In this case we renamed the adapter and give the nic a static IP.

The next steps Will be creating the NLB with his own IP and Remove the default port rule and use only ports that I want say port 80

imageimageimage

Well that was easy Creating the NLB Next step will be delete the port rule and create a 80 port rule 

imageimage

We will remove the default line and just create a rule for one port that I need in this case port 80

Network Load Balancing parameters

http://technet.microsoft.com/en-us/library/cc778263(v=ws.10).aspx

 

 

These steps can be done in just a few more PowerShell lines ( I use variables see below the post for the complete script )

#Creating new cluster
Write-Host "Creating NLB Cluster…" -ForegroundColor yellow
New-NlbCluster -ClusterName $ClusterFqdn -InterfaceName $InterfaceName -ClusterPrimaryIP $ClusterPrimaryIP -SubnetMask $ClusterPrimaryIPSubnetMask -OperationMode $OperationMode

#Removing default port rule for the new cluster
Write-Host "Removing default port rule…" -ForegroundColor yellow
Get-NlbClusterPortRule -HostName . | Remove-NlbClusterPortRule -Force

image

But now what we have only One Server and we need to add the other node or nodes.

imageimage

With two more confirmations screens you are done and have a Configured NLB on One 1 IP listening on port 80

Suppose you have multiple websites and all running on different IP or hostnames just add a cluster IP

imageimageimage

Now that the NLB is created We can do some testing

Now to get this to work with IIS

image

That is right page not found. Check the DNS see if the record is created. and make sure the website IIS is running on this IP

Go to the IIS manager and check the website bindings, default it is listening on all IP but this is not the behavior that I want I want a NLB. So we need to set the website on the NLB IP configured earlier.  When Having multiple IP on the NLB pick the right IP!

imageimageimageimage

Remember this you need to do this on all the Webservers!

image

 

A complete script to automate all these steps and add a second node. only the IP is fixed in the script and can be set as variable but this is up to you.

use this at free will. I created small steps so you can use also little steps if you need this or just give you an Idea.

<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

#Set IP for NLB
Write-Host "Set NLB IP and change Network adapter" -ForegroundColor yellow
Rename-NetAdapter -Name "Ethernet 2" -NewName "NLB"
New-NetIPAddress -IPAddress 10.255.255.93 -InterfaceAlias "NLB" -AddressFamily IPv4 -PrefixLength 24

#Set ExecutionPolicy
Write-Host "Set ExecutionPolicy" -ForegroundColor yellow
Set-ExecutionPolicy -scope LocalMachine RemoteSigned –force

#Add-WindowsFeature
Write-Host "Add-WindowsFeature NLB" -ForegroundColor yellow
add-WindowsFeature NLB
add-WindowsFeature RSAT-NLB

#Variables for creating the new cluster
Write-Host "Variables for creating the new cluster" -ForegroundColor yellow
$ClusterFqdn = Read-Host "Enter NLB cluster Name FQDN"
$InterfaceName = Read-Host "Enter interface name for NLB-adapter"
$ClusterPrimaryIP = Read-Host "Enter cluster primary IP"
$ClusterPrimaryIPSubnetMask = Read-Host "Enter subnetmask for cluster primary IP"

Write-Host "Choose cluster operation mode"
Write-Host "1 – Unicast"
Write-Host "2 – Multicast"
Write-Host "3 – IGMP Multicast"
switch (Read-Host "Enter the number for your chosen operation mode")
{
1 {$OperationMode = "unicast"}
2 {$OperationMode = "multicastcast"}
3 {$OperationMode = "igmpmulticast"}
default {Write-Warning "Invalid option, choose ‘1’, ‘2’ or ‘3’";return}
}

#Creating new cluster
Write-Host "Creating NLB Cluster…" -ForegroundColor yellow
New-NlbCluster -ClusterName $ClusterFqdn -InterfaceName $InterfaceName -ClusterPrimaryIP $ClusterPrimaryIP -SubnetMask $ClusterPrimaryIPSubnetMask -OperationMode $OperationMode

#Removing default port rule for the new cluster
Write-Host "Removing default port rule…" -ForegroundColor yellow
Get-NlbClusterPortRule -HostName . | Remove-NlbClusterPortRule -Force

#Adding port rules

Add-NlbClusterPortRule -Protocol Tcp -Mode Multiple -Affinity Single -StartPort 80 -EndPort 80 -InterfaceName $InterfaceName | Out-Null
Write-Host "Added port rule for http (tcp 80)" -ForegroundColor yellow

Add-NlbClusterPortRule -Protocol Tcp -Mode Multiple -Affinity Single -StartPort 443 -EndPort 443 -InterfaceName $InterfaceName | Out-Null
Write-Host "Added port rule for https (tcp 443)" -ForegroundColor yellow

#Adding additional cluster nodes based on user input
Write-Host "Give Second NLB host" -ForegroundColor yellow
$Node2Fqdn = Read-Host "Enter 2e NLB node"

#Set Network Adapter
Enter-PSSession -ComputerName $Node2Fqdn
invoke-command -computername $Node2Fqdn -scriptblock { Rename-NetAdapter -Name "Ethernet 2" -NewName "NLB"}
invoke-command -computername $Node2Fqdn -scriptblock { New-NetIPAddress -IPAddress 10.255.255.92 -InterfaceAlias "NLB" -AddressFamily IPv4 -PrefixLength 24}
Write-Host "Placed NLB IP and changed NIC to NLB" -ForegroundColor yellow
exit-PSSession

#Add-WindowsFeature
Write-Host "Add-WindowsFeature NLB" -ForegroundColor yellow
Enter-PSSession -ComputerName $Node2Fqdn
invoke-command -computername $Node2Fqdn { add-WindowsFeature NLB}
invoke-command -computername $Node2Fqdn { add-WindowsFeature RSAT-NLB}
exit-pssession

#Add Remote Node To NLB
Write-Host "Adding cluster node $Node2Fqdn" -ForegroundColor yellow
Get-NlbCluster | Add-NlbClusterNode -NewNodeName $Node2Fqdn -NewNodeInterface NLB

 

Have fun

Robert Smit

Twitter : @clustermvpTwitter : @clustermvp

http://robertsmit.wordpress.com/

  • Now Reading

    Microsoft Windows Server vNext
  • Follow

    Get every new post delivered to your Inbox.

    Join 1,268 other followers

    %d bloggers like this: