vSphere Agent Requirements
vSphere endpoint credentials, or the credentials under which the agent service runs, must have administrative access to the installation host. Multiple vSphere agents must meet vRealize Automation configuration requirements.
Credentials
When creating an endpoint representing the vCenter Server instance to be managed by a vSphere agent, the agent can use the credentials that the service is running under to interact with the vCenter Server or specify separate endpoint credentials.
The following table lists the permissions that the vSphere endpoint credentials must have to manage a vCenter Server instance. The permissions must be enabled for all clusters in vCenter Server, not just clusters that will host endpoints.
Attribute Value
|
Permission
| |
|---|---|---|
Datastore
|
Allocate Space
| |
Browse Datastore
| ||
Datastore Cluster
|
Configure a Datastore Cluster
| |
Folder
|
Create Folder
| |
Delete Folder
| ||
Global
|
Manage Custom Attributes
| |
Set Custom Attribute
| ||
Network
|
Assign Network
| |
Permissions
|
Modify Permission
| |
Resource
|
Assign VM to Res Pool
| |
Migrate Powered Off Virtual Machine
| ||
Migrate Powered On Virtual Machine
| ||
Virtual Machine
|
Inventory
|
Create from existing
|
Create New
| ||
Move
| ||
Remove
| ||
Interaction
|
Configure CD Media
| |
Console Interaction
| ||
Device Connection
| ||
Power Off
| ||
Power On
| ||
Reset
| ||
Suspend
| ||
Tools Install
| ||
Configuration
|
Add Existing Disk
| |
Add New Disk
| ||
Add or Remove Device
| ||
Remove Disk
| ||
Advanced
| ||
Change CPU Count
| ||
Change Resource
| ||
Extend Virtual Disk
| ||
Disk Change Tracking
| ||
Memory
| ||
Modify Device Settings
| ||
Rename
| ||
Set Annotation (version 5.0 and later)
| ||
Settings
| ||
Swapfile Placement
| ||
Provisioning
|
Customize
| |
Clone Template
| ||
Clone Virtual Machine
| ||
Deploy Template
| ||
Read Customization Specs
| ||
State
|
Create Snapshot
| |
Remove Snapshot
| ||
Revert to Snapshot
| ||
Disable or reconfigure any third-party software that might change the power state of virtual machines outside of vRealize Automation. Such changes can interfere with the management of the machine life cycle by vRealize Automation.
Hyper-V and Xen Server Agent Requirements
Hyper-V Hypervisor proxy agents require system administrator credentials for installation.
The credentials under which to run the agent service must have administrative access to the installation host.
Administrator-level credentials are required for all XenServer or Hyper-V instances on the hosts to be managed by the agent.
If you are using Xen pools, all nodes within the Xen pool must be identified by their fully qualified domain names.
Note:
By default, Hyper-V is not configured for remote management. A vRealize Automation Hyper-V proxy agent cannot communicate with a Hyper-V server unless remote management has been enabled.
See the Microsoft Windows Server documentation for information about how to configure Hyper-V for remote management.
VDI Agent for Xen Desktop Requirements
A system administrator installs a Virtual Desktop Infrastructure (VDI) agent to integrate XenDesktop servers into vRealize Automation.
You can install a general VDI agent to interact with multiple servers. If you are installing one dedicated agent per server for load balancing or authorization reasons, you must provide the name of the XenDesktop DDC server when installing the agent. A dedicated agent can handle only registration requests directed to the server specified in its configuration.
Consult the vRealize Automation Support Matrix on the VMware Web site for information about supported versions of XenDesktop for XenDesktop DDC servers.
Installation Host and Credentials
The credentials under which the agent runs must have administrative access to all XenDesktop DDC servers with which it interacts.
XenDesktop Requirements
The name given to the XenServer Host on your XenDesktop server must match the UUID of the Xen Pool in XenCenter. See Set the XenServer Host Name for more information.
Each XenDesktop DDC server with which you intend to register machines must be configured in the following way:
- The group/catalog type must be set to Existing for use with vRealize Automation.
- The name of a vCenter Server host on a DDC server must match the name of thevCenter Server instance as entered in the vRealize Automation vSphere endpoint, without the domain. The endpoint must be configured with a fully qualified domain name (FQDN), and not with an IP address. For example, if the address in the endpoint is https://virtual-center27.domain/sdk, the name of the host on the DDC server must be set to virtual-center27.If your vRealize Automation vSphere endpoint has been configured with an IP address, you must change it to use an FQDN. See IaaS Configuration for more information about setting up endpoints.
XenDesktop Agent Host requirements
Citrix XenDesktop SDK must be installed. The SDK for XenDesktop is included on the XenDesktop installation disc.
Verify that Microsoft PowerShell is installed on the installation host before agent installation. The version required depends on the operating system of the installation host. See Microsoft Help and Support.
MS PowerShell Execution Policy is set to RemoteSigned or Unrestricted. See Set the PowerShell Execution Policy to RemoteSigned.
For more information about PowerShell Execution Policy, run
help about_signing or help Set-ExecutionPolicy at the PowerShell command prompt.
EPI Agent for Citrix Requirements
A system administrator uses External Provisioning Infrastructure (EPI) agents to integrate Citrix provisioning servers and to enable the use of Visual Basic scripts in the provisioning process.
Installation Location and Credentials
Install the agent on the PVS host for Citrix Provisioning Services instances. Verify that the installation host meets Citrix Agent Host Requirements before you install the agent.
Although an EPI agent can generally interact with multiple servers, Citrix Provisioning Server requires a dedicated EPI agent. You must install one EPI agent for each Citrix Provisioning Server instance, providing the name of the server hosting it. The credentials under which the agent runs must have administrative access to the Citrix Provisioning Server instance.
Consult the vRealize Automation Support Matrix for information about supported versions of Citrix PVS.
Citrix Agent Host Requirements
PowerShell and Citrix Provisioning Services SDK must be installed on the installation host prior to agent installation. Consult the vRealize Automation Support Matrix on the VMware Web site for details.
Verify that Microsoft PowerShell is installed on the installation host before agent installation. The version required depends on the operating system of the installation host. See Microsoft Help and Support.
You must also ensure that the PowerShell Snap-In is installed. For more information, see the Citrix Provisioning Services PowerShell Programmer's Guide on the Citrix Web site.
MS PowerShell Execution Policy is set to RemoteSigned or Unrestricted. See Set the PowerShell Execution Policy to RemoteSigned.
For more information about PowerShell Execution Policy, run
help about_signing or help Set-ExecutionPolicy at the PowerShell command prompt.
EPI Agent for Visual Basic Requirements
A system administrator installs External Provisioning Infrastructure (EPI) agents to enable the use of Visual Basic scripts in the provisioning process.
The following table describes the requirements that apply to installing an EPI agent to enable the use of Visual Basic scripts in the provisioning process.
Requirement
|
Description
|
|---|---|
Credentials
|
Credentials under which the agent will run must have administrative access to the installation host.
|
Microsoft PowerShell
|
Microsoft PowerShell must be installed on the installation host prior to agent installation: The version required depends on the operating system of the installation host and might have been installed with that operating system. Visit http://support.microsoft.com for more information.
|
MS PowerShell Execution Policy
|
MS PowerShell Execution Policy must be set to RemoteSigned or Unrestricted.
For information on PowerShell Execution Policy issue one of the following commands at Power-Shell command prompt:
help about_signing help Set-ExecutionPolicy |
WMI Agent Requirements
To use WMI agents, remote WMI requests must be enabled on the managed Windows servers.
No comments:
Post a Comment