What's New in System Center 2012 - Virtual Machine Manager
Updated: September 8, 2011
Applies To: System Center 2012 - Virtual Machine Manager Release Candidate
The following is a list of some of the new tasks that you can perform in System Center 2012 – Virtual Machine Manager (VMM). For an overview of VMM, see Overview of System Center 2012 - Virtual Machine Manager.
Deploying VMM
| Task | For more information |
|---|---|
Install a highly available VMM management server |
Configuring Security in VMM
| Task | For more information |
|---|---|
Create Run As accounts to provide the necessary credentials for performing operations in VMM | |
Use the new capabilities available to the Delegated Administrator and Self-Service User user roles to give users the ability to perform tasks that are new to VMM | |
Create a Read-Only Administrator user role |
Configuring Fabric Resources in VMM
| Task | For more information |
|---|---|
Discover physical computers on the network (for example, bare-metal computers), automatically install the Windows Server 2008 R2 operating system, and convert the computers into managed Hyper-V hosts | |
Use the VMM console to create a Hyper-V cluster from two or more stand-alone Hyper-V hosts that are managed by VMM | |
Use Citrix XenServer as a virtual machine host | |
Use the VMM console to configure networking resources (for example, logical networks, IP address pools, and load balancers) to be used to deploy virtual machines and services | |
Use the VMM console to configure the storage resources (for example, storage classifications, logical units, and storage pools) to be used by Hyper-V hosts and host clusters | |
Scan servers (for example, Hyper-V hosts and library servers) for update compliance based on an update baseline, view update compliance status, and perform update remediation by using a Windows Server Update Services (WSUS) server | |
Perform resource balancing by migrating virtual machines within host clusters that support live migration (Dynamic Optimization) | Configuring Dynamic Optimization and Power Optimization in VMM |
Turn off hosts that are not needed to meet resource requirements within a host cluster and then turn the hosts back on when they are needed again (Power Optimization) | Configuring Dynamic Optimization and Power Optimization in VMM |
Deploying Virtual Machines and Services in a Private Cloud in VMM
| Task | For more information |
|---|---|
Create a private cloud by combining hosts and networking, storage, and library resources together | |
Use Server Application Virtualization (Server App-V) to sequence applications to be deployed by VMM | |
Create a custom capability profile to limit the resources that are used by virtual machines that are created in a private cloud | |
Create an application profile that provides instructions for installing Microsoft Server App-V applications, Microsoft Web Deploy applications, and Microsoft SQL Server data-tier applications (DACs), as well as for running scripts when deploying a virtual machine as part of a service | |
Create a SQL Server profile that provides instructions for customizing an instance of Microsoft SQL Server for a SQL Server DAC application when deploying a virtual machine as part of a service | |
Deploy virtual machines to private clouds by using virtual machine templates | |
Use the Service Template Designer to create service templates that can be used to deploy services | |
Deploy services to private clouds or hosts by using a service template | |
Scale out a service (add additional virtual machines to a deployed service) | |
Update a service (make changes to a deployed service) | |
Export and import service templates (and virtual machine templates) |
Additional information
The following are some other differences in System Center 2012 – Virtual Machine Manager that you might need to consider:
-
Self-service users can now use the VMM console instead of the VMM Self-Service Portal to perform tasks, such as deploying virtual machines and services.
-
SQL Server Express is no longer supported for the VMM database.
-
Virtual machine hosts that are running Microsoft Virtual Server 2005 R2 are no longer supported.
-
Virtual machine hosts that are running VMware ESX 3.0 or ESXi 3.0 are no longer supported.
