VMware vRealize Operations for Published Applications - 6.4 Installation Manual
VMware vRealize Operations for
Published Applications Installation and
Administration
VMware vRealize Operations for Published Applications 6.4
VMware vRealize Operations for Published Applications Installation and Administration
You can find the most up-to-date technical documentation on the VMware Web site at:
hps://docs.vmware.com/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2017 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
VMware vRealize Operations for Published Applications Installation and
1
Administration 5
Introducing vRealize Operations for Published Applications 7
2
vRealize Operations for Published Applications Architecture 8
vRealize Operations for Published Applications Desktop Agent 9
vRealize Operations for Published Applications Broker Agent 9
vRealize Operations for Published Applications Adapter 9
System Requirements for vRealize Operations for Published Applications 11
3
Product Compatibility for vRealize Operations for Published Applications 11
Software Requirements for vRealize Operations for Published Applications 11
Installing and Conguring vRealize Operations for Published Applications 13
4
Install and Congure vRealize Operations for Published Applications 13
Enable PowerShell Remoting on the Server 27
5
Enabling HTTP or HTTPS Protocols for PowerShell Remoting 29
6
Enable HTTP Protocol for PowerShell Remoting 29
Enable HTTPS Protocol for PowerShell Remoting 30
Congure a Firewall 33
Update the etc/host le for DNS Resolution 33
Install the Certicate on the Client 33
Test the Connection from the Client Machine 34
Use makecert for SSL Certication 34
VMware, Inc.
Monitoring Your Citrix XenDesktop and Citrix XenApp Environments 35
7
Using the XD-XA Dashboards 35
Using the XD-XA Reports 43
Using the vRealize Operations for Published Applications Alerts 45
Managing RMI Communication in
8
vRealize Operations for Published Applications 47
RMI Services 47
Default Ports for RMI Services 48
Changing the Default RMI Service Ports 48
3
VMware vRealize Operations for Published Applications Installation and Administration
Changing the Default TLS Conguration in
9
vRealize Operations for Published Applications 51
Default TLS Protocols and Ciphers for vRealize Operations for Published Applications 51
TLS Conguration Properties 52
Change the Default TLS Conguration for Servers 52
Change the Default TLS for Agents 52
Managing Authentication in vRealize Operations for Published Applications 55
10
Understanding Authentication for Each Component 55
Certicate and Trust Store Files 57
11
vRealize Operations for Published Applications Adapter Certicate and Trust Store Files 57
Broker Agent Certicate and Trust Store Files 58
Replacing the Default Certicates 59
12
Replace the Default Certicate for the vRealize Operations for Published Applications Adapter 59
Replace the Default Certicate for the Broker Agent 61
Certicate Pairing 63
13
SSL/TLS and Authentication-Related Log Messages 65
14
Upgrade vRealize Operations for Published Applications 67
15
Upgrade Broker Agent 68
Upgrade Desktop Agent 69
Create a vRealize Operations Manager Support Bundle 71
16
Download vRealize Operations for Published Applications Broker Agent Log
17
Files 73
Download vRealize Operations for Published Applications Desktop Agent Log
18
Files 75
View Collector and vRealize Operations for Published Applications Adapter
19
Log Files 77
Modify the Logging Level for vRealize Operations for Published Applications
20
Adapter Log Files 79
Index 81
4 VMware, Inc.
VMware vRealize Operations for
Published Applications Installation
and Administration 1
VMware vRealize Operations for Published Applications Installation and Administration provides information about how to monitor the performance of your Citrix XenDesktop/Citrix XenApp 7.6, 7.7, 7.8, 7.9, and 7.11 environments in VMware vRealize™ Operations Manager™.
Intended Audience
This information is intended for users who monitor the performance of a Citrix XenDesktop/Citrix XenApp
7.6, 7.7, 7.8, 7.9, and 7.11 environments in VMware vRealize Operations Manager and administrators who
are responsible for maintaining and troubleshooting a Citrix XenDesktop/Citrix XenApp 7.6, 7.7, 7.8, 7.9,
and 7.11 environments.
VMware, Inc.
5
VMware vRealize Operations for Published Applications Installation and Administration
6 VMware, Inc.
Introducing
vRealize Operations for Published
Applications 2
vRealize Operations for Published Applications collects performance data from monitored software and
hardware objects in your XenDesktop/XenApp 7.8/7.9/7.11, and vCenter environments and provides
predictive analysis and real-time information about problems in your XD-XA infrastructure.
vRealize Operations for Published Applications presents data through alerts, on congurable dashboards,
and on predened pages in vRealize Operations Manager.
IT administrators can use vRealize Operations for Published Applications to quickly obtain an overview of
how the XenDesktop and XenApp environments are behaving and view important metrics associated with
that environment. Help desk specialists can view objects related to end user sessions, perform basic
troubleshooting, and resolve user problems.
This chapter includes the following topics:
“vRealize Operations for Published Applications Architecture,” on page 8
n
“vRealize Operations for Published Applications Desktop Agent,” on page 9
n
“vRealize Operations for Published Applications Broker Agent,” on page 9
n
“vRealize Operations for Published Applications Adapter,” on page 9
n
VMware, Inc.
7
vRealize Operations Manager
vApp deployment
VMware
adapter
Published Apps
adapter
vRealize Operations Manager
User Interface
Published Apps
dashboards
Resources, metrics, relationships,
KPIs, alerts, views and reports
Desktop metrics:
CPU, memory,disk,
ICA, Session information,
App Stack information
App Volumes
vCenter Server
vSphere metrics:
ESXi, VM,
datastore,
datacenter
XD-XA Licensing Server
Desktop agent
XD-XA Storefront Server
Desktop agent
XD-XA Desktop OS Machine
Desktop agent
XD-XA Session-host Server
Desktop agent
Powershell script
Monitor Service API
App Volumes API
WMI
XD-XA Controller Server
Broker agent Desktop agent
Broker Data:
Environment Topology
Health Monitoring
VMware vRealize Operations for Published Applications Installation and Administration
vRealize Operations for Published Applications Architecture
The vRealize Operations for Published Applications components include the XD-XA adapter, broker agent,
and desktop agents.
VMware vRealize Operations for Published Applications Architecture
8 VMware, Inc.
Chapter 2 Introducing vRealize Operations for Published Applications
vRealize Operations for Published Applications Desktop Agent
The vRealize Operations for Published Applications desktop agent runs as a service on the XenDesktop
Delivery Controller on each License server, RDS host, Store Front server, and on all VDI machines.
The desktop agent monitors Citrix ICA sessions and HDX sessions and applications launched in the Citrix
ICA and HDX sessions by using standard functions and APIs of Windows OS. The desktop agent
periodically collects the Citrix ICA sessions' data on properties and performance, and sends the data to the
adapter using a secure connection.
vRealize Operations for Published Applications Broker Agent
The vRealize Operations for Published Applications broker agent runs on an active delivery controller, and
collects and sends information to the XD-XA adapter.
When you congure a broker agent, you pair the broker agent with a XD-XA adapter instance.
vRealize Operations for Published Applications Adapter
The vRealize Operations for Published Applications adapter collects Citrix XenDesktop inventory
information from the broker agent and collects metrics and performance data from desktop agents. The
vRealize Operations for Published Applications adapter sends that information to
vRealize Operations Manager. The information is displayed in pre-congured XenDesktop dashboards in
the vRealize Operations Manager user interface.
The vRealize Operations for Published Applications adapter runs on a cluster node or remote collector node
in vRealize Operations Manager. You can create a single vRealize Operations for Published Applications
adapter instance to monitor multiple XenDesktop 7.6/7.7/7.8/7.9/7.11 sites. During broker agent
conguration, you pair the broker agent with a vRealize Operations for Published Applications adapter
instance.
If you are monitoring multiple XenDesktop sites, you can pair the broker agent installed in each site with the
same vRealize Operations for Published Applications adapter instance as long as the total number of objects
that the vRealize Operations for Published Applications adapter instance handles does not exceed 10,000.
You can create more vRealize Operations for Published Applications adapter instances on dierent remote
nodes to support large scale environments.
I Creating more than one vRealize Operations for Published Applications adapter instance for
each cluster node or remote collector is not supported. Also, creating more than one
vRealize Operations for Published Applications adapter instance for each site is not supported. vRealize
Operations for Published Applications 7.6/7.7/7.8/7.9/7.11 adapter cannot monitor the XenApp 6.5
environments.
VMware, Inc. 9
VMware vRealize Operations for Published Applications Installation and Administration
If your vRealize Operations for Published Applications environment resembles one of the following
congurations, VMware recommends that you create the vRealize Operations for Published Applications
adapter instance on a remote collector node.
XenDesktop
deployments with
multiple sites
Remote datacenters
To improve scalability, create the
vRealize Operations for Published Applications adapter instance on a remote
collector node to ooad processing from the vRealize Operations Manager
cluster data nodes.
To minimize network trac across WAN or other slow connections, install a
remote collector node with a separate
vRealize Operations for Published Applications adapter instance in remote
datacenters. Pair each vRealize Operations for Published Applications
adapter instance with the broker agent that is located in the same remote
datacenter.
10 VMware, Inc.
System Requirements for
vRealize Operations for Published
Applications 3
vRealize Operations for Published Applications has specic system requirements. Verify that your
environment meets these system requirements before you install
vRealize Operations for Published Applications.
This chapter includes the following topics:
“Product Compatibility for vRealize Operations for Published Applications,” on page 11
n
“Software Requirements for vRealize Operations for Published Applications,” on page 11
n
Product Compatibility for vRealize Operations for Published Applications
vRealize Operations for Published Applications is compatible with the following products.
vCenter Server 5.5 and 6.0
n
App Volumes 2.11 and 2.12 (App Volumes 3.x not supported for
n
vRealize Operations for Published Applications 6.4)
vRealize Operations Manager 6.2, 6.2.1, 6.3, and 6.4
n
Citrix XenDesktop/XenApp 7.6/7.7/7.8/7.9/7.11 running on Windows Server 2008R2 (SP1) and Windows
n
Server 2012.
N Refer to vRealize Operations for Published Application 6.1 for support of Citrix XenApp 6.5.
Software Requirements for vRealize Operations for Published Applications
Each component of vRealize Operations for Published Applications has requirements for the software on the
system where it is installed.
vRealize Operations for Published Applications Desktop Agent Software
Requirements
You install the vRealize Operations for Published Applications desktop agent on Citrix Delivery Controllers,
Session RDS servers, Store Front server, License server, and the VDI machines.
vRealize Operations for Published Applications Broker Agent Software
Requirements
You install the vRealize Operations for Published Applications broker agent on an active delivery controller.
VMware, Inc.
11
VMware vRealize Operations for Published Applications Installation and Administration
The vRealize Operations for Published Applications broker agent has the following software requirements.
Verify that you enable PS remoting on the deliver controller by using Microsoft PowerShell before you
install the broker agent.
Windows Server 2008R2 SP1 or Windows Server 2012
n
Microsoft .Net Framework 4.5.1
n
vRealize Operations for Published Applications Adapter Software
Requirements
You install the vRealize Operations for Published Applications adapter on a vRealize Operations Manager
server that is running.
The vRealize Operations for Published Applications adapter has the following software requirements.
VMware vRealize Operations Manager 6.2, 6.2.1, 6.3, and 6.4
n
Setting Remote Signed Execution Policy
To set the remote signed execution policy, perform the following steps:
Set-ExecutionPolicy RemoteSigned
Enable-PSRemoting
Restart WinRM service
net stop winrm
net start winrm
Restart Broker-Agent service
12 VMware, Inc.
Installing and Configuring
vRealize Operations for Published
Applications 4
Installing vRealize Operations for Published Applications involves downloading the installation les from
the VMware product download page and installing and conguring software components on machines in
your vRealize Operations for Published Applications environment.
Install and Configure vRealize Operations for Published Applications
You install and congure vRealize Operations for Published Applications software components on machines
in your Citrix XenDesktop/XenApp 7.6/7.7/7.8/7.9/7.11 and vRealize Operations Manager environments.
Prerequisites
Verify that your environment meets product compatibility, hardware, and software requirements. See
n
Chapter 3, “System Requirements for vRealize Operations for Published Applications,” on page 11.
Verify that vRealize Operations Manager is deployed and running. If you need to upgrade
n
vRealize Operations Manager, perform the upgrade before you install
vRealize Operations for Published Applications.
Download the vRealize Operations for Published Applications installation les from the product
n
download page. See “Downloading the vRealize Operations for Published Applications Installation
Files,” on page 15.
Verify that you have a license key for the vRealize Operations for Published Applications solution.
n
Verify that you have a license key for vRealize Operations Manager.
n
The time on all the servers must be synced to a NTP server.
n
N Upgrading from vRealize Operations for Published Applications 6.1 to vRealize Operations for
Published Applications 6.4 is not supported.
N For vRealize Operations for Published Applications 6.1 and
vRealize Operations for Published Applications 6.4 to co-exist, they must be installed on dierent collector
nodes.
Procedure
1 Downloading the vRealize Operations for Published Applications Installation Files on page 15
Registered VMware users can download the vRealize Operations for Published Applications
installation les from the product download page.
2 Install the vRealize Operations for Published Applications Solution on page 15
You install the vRealize Operations for Published Applications solution from a PAK le in
vRealize Operations Manager.
VMware, Inc.
13
VMware vRealize Operations for Published Applications Installation and Administration
3 Open the Ports Used by vRealize Operations for Published Applications on page 16
After you install the vRealize Operations for Published Applications adapter, you disable the rewall
service, open the default ports, and restart the rewall.
4 Adding a vRealize Operations for Published Applications License Key on page 16
After you install the vRealize Operations for Published Applications solution, you must add a
vRealize Operations for Published Applications license key in the vRealize Operations Manager user
interface. vRealize Operations for Published Applications is not functional until it is licensed.
5 Associate XD-XA Objects with Your vRealize Operations for Published Applications License Key on
page 17
You must associate XD-XA objects with your vRealize Operations for Published Applications license
key by editing license groups in vRealize Operations Manager.
6 Create an Instance of the vRealize Operations for Published Applications 6.4 Adapter on page 18
After you install the vRealize Operations for Published Applications solution, you must create an
instance of the vRealize Operations for Published Applications adapter in
vRealize Operations Manager.
7 Enabling Firewall Rules for XenDesktop Delivery Controllers and PVS Server on page 19
Before you install the broker agent and desktop agent, you must enable specic rewall rules for the
XenDesktop Delivery Controller and PVS server.
8 Install the vRealize Operations for Published Applications Broker Agent on page 20
You install the vRealize Operations for Published Applications broker agent on an Active XenDesktop
Delivery Controller.
9 Congure the vRealize Operations for Published Applications Broker Agent on page 21
After you install the broker agent, you use the Broker Agent Conguration wizard to congure the
broker agent on the Citrix XenDesktop Delivery Controller where you installed the broker agent. You
can also use the Broker Agent Conguration wizard to make changes to your broker agent
conguration.
10 Congure Broker Agent to use Non-Admin User for Citrix Desktop Delivery Controller on page 23
You can congure broker agent to use non-admin user for Citrix Desktop Delivery Controller.
11 Install a vRealize Operations for Published Applications Desktop Agent on page 24
You install desktop agents on all Delivery Controllers, Store Front server, RDS host, License server,
and VDI machines.
12 Push the vRealize Operations for Published Applications Desktop Agent Pair Token Using a Group
Policy on page 24
To use vRealize Operations for Published Applications to monitor a XenDesktop Site, you must create
a Group Policy (GPO) to contain the vRealize Operations for Published Applications group policies.
You then apply the GPO to the remote desktops that you want to monitor.
14 VMware, Inc.
Chapter 4 Installing and Configuring vRealize Operations for Published Applications
Downloading the vRealize Operations for Published Applications Installation Files
Registered VMware users can download the vRealize Operations for Published Applications installation
les from the product download page.
Table 4‑1. vRealize Operations for Published Applications Installation Files
File Name Component Where to Install
VMware-vrops-v4paadapter-6.4buildnumber.pak
VMware-v4pabrokeragentx86_64-6.4-buildnumber.exe
VMware-v4padesktopagentx86_64-6.4-buildnumber.exe
VMware-v4padesktopagent-6.4buildnumber.exe
Adapter vRealize Operations Manager server
Broker agent installer for 64-bit
Windows OS
Desktop agent installer for 64-bit
Windows OS
Desktop agent installer for 32-bit
Windows OS
On XenDesktop Controller
On XenDesktop Controllers, RDS
servers, Store Front servers, Licence
servers, and VDI machines
On Session Host servers and VDI
machines
Install the vRealize Operations for Published Applications Solution
You install the vRealize Operations for Published Applications solution from a PAK le in
vRealize Operations Manager.
Procedure
1 Copy the VMware-vrops-v4paadapter-6.4-buildnumber.pak le to a temporary folder.
2 Log in to the vRealize Operations Manager user interface with administrator privileges.
3 In the left pane of vRealize Operations Manager, click the Administration icon and click Solutions.
4 Install the vRealize Operations for Published Applications solution.
a On the Solutions tab, click the plus sign.
b Browse to locate the temporary folder and select the PAK le.
c Click Upload.
The upload might take several minutes.
d Read and accept the EULA and click Next.
Installation details appear in the window during the upload process.
e When the installation is complete, click Finish.
After the installation is nished, vRealize Operations for Published Applications is listed as a solution.
What to do next
Provide licensing information for the vRealize Operations for Published Applications solution. See “Adding
a vRealize Operations for Published Applications License Key,” on page 16.
VMware, Inc. 15
VMware vRealize Operations for Published Applications Installation and Administration
Open the Ports Used by vRealize Operations for Published Applications
After you install the vRealize Operations for Published Applications adapter, you disable the rewall
service, open the default ports, and restart the rewall.
Prerequisites
N If you are using vRealize Operations Manager 6.4, opening the ports is not necessary.
Install the vRealize Operations for Published Applications adapter.
n
Verify that you have root privileges.
n
Procedure
1 Log in to vRealize Operations Manager collector server.
2 Access the command prompt and run the service vmware-vcops-firewall stop to disable the
vRealize Operations Manager rewall service.
3 Open the default ports by editing the conguration le.
Option Action
a
Linux
Windows
4 Run the vmware-vcops-firewall start command to start the service.
Access the vmware-vcops-firewall.conf le in
the/opt/vmware/etc/vmware-vcops-firewall.conf directory.
b In a text editor, modify the properties for the RMI service ports that
you want to change, for example TCPPORTS="$TCPPORTS
3095:3098" .
a Access Windows Firewall and select Windows Firewall > Advanced
> Inbound Rules > New Rule > Port and click Next.
b Select local ports and type the ports that you are using, for
example3095-3098.
The default ports are 3095-3098. If you changed the default ports,
specify the ports that you are using.
If the service vmware-vcops-firewall start command does not enable the ports, start the collector
server.
What to do next
Add a vRealize Operations for Published Applications license key. See “Adding a vRealize Operations for
Published Applications License Key,” on page 16
Adding a vRealize Operations for Published Applications License Key
After you install the vRealize Operations for Published Applications solution, you must add a
vRealize Operations for Published Applications license key in the vRealize Operations Manager user
interface. vRealize Operations for Published Applications is not functional until it is licensed.
N You must also add a license key for vRealize Operations Manager.
You can have an evaluation license key or a product license key for
vRealize Operations for Published Applications. The evaluation license key (eval/EVAL) provides 60 days of
unlimited product use. A product license key is encoded with an expiration date and a license count.
16 VMware, Inc.
Chapter 4 Installing and Configuring vRealize Operations for Published Applications
To add your vRealize Operations for Published Applications license key, select Administration > Licensing
in the vRealize Operations Manager user interface and add your license key to VMware Published Apps
Solution on the License Keys tab.
For detailed information about adding license keys, see the vRealize Operations Manager Customization and
Administration Guide.
If your vRealize Operations for Published Applications license key expires, the
vRealize Operations for Published Applications adapter stops populating vRealize Operations Manager
with data. If you have a valid license key but you exceed the license count, vRealize Operations Manager
generates alerts on certain dashboards. The vRealize Operations for Published Applications adapter does
not restrict data when the license count is exceeded.
Associate XD-XA Objects with Your vRealize Operations for Published Applications License Key
You must associate XD-XA objects with your vRealize Operations for Published Applications license key by
editing license groups in vRealize Operations Manager.
A license group is a way to gather certain objects, called license group members, under a particular license
key. By default, the vRealize Operations Manager and vRealize Operations for Published Applications
license groups both include all host, virtual machine, and datastore objects. Because these objects are
members of both license groups, they are covered by both your vRealize Operations Manager license and
your vRealize Operations for Published Applications license.
Each license group includes membership criteria that you can use to lter the objects that are members of
the license group. By editing the membership criteria for the vRealize Operations Manager and
vRealize Operations for Published Applications license groups, you can specify that certain objects are
covered only under your vRealize Operations for Published Applications license key.
Prerequisites
Add your vRealize Operations for Published Applications license key. See “Adding a vRealize Operations
for Published Applications License Key,” on page 16.
Procedure
1 Log in to the vRealize Operations Manager user interface.
2 In the left pane, select Administration > Licensing.
3 Click the License Groups tab.
License groups appear in the top pane. The license group for
vRealize Operations for Published Applications is called VMware VRealize Operations for Published
Apps 6.4 Licensing. The license group for vRealize Operations Manager is called Product Licensing.
4 Edit the membership criteria for the VMware Published Application Licensing group.
a Select VMware vRealize Operations for Published Apps 6.4 Licensing and click Edit on the
toolbar.
b Select the vRealize Operations for Published Applications license key under VMware vRealize
Operations for Published Applications and click Next.
c In the rst Select the Object Type that matches all of the following criteria drop-down menu,
select XSite, dene the criteria Relationship, Descendant of, is, and type XEnvironment in the
Object name text box.
d In the second Select the Object Type that matches all of the following criteria drop-down menu,
select Host System, dene the criteria Relationship, Descendant of, is, and type XEnvironment in
the Object name text box.
VMware, Inc. 17
VMware vRealize Operations for Published Applications Installation and Administration
e In the third Select the Object Type that matches all of the following criteria drop-down menu,
select Virtual Machine, dene the criteria Relationship, Descendant of, is, and type XEnvironment
in the Object name text box.
f In the fourth Select the Object Type that matches all of the following criteria drop-down menu,
select Datastore, dene the criteria Relationship, Descendant of, is, and type XEnvironment in the
Object name text box.
g Click Next and then click Finish to save your conguration.
5 Edit the membership criteria for the Product Licensing group.
You must edit the membership criteria for the Product Licensing group to exclude the objects that you
included in the VMware Published Application Licensing group.
a Select Product Licensing and click Edit on the toolbar.
b Select the vRealize Operations Manager license key under vRealize Operations Manager and click
Next.
c In the rst Select the Object Type that matches all of the following criteria drop-down menu, select
Host System, dene the criteria Relationship, Descendant of, is not, and type Xenvironment in the
Object name text box.
d In the second Select the Object Type that matches all of the following criteria drop-down menu,
select Virtual Machine, dene the criteria Relationship, Descendant of, is not, and type
Xenvironment in the Object name text box.
e In the third Select the Object Type that matches all of the following criteria drop-down menu,
select Datastore, dene the criteria Relationship, Descendant of, is not, and type Xenvironment in
the Object name text box.
f In the fourth Select the Object Type that matches all of the following criteria drop-down menu,
select Datastore, dene the criteria Relationship, Descendant of, is not, and type Xenvironment in
the Object name text box.
g Click Next and then click Finish to save your conguration.
Create an Instance of the vRealize Operations for Published Applications 6.4 Adapter
After you install the vRealize Operations for Published Applications solution, you must create an instance of
the vRealize Operations for Published Applications adapter in vRealize Operations Manager.
You can create a single vRealize Operations for Published Applications adapter instance to monitor multiple
XenDesktop sites. If you need to create multiple vRealize Operations for Published Applications adapter
instances, you must create each adapter instance on a unique cluster node or remote collector.
When you restart a vRealize Operations for Published Applications adapter instance, it takes several
minutes before the vRealize Operations for Published Applications desktop agent and broker agent send
information to the vRealize Operations for Published Applications adapter.
Prerequisites
Install the vRealize Operations for Published Applications solution and add your license key.
Procedure
1 Log in to the vRealize Operations Manager user interface with administrator privileges.
2 Click the Administration icon and click Solutions.
3 Select VMware vRealize Operations for Published Apps XD-XA and click the (gear) icon
on the toolbar.
18 VMware, Inc.
Chapter 4 Installing and Configuring vRealize Operations for Published Applications
4 Select vRealize Operations for Published Apps XD-XA in the adapter table.
5 Click the Add (plus sign) icon on the lower pane toolbar to add an adapter instance.
6 In Adapter , type a name and description for the adapter instance.
7 In Basic , congure an adapter ID and credential for the adapter instance.
a Type an identier for the adapter instance in the Adapter ID text box.
The identier must be unique across all vRealize Operations for Published Applications adapter
instances in the cluster.
b Congure the credential to use when the broker agent pairs with the
vRealize Operations for Published Applications adapter instance.
Option Action
Use an existing credential
Add a new credential
Select the credential from the Credential drop-down menu. When you
create a vRealize Operations for Published Applications adapter
instance for the rst time, the Credential drop-down menu is empty.
1 Click the Add New (plus sign) icon .
2 Type a name for the credential in the Credential name text box.
3 Type a server key for the adapter instance in the Server Key text
box. The server key is required to enable pairing between the
broker agent and the adapter. A server key is user-dened and
functions like a password; remember your server key, as you must
provide it when you congure the broker agent.
4 Click OK to save the new credential.
5 Select the new credential from the Credential drop-down menu.
c Click Test Connection to test the connection with the credential that you selected.
8 In Advanced , select a collector to manage the adapter processes from the Collector/Groups
drop-down menu.
To run the adapter instance on a remote collector, select the remote collector. If you do not have a
remote collector, select Default collector group.
9 Click Save to save the adapter instance.
The adapter instance is added to the list.
What to do next
Install the vRealize Operations for Published Applications broker agent. See “Install the vRealize Operations
for Published Applications Broker Agent,” on page 20.
Enabling Firewall Rules for XenDesktop Delivery Controllers and PVS Server
Before you install the broker agent and desktop agent, you must enable specic rewall rules for the
XenDesktop Delivery Controller and PVS server.
The broker agent cannot communicate with the XenDesktop Delivery Controller and PVS server if the
rewall is enabled on these servers.
Enable the following rules in XenDesktop Delivery Controller servers and PVS server.
Enable Ping in the rewall for all servers using the File and Printer Sharing (Echo Request - ICMPv4-In)
n
rule.
Enable Remote WMI in the rewall for all servers using the Windows Management Instrumentation
n
(WMI-In) rule.
VMware, Inc. 19
VMware vRealize Operations for Published Applications Installation and Administration
Enable the following rule in XenDesktop Delivery Controller Server.
Enable Remote Powershell by running the Enable-PSRemoting command in PowerShell command
n
prompt.
If the PVS Server in Citrix XenDesktop environment is not in same domain as Delivery Controller, you can
add a new eld manually in broker agent conguration le: <pvs_server_credentials>
</pvs_server_credentials>
Broker Agent conguration le can be found at following location: C:\ProgramData\VMware\vRealize
Operations for Published Apps\Broker Agent\conf\v4pa-brokeragent.config.
Install the vRealize Operations for Published Applications Broker Agent
You install the vRealize Operations for Published Applications broker agent on an Active XenDesktop
Delivery Controller.
You only install one broker agent for each XenDesktop Site.
A check box in the Broker Agent Setup wizard controls whether the Broker Agent Conguration wizard
opens immediately after you install the broker agent. This check box is selected by default.
Prerequisites
Install the vRealize Operations for Published Applications solution, add your license key, and create an
n
instance of the vRealize Operations for Published Applications adapter.
Verify that you downloaded the broker agent installation le.
n
Verify that you congured the XenDesktop Controller, Store Front, and PVS server for remote WMI by
n
granting DCOM remote access/activation permissions to the servers. The user name must include the
user name that you indicated for the servers.
XenDesktop Delivery controller's SSL certicate should be added as a trusted certicate if HTTPS (SSL)
n
is enabled for OData (Monitoring Service).
If OData (Citrix Monitoring Service) is congured on listen on SSL, the Broker Agent will create
n
connections to XenDesktop Delivery Controller using HTTPS.
So a valid certicate should be installed on Delivery Controller and this certicate should be added as a
trusted certicate in Delivery Controller.
OR
If the certicate is issued by a Certicate Authority, this CA should be a trusted publisher in Delivery
Controller.
Procedure
1 Log in to the machine where you plan to install the broker agent using a domain account that is part of
the local administrators group.
20 VMware, Inc.
Chapter 4 Installing and Configuring vRealize Operations for Published Applications
2 Install the broker agent.
Option Action
Command line
EXE file
a Access the command prompt.
b
Install the broker agent for your environment using the /s, v, or /qn
options.
n
Run the VMware-v4pabrokeragent-x86_64-6.4buildnumber.exe command.
a Copy the le for your environment to a temporary folder, and double-
click the EXE le to start the installation procedure.
n
Double-click the VMware-v4pabrokeragent-x86_64-6.4-
buildnumber.exe le.
b Follow the steps in the installer.
The broker agent is installed and saved to the Program Files folder.
What to do next
Congure the broker agent. See “Congure the vRealize Operations for Published Applications Broker
Agent,” on page 21.
Configure the vRealize Operations for Published Applications Broker Agent
After you install the broker agent, you use the Broker Agent Conguration wizard to congure the broker
agent on the Citrix XenDesktop Delivery Controller where you installed the broker agent. You can also use
the Broker Agent Conguration wizard to make changes to your broker agent conguration.
A check box in the Broker Agent Setup wizard controls whether the Broker Agent Conguration wizard
opens immediately after you install the broker agent. This check box is selected by default.
During broker agent conguration, you pair the broker agent with a
vRealize Operations for Published Applications adapter instance. Pairing the broker agent with a
vRealize Operations for Published Applications adapter instance is a necessary authentication step that
enables the broker agent and desktop agents to communicate with the
vRealize Operations for Published Applications adapter. The broker agent and desktop agents cannot
communicate with the vRealize Operations for Published Applications adapter until the pairing process is
complete.
If you are monitoring multiple XenDesktop Sites, you can pair the broker agent installed in each Site with
the same vRealize Operations for Published Applications adapter instance as long as the total number of
desktops that the vRealize Operations for Published Applications adapter instance handles does not exceed
10,000.
Each time you restart the broker agent service, a new log le is created.
If a log le was created for the day and the broker agent is restarted on that day, a new log le is created.
The name of the new log le is v4pa_brokeragent_svc_<date>_00.log, and the log rotation follows this
series.
Prerequisites
Install the vRealize Operations for Published Applications broker agent. See “Install the vRealize
n
Operations for Published Applications Broker Agent,” on page 20.
Verify that you have the server key for the vRealize Operations for Published Applications adapter. You
n
specied the server key when you created a credential for the adapter instance.
Verify that you have the IP address or FQDN of the machine where you installed the
n
vRealize Operations for Published Applications adapter.
VMware, Inc. 21
VMware vRealize Operations for Published Applications Installation and Administration
Procedure
1 If the Broker Agent Conguration wizard is not already open, start it by selecting Start > VMware >
vRealize Operations for Published Apps Broker Agent .
2 In the Adapter IP/FQDN Address text box, type the IP address of the vRealize Operations Manager
node or remote collector where the vRealize Operations for Published Applications adapter instance is
running.
3 In the Port text box, type the port used to connect to the vRealize Operations for Published Applications
adapter.
By default, the broker agent uses port 3095 to communicate with the
vRealize Operations for Published Applications adapter. You can modify the default port number,
depending on your network conguration.
4 Type and conrm the pairing key for the vRealize Operations for Published Applications adapter.
5 Click Pair to pair the broker agent with the vRealize Operations for Published Applications adapter,
and click Test to test the connection.
The status of the pairing process appears in the Text area.
6 After the pairing process succeeds, click Next.
7 On the Copy Information page, click Copy to copy the certicate string to the clipboard and click Next.
Save this text to copy to the GPO Template.
8 Provide the requested information on the Citrix Delivery Controller Information window.
a Type the XenDesktop environment domain name, domain administrator, and credentials.
b Click Test to validate the connection to the XenDesktop Controller server.
c Click Next.
9 (Optional) Select the App Volumes check box.
a Enter the FQDN and/or IP address of the App Volumes Manager to monitor.
b Enter the port for App Volumes.
c Enter the administrator username for the App Volumes Manager.
d Enter the password for the App Volumes Manager.
e Click Test to test the connection.
f Repeat for any other App Volumes Managers you want to monitor.
10 (Optional) Edit the interval values on the Intervals and Timeouts page, and click Next.
11 (Optional) Congure the logging level and log rotation on the Congure the logging parameters page,
and click Next.
12 When the Service Conguration window appears, select Start/Restart, and then click Next.
13 Review the congurations and click Finish to apply the congurations.
The vRealize Operations for Published Applications broker agent is congured and available.
N To congure the Broker-Agent to use a Read-Only/Custom Administrator account for XenDesktop
Delivery Controller, go to “Congure Broker Agent to use Non-Admin User for Citrix Desktop Delivery
Controller,” on page 23.
22 VMware, Inc.
Chapter 4 Installing and Configuring vRealize Operations for Published Applications
What to do next
Verify the status of the vRealize Operations for Published Applications broker agent in the Windows
Services Management Console.
Review the logs by browsing to the C:\ProgramData\VMware\VMware vRealize Operations for Published
Apps\Broker Agent\logs directory.
Configure Broker Agent to use Non-Admin User for Citrix Desktop Delivery Controller
You can congure broker agent to use non-admin user for Citrix Desktop Delivery Controller.
Prerequisites
If you want to congure broker agent to use Read-Only/Custom administrator for connecting to Citrix
delivery controller, follow these steps:
Ensure that the Read-Only/Custom Administrator has read access to Site and Monitoring Databases.
n
Ensure that Read-Only/Custom Administrator has read/execute/remote access over WinRM,
n
RemotePowershell and WMI (Root\CIMV2).
Procedure
1 You can achieve this by adding the user to local "Administrators" group of the delivery controller
machine.
or
2 Follow these steps if you don't want the user to have Administrator access on delivery controller.
a Login to delivery controller as full administrator.
b Run command winrm configSDDL default from command prompt. Add Read/Execute permissions
for Read-Only/Custom Administrator.
c Run Set-PSSessionConfiguration -name Microsoft.PowerShell -ShowSecurityDescriptorUI from
powershell prompt. Add Read/Execute permissions for Read-Only/Custom Administrator.
d Go to Computer Management > Services and Applications > WMI Control.
e Right click and select Properties.
f Go to Security tab.
g Click CIMV2 > Security.
Add Execute Methods and Remote Enable permissions for Read-Only/Custom Administrator.
h Restart the WinRM Service.
i Download and install the "subinacl" tool from
hp://www.microsoft.com/en-us/download/details.aspx?id=23510.
j Add Execute Methods and Remote Enable permissions for Read-Only/Custom Administrator.
k From Command Prompt, navigate to subinacl installation directory. By default, it gets installed in
"C:\Program Files (x86)\Windows Resource Kits\Tools".
l Run subinacl.exe /service CitrixBrokerService /grant=DOMAIN\USER_NAME=S.
VMware, Inc. 23
VMware vRealize Operations for Published Applications Installation and Administration
Install a vRealize Operations for Published Applications Desktop Agent
You install desktop agents on all Delivery Controllers, Store Front server, RDS host, License server, and VDI
machines.
Prerequisites
Verify that you downloaded the desktop agent installation le.
Procedure
1 Log in to the machine where you plan to install the desktop agent, using a domain account that is part
of the local administrators group.
2 Install the desktop agent.
Option Action
Command line
EXE file
a Access the command prompt.
b Run the Desktop agent:
n
For 64-bit: Run the VMware-v4padesktopagent-x86_64-6.4buildnumber.exe command using the /s /v/qn options.
n
For 32-bit: Run the VMware-v4padesktopagent-6.4buildnumber.exe command using the /s /v/qn options.
a
Copy the VMware-v4padesktopagent-x86_64-6.4-
buildnumber.exe (64-bit) or VMware-v4padesktopagent-6.4-
buildnumber.exe (32-bit) le to a temporary folder.
b
Double-click the VMware-v4padesktopagent-x86_64-6.4-
buildnumber.exe or the VMware-v4padesktopagent-x86_64-6.4-
buildnumber.exe (64-bit) or VMware-v4padesktopagent-6.4-
buildnumber.exe (32-bit)file.
c Follow the steps to complete the installer.
The desktop agent is installed in Program Files folder.
Push the vRealize Operations for Published Applications Desktop Agent Pair Token Using a Group Policy
To use vRealize Operations for Published Applications to monitor a XenDesktop Site, you must create a
Group Policy (GPO) to contain the vRealize Operations for Published Applications group policies. You then
apply the GPO to the remote desktops that you want to monitor.
You use the Microsoft Group Policy Editor to create the GPO. After you create the GPO, you must apply it to
a base image or to an Organizational Unit (OU) on your Active Directory server, depending on your
conguration.
vRealize Operations for Published Applications group-policy seings are provided in the
v4pa_desktopagent.admx le that is installed in the %programfiles%\VMware\vRealize Operations for
Published Apps\Broker Agent\extras\GroupPolicyFiles directory.
The language-specic resources, for example .adml les, are installed in the %programfiles
%\VMware\vRealize Operations for Published Apps\Broker Agent\extras\GroupPolicyFilese\language
directory.
If there is an Authentication Failure for a desktop agent you must update the GPO policy for desktop agent
authentication. When you update the GPO policy for desktop agent authentication, and there are other
policies that require updating, all pending policies are updated, not just the GPO policy for desktop agent
authentication.
24 VMware, Inc.
Chapter 4 Installing and Configuring vRealize Operations for Published Applications
Procedure
1 Create an organizational unit (OU) in the domain controller machine.
2 If the XD-XA server was already added to the computer account, move the XD-XA server to the OU.
a Access Active Directory Users Computers, and select Computer, right-click your XD-XA server,
and in the context menu select Move....
b In the Move object into container window, select the OU you created.
The XD-XA server is now moved to the OU.
3 Create a Group Policy object using the Group Policy Management Console (GPMC).
4 Copy the certicate string and the RMI URL from the broker agent conguration utility.
5 Copy the v4pa_desktopagent.admx le to PolicyDefinitions folder, which is in the
c:\Windows\PolicyDefinitions directory.
The v4pa_desktopagent.admx le is in the "%ProgramFiles%\VMware\vRealize Operations for
Published Apps\Broker Agent\extras\GroupPolicyFiles directory.
6 Copy the v4pa_desktopagent.adml le to en-us folder, which is in the
c:\Windows\PolicyDefinitions\en-us directory.
The v4pa_desktopagent.adml le is in the "%ProgramFiles%\VMware\vRealize Operations for
Published Apps\Broker Agent\extras\GroupPolicyFiles\en_us directory.
7 Set the Group Policy.
a On the controller machine, click Start and type the gpmc.msc command in the search box.
b Right-click the GPO that you created and select Edit.
c Select Computer > Policies > Administrative Templates > VMware Published
Apps Agent > vRealize Operations, and double-click the item in the right pane.
d Select Enable and copy the RMI URL and certicate string in the policy template.
You might receive a warning that you exceeded the maximum number of characters per line.
e (Optional) Break the line by pressing Enter, and click Apply, and then click OK.
8 Verify on the XD-XA server machine that the RMI URL and certicate string in the
HKLM\Software\Policies\VMware, Inc.\vRealize operations for published Apps\Desktop Agent
directory. RMI URL is of the format rmi://<vrops_ip>:3095.
What to do next
Install desktop agent on the VDI and RDSH hosts you want to monitor. If you already installed a desktop
agent and planned to push through GPO at later stage, there might be exceptions in the desktop agent log
les. After the pair token is pushed using the GPO, you should restart the desktop agent service.
VMware, Inc. 25
Loading...