The configuration registry database is corrupt (0x800703F1).Error 2912 while VM template creation failed.

If you trying to Create A template and get’s the following error Message.

template deployment

Initially start the troubleshooting from the WinRm run the below command on the Host.

winrm set winrm/config @{MaxTimeoutms = “1800000”}

winrm set winrm/config/Service @{MaxConcurrentOperationsPerUser=”1500″}

net stop winrm

net start winrm

net start scvmmagent

Below also Could be the following reason’s.

Do not turn off the VM from the Hyper-V or SCVMM Console.

Gracefully Shutdown the VM from inside the VM and then Retry the Process.

Either the VM that you have deployed is the Syspred VM.

If you have configured Hyper-V Replica to use certificate based authentication over port 443.  SCVMM had also configured BITS to use certificate based authentication over port 443.  The result was that whenever SCVMM tried to use BITS to transfer a file – it would fail.

Fortunately – both BITS and Hyper-V Replica allow you to change the port that they use.  In my case I decided to change the port used by Hyper-V Replica from 443 to 444.  You can do this under the Hyper-V Settings:

Template1

 

Advertisements

Virtual machine creation fails when you try to deploy a virtual machine in Windows Azure Pack

When you try to deploy a virtual machine in Windows Azure Pack to a cloud that has a capability profile selected, virtual machine creation may fail, and you receive the following errors:

cloud

  • Log on to the System Center Virtual Machine Manager Admin console as an account that has administrative permissions.
  • Locate VMs and Services, select Clouds, and then select the cloud to which you are deploying.
  • Right-click the cloud, and then select Properties.
  • Select Capability Profiles.
  • Click to clear the check boxes for any profiles that are selected. Disabling all profiles enables deployment to any hypervisor.
  • Restart the deployment from WAP Portal.

Virtual Machine could not be started because the hypervisor is not running

hyper-v-error.jpg

Whenever I want to turn on any machine inside of Hyper-V, the following error message appears:

“Virtual Machine could not be started because the hypervisor is not running”

Whenever this happens, I run the following command:

bcdedit /set hypervisorlaunchtype Auto and reboot the Server. After a reboot, all Virtual Machines can be started without Problems.

The Hyper-V Virtual Machine Management service is set to Automatic.

Also try to change the valuve of hvservice from Regedit

Open Regedit

HKLM\SYSTEM\Current Control Set\Services\Hvservice change start DWORD value to “2”.

If you are Using Nested Virtualization.

Deploying Hyper-V over VMware Exsi check below update :-

Turn off the VM from the Vcenter

Go to Edit Setting from the VM go to option

Go to CPU/MMU Virtualization Enable VT-x and Intel APT/AMD

vmware intel

Upgrade the Hardware Version to 11 for ESXi 6.0 and 13 for ESXi for 6.5

  1. Start the vSphere Client or vSphere Web Client and log in to the vCenter Server.
  2. Select the host or cluster that contains the virtual machines to upgrade.
  3. Click the Virtual Machines tab.
  4. Select and power off the virtual machines to upgrade.
  5. Right-click your selections.
  6. Select Upgrade Virtual Hardware and click Yes.
  7. Power on the virtual machines.

SCVMM Build Numbers

System Center Virtual Machine Manager 2016 build numbers

Build Number KB Release Date Description
3.2.9013.0 SCVMM 2016 Technical Preview
3.2.9234.0 SCVMM 2016 Technical Preview 2
3.2.9362.0 SCVMM 2016 Technical Preview 3
4.0.1075.0 SCVMM 2016 Technical Preview 4
4.0.1091.0 KB3119301 Update for SCVMM 2016 Technical Preview 4
4.0.1374.0 SCVMM 2016 Technical Preview 5
4.0.1379.0 KB3158141 Cumulative Update 1 (CU1) for SCVMM 2016 Technical Preview 5
4.0.1381.0 KB3160164 Cumulative Update 2 (CU2) for SCVMM 2016 Technical Preview 5
4.0.1390.0 KB3164176 Cumulative Update 3 (CU3) for SCVMM 2016 Technical Preview 5
4.0.1662.0 Download 2016 September 26 SCVMM 2016 RTM
4.0.1968.0 KB3190597 2016 October 13 Update Rollup 1 for SCVMM 2016
4.0.1968.10 KB3208888 2016 December 12 Hotfix 1 for SCVMM 2016 Update Rollup 1
4.0.2043.0 KB3209586 2017 January 24 Update Rollup 2 for SCVMM 2016
4.0.2051.0 KB4011491 2017 February 22 Update Rollup 2.1 for SCVMM 2016
4.0.2051.1 Download 2017 March 13 Hotfix for VMM 2016 – Test replica failover issue
4.0.2139.0 KB4014528 2017 May 23 Update Rollup 3 for SCVMM 2016
4.0.2244.0 KB4041074 2017 October 23 Update Rollup 4 for SCVMM 2016

System Center Virtual Machine Manager 2012 R2 build numbers

Build Number KB Description
3.1.7200.0 SCVMM 2012 R2 Preview
3.2.7510.0 SCVMM 2012 R2 RTM
3.2.7620.0 KB2904712 SCVMM 2012 R2 Update Rollup 1
3.2.7634.0 KB2932926 SCVMM 2012 R2 Update Rollup 2
3.2.7672.0 KB2965414 SCVMM 2012 R2 Update Rollup 3 (2014 July 29)
3.2.7768.0 KB2992024 SCVMM 2012 R2 Update Rollup 4 (2014 October 28)
3.2.7895.0 KB3023195 SCVMM 2012 R2 Update Rollup 5 (2015 February 10)
3.2.7986.0 KB3039296 SCVMM 2012 R2 HOTFIX For Update Rollup 5 (2015 February 23)
3.2.8002.0 KB3050317 SCVMM 2012 R2 Update Rollup 6 (2015 April 28)
3.2.8071.0 KB3066340 SCVMM 2012 R2 Update Rollup 7 (2015 July 28)
3.2.8117.0 KB3096389 SCVMM 2012 R2 Update Rollup 8 (2015 October 27)
3.2.8145.0 KB3129784 SCVMM 2012 R2 Update Rollup 9 (2016 January 27)
3.2.8169.0 KB3147167 SCVMM 2012 R2 Update Rollup 10 (2016 May 24)
3.2.8224.0 KB3184831 SCVMM 2012 R2 Update Rollup 11 (2016 August 23)
3.2.8228.0 KB3199246 Hotfix 1 for SCVMM 2012 R2 Update Rollup 11 (2016 October 21)
3.2.8292.0 KB3209585 SCVMM 2012 R2 Update Rollup 12 (2017 January 24)
3.2.8292.20 Download Hotfix for VMM 2012 R2- Test replica failover and cmdlet generated for VLAN isolation issues (2017 March 13)
3.2.8377.0 KB4014525 SCVMM 2012 R2 Update Rollup 13 (2017 May 23)

 

System Center Virtual Machine Manager 2012 SP1 build numbers

Build Number KB Description
3.1.1042.0 SCVMM 2012 SP1 CTP1
3.1.3010.0 SCVMM 2012 SP1 CTP2
3.1.3612.0 SCVMM 2012 SP1 Beta
3.1.5016.0 SCVMM 2012 SP1 RC
3.1.6011.0 SCVMM 2012 SP1 RTM
3.1.6018.0 KB2785682 SCVMM 2012 SP1 Update Rollup 1
3.1.6020.0 KB2802159 SCVMM 2012 SP1 Update Rollup 2
3.1.6027.0 KB2836751 SCVMM 2012 SP1 Update Rollup 3
3.1.6032.0 KB2879276 SCVMM 2012 SP1 Update Rollup 4
3.1.6038.0 KB2904727 SCVMM 2012 SP1 Update Rollup 5
3.1.6046.0 KB2932860 SCVMM 2012 SP1 Update Rollup 6
3.1.6084.0 KB2965410 SCVMM 2012 SP1 Update Rollup 7
3.1.6099.0 KB3023196 SCVMM 2012 SP1 Update Rollup 9
3.1.6108.0 KB3076889 SCVMM 2012 SP1 Update Rollup 10 (2015 July 28)
3.1.6109.0 KB3101195 SCVMM 2012 SP1 Update Rollup 11 (2015 October 27)

System Center Virtual Machine Manager 2012 build numbers

Build Number KB Description
3.0.5007.0 SCVMM 2012 RC
3.0.6005.0 SCVMM 2012 RTM
3.0.6019.0 KB2686249 SCVMM 2012 Update Rollup 1
3.0.6040.0 KB2706783 SCVMM 2012 Update Rollup 2
3.0.6055.0 KB2785681 SCVMM 2012 Update Rollup 4
3.0.6057.0 KB2822776 SCVMM 2012 Update Rollup 5
3.0.6060.0 KB2861038 SCVMM 2012 Update Rollup 6
3.0.6062.0 KB2888943 SCVMM 2012 Update Rollup 7

System Center Virtual Machine Manager 2008 R2 SP1 build numbers

Build Number KB Release Date Description
2.0.4521.0 24/03/2011 SCVMM 2008 R2 SP1
2.0.4571.0 KB2562466 12/07/2011 SCVMM 2008 R2 SP1 Update Rollup 1
2.0.4600.0 KB2691812 22/05/2012 SCVMM 2008 R2 SP1 Update Rollup 2

System Center Virtual Machine Manager 2008 R2 build numbers

Build Number KB Release Date Description
2009 August 24 SCVMM 2008 R2 RTM
2.0.4272.0 KB976244 2009 November 10 SCVMM 2008 R2 hotfix rollup package
2.0.4273.0 KB978560 2010 February 9 SCVMM 2008 R2 hotfix rollup package
2.0.4273.0 KB982523 2010 June 8 SCVMM 2008 R2 Admin Console hotfix rollup package
2.0.4274.0 KB982522 2010 June 8 SCVMM 2008 R2 hotfix rollup package
2.0.4272.0 – 2.0.4275.0 KB2308590 2010 September 14 SCVMM 2008 R2 hotfix rollup package
2.0.4272.0 – 2.0.4276.0 KB2492980 2011 February 8 SCVMM 2008 R2 hotfix rollup package

 

VM Unsupported Configuration in VMM

VM’s were showing status as “Unsupported VM Configuration”

Follow below steps :-

001.png

By opening the properties of the VM we can highlight the error and see why it is failing – in this case it was due to an iso file error.

002.png

Attempts to remove the iso from the VM were unsuccessful from VMM.

003.PNG

004.PNG

UR2 is supposed to resolve this issue, but I validated that UR2 was already applied per the KB #2690619 (Virtual machine configured to use an ISO has a status of Unsupported VM Configuration in System Center 2012 Virtual Machine Manager) by viewing the update history on the VMM server.

To fix this, use the workaround in the article – dismount the ISO via Hyper-V manager on the host system.

Summary:  To fix the “Unsupported VM Configuration” issue, dismount the ISO via Hyper-V manager on the host system.

How to Install SCVMM Service Portal

To start the Microsoft System Center 2012 Virtual Machine Manager Setup Wizard, on your installation media, right-click setup.exe, and then click Run as administrator.

Before beginning the installation of VMM, close any open programs and ensure that there are no pending restarts on the computer.

For example, if you have installed a server role by using Server Manager or have applied a security update, you may need to restart the computer and then log on to the computer with the same user account to finish the installation of the server role or the security update.

On the main setup page, click Install.

On the Select features to install page, select the VMM Self-Service Portal check box, and then click Next.

On the Please read this notice page, click I agree with the terms of this notice, and then click Next.

On the Microsoft Update page, select whether or not you want to use Microsoft Update, and then click Next.

If you have previously chosen to use Microsoft Update on this computer, the Microsoft Update page does not appear.

On the Installation location page, use the default path or type a different installation path for the VMM program files, and then click Next.

The computer on which you are installing the VMM Self-Service Portal will be checked to ensure that the appropriate hardware and software requirements are met.

If a prerequisite is not met, a page will appear with information about which prerequisite has not been met and how to resolve the issue.

For information about hardware and software requirements for VMM, see System Requirements: VMM 2012 and VMM 2012 SP1.

If all prerequisites have been met, the Self-Service portal configuration page will appear.

On the Self-Service portal configuration page, specify the following:

The name of the VMM management server to which the VMM Self-Service Portal will connect.

The port that the VMM Self-Service Portal will use to communicate with the VMM management server.

Under Web Server, the port that self-service users will use to connect to the VMM Self-Service Portal.

If the default port for the VMM Self-Service Portal (port 80) is being used by another web site on the computer, you must either use a different dedicated port or specify a host header for the Self-Service Portal. For more information about host headers, see Configure a Host Header for a Web Site (IIS 7).

On the Installation summary page, review your selections and do one of the following:

Click Previous to change any selections.

Click Install to install the VMM Self-Service Portal.

After you click Install, the Installing features page appears and installation progress is displayed.

On the Setup completed successfully page, click Close.

NOTE :- If there is a problem with setup completing successfully, consult the log files in the %SYSTEMDRIVE%\ProgramData\VMMLogs folder. ProgramData is a hidden folder.

Prerequisite for Installing SCVMM 2016

Operating System
Server 2016 Standard (with Desktop Experience)
SQL Server 2016 Standard
Windows Assessment and Deployment Kit - 10 (ADK) You can download it here.
Command Line Utilities 11 for SQL Server
https://www.microsoft.com/en-us/download/details.aspx?id=36433
ODBC Driver 11 for SQL Server
https://www.microsoft.com/en-us/download/details.aspx?id=36434

SUPPORTED SQL
  • SQL Server 2012 SP2 Enterprise, Standard (64 bit)
  • SQL Server 2014 Enterprise, Standard (64-bit)
  • SQL Server 2014 SP1 Enterprise, Standard (64-bit)
  • SQL Server 2016, Enterprise, Standard (64-bit)

Client Operating Systems to which the SCVMM Administrator Console can be installed Windows 8 Windows 8.1 Windows Server 2008 R2 SP1 Windows Server 2012 Windows Server 2012 R2 Standard, Datacenter Windows 10 Enterprise Windows Server 2016 Standard, Datacenter

NOTE :-
SCVMM 2016 can only be installed on Windows Server 2016. 
It can not be installed on the Nano Server However you can Manage Nano Server a Host.
The server name should not contain any special characters. 
Example: SCVMM-Server CAN NOT be SCVMM Server.
The SCVMM 2016 product can be installed as a virtual machine. 
If you want to use Dynamic memory, Startup RAM has to be 2GB.