Things that you can not do with SCVMM but Hyper-V console

[guest]

In our company we are testing Hyper-V and in not much time we will be using it in prodcution. Currently we have a virtualization team and a windows team. Who is going to be responsible of it not decided yet but we are thinking windows team to manage hyper-v hosts and cluster and virtualization team to manage SCVMM.



I wonder what they might miss if they only use SCVMM, i have been told that some jobs can not be done from SCVMM, so what are they?



I have searched but couldnt found any info.

[guest]

Ok.. these are the things that you will miss.. hope that I did not forget any thing



· - Quick storage migration: This enables migration of a VM's storage both within the same host and across hosts while the VM is running, with minimal downtime.

· - Live migration queuing: This lets you perform multiple live migrations without needing to keep track of other live migrations within the cluster.

· - Physical to virtual (P2V) conversion: The enhancements in R2 let you do the P2V conversion through a simple wizard, which uses an agent that gets pushed out to the physical machine to perform the conversion.

· - Other great features include Maintenance Mode, which automates the process of migrating VMs to other hosts for maintenance or upgrades, the improved SAN management, and increased third-party support.

· -You should also note that that you can use VMM to manage more than just your Hyper-V environment. You can also manage ESX hosts through VMware vCenter Server (VMM can manage multiple vCenter Servers). But it cannot manage Citrix Xen Server, although that capability may be coming soon.

· -Integration with SCOM to provide performance resource optimization, by using Performance and Resource Optimization (PRO) in System Center Virtual Machine Manager (VMM) 2008, VMM customers can tie specific System Center Operations Manager alerts to remediation actions in VMM. For example, PRO can load-balance virtual machines between physical hosts when specific thresholds are exceeded, or it can migrate virtual machines to a host on a different physical computer after a hardware failure.

· - Delegated Administration with User Roles, In VMM 2008, administrators control access to hosts through user roles. There are three user roles in VMM 2008: Administrator, Delegated Administrator, and Self-Service. The Administrator user role grants users administrative rights across the entire environment. The Delegated Administrator user role grants users administrative permissions within a scoped environment. The Self-Service user role determines what actions users can take on their own virtual machines using a Web interface: the Virtual Machine Manager Self-Service Portal. The Self-Service user role may be assigned a quota to limit the number of virtual machines the user can create.

· - Support for Self Service Portal which give the end users the ability to create and manage Vms using VMM SSP (web site)

[guest]

I did double check with My Hyper-V server and here what I found.

- Import and Export should be done using Hyper-V Server console

- Hyper-V Server Configuration ( Keyboard, mouse release key, User credential)

[guest]

SCVMM focuses on managing the VMs ands adds provisioning and the Library concept and the migration features (that are not "Live Migration").

The Hyper-V Managment Console focuses on manging the hypervisor and the hardware.

SCVMM does handle those hypervisor configuraiton actions that relate directly to VMs (such as virtual networks).

Does SCVMM requre SCOM or any more - no it is does not - those are optional integration points.


--------------------------------------------------------------------------------