Video introducing the Microsoft Cloud Platform System.
Microsoft Virtual Machine Converter (MVMC) is a Microsoft-supported, stand-alone solution for the information technology (IT) pro or solution provider who wants to
- convert virtual machines and disks from VMware hosts to Hyper-V hosts and Microsoft Azure.
- convert physical machines and disks to Hyper-V
This guide is intended for the enterprise customer in an IT role, such as the IT decision maker (ITDM), IT pro, or IT implementer. It provides an overview of MVMC features and functionality, as well as information about how to install and use MVMC as a conversion solution.
MVMC can be deployed with minimal dependencies. Because MVMC provides native support for Windows PowerShell, it enables scripting and integration with data center automation workflows such as those authored and run within Microsoft System Center Orchestrator 2012 R2. It can also be invoked through the Windows PowerShell command-line interface. The solution is simple to download, install, and use. In addition to the Windows PowerShell capability, MVMC provides a wizard-driven GUI to facilitate virtual machine conversion.
New Features in MVMC 3.0
MVMC 3.0 release of MVMC includes the following new features:
- Online conversion of physical machines to virtual hard disks (VHDs) that can be uploaded to Hyper-V hosts
Key MVMC Features
In addition to the new feature above, MVMC provides the following functionality:
- Converts and deploys virtual machines from VMware hosts to Hyper-V hosts on any of the following operating systems:
- Windows Server 2012 R2
- Windows Server 2012
- Windows Server 2008 R2 SP1
- Converts VMware virtual machines, virtual disks, and configurations for memory, virtual processor, and other virtual computing resources from the source to Hyper-V.
- Adds virtual network interface cards (NICs) to the converted virtual machine on Hyper-V.
- Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.1, and VMware vSphere 4.1 hosts to Hyper-V.
- Has a wizard-driven GUI, which simplifies performing virtual machine conversions.
- Uninstalls VMware Tools before online conversion (online only) to provide a clean way to migrate VMware-based virtual machines to Hyper-V.
Important MVMC takes a snapshot of the virtual machine that you are converting before you uninstall VMware Tools, and then shuts down the source machine to preserve state during conversion. The virtual machine is restored to its previous state after the source disks that are attached to the virtual machine are successfully copied to the machine where the conversion process is run. At that point, the source machine in VMware can be turned on, if required.
Important MVMC does not uninstall VMware Tools in an offline conversion. Instead, it disables VMware services, drivers, and programs only for Windows Server guest operating systems. For file conversions with Linux guest operating systems, VMware Tools are not disabled or uninstalled. We highly recommend that you manually uninstall VMware Tools when you convert an offline virtual machine.
- Supports Windows Server and Linux guest operating system conversion. For more details, see the section “Supported Configurations for Virtual Machine Conversion” in this guide.
- Provides native Windows PowerShell capability that enables scripting and integration into IT automation workflows.
Note The command-line interface (CLI) in MVMC 1.0 has been replaced by Windows PowerShell in MVMC 2.0.
- Supports conversion and provisioning of Linux-based guest operating systems from VMware hosts to Hyper-V hosts.
- Supports conversion of offline virtual machines.
- Supports the new virtual hard disk format (VHDX) when converting and provisioning in Hyper-V in Windows Server 2012 R2 and Windows Server 2012.(Does not apply to physical machine conversions.)
- Supports Windows Server 2008 through Windows Server 2012 R2, and Windows Vista through Windows 8 as guest operating systems that you can select for conversion, along with an umber of Linux distributions. See the section “Supported Configurations for Virtual Machine Conversion” for more detail.
- Includes Windows PowerShell capability for offline conversions of VMware-based virtual hard disks (VMDK) to a Hyper-V–based virtual hard disk file format (.vhd file).
Note The offline disk conversion does not include driver fixes.
And ofcourse there are Powershell CMDlets to do conversions and handy for automation.
This script is a representative sample of the entire flow to perform a physical to virtual machine conversion:
## Create the credentials
$user = ‘User Name’
$pass = convertto-securestring ‘Password’ -asplaintext -force
$cred = new-object pscredential ($user, $pass)
## Import the module
Import-Module “C:\Program Files\Microsoft Virtual Machine Converter\MvmcCmdlet.psd1″
$SourceMachine = ‘SourceMachineName’
## Get system information and logical drives
$conn = new-mvmcp2vsourceconnection -physicalserver $SourceMachine -sourcecredential $cred
$sys = Get-MvmcP2VSourceSystemInformation -P2VSourceConnection $conn
$lcs = $sys.LogicalDrives
$lcs | ft driveletter
$nads = $sys.NetworkAdapters
## Create the P2V target VM configuration
$p2vparam = New-MvmcP2VRequestParam
$p2vparam.CpuCount = 1 ##Number of PRocessors on the destination VM
$p2vparam.StartupMemoryInMB = 512 ##Memory for the destination VM
$p2vparam.UseDynamicMemory = $false ##Memory Static or Dynamic
$p2vparam.SelectedNetworkAdapters.add($nads, “External”) ##VSwitch Name on the HyperV Host
$HyperVHostName = ‘DestinationHostName’
$HyperVHostUser = ‘DestinationUserName’
$HyperVHostPass = convertto-securestring ‘DestinationPassword’ -asplaintext -force
$HyperVHostCred = new-object pscredential ($HyperVHostUser, $HyperVHostPass)
$hvconn = New-MVMCHyperVHostConnection -HyperVServer $HyperVHostName -HostCredential $HyperVHostCred
$DestinationPath = ‘FinalPath’ #THis can be a local path (c:\VMPath), if the converter and host are the same machine, else only a share path (\\Server\Share)
$TempWorkingFolder = ‘Temp Path’ #this path is used for disk fixups, and must be a local path (c:\temp)
$VMName = ‘VM Name’
## P2V conversion
ConvertTo-MvmcP2V -SourceMachineConnection $conn -DestinationLiteralPath $DestinationPath -DestinationHyperVHostConnection $hvconn -TempWorkingFolder $TempWorkingFolder -VmName $VMName -P2VRequestParam $p2vparam -Verbose -Debug
Here you can download the Microsoft Virtual Machine Converter 3.0 and all documentation with the Powershell commands guide included.
When you want to learn more about all the Microsoft Products like :
- Windows Server 2012 R2
- Windows Server 2012 R2 Hyper-V
- System Center 2012 R2
- Microsoft Azure
- App Development in the Microsoft Azure Cloud
- Microsoft SQL Server 2014
- Windows 8.1
- and More……….
You have to go to this awesome Microsoft Virtual Academy site for Free E-books
And ofcourse you can follow online Microsoft Courses and Live Events at Microsoft Virtual Academy site for Free
Organization of this book
This ebook explains thirteen recommended patterns for cloud development. “Pattern” is used here in a broad sense to mean a recommended way to do things: how best to go about developing, designing, and coding cloud apps. These are key patterns that will help you “fall into the pit of success” if you follow them.
• Automate everything
• Use scripts to maximize efficiency and minimize errors in repetitive processes.
• Demo: Azure management scripts.
• Source control
• Set up branching structures in source control to facilitate a DevOps workflow.
• Demo: add scripts to source control.
• Demo: keep sensitive data out of source control.
• Demo: use Git in Visual Studio.
• Continuous integration and delivery
• Automate build and deployment with each source control check-in.
• Web development best practices
• Keep web tier stateless
• Demo: scaling and autoscaling in Azure Websites.
• Avoid session state.
• Use a Content Delivery Network (CDN).
• Use an asynchronous programming model.
• Demo: async in ASP.NET MVC and Entity Framework.
• Single sign-on
• Introduction to Azure Active Directory.
• Demo: create an ASP.NET app that uses Azure Active Directory.
• Data storage options
• Types of data stores.
• How to choose the right data store.
• Demo: Azure SQL Database.
• Data partitioning strategies
• Partition data vertically, horizontally, or both to facilitate scaling a relational database.
• Unstructured blob storage
• Store files in the cloud by using the Blob service.
• Demo: using blob storage in the Fix It app.
• Design to survive failures
• Types of failures.
• Failure scope.
• Understanding SLAs.
• Monitoring and telemetry
• Why you should both buy a telemetry app and write your own code to instrument your app.
• Demo: New Relic for Azure
• Demo: logging code in the Fix It app.
• Demo: built-in logging support in Azure.
• Transient fault handling
• Use smart retry/back-off logic to mitigate the effect of transient failures.
• Demo: retry/back-off in Entity Framework 6.
• Distributed caching
• Improve scalability and reduce database transaction costs by using distributed caching.
• Queue-centric work pattern
• Enable high availability and improve scalability by loosely coupling web and worker tiers.
• Demo: Azure storage queues in the Fix It app. 11
More cloud app patterns and guidance
• Appendix: The Fix It Sample Application
• Known issues.
• Best practices.
• Download, build, run, and deploy instructions.
These patterns apply to all cloud environments, but we’ll illustrate them by using examples based on Microsoft technologies and services, such as Visual Studio, Team Foundation Service, ASP.NET, and Azure.
This white paper demonstrates the capabilities and performance for Violin Windows Flash Array (WFA), a next generation All-Flash Array storage platform. With the joint efforts of Microsoft and Violin Memory, WFA provides built-in high performance, availability and scalability by the tight integration of Violin’s All Flash Array and Microsoft Windows Server 2012 R2 Scale-Out File Server Cluster.
Configuration Manager 2012 R2 disaster recovery is a complex process. It requires sufficient knowledge of the Configuration Manager Product & dependent components. This document describes the steps to recover a full Configuration Manager 2012 R2 hierarchy in case of disaster. This document also describes the steps to recovery either CAS or Primary sites as well as additional steps that Configuration Manager Administrators should follow in order to restore a Configuration Manager Hierarchy or Sites without data loss. This document also provides some helpful troubleshooting tips.
At a higher level, there are the following few steps described below to recover an entire hierarchy in the event of disaster. Please note that the steps are different for recovering an entire hierarchy and individual site servers such as CAS or Primary sites. Please refer to appropriate sections within this document to recover appropriate site servers. The approximate time noted below in each of the tasks may vary significantly as there are many factors involved when recovering an entire hierarchy so use this timing as an example ONLY.
- Collect CAS & Primary Site Information (~1 hour) In this step, collect & document all the necessary information required from the existing hierarchy. This task should be followed regularly whenever there are updates/changes at the site level so that it will save time at the time of disaster recovery.
- Backup Sites – CAS & Primary (~3 hrs.) This section describes backup options.
- Recover CAS Site (~3 to 48 hrs.) This section provides the steps to recover the CAS Site server. Global data can be recovered within 3-4 hours but for site data it can take up to 48 hours.
- Recover Primary Site(s) (~3 to 48 hrs.) This section provides the steps to recover Primary Site servers. Global data can be recovered within 3-4 hours but for site data it can take up to 48 hours. Recover from supplemental backups (~2 hrs.)
- This section describes the steps to recover the additional components of Configuration Manager.