Hi all, this is Vladimir from the VMM team and today I want to very quickly show how easy it is create and configure a private cloud in System Center 2012 Virtual Machine Manager (VMM 2012) and enable users to access already existing virtual machines.
First of all, you will need to configure your backend infrastructure such as storage, networks, Hyper-V/ESX/Xen hosts, etc. Once all that is done, you are ready to create a private cloud. Here are the general steps:
1. Create a private cloud by clicking on the “Create Cloud” button under the VMs and Service tab.
2. While creating the cloud, assign a host group to the cloud and configure it as appropriate for your environment.
3. Once the cloud is created, assign one or more VMs to the cloud. You can do this by going into the VM’s properties and changing the ‘Cloud’ setting under the general tab as you can see below.
4. Next, create a Self-Service User role by clicking on the ‘Create User Role’ button under the Settings->Security->User Roles. When creating the user role, ensure the following:
a. Ensure that you assign the cloud created in step 1 to this user role’s scope:
b. Under the resources tab, add to the list the VMs that you want this user role to have access to. In the example below, I want the members of this user role to only have access to one VM.
After the Self-Service User role is created, the members of this user role should be able to access the VM through VMM console, VMM Self-Service portal, or AppController.
I hope that reading this post was of use for you. See you soon!
Vladimir Petrosyan | Support Engineer | Management and Security Division
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Definitely Picture worth 1000 words
I have a question about the point 2 of this article where you state that while creating the cloud, I can assign VMs to the cloud. My question is, what happens to the VM that is currently in the HOST and when the move to the cloud, it disappears from the HOST? important because it would be no longer in the host, but only in the cloud, or not knowing where the VM host is, but that was part of the cloud.
I'd appreciate if you explain this point, I'm about to implement a private cloud with SCVMM 2012, but now I have 4 hosts, where I have 4 VMs on each host, and I want to include another server where I have installed SCVMM 2012, add these 4 hosts to the cloud and I want my VMs are not in the HOST but now in the cloud.
The VM will not be removed from the host. It will be still running on the host, but now your Self-Service Users will be able to access it through the private cloud.