Error 13206 Virtual Machine Manager

21, 20084 0 0 0 When creating a new VM from scratch with a blank VHD or a VHD with a non-Windows OS, you will get the warning scvmm 2012 r2 error 13206 (VMM does peak inside the VHD as part of the creation process to error (13206) virtual machine manager cannot locate the boot or system volume determine this). This warning can be ignored. To have the VM autostart after completion, make sure the ‘Start the VM scvmm 2012 r2 update rollup 9 after deploying…’ checkbox is check at the end of the wizard: When creating a new VM from template, and that template contains a blank VHD or a non-Windows OS or a Windows OS that has not been generalized (i.e. the OS is not sysprepped), then the job will fail because VMM expects a VM from template to go through the sysprep customization process (hence why we ask for an OS profile). VMM will crack open the VHD and check of the OS is in a sysprep state. If not, then the job will fail. To create a proper template, you can use an existing Vm with a running Windows OS (right click on it and select New Template… this will kick off sysprep in the OS and then store the VM to Library as template… this removes the original VM). Or… if you already have VHDs that have been sysprepped, simply import them to the Library and then when you create a new template… attach that VHD instead of the blank one. Last… you can create a new template that does not require a sysprepped OS by selecting ‘Customization Not Required’ from the Guest OS profile dropdown: Keep in mind that of the VHD is blank or contains a non-Windows OS, it will complete with the same warning. Below are the job views to confirm that we are on the same page New VM from blank VHD (warning) New VM from template from a blank VHD (error) New Vm from template from blank VHD with ‘Customization Not Required’ (warning)

360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://blogs.technet.microsoft.com/hectorl/2008/08/21/digging-deeper-into-error-13206-virtual-machine-manager-cannot-locate-the-boot-or-system-volume-on-virtual-machine/ Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/3096389 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States)‎ Terms of use Privacy & cookies Trademarks © 2016 Microsoft

Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more http://serverfault.com/questions/718902/scvmm-error-13206-failed-to-install-vm-components about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask http://jaredheinrichs.com/how-to-setup-a-template-in-virtual-machine-manager-2008-r2.html Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SCVMM Error 13206 Failed to Install VM components up vote 0 down vote favorite I'm running error 13206 a MS Windows Failover Cluster with 4 nodes and one SCVMM host. All servers have the latest update of Windows Server 2012 R2. What I'm trying to do is create some virtual machines on the SCVMM Host and then migrate them onto the cluster and vice versa. The problem occurs every single time when migrating to or from Node 4. If I create 4 VMs and migrate them to the 4 nodes, 3 complete successfully and the 4th virtual machine manager one fails. The only difference I noticed is one extra step introduced when working with Node 4. The step is Install VM components. Successful migration to all other nodes: Move virtual machine VM-3 from VMMHost to Node-3 using SAN Run pre checks for transfer Change virtual machine status Export Hyper-V virtual machine Deploy file (using LAN) Deploy file (using LAN) Deploy file (using SAN transfer) Import Hyper-V virtual machine Remove virtual machine Failed migration with the extra step to Node 4: Move virtual machine VM-4 from VMMHost to Node-4 using SAN Run pre checks for transfer Change virtual machine status Export Hyper-V virtual machine Deploy file (using LAN) Deploy file (using LAN) Deploy file (using SAN transfer) Import Hyper-V virtual machine Remove virtual machine Install VM components The same step occurs even when I attempt the process with 8 VMs instead of 4. Any other number (1,2,3) of VMs does not encounter the additional step. The issue also occurs when migrating from cluster to host with the same error on the same VM and the same Node. This is the error shown by VMM: Error (13206) Virtual Machine Manager cannot locate the boot or system volume on virtual machine VM-4. The resulting virtual machine might not start or operate properly. I checked the Roles and Features on all the nodes and they are the same. Also, up do date. SCVMM is also up

to setup a template in Virtual Machine Manager 2008 R2 I was having all kind of issues trying to setup a template in VMM 2008. I originally got the dreaded: Error (13206)Virtual Machine Manager cannot locate the boot or system volume on virtual machine. I found a great article on the subject where it says you can’t create a virtual machine from a template that uses a blank or Non-Microsoft based OS! The reason for this is the VMM is smart and it can actually peak inside the VHD to see what OS is in it. In order to setup a template you need to make at least one virtual machine prior to making a template. The virtual machine that you made will be used and DESTROYED to make a template. I will repeat this again. The virtual machine that will be used for creating the template will be DESTROYED! What does this mean to you? You will need to create one virtual machine that will have nothing else installed on it. This walkthrough assumes you have VMM setup and you’ve deployed at least one VM that has the same OS of the template you are wanting to make. The Setup I’ve already created a virtual machine called DC. It really isn’t a DC. I was originally planning on using it as one until I realized my newly created template did not work Looking back on things I would have called it something like “Lemming” or “Born2Die”. You will need to click on the “Library” tab on the left side of the screen: After you have done that you will need to click on “New Template” in the right hand column under “Library Actions”. You will need to switch the default selection from “Use an existing template…” to “From an existing virtual machine that is deployed on a host”. Click “Browse”. A new window called “Select template source” will open. You will select the VM that you will sacrifice to the Microsoft Gods. In my case it is “DC”. Click “OK” and then “Next” on the “select source” window. Again you will be warned that the virtual machine that you selected will be used in a sacrifice for the greater good of easily creating VM’s with templates. Fill out what you want to call the template. You will need to leave these setting along. If you change the settings to something different from the virtual machine that was already made you will get a warning 10666 at the end of the procedure stating that