Zeros & Ones : VMM R2

VMM hotfixes... The entire collection :)

Fawzi — Thu, 23 Sep 2010 16:43:00 GMT

This article describes recommended updates to install to address issues when you are managing hosts or are performing a physical-to-virtual (P2V) conversion by using Microsoft System Center Virtual Machine Manager 2008 R2.

Use the information in the "More information" section to help you determine whether a particular hotfix or update applies to your environment.

Now time for the collection

Press here... Or there :) http://support.microsoft.com/kb/2397711

do not forget that one too http://support.microsoft.com/kb/2308590

VMM Tricks: VMM Self Service Portal and NLB

Fawzi — Tue, 21 Sep 2010 10:22:00 GMT

A very interesting question in Technet forums about VMM SSP high availability

“Virtual Machine Manager does not support Network Load Balancing (NLB) clusters in Windows Server 2008, which are required in order to distribute the network traffic among self-service users on multiple Web sites.

what problems or issues present this configuration?”

Well, a basic bing did not get any answer for that so I decided to ask a friend “Brandon” from MS Support and goth that answer

“I understand you are concerning why VMM SSP doesn’t support NLB for load balancing. Please correct me if I have any misunderstanding.

We had intensively discussed this limitation with our development team previously and the main reasons are that it is not a tested scenario and SSP is not stateless.

1. The main thing is that the SSP is not stateless, thus when a user connects to it he/she can’t bounce around without a loss of state.

2. we haven’t tested this scenario as a major scenario for VMM 2008 R2.

3. We know customers that are using it for fault tolerance purposes. In order for this to work you need to enable persistence on your load balancer.

Currently , I think the only gain from NLB would be to protect against the web server failure, in which case only the users who were assigned to that webserver would get booted off, but when they login again they would hit the remaining server(s) and be OK. So you can get some mild reliability enhancements but not really performance gains (loading balance). “

I had tested SSP load balancing before and it was fine. I did not get the cahnce to test it in huge production environment but I think I will try to do that.

That all for now folks..

VMM tricks: Saving and re-applying the #virtual machine metadata in #VMM

Fawzi — Tue, 24 Aug 2010 21:30:00 GMT

Michael Michael has posted a great blog that outlines exactly how to restore the metadata through the use of powershell scripts.

http://blogs.technet.com/b/m2/archive/2010/04/16/saving-and-re-applying-the-virtual-machine-metadata-in-vmm.aspx

The saved metadata can be applied later on in the event that you add and remove the host from VMM management. A scenario where this issue comes up is when something goes wrong with your host in VMM and you need to remove it from management and re-add it to VMM (the host can also be a cluster). Typically in a situation like this you will loose all the metadata associated with your virtual machines. Such metadata includes the custom properties, descriptions, tags, owner, cost center, etc. If it is 1 or 2 VMs, its not a big deal to add them back, but when you are talking about a cluster with 200 VMs it is quite an effort.

P2V fails with Error 2912 0x80072F0C with System Center Virtual Machine Manager 2008

Fawzi — Mon, 23 Aug 2010 21:38:00 GMT

When using System Center Virtual Machine Manager (SCVMM) to perform a Physical to Virtual (P2V) conversion, the job may fail at 60% with the following error:

Error (2912)
An internal error has occurred trying to contact an agent on the vmmserver.contoso.com server.

Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.

Cause:

During the ‘Make operating system virtualizable’ step, files are copied from the destination host (the server that will host the virtualized system) to the SCVMM Server. This BITS operation fails due to a certificate problem as indicated by the error 0x80072F0C (ERROR_INTERNET_CLIENT_AUTH_CERT_NEEDED).

Resolution:

To resolve this issue, remove the managed host from the SCVMM server and also delete any residual certificates from the host on the VMM server, then re-add the host:

1. On the SCVMM server, remove the managed host from the console. The steps on how to remove a managed host are outlined in the following TechNet article:

http://technet.microsoft.com/en-us/library/cc956121.aspx (http://technet.microsoft.com/en-us/library/cc956121.aspx)

2. Now we need to locate and delete any certificates for the Host computer.

3. Open the Certificate console on the SCVMM server.

a. Open a new mmc and add the certificates snap-in.
b. Select the option of ‘computer account’ and ‘local computer’.
c. Select Finish and Ok to load the snap-in.

4. The certificates for the Host computer can be in any of the following locations.

a. Personal Certificates.
b. Trusted People (if the host is W2K8 or W2K8 R2).
c. Trusted Root Authorities (If the host is W2K3).

5. In each store, expand the Friendly Name field and locate the certificate[s] for the Host server that have a Friendly Name starting with ‘SCVMM_CERTIFICATE_KEY_CONTAINER’ followed by either the FQDN / IP address / NetBIOS name of the Host server and delete them.

6. Re-add the host in SCVMM which recreates the certificates as needed.

More Information:

SCVMM uses BITS to transfer payload between SCVMM managed computers. These data transfers are encrypted by using a self-signed certificate generated at the time a host machine is added to SCVMM. If these certificates are missing or corrupted from the SCVMM server or managed computers, the payload deployment job can fail. Deleting the certificates and re-adding the host will cause the certificates to be regenerated.

For the latest information on this issue see the following Knowledge Base article:

KB2385280 – P2V fails with Error 2912 0x80072F0C with System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2

J.C. Hornbeck | System Center Knowledge Engineer

VMM Tricks: VMM Domain Function Level … Why

Fawzi — Mon, 02 Aug 2010 11:58:00 GMT

So most of use already knows that VMM 2008 R2 required Windows 2003 Domain level for the installation and I already blogged about some error that you may face if VMM is connected and authenticated by windows 2000 domain controller in the installation phase.

But it was a new question when one asked me “Why Windows 2003 Domain Level?”

Kerberos authentication is a prerequisite for VMM. To configure your environment to allow users in one Active Directory Domain Services (AD DS) domain to access VMM resources in another domain, you can either ensure that both domains are in the same forest or configure a forest-level trust relationship and use Kerberos authentication. To set up a forest-level trust relationship, both domains must be in Windows Server 2003 forest mode. Windows 2000 Server does not support forest-level trusts.

Windows Server 2003 and Windows 2000 Server environments that contain complex group structures can encounter problems with an access token limitation during authentication.

The Kerberos Access Token in Windows 2000 native mode environment had many limitations and the resolution is just simply to raise domain function level to Windows 2003.

Check MS Addressing Problems Due to Access Token Limitation

http://download.microsoft.com/download/8/f/3/8f36dfe4-47d0-4775-ad5a-5614384921aa/AccessTokenLimitation.doc

Microsoft System Center Virtual Machine Manager Self-Service Portal 2.0 Step by Step Guide- Part Two

Fawzi — Fri, 23 Jul 2010 17:01:00 GMT

Self-Service Portal Components

The self-service portal consists of three components:

VMMSSP website: A Web-based component that provides a user interface to the self-service portal. Through the VMMSSP website, users can perform various tasks such as pooling infrastructure assets in the self-service portal, extending virtual machine actions, creating business unit and infrastructure requests, validating and approving requests, and provisioning virtual machines (using the self service virtual machine provisioning feature). Users can also use the website to view information related to these tasks.

VMMSSP database: A SQL Server® database that stores information about configured assets, information related to business units and requests, and information about what has been provisioned to various business units. The database also stores the XML that encodes default and customized virtual machine actions and other information related to the configuration of the self-service portal.

VMMSSP server: A Windows service that runs default and customized virtual machine actions that the user requests through the VMMSSP website. The service uses a Windows Communication Foundation (WCF) TCP endpoint to listen for client communication, and hosts a Windows Workflow Foundation (WF) run-time environment. Using WF, the server component runs the sequences of tasks that comprise virtual machine actions. You can optimize the performance of the server component using parameters available in the self-service portal or in configuration files; these parameters control or “throttle” the number of operations that can run simultaneously

Test Lab Setup: Single-Machine Deployment Scenario

Figure 1 illustrates the single-machine deployment scenario. In this scenario, you must install the self-service portal components on a physical computer or virtual machine that also runs the System Center Virtual Machine Manager (VMM) Administrator Console and SQL Server 2008. The VMM server component (including the VMM Library) and the virtual machine hosts all run on separate computers.

Figure 1. Topology of the single-machine deployment scenario

Environmental Prerequisites

When you install a component of the self-service portal, the Setup wizard checks the target computer for the components and settings required for that component. However, the self-service portal components have general requirements that this prerequisite check cannot detect. These requirements are referred to as environmental prerequisites—they apply to the whole environment in which the self-service portal components function. To ensure that the self-service portal components deploy smoothly and function as expected, prepare the environment before you run the Setup wizard.
Important: Because environmental changes affect more than the self-service portal components, exercise due caution when making sweeping changes.
This section describes the environmental prerequisites for the self-service portal, including Active Directory® Domain Services (AD DS) requirements and security considerations.

Infrastructure

Before you install the self-service portal components, make sure that the computers you intend to use for the self-service portal components belong to an AD DS domain. You must also ensure that you have installed Virtual Machine Manager 2008 R2 to manage virtual machines in your environment. For information about configuring VMM to work with the self-service portal, see “Configuring Hyper-V and VMM Resources to Work with the Self-Service Portal” in the Virtual Machine Manager 2008 R2 VMMSSP Datacenter Administration Guide.

Security Considerations

Securing the environment for the self-service portal involves the following tasks:
• Understanding and planning the default and custom user roles that are defined in the self-service portal.
• Planning and preparing the service accounts.
• Understanding the ports and protocols required for establishing communication channels between various self-service portal components.
• Hardening the Web server that will run the VMMSSP website component.

Source & more information: VMMSSP Deployment Guide

System Center Virtual Machine Manager Self Service Portal: Private Cloud Customer Case Study!

Fawzi — Fri, 23 Jul 2010 17:01:00 GMT

Hi folks,

Last week at the WPC, we sannounced the release candidate for the System Center Virtual Machine Manager Self-Service Portal (SC VMM Self Service Portal). The SC VMM Self Service Portal allows our enterprise customers set up their own private cloud environments using our Server platform, comprised of Windows Server and System Center.

We’d like to share how Lionbridge, a leading provider of language, development and test services is using the SC VMM Self Service Portal to simplify its processes and improve agility by building their private cloud environment on the Microsoft platform. Go here for more details on this fantastic case study!

Like Lionbridge, we encourage you to enhance your existing investments in the familiar and well supported Microsoft Server platform! Go for it: build your own private clouds and start reaping the benefits of cloud computing!

We’re all in! Are you with us?

Cheers,

Anant (ansundar@microsoft.com) , Senior Product Manager

System Center Marketing, Microsoft Corporation

SCVMM and Dynamic Memory support

Fawzi — Fri, 23 Jul 2010 17:01:00 GMT

This is a very important question… When SCVMM will support Dynamic Memory feature introduced in Windows 2008 R2 SP1 Hyper-V server?

There is less public information about the new features that integrated with Windows 2008 R2 SP1 so far, So I had to check with MS private newsgroup.

Brandon for newsgroup came back with this answer ” I had consulted our SCVMM product team and the answer I got is there will be a “feature pack” for SCVMM 2008 R2 that will add-in the capability to manage the new Dynamic Memory feature coming in Windows Server 2008 R2 SP1. Our product team will try to RTM SCVMM package very shortly after the RMT date of Windows 2008 R2 SP1. There will be no SCVMM support for pre-release builds of Windows 08 R2 SP1 until the RC milestone. “

Service Pack 1 for Windows 7 and Windows Server 2008 R2 will be released “within the first half of calendar year 2011,” Microsoft announced this week.

The service pack is currently available as a beta for test purposes, having been released earlier this month. However, this week, Microsoft published a FAQ on the SP1 beta, which disclosed the approximate product release date for the service pack, perhaps for the first time.

So nothing expected before the first half of calendar year 2011.

VMM tricks: “Virtual Machine Manager lost the connection to the virtual machine because another connection was established to the machine”

Fawzi — Fri, 23 Jul 2010 17:01:00 GMT

After finishing my new test lab to test my new VDI solution I faced this problem.

My Lab:

2 Windows 2008 R2 Hyper-V hosts Clustered with failover cluster
VMM 2008 R2 Server
A new VM with Windows 2008

Finished my Cluster setup and Installed VMM on 3th server.. Add Cluster hosts went fine without any problems… Then I tried to connect my VM through VMM console and Ooops …

I got this error message “Virtual machine manager lost the connection to the virtual machine because another connection was established to the machine”.

I am using Enterprise administrator account since it is a test lab.. make sure that no other connection form Hyper-V console to this VM. Try to press Reconnect bottom.. No thing same error

mm.. trying to connect using Hyper-V Manager went fine.. Remote desktop connection no problems

Virtual Machine Manager is run as administrator. So I closed the console and right click the SCVMM console, and select “run as administrator”. No Changes .. grrrrrrrrrr.

Removing the Hyper-V Cluster and add it again… Same error

So I created a new User with domain admin privilege and add it to VMM admins group.. trying to connect and it is working.

So the problem was in my Enterprise administrator account.. looks like VMM is having problem with this account, So I deleted it from VMM User roles and added it again and guess what.. it is working.

Microsoft System Center Virtual Machine Manager Self-Service Portal 2.0 Step by Step Guide- Part One

Fawzi — Fri, 16 Jul 2010 12:49:00 GMT

What is Microsoft System Center Virtual Machine Manager Self-Service Portal 2.0?
Microsoft is enabling customers to build the foundation for private cloud infrastructure using Windows Server/Hyper-V and the System Center family of products with the System Center Virtual Machine Manager Self-Service Portal 2.0 (previously known as the Dynamic Datacenter Toolkit). Click here to download the release candidate.

The System Center Virtual Machine Manager Self-Service Portal 2.0 is a free, partner-extensible toolkit that will enable datacenters to dynamically pool, allocate, and manage virtualized resources to enable Infrastructure-as-a-Service. This solution will deliver:
• Tested guidance and best practices to help configure and deploy private cloud infrastructures.
• Automated web portals and infrastructure provisioning engine that’s integrated with System Center.
• Guidance to help partners easily extend functionality.

Today, customers can also leverage Dynamic Datacenter Alliance (DDA) offerings from service providers (Microsoft hosting partners) to extend their on-premises private clouds in a secure manner. These service providers use the Dynamic Datacenter Toolkit for Hosters (DDTK-H), which is also built on top of Windows Server/Hyper-V and System Center, thus enabling a consistent off- premises cloud capability to tap into. There are more than 63 hosters that have live DDA offerings as of today, while over 100 others have offerings in the pipeline.

Interesting… So How can I do that ?

The self-service portal provides a way for groups within an organization (referred to as business units) to manage their own IT needs, while the organization manages a centralized pool of physical resources (servers, networks, and related hardware, referred to as the datacenter).
Instead of using physical servers and related hardware to build an IT infrastructure, a business unit IT (BUIT) administrator uses the self-service portal to build an IT infrastructure from virtual machines. The datacenter provides the physical resources to support the virtual machines, and the self-service provides the database that relates the business unit infrastructures to the physical resources and an extensible interface for the central IT administrator (referred to as the datacenter or DC administrator) to use to provision resources for the business units.

To use resources managed by the self-service portal, a business unit submits a Web-based registration form. By approving the request, the DC administrator adds the business unit to the VMMSSP database (this process is sometimes referred to as “onboarding.”) The DC administrator allocates capacity for the business unit infrastructure in the datacenter resources. The self-service portal tracks how each business unit uses its resources, and, if appropriate, provides the DC administrator with charge-back data—the information needed to quantify resource usage in terms of the organization’s internal budgeting system.

In addition to these functions, the self-service portal can also enforce change control processes. Although business unit users can perform a number of virtual machine operations (such as starting or stopping) as needed, most configuration changes require that the BUIT administrator submit a change request. The DC administrator reviews this request, and can approve or reject it. The DC administrator can then provision any approved changes, and the self-service portal tracks the changes made.

More Information

Microsoft Private Cloud

Microsoft System Center Virtual Machine Manager Self-Service Portal 2.0 Release Candidate

Fawzi — Fri, 16 Jul 2010 12:47:00 GMT

The Journey to the Private Cloud

Today customers can begin their journey to the private cloud by deploying the Microsoft products and technologies they know and trust. The flexible and familiar platform and tools you use today will become the foundation for your private cloud. Going forward, Microsoft will deliver richer private cloud capabilities for your use in subsequent releases of Windows Server and System Center.

Evolving Your Datacenters to Derive Cloud Benefits Today

Microsoft is enabling customers to build the foundation for private cloud infrastructure using Windows Server/Hyper-V and the System Center family of products with the System Center Virtual Machine Manager Self-Service Portal 2.0 (previously known as the Dynamic Datacenter Toolkit). Click here to download the release candidate.

The System Center Virtual Machine Manager Self-Service Portal 2.0 is a free, partner-extensible toolkit that will enable datacenters to dynamically pool, allocate, and manage virtualized resources to enable Infrastructure-as-a-Service. This solution will deliver:

Tested guidance and best practices to help configure and deploy private cloud infrastructures.
Automated web portals and infrastructure provisioning engine that’s integrated with System Center.
Guidance to help partners easily extend functionality.

Overview

VMMSSP (also referred to as the self-service portal) is a fully supported, partner-extensible solution built on top of Windows Server 2008 R2, Hyper-V, and System Center VMM. You can use it to pool, allocate, and manage resources to offer infrastructure as a service and to deliver the foundation for a private cloud platform inside your datacenter. VMMSSP includes a pre-built web-based user interface that has sections for both the datacenter managers and the business unit IT consumers, with role-based access control. VMMSSP also includes a dynamic provisioning engine. VMMSSP reduces the time needed to provision infrastructures and their components by offering business unit “on-boarding,” infrastructure request and change management. The VMMSSP package also includes detailed guidance on how to implement VMMSSP inside your environment.

Important: VMMSSP is not an upgrade to the existing VMM 2008 R2 self-service portal. You can choose to deploy and use one or both self-service portals depending on your requirements.

The self-service portal provides the following features that are exposed through a web-based user interface:

Configuration and allocation of datacenter resources: Store management and configuration information related to compute, network and storage resources as assets in the VMMSSP database.
Customization of virtual machine actions: Provide a simple web-based interface to extend the default virtual machine actions; for example, you can add scripts that interact with Storage Area Networks for rapid deployment of virtual machines.
Business unit on-boarding: Standardized forms and a simple workflow for registering and approving or rejecting business units to enroll in the portal.
Infrastructure request and change management: Standardized forms and human-driven workflow that results in reducing the time needed to provision infrastructures in your environment.
Self-Service provisioning: Supports bulk creation of virtual machines on provisioned infrastructure through the web-based interface.Helps business units to manage their virtual machines based on delegated roles.

Citrix Branch Repeater VPX Going Hyper-V

Fawzi — Fri, 09 Jul 2010 17:33:00 GMT

06 Jun 2010 10:28 PM EDT

Today we are excited to unveil a tech preview of our upcoming Branch Repeater VPX for Hyper-V at Microsoft TechEd in New Orleans. This tech preview makes Citrix the first and only WAN Optimization vendor[1] as well as the first and only Microsoft Networking Alliance partner to announce a virtual WAN Optimization appliance for Microsoft Hyper-V.

IT is increasingly moving toward a virtualized world – from virtualizing servers and storage in the datacenter to desktops in offices and now to the new frontiers – branch offices and networks. As virtualization enters a hyper growth phase and our customers establish virtualization on these new frontiers, we remain committed to supporting Branch Repeater VPX on all the leading type-1 hypervisors – Citrix XenServer, Microsoft Hyper-V and VMware ESX.

The tech preview of Branch Repeater VPX for Hyper-V comes less than 100 days after we introduced Branch Repeater VPX for XenServer. Organizations have a variety of branch offices. Some are suited for the plug-n-play of consolidated ‘Windows + WAN optimization’ hardware appliances from a single vendor. Others are equipped for and require the flexibility of virtual appliances to support broader applications and non-Windows systems in the branch. While VMware ESX has been prevalent in customers’ datacenters, Microsoft infrastructure is more prevalent in their branch offices.

Branch Repeater 5.7 (supports Microsoft Windows Server 2008 R2) and this tech preview enable customers address such a mix of branch offices, delivering a high-definition HDX experience, enabling server consolidation and server centralization.

If you are interested, we will directly help you acquire the tech preview and documentation. Please contact your Citrix representative or drop me a note.

If you are in the wonderful city of New Orleans for Microsoft Tech Ed this week, please drop by our Citrix booth for a special preview of Branch Repeater VPX for Hyper-V.

Sai Allavarpu

¹ Vendors as shown in the 2009 Gartner Magic Quadrant for WAN Optimization Controllers

Recent Highlights;

VMM tricks: Adding VMware Host error “Unable to connect to the remote server.”

Fawzi — Fri, 09 Jul 2010 17:30:00 GMT

Sometimes when you try to add VMware host ( VCenter) you see this error

“VMM cannot complete the VMware operation on VMware Host IP server because of the error:
Unable to connect to the remote server.Resolve the issue in VMware and then try the operation again.
ID 12701:Details: Unknown error (0×194) “

VMM is using different protocols to manage VMware host and communicate with as per MS http://technet.microsoft.com/en-us/library/cc764268.aspx

Connection type	Protocol	Default port	Where to change the port setting
VMware Web Services communication	HTTPS	443	VMM Administrator Console, registry
SFTP file transfer from VMWare ESX Server 3.0 and VMware ESX Server 3.5 hosts	SFTP	22	Registry
SFTP file transfer from VMM server to VMWare ESX Server 3i hosts	HTTPS	443	Registry

To manage VMware Virtualcenter server, VMM need dispatch VMMagent to this server which will involve some sFTP and HTTPS communication and traffic. It appears there are some failures during the process.

so check if you are able to connect to VMware Virtual center on ports 22,443 and then try again.

VMM tricks: How to forcefully remove a Virtual Machine from the SCVMM admin console

Fawzi — Thu, 01 Jul 2010 17:13:00 GMT

Source

My buddy Jonathan Jordan recently came across an interesting issue and wrote up a great solution, and since he’s out today I thought I’d take the liberty of posting it. If you ever find yourself in a position where you tried to remove a VM but it ended up being stuck in a state of limbo then this one’s for you:

========

Issue: A VM has been removed from SCVMM but still appears in the VMM Admin Console. The VM may have been removed in Hyper-V, SCVMM, or Cluster Administrator. When the VM is right clicked on there are two choices: Repair and Delete. Neither work.

Environment:
Windows 2003 with SCVMM 2007
Windows 2008 with SCVMM 2008

Resolution: If after attempting to remove the VM through normal means the machine name is still present, perform these steps:

> Method 1: Locate the .XML file for the machine and delete it.
- On the host that the VM ran on (or hosts if you are unsure which one), at a command prompt:
Type the drive letter to change to such as C: and hit enter, then…
dir *.xml /s | find /i “vm name”
- Replacing “vm name” with the name of the VM, this will search a volume for the .XML file that describes the VM
- Move the .XML file to a location that SCVMM does not use for hosted VMs or Library files
- Refresh SCVMM Admin Console

> Method 2: Force removal of VM with PowerShell. If Method 1 did not work, follow the steps below then refresh the SCVMM Admin Console:

- In the SCVMM Admin Console click the ‘PowerShell’ button. Type ‘A’ for ‘Always’ if prompted by security
- Test PowerShell (this will just list information so that you will know that PowerShell is working properly):
Get-VMMServer -ComputerName localhost
- This should just list out some VMM info

- Remove VM: Replace “VM Name” with the name of the VM as it appears in SCVMM
$VM = Get-VM -Name “VM Name”
Remove-VM -VM $VM -Force

Note: If the virtual machine still exists as an .XML file as mentioned in Method 1, refresher will repopulate the VM as being present

VMM tricks: How to manually remove a host from the VMM database

Fawzi — Thu, 01 Jul 2010 17:12:00 GMT

Source

The following steps outline the procedure to manually remove a host cluster from the VMM database. In this specific example, we are removing a two node cluster.

Note The GUIDs listed below are specific to this example. If following these instructions, you will need to determine this same information for your specific environment. This information can be found in the tbl_ADHC_Host.

The following steps outline the manual process of removing all references to the existing host from the VMM database. This should only be used as a last resort option after all other means have been exhausted.

First, stop the VMMservice.
Then, take a backup of the existing DB using SQL Management studio. (Right click on DB name, choose tasks, click on Back up, chose a full backup).
Now, right click on table tbl_ADHC_Host and select view or open rows.
Click on the SQL button from the tool bar to get the SQL query for the view.
In there, start pasting the commands below one by one and verifying they executed correctly. (To execute, you can highlight the command and press F5 or press the “!” symbol).

DELETE FROM tbl_ADHC_HostNetworkAdapter WHERE (HostID = ’85099616-fdc8-4f85-a702-979a4251f050′)
DELETE FROM tbl_ADHC_HostNetworkAdapter WHERE HostID=’8cfff5ad-0990-4a92-bd6d-4d24190e5d5a ‘
DELETE FROM tbl_ADHC_VirtualNetwork WHERE (HostID = ’85099616-fdc8-4f85-a702-979a4251f050′)
DELETE FROM tbl_ADHC_VirtualNetwork WHERE (HostID = ’8cfff5ad-0990-4a92-bd6d-4d24190e5d5a ‘)
DELETE FROM tbl_ADHC_HostVolume WHERE (HostID = ’85099616-fdc8-4f85-a702-979a4251f050′) OR (HostID = ’8cfff5ad-0990-4a92-bd6d-4d24190e5d5a ‘)
DELETE FROM tbl_ADHC_HostDisk WHERE (HostID = ’85099616-fdc8-4f85-a702-979a4251f050′) OR (HostID = ’8cfff5ad-0990-4a92-bd6d-4d24190e5d5a ‘)
DELETE FROM tbl_WLC_PhysicalObject WHERE (HostId = ’85099616-fdc8-4f85-a702-979a4251f050′) OR (HostId = ’8cfff5ad-0990-4a92-bd6d-4d24190e5d5a ‘)
DELETE FROM tbl_WLC_VObject WHERE (HostId = ’85099616-fdc8-4f85-a702-979a4251f050′) OR (HostId = ’8cfff5ad-0990-4a92-bd6d-4d24190e5d5a ‘)
DELETE FROM tbl_ADHC_Host WHERE (HostID = ’85099616-fdc8-4f85-a702-979a4251f050′) OR (HostID = ’8cfff5ad-0990-4a92-bd6d-4d24190e5d5a ‘)
DELETE FROM tbl_ADHC_ClusterDisk WHERE (ClusterID = ’1148853c-cde3-45d2-82ee-bb04259d6a79′)
DELETE FROM tbl_ADHC_HostCluster WHERE (ClusterID = ’1148853c-cde3-45d2-82ee-bb04259d6a79′)
DELETE FROM tbl_ADHC_AgentServerRelation WHERE (AgentServerID = ’648e977e-d10e-40b6-aca2-d9d2dc63b790′)
DELETE FROM tbl_ADHC_AgentServer WHERE (ComputerName = ‘Server_Node1′)
DELETE FROM tbl_ADHC_AgentServer WHERE (ComputerName = ‘Server_Node2′)

6. Now start the vmmservice and open the VMM console.