Microsoft just released the Azure Cloud Shell option in the Azure Portal. here is a quick step by step on how to use this and how to add this with storage explorer when creating a storage account.
Azure CLI 2.0 is optimized for managing and administering Azure resources from the command line, and for building automation scripts that work against the Azure Resource Manager
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
a LRS storage account is created on your behalf with an Azure file share containing a default 5-GB disk image.
This disk image is used to sync and persist your $Home directory. Regular storage costs apply. Three resources will be created on your behalf:
- Resource Group named: cloud-shell-storage-<region>
- Storage Account named: cs-uniqueGuid
- File Share named: cs-<user>-<domain>-com-uniqueGuid
So that’s it. To easy?
As the default help shows you with az account list you get a list off your azure subscriptions
For selecting the right subscription when creating resources
- az account set –subscription "MVP-platforms"
Remember using options use – and not like in powershell –
Now creating a Resource group in the selected Subscription
- az group create –name clustermvp –location westus
So very handy on quick creating items in the shell, Still I prefer PowerShell but that’s my thing and I see the options of this and It is a nice new feature.
Quick on creating a new storage account and get the right connection
create a new storage account
- az storage account create –resource-group clustermvp –location westus –name clustermvp –sku Standard_LRS –kind Storage
Now you need to get the connection string to use
az storage account show-connection-string –resource-group clustermvp –name clustermvp
Copy the connection string for usage in storage explorer or other usage.
Using the connection string in storage explorer
Fully working string.
If you want to know more about the Azure CLI check the docs site on azure CLI
https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w
LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog
Like this:
Like Loading...
In the past 6 months I haven’t done much with SCCM only sideways jobs but with all the new features in the Preview Branch SCCM will survive the Cloud. as it moves more and more to the cloud and integrates with it. As I build a fresh lab environment with all the latest updates and previews. As I broke my previous lab environment ( FUBAR – Fucked up beyond all repair) So Becarefull when you upgrade your machine make backup/ snapshots. Or just start over. this could be a learn full process also you may want to get things faster easier and before you know it you spend weeks on everything except on the SCCM blog post.
Well as I did take my time to write this blog post there is already a new version the 1704 for the Technical Preview Branch of System Center Configuration Manager. The installation process is the same. For more info about the 1704 build checkout the two links below,
https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1704
https://docs.microsoft.com/en-us/sccm/core/get-started/technical-preview
New features in the 1704 version are:
- Improvements to operating system deployment
- Reload boot images with current Windows PE version
- Configure Android apps with app configuration policies
- Add child task sequences to a task sequence
- Hardware inventory collects Secure Boot information
New features in the 1702 version are:
- Azure Active Directory Domain Services support – You can install a ConfigMgr site on an Azure virtual machine that is connected to Azure Active Directory Domain Services, and use the site to manage other Azure virtual machines connected to the same domain.
- Improvements for in-console search – Based on User Voice feedback, we have added several improvements to in-console search, including searching by Object Path, preservation of search text and preservation of your decision to search sub-nodes.
- Windows Update for Business integration – You can now implement Windows Update for Business assessment results as part of Conditional Access compliance policy conditional rules.
- Customize high-risk deployment warning – You can now customize the Software Center warning when running a high-risk deployment, such as a task sequence to install a new operating system. The default string regarding data may not apply in scenarios like in-place upgrade.
- Close executable files at the deadline when they would block application installation – If executable files are listed on the Install Behavior tab for a deployment type and the application is deployed to a collection as required, then a more intrusive notification experience is provided to inform the user, and the specified executable files will be closed automatically at the deadline.
This release also includes the following improvements for customers using System Center Configuration Manager connected with Microsoft Intune to manage mobile devices:
- Non-Compliant Apps Compliance Settings – Add iOS and Android applications to a non-compliant apps rule in a compliance policy to trigger conditional access if the devices have those applications installed.
- PFX Certificate Creation and Distribution and S/MIME Support – Admins can create and deploy PFX certificates to users. These certificates can then be used for S/MIME encryption and decryption by devices that the user has enrolled.
- Android for Work Support – You can now manage Android for Work devices. This enables you to enroll devices, approve and deploy apps, and configure policies for Android for Work devices.
Update 1702 for Technical Preview Branch is available in the Configuration Manager console. For new installations please use the 1610 baseline version of Configuration Manager Technical and upgrade from this.
To get the Updates go to the cloud services and check for updates. this could take a whale.
But when the Update is arrived you can update the SCCM version. I choose for the test first and do later the Update. Just to make sure I don’t wreck the SCCM server directly. and as always in SCCM there are plenty of log files.
As showing the Progress in the GUI you can check every step. So installing this is just easy and I did first the prereqs check and then when installing there is no point off doing the check again therefor there is a little checkbox.
As you can see I can select the options but If you can’t no problem you can do this later. just go to the Hierarchy Setting Properties, under General, check the box “Consent to use Pre-Release features“. Furthermore once you decide to use these features and enable it, you cannot undo the changes. So if you have decided to use these features, check the box, click Apply and OK. And every preview is only valid for 90 days so once updated you need to go with the updates every time.
I don’t have a preview collection everything is already test so start the installation.
The installation is taking some time so don’t worry it things are going that fast.
When opening the console again the console does his upgrade to the new version.
After this the new Version is installed and ready for testing. But for this testing you may need to install some other updates than SCCM what about the ADK version for the new Windows 10 deployments ?
While upgrading do the Update from the ADK also Download Windows ADK for Windows 10 Version 1703
What’s new in ADK kits and tools
Windows Configuration Designer
Previously known as Windows Imaging and Configuration Designer (ICD), the tool for creating provisioning packages is renamed Windows Configuration Designer. Windows Configuration Designer in Windows 10, version 1703, includes several new wizards to make it easier to create provisioning packages.
And even this simple installation It has some prereq’s to to.
To see the newest unattended settings, go to Changed answer file settings for Windows 10 for desktop editions.
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w
LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog
Like this:
Like Loading...
Well it is here it took some time but now you can start testing with the Xenapp Essentials. Is it any good and Can I use it for production. Well I was a little disappointed I was charged upfront and the VM image I used was not usable because the Xenapp Essentials can’t handle Azure managed disks, As azure is pushing use managed disk. is Citrix Xenapp Essentials not capable of using managed disk. therefore I had to rebuild a new Image. The look and feel is the same as in Azure RemoteApp the nice thing is you can change sizing and scaling and to save money a time schedule. But for testing in a MSDN subscription I hate the upfront billing and Citrix did not tell this.
But why not build a RDS farm in Azure ? will show this in a the post below and using a Profile Cluster in Azure is also supported.
https://technet.microsoft.com/en-us/windows-server-docs/compute/remote-desktop-services/rds-storage-spaces-direct-deployment
For those who are unfamiliar with Azure Remote App check my blog post below.
https://robertsmit.wordpress.com/2014/06/20/microsoft-azure-hybrid-deployment-of-remoteapp-step-by-step-azure-microsoft-remoteapp-mvpbuzz-rds-hrdaas/
In this part I show you how to set things up. there are multiple ways and each has is own choices. Citrix is delivering a default Image and this is a Windows 2012 Image, well I’m not going for a default image but a custom. this need some work. This will be a log blog post and tons of pictures in it, As I tried to do step by step but some items you just need to know in Azure. Else it is gonna be a real long blog. But If you need more info on any item just ping me.
Well first I thought lets do this and writ a quick blog on hoe great this is. The amount off steps it took to get thing running is more than I expected. but it is not a bad thing. But be prepared it takes time!
The interesting part is should I use the Same Image or is there an easy migration path. Well it all depends as most things in IT.
The Deployment Xenapp Essentials workflow in just 7 tiles you are done. but some tiles takes several other little steps.
Do you want to stay on Windows server 2012R2 ? Well I don’t think so but there are good reasons to migrate as is but will this work. As this blog post is just on how to setup the Citrix Xenapp Essentials, the next post would be this integration and migration
As the Citrix Xenapp Essentials is in the Azure market place we also need a Citrix Account.
You can easily create a new Citrix Cloud by going to the following site: https://onboarding.cloud.com
there are a couple of questions and then you are ready to use the account.
In case you have an issue with your account just open a support ticket and the Citrix Support will fix your issue quickly.
So In the Azure portal you can add the Citrix to the menu and go from there.
You can only manage from here and not add any this, so go to the Azure Marketplace (click NEW or +) do a Citrix search.
Select the Citrix XenApp Essentials
Do Create. and pick a name for the resource and use or create a resource group.
Give it a name and create or use an existing Resource Group.
As things are default you can change it and read the Text. Default it creates 25 users Cost Estimate : $456.25 per month
Well for my demo I don’t need 25 users In need just 1.
Oh the minimum usage is 25 Ok then I need 25 users.
Pricing
$12.00 per user per month for XenApp Essentials Service, including Citrix NetScaler Gateway Service for secure access and 1 GB data transfer per user per month.
Users added today will be charged at the a prorated rate of $11.60 for the remainder of the current month. This amount will be charged immediately.
$6.25 per user per month for Microsoft Remote Access fee to use XenApp Essentials Service without purchasing a separate RDS CAL for this workload. Contact your Microsoft representative to bring your own RDS CAL.
Users added today will be charged at the a prorated rate of $6.04 for the remainder of the current month. This amount will be charged immediately.
You can purchase additional 25 GB Data Transfer Add-on. The cost is $12.00 per add-on per month
When you add users and data transfer add-on to the service, the new charges apply immediately. You can change the number of users and data transfer add-on each month. Your subscription renews automatically at the end of each month unless canceled.
Well the deployment took 6 seconds. that is the Place holder and not the VM’s self An order may take up to 4 hours to provision your service.
Shown from the Azure Portal
Visit Citrix Cloud to simplify the provisioning, on-going management and monitoring of Windows apps hosted on Azure. Here in the Azure portal, purchase additional seats and data transfer add-ons on-demand to meet the needs of a dynamic workforce.
An order may take up to 4 hours to provision your service, and you will receive an email from the Citrix Cloud when your service is ready. If you do not receive an email within this time, please contact Citrix Support
Log into the XA Essentials Portal https://essentials.apps.cloud.com/
If you need more users you can add them in Azure.
Log into the XA Essentials Portal https://essentials.apps.cloud.com/
An order may take up to 4 hours to provision your service, and you will receive an email from the Citrix Cloud when your service is ready. If you do not receive an email within this time, please contact Citrix Support
In almost 4 hours I got the email 
Your Citrix product has been shipped via electronic delivery on April 01, 2017, to the email specified on your
purchase order.
Your Citrix order is completely fulfilled. All items on your purchase order have been shipped to the requested
address.
Depending on your other Citrix product you choose the Xenapp Service.
There are 3 steps needed Linking the Subscription and upload a master Image and last create your catalog.
The Microsoft login dialog box us prompting for credentials . You mus use an account that has admin privileges to your Azure Subscription.
Remember : If your user account is not working. the Account MUST be an Azure AD Account.
Next step is creating the XA Essentials Catalog. In these steps the Image will be mounted ,AD connections ,Network,Applications.
A important step with full of options. To setup XA Essentials you need:
- Azure Subscription
- Resource Group’s for Cloud connector,Images,etc but you can also use just one Resource Group
- Domain Controller with Active Directory Domain Services and DNS
- Virtual Network configured for domain usage
- A Subnet with free IP addresses
Click Create Catalog.
Select the Network and the Resource group
As I need some extra resources for creating Image I’ll use Extra Storage accounts
Image Requirements
Use the following requirements to create a custom image:
- Create the image by using Azure Resource Manager.
- Configure the image to use standard (not premium) storage.
- Select Windows Server 2012 R2 or later.
- Install and configure your apps
- Install the Server OS VDA. You can download the VDA by using the Downloads link on the navigation bar.
- Shut down the virtual machine and note the VHD location. Do not Sysprep the image.
And DON’T use Managed Storage accounts for a Custom Image in Xenapp Essentials Can’t use this in the Citrix Images #Fail.
and a good thing there is a brake on my Azure credits. Not for the blog. Seems Citrix is charging upfront. another Failure #Fail but this is only on my MSDN subscription. at this point I can’t finish my blog post #GRRRRR
So but the nice thing are picking my machine type like an G5 just for fun or needed.
Using a default VM as a D2 and for a default of 25 users. Think again and see your Perf resources right now. the cost will be at least the double for 25 users.
Scale settings For my Current Costumers we had a custom script in place for Automatic Scaling of Remote Desktop Session Hosts in Azure Virtual Machines
https://gallery.technet.microsoft.com/scriptcenter/Automatic-Scaling-of-9b4f5e76/view/Discussions
but in Citrix it is all there Currently it is maximized to 200 users but If I build more collections I can scale up even in the test environment
yes there are flaws in it but it is a replacement for ARA. second building this could take up some time but as you already paid for a month that renewing every month!
the pricing is as described on the citrix site
Requires 25 user minimum. Includes NetScaler Gateway Service with 1 GB Data transfer per user per month. Additional NetScaler Gateway Service 25 GB Data transfer Add-on available for $12 per pack per month
Available from Azure Marketplace when purchasing XenApp Essentials. Please consult your Microsoft representative to bring your own RDS CAL.
So there are now a couple options build a RDS farm in Azure good for large Company’s or who are in need of more flexibility or using Citrix XenApp essentials and will microsoft come with an replacement for Azure remote App, when checking my blog post I see a huge hit on Azure RDS. the Citrix solution isn’t that cheap and has a minimum of 25 users. but building it you self it could be done on 1 server but the price will be more than $486 but who wants to run >2 users on a D2. when using SaaS applications or other Webbase stuff the 3 Gb memory and 14% or more CPU usage is not uncommon
Cheap No use full yes and an Azure Remote App Replacement yes Perfect absolutely NOT
In my next post I will do a dive deep into some configuration issues. see this like Azure RDS vs CXE.
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w
LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog
Like this:
Like Loading...
When using System Center Configuration Manager current branch Build 1610, you can extend it to OMS and you don’t need the OMS portal or the Classic portal. All from the Azure Resource Manager portal.
When opening the SCCM Manager it maybe that the OMS Connector option is not available, This connector is currently in preview and therefore you need to enable this option by hand. All the SCCM servers need to have a OMS Agent (at least the service connection point site system role Server)
In the Option can be enabled in Consent to Use Pre-Release Features.
Navigate to the Administration workspace in your Config Manager console, expand Site Configuration and select Sites.
Click on the Hierarchy Settings tab at the top of your screen.
select the General tab, and read the disclaimer under the Consent to use Pre-Release features.
After that You need to enable the feature in update and servicing. Right Click and turn it on.
Close and open the Management console and the option is there.
But before we can use this we need to configure the Web Api in Azure Resource Manager.
Logon to the Azure Portal and go the the Azure Active Directory and check the App registrations and ADD a new APP
Create a New APP Pick a name and Sign-on URL as we are not using the url it does not Mather what name it is.
When created we can change some properties like a Custom Logo
Placing a custom logo is not needed but it looks nice when you search the app 
Next Step is creating a KEY for the APP SCCM is using this key to connect to OMS.
Just choose a Name and a valid certificate expire date and a value and check save else the key is not saved.
Now to give the application the proper permissions in OMS we need to give the APP rights on the Resource Group where OMS based.
Go to the OMS resource group and pick Access Control IAM and add a new USER.
Select the Contributor Role and add this to the Just create application.
Now the Azure part is ready the next step is Creating the Connector in SCCM.
In the Cloud Services open the OMS connection Click on “Create connection to Operations Management Suite”
Now you’ll need to enter the details of your Azure AD tenant (The name) and the Client ID and Key from the Azure AD Application created previously then click Verify to ensure the details are correct and finally click Next.
The Tenant is your Tenant azure Account.
the Application ID is the Client ID
and the Client Secret is the Key that you created.
If you are using the Classic portal you should use the Client ID
With this we are almost ready just pick the groups that you want to populated in the OMS site.
Selecting the Groups and you are ready. In the OMS site you can see the SCCM option connected.
It could take some time to connect to all the groups. and only Groups with an agent are connected to azure so empty groups will not be used or seen in OMS. the connector runs every 6 hours so just wait.
Type=ComputerGroup (GroupSource=”SCCM”) | measure count() by Group
Type=ComputerGroup GroupSource=SCCM
As I just set this up I did not have any results. and this is also the option for a Part 2 SCCM with OMS. But with the results you can create a custom dashboard to show the status.
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w
LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog
Like this:
Like Loading...
When rebuilding your windows 10 desktop that hold a digital license key there is no piece of paper that tells you the activation key.
with the following command you can read the product key
$service = get-wmiObject -query ‘select * from SoftwareLicensingService’
$service.OA3xOriginalProductKey
$key=$service.OA3xOriginalProductKey
this is handy for getting the key but when you are deploying a WDS image and everything needs to be unattended you will need a little PowerShell script
As an option there to place a different key for if you are in a mixed environment.
$service = get-wmiObject -query ‘select * from SoftwareLicensingService’
$service.OA3xOriginalProductKey
$key=$service.OA3xOriginalProductKey
$service.InstallProductKey($key)
$service = get-wmiObject -query ‘select * from SoftwareLicensingService’
if($key = $service.OA3xOriginalProductKey){
Write-Host ‘Activating using product Key:’ $service.OA3xOriginalProductKey
$service.InstallProductKey($key)
}else{
#Write-Host ‘Key not found., use a different license’
# $service.InstallProductKey(‘Put your License KEY here’)
}
Save this as a Powershell script and put this in the unattended.xml and when deploying the Windows 10 will be auto activated
Get the script from the site or from the TechNet gallery.
https://gallery.technet.microsoft.com/Get-windows-10-digital-7653fae4
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w
LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog
Like this:
Like Loading...
When building complex network configurations with Server 2016 you will need to adjust sometimes configuration settings that are not that easily to change in the GUI.
Suppose I have a big S2D cluster Or a NLB farm
In this configuration I have a Cluster that is using Storage spaces direct #S2D but On the SMB nic I don’t want to connect with RDP
Or in the NLB farm I want to use a NLB nic that is used for RDP.
with the Get-NetIPInterface we get a listing of the networks
Get-NetAdapter shows us the name and nic name
Our net step is list the current configuration and his settings for the Ports, in this case RDP
# list current settings
gwmi Win32_TSNetworkAdapterSetting -filter "TerminalName=’RDP-Tcp’" -namespace "root/cimv2/TerminalServices" | Select NetworkAdapterLanaID,NetworkAdapterName
ID 0 which is "All network adapters configured with this protocol"
More info about Win32_TSNetworkAdapterSetting can be found here :
https://msdn.microsoft.com/en-us/library/aa383811(v=vs.85).aspx
when we combine this in a variable to get some more info
#show netadapter bindings for RDS
$MVPRDP = gwmi Win32_TSNetworkAdapterSetting -filter "TerminalName=’RDP-Tcp’" -namespace "root/cimv2/TerminalServices"
$MVPRDP | select -expand DeviceIDList
As this is the network name it is not that handy use this with the get-netadapter
$MVPRDP | select -expand NetworkAdapterList
Now we know what to set on which adapter
# ID 0 which is "All network adapters configured with this protocol". 0,1,2,3
SO ID 0 is all and start counting with 1 as I want RDP only on my MGT lan I set this on Adapter 2
$MVPRDP.SetNetworkAdapterLanaID(2)
gwmi Win32_TSNetworkAdapterSetting -filter "TerminalName=’RDP-Tcp’" -namespace "root/cimv2/TerminalServices" | Select NetworkAdapterLanaID,NetworkAdapterName
now a little reboot and just to make sure there are no old connections and your done.
Or use a register key to set this option but what fun is that.
set HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Terminal Server\Winstations\RDP-tcp\LanAdapter
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w
LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog
Like this:
Like Loading...
Site Recovery is an Azure service that contributes to your business continuity and disaster recovery (BCDR) strategy. Site Recovery orchestrates replication of on-premises physical servers and virtual machines to the cloud (Azure), or to a secondary datacenter. When outages occur in your primary location, you fail over to the secondary location to keep apps and workloads available. You fail back to your primary location when it returns to normal operations. Using ASR can be directly from the Azure Portal or Using OMS.
One or more Hyper-V server, running at least Windows Server 2012 R2 with the latest updates and the Hyper-V role enabled, or running Microsoft Hyper-V Server 2012 R2, with the latest updates. Hyper-V hosts need internet access, and need to be able to access specific URLs directly, or via a proxy.
Individual disk capacity on protected machines shouldn’t be more than 1023 GB. A VM can have up to 64 disks (thus up to 64 TB).
In this case I build a replica between a Hyper-v server and Azure.
In the Azure portal we search for backup.
Picked the Backup and Site Recovery (OMS) and create a Recovery vault. That’s it.. well .. close.
Opening this vault or if you don’t know where it is select the resource group and go from there to the ASR.
Selecting our ASR vault brings us to the backup and ASR.
It is a very busy menu and a lot of options are there and still new options may appear. And there are several ways to start with ASR.
Selecting the Site Recovery Infrastructure a new menu opens and already there are 3 configs. Hyper-v , vmware or VMM
We do the Hyper-v option.
It is all step by step and seams all very easy but you need to take care of some steps before you can complete the steps.
Register your Hyper-V host(s)
On-premises
-
Make sure the host is running Windows Server 2012 R2 or above.
-
Download the Agent
-
the installer for the Microsoft Azure Site Recovery Provider.
-
Download the vault registration key to register the host in a Hyper-V site
This download is replication agent to Azure and need to be installed on the Hyper-v Server
Selecting the Site Recovery and start with Step 1
In this step We select our Protection goal select To Azure, and select Yes, with Hyper-V. Select No to confirm you’re not using VMM.
We need to create a Site of this hyper-v server. this is a Cosmetic name and points to the Hyper-v server or servers, if this is a Test server then this should be HVtest etc.
My site is Single Hyper-v server and already there a a few steps I need to install the Agent downloaded earlier and use the vault keys to connect to Azure.Also downloaded here
Installing the Hyper-v Agent
Use the Exe just downloaded and follow the steps.
Use a location be careful if not installing on the C drive and not replication the other drive there can be miscommunication in the VM. Better leave this default.
But in case You already played with this or want different naming and started all over the may be an issue “ the server is already registered”
To fix this error and enable the ASR Provider and agent setup to complete successfully, follow these steps:
- Go to the Register
- Make a backup of the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure Site Recovery
- Delete the registry key that you backed up in step 2.
- Restart the Provider and agent setup.
Use the downloaded Keys and import them.
Checking the Register you can see that the key is valid and all the info is there.
And the installation is done. It can take some time to add the server to Azure maybe several hops back and forth to the menu
You can see the process running in the Task manager.
Jumping back and to the step 2 you can see the Hyper-v server is added to the Vault.
Added a storage account and a network. If this is not the storage account or network you want no worry you can change this befor the replication starts.
Check this if you want a new account or different network.
Next step would be creating a replication policy.
- In Create and associate policy specify a policy name.
- In Copy frequency specify how often you want to replicate delta data after the initial replication (every 30 seconds, 5 or 15 minutes).
- In Recovery point retention, specify in hours how long the retention window will be for each recovery point. Protected machines can be recovered to any point within a window.
- In App-consistent snapshot frequency specify how frequently (1-12 hours) recovery points containing application-consistent snapshots will be created. Hyper-V uses two types of snapshots — a standard snapshot that provides an incremental snapshot of the entire virtual machine, and an application-consistent snapshot that takes a point-in-time snapshot of the application data inside the virtual machine. Application-consistent snapshots use Volume Shadow Copy Service (VSS) to ensure that applications are in a consistent state when the snapshot is taken. Note that if you enable application-consistent snapshots, it will affect the performance of applications running on source virtual machines. Ensure that the value you set is less than the number of additional recovery points you configure.
-
In Initial replication start time specify when to start the initial replication. The replication occurs over your internet bandwidth so you might want to schedule it outside your busy hours.
As you can see the policy’s are applied but you can create multiple but you can use only one at each site.
Site Recovery performs optimally when sufficient network bandwidth and storage are provisioned. Allocating insufficient capacity can lead to replication issues. Site Recovery provides a capacity planner to help you allocate the right resources for your source environment, the site recovery components, networking and storage. You can run the planner in quick mode for estimations based on an average number of VMs, disks, and storage, or in detailed mode in which you’ll input figures at the workload level.
Get the Azure Site Recovery Capacity planner here : Download
A quick overview of the Azure Site Recovery Capacity planner
If you skip this or thinking this will be fine I’ll show you later what can happen.
Now that all steps are completed in the ASR infrastructure we can start with step 2.
The replication can’t be Throttled only for backup operations you can Enable internet bandwidth usage throttling.
Selecting the Right networks for the replicated VM’s and subnets and the correct Storage account.
Next is selecting what VM’s I need to replicate. If there is no VM list then there is something wrong with your connection.
As my DPM machine has a disk larger than 1023 GB this can’t be replicated.
Selecting a few VM’s you can see even the names can be changed to the right Azure style or if there a characters in the name that are not supported.
In the old days you could only replicated one disk but now 64 Disks are supported. and you can select what disk you want and what to skip.
After these final steps we are ready to replicate
In a quick overview we can start the replication.
the replication is started and as you can see here comes the ASR Capacity planner.
OK this seams to be an issue for my other running VM’s on this hyper-v server.
Checking the Hyper-v server you can see the progress there or in Azure
But As ASR is using ASR you can also drill down on the replica options.
When the replica is done you can change the Azure VM in any way change the network , VM size the VM can be better than on prem.
As ASR stands for recovery you can do a test failover or planned. As you are not using VMM the Azure portal is the Orchestrator for the Failover.
Testing the VM is easy a you can run the VM Side by Side and you can change all the settings. A great option to get started with Azure.
Follow Me on Twitter @ClusterMVP
Follow My blog https://robertsmit.wordpress.com
Linkedin Profile Http://nl.linkedin.com/in/robertsmit
Google Me : https://www.google.nl
Bing Me : http://tinyurl.com/j6ny39w
LMGTFY : http://lmgtfy.com/?q=robert+smit+mvp+blog
Like this:
Like Loading...
