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.

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.

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.

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

Share this:

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.

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

We are installing this on the VMM Server!

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

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

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

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!

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

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

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

Pick the VMM server name in FQDN

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

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

Select Configure Protection

here we can select a target and we pick Microsoft Azure

A new screen with lots of settings opens

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.

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! ( replication will start immediately !!! )

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

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

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

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

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

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

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.

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

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

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.

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

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

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.

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

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

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.

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

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

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

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

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

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.

Share this:

In this blog post I’ll show you how to create a Hybrid RemoteApp Configuration. It is still a Preview and Improvements could be made.

If you want to run your own applications in Azure like on Citrix or with RDS till now it was not a build in services Microsoft provided.

But with RemoteApp you can easy deploy a default set as below or Create a Hybrid Environment. And there are lots of new options in a Hybrid RDS Azure Site #HRDAAS Hybrid Remote Desktop As a Service

The Quick Create is no fun just hit Create

Now Creating a Hybrid Environment. You will need a syspreped Template with no unattend.xml in it. There For I created a fresh new template clean install with Remote Desktop Session Host installed and most important you need to set a registry key if you don’t do this all will fail!

When Logged on We see all the Apps I made a Text change in de Word app

However I logged on the session is still inactive

This is still a Preview what I really like is using your own apps in your own domain there are still some issues with the creation of the RemoteApp but if you have configured all this and it is working you can even use this On a Android and or on your Surface how Cool is that.

I installed the latest version of RDP on my android phone I opened a CMD box on my phone totally useless but you can. It works much better on my Surface.