Administrators cannot modify core VMM settings nor add or remove members of
the Administrator’s user role.
Read-Only Administrator Can view all properties, status, and job objects within
their assigned host groups, clouds, and library servers but cannot modify objects.
Can also view Run As accounts that have been assigned to the role.
Tenant Administrator Can manage self-service users and VM networks for their
delegated clouds. Tenant Administrators can also create and manage their own
VMs and services but cannot view other resources in the cloud not owned by them.
Application Administrator (Self-Service User) Can perform the actions
assigned to them on the assigned clouds. This commonly includes the ability to
create and control VMs and services.By installing the SCVMM 2016 console on machines, you can remotely manage
SCVMM and avoid having to log on to the SCVMM server. I like to install all of the
various management consoles from Windows and System Center on a remote desktop
session host and then publish the administrator tools by using RDP. I can then get to
the admin tools from any device and operating system. I walk through the process in a
video at http://youtu.be/ _dkxyr03Er4.
Once you start using SCVMM for managing your Hyper-V environments, you should
not use Hyper-V Manager or the Failover Cluster Management tool for normal
virtualization resource management. If you do make changes using Hyper-V Manager
directly, SCVMM may not be aware of the change and may need some time to detect it,
giving inconsistent views between Hyper-V Manager and SCVMM. For best results,
after SCVMM is implemented and managing virtualization resources, don’t use other
management tools to manage the same resources.
UNLOCKING ALL POSSIBILITIES WITH POWERSHELL
When you look at any resource on System Center 2012 and newer, or on Windows
Server 2012 and newer, one common theme is the prevalence of PowerShell.
Everything that is done in the System Center consoles is performed by an
underlying PowerShell cmdlet. As you make a selection in a console and click an
action, the console composes the correct PowerShell command and executes it
behind the scenes. There are many actions that you can take only with
PowerShell, and as you become more acquainted with System Center, you will
start to use PowerShell more and more. I'm not talking about manually running
actions, but when you consider that you can perform every management action
for the entire System Center 2012 and System Center 2016 product by using
PowerShell, the automation possibilities can truly be realized, and you will start
to automate more and more processes.
A great way to get started with PowerShell is to use the graphical interface to
perform an action, such as creating a new virtual machine. In the Summary stage