Specifications
VMware, Inc. 265
Chapter 17 Managing Users, Groups, Permissions, and Roles
Example3:Addingavirtualmachine
Role3canaddvirtualmachines.
Role4isreadonly.
GroupCisgrantedRole3onHost1.
GroupCisalsograntedRole4ontheparentfolderordatacenterforHost1’s
associateddatastoresandnetworks.
Theseobjectsinherittheirpermissionsfromtheirparentfolderordatacenter.
SettingbothpermissionsallowsGroupCuserstoaddavirtualmachinetothe
host.
Example4:Delegatingresources
UsingdefaultrolesforResourcePoolAdministrator,VirtualMachineUser,
andReadOnly
GrantUser1theroleofResourcePoolAdministratoronResourcePoolA.
GrantUser1theroleofVirtualMachineUseronallthevirtualmachinesin
ResourcePoolA.
GrantUser1therole,ReadOnlyonthefolderordatacentercontainingthe
datastoresandnetworksassociatedwithResourcePoolA.
Becauseresourcepoolsaffectmultipleinventoryobjectsyoumustassignvarious
privilegesonselectedobjectstoeffectivelyperformtasks(inthiscase,delegating
resourceswithinaresourcepoolontothe
virtualmachinesinthatresourcepool).
Users
AuserisanindividualauthorizedtologintoanESXServerhostortoVirtualCenter.
Usersonahostfallintotwocategories:thosewhocanaccesstheESXServerhost
throughVirtualCenterandthosewhocanaccessthehostbydirectlyloggingintothe
hostfromVI
Client,VIWebAccess,athird‐partyclient,oracommandshell.Thesetwo
categoriesdrawusersfromdifferentsources:
VirtualCenterusers–AuthorizedusersforVirtualCenterarethoseincludedinthe
WindowsdomainlistreferencedbyVirtualCenterorlocalWindowsusersonthe
VirtualCenterhost.
YoucannotuseVirtualCentertomanuallycreate,remove,orotherwisechange
users.Ifyouneedtomanipulatetheuserlistorchangeuserpasswords,you
must
dosothroughthetoolsyounormallyusetomanageyourWindowsdomain.