Setting up the desktop agents for vCenter Operations for View with View 5.0 and 5.1

I’ve recently done quite a lot of work with the new release of vCenter Operations for View (V4V) 1.5.  The new version is a cinch to deploy – for SEs this is a great thing – we can spend more of our time with clients showing them how to use the product (the useful stuff) instead of how to install it.

V4V 1.5 is very straightforward to deploy and the installation guide at http://pubs.vmware.com/vcops-view-15/topic/com.vmware.ICbase/PDF/vcops-view-15-installation-guide.pdf will step you through the process – the whole install shouldn’t take more than an hour.

That said, we have had several occasions when deploying V4V against View 5.0/5.1 where the desktop agent was not getting installed/configured correctly.  Getting data from the desktop VMs and PCOIP sessions is pretty fundamental.  Without this data you will end up with lots of these in your console:

missing vCOPS objects

…so I thought I would document the steps you need to follow.

Note: if you are running View 5.2 you don’t need to do any of this as the regular View 5.2 agent and client software have this functionality built in so there is no need to install an additional V4V agent.

1 – Disable RMI Authentication on the Analytics Server

This involves editing a configuration file on the vCenter Operations Analytics server so you are probably going to be in the console trying to remember how to run VI 🙂  !  If you need a reminder have a look here: http://www.cs.rit.edu/~cslab/vi.html

You need to add the line disable-authentication into the

/usr/lib/vmware-vcops/user/plugins/inbound/V4V_adapter3/work/msgserver.properties file.

Analytics Server Console

There are some security implications of doing this which you can read about in the security guide: http://pubs.vmware.com/vcops-view-15/topic/com.vmware.ICbase/PDF/vcops-view-15-security-guide.pdf

2 – Install the V4V agent on each desktop VM to be monitored

You need to get the V4V agent onto each desktop that you are monitoring.  How you do this will depend on whether you use stateless or persistent desktops.

Either way you obviously need to have the agent added to you master build so that newly provisioned desktops get it so I would do that first.

Next put the V4V agent into your existing desktops.  For our lab environment I just did a recompose, for environments with persistent desktops you may need to install manually in each desktop.
The install is simple – just run the 32-bit or 64-bit exe and hit next | next |next…there is no further configuration!

3 – Install the GPO and configure it to point the above agent at the Analytics sever (you may do this at the same time you do step 2 above)

The GPO adm file is located on the View server where the V4V broker agent has been installed – in this directory C:\Program Files\VMware\VMwareView\Server\extras\GroupPolicyFiles

Similar to step 2 you can either make the GPO change in your base image and recompose or manually add it to existing desktops.  Alternatively you can make the change on your Active Directory server and apply it to the relevant OU and it will propagate out automatically.

Here are the steps (straight from the manual!):

1 – In Windows, run gpedit.msc .

2  – Expand Computer Configuration, right-click Administrative Templates, and select Add/Remove Templates from the context menu.

3 – In the Add/Remove Templates dialog box, click Add, browse for the v4v_desktopagent.adm file, click OK to add the template, and close the dialog box.

4 – Under Computer Configuration, expand Administrative Templates > Classic Administrative Templates (ADM) > VMware View Agent Configuration, and click vCenter Operations Manager.

5 – Double-click View adapter location on the right, and select Enabled.

6 – In the View adapter URL text box, type the IP address of the Analytics VM where the vCenter Operations Manager for Horizon View adapter is installed.

The format is rmi://<Analytics VM IP>:3091 below is an example

Screen Shot 2013-07-19 at 15.13.00

7 – Click OK.

Final thing to note – when you do upgrade to View 5.2 don’t forget to strip all the above out of your builds and turn RMI Authentication back on!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s