Skip to main content

Creating a Private Cloud in VMM Overview

A private cloud is a cloud that is provisioned and managed on-premise by an organization. The private cloud is deployed using an organization’s own hardware to leverage the advantages of the private cloud model. Through VMM, an organization can manage the private cloud definition, access to the private cloud, and the underlying physical resources.

In VMM, a private cloud provides the following benefits:
Self service. Administrators can delegate management and usage of the private cloud while retaining the opaque usage model. Self-service users do not need to ask the private cloud provider for administrative changes beyond increasing capacity and quotas as their needs change.

Resource pooling. Through the private cloud, administrators can collect and present an aggregate set of resources, such as storage and networking resources. Resource usage is limited by the capacity of the private cloud and by user role quotas.

Opacity. Self-service users have no knowledge of the underlying physical resources.

Elasticity. Administrators can add resources to a private cloud to increase the capacity.

Optimization. Usage of the underlying resources is continually optimized without affecting the overall private cloud user experience.

You can create a private cloud from either of the following sources:
Host groups that contain resources from Hyper-V hosts, VMware ESX hosts and Citrix XenServer hosts

A VMware resource pool

During private cloud creation, you select the underlying fabric resources that will be available in the private cloud, configure library paths for private cloud users, and set the capacity for the private cloud. Therefore, before you create a private cloud, you should configure the fabric resources, such as storage, networking, library servers and shares, host groups, and hosts. For information about how to configure the fabric and add hosts to VMM management, see the following sections:

Example Scenario Overview

In the example scenarios, a private cloud that is named Finance is created from resources in configured host groups. A private cloud that is named Marketing is created from a VMware resource pool.
Private CloudResource
(Private cloud created from host groups)
Host groups: Seattle\Tier0_SEASeattle\Tier1_SEANew York\Tier0_NYNew York\Tier1_NY
Logical network: BACKEND
Load balancer:
VIP profile: Web tier (HTTPS traffic)
Storage classification: GOLD and SILVER
Read-only library shares: SEALibrary and NYLibrary
Stored virtual machine path: VMMServer01\Finance\StoredVMs
Capability profile: Hyper-V
(Private cloud created from a VMware resource pool)
VMware resource pool: Resource pool 1
Logical network: BACKEND
Load balancer:
VIP profile: Web tier (HTTPS traffic)
Read-only library shares: SEALibrary and NYLibrary
Stored virtual machine path: VMMServer01\Marketing\StoredVMs
Capability profile: ESX Server

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N