251
edits
Changes
m
Text replacement - "<google>BUY_VMM_BOTTOM</google>" to "<htmlet>vmm</htmlet>"
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[Converting VMware Virtual Machines to Hyper-V using VMM 2008 V2V|Previous]]<td align="center">[[VMM 2008 Essentials|Table of Contents]]<td width="20%" align="right">[[Deploying a VMM 2008 Self-Service Portal|Next]]</td>
<tr>
<td width="20%">Converting VMware Virtual Machines to Hyper-V using VMM 2008 V2V<td align="center"><td width="20%" align="right">Deploying a VMM 2008 Self-Service Portal</td>
</table>
<hr>
<htmlet>vmm</htmlet>
Microsoft's Virtual Machine Manager (VMM 2008) provides considerable power of control over distributed virtualization environments. With great power, as the saying goes, comes great responsibility. A VMM user with full administrative privileges can create, configure and destroy virtual machines and any associated storage at will with a few mouse clicks. Given unrestrained access to the VMM environment to the wrong person would be nothing short of a disaster.
It should come as no surprise, therefore, that VMM 2008 provides the ability to control which users have access to the management environment, and what they can do once they have gained that access. This is performed using a concept known as ''User Roles''. Roles define what actions can be performed within the VMM 2008 environment. Users are then assigned as members of a role and thereby limited to the actions permitted by that role.
== Types of VMM 2008 User Roles ==
Once the required configuration settings have been made, click ''OK'' to commit the changes.
<htmlet>vmm</htmlet>
