Just wanted to share a VMware vCenter Operations for View installation session. This solution is one of the most useful VMware View monitoring and Analytics solution.

Just a brief reminder about this VMware product : It’s licensed and sold in two ways depending of your situation:

You’re already a VMware vCops customer (Adv. or Enterprise) :
So you need to install the View Adapter like any other existing adapters

You don’t have any vCops instance installed :
You’ll get a bundled version of vCops with the adapter

So, in this post, we’ll review an installation into vCops Enterprise, similar to an Advanced one.

2) Pre-requisites:

VMware View 5.0 mini and above running

VMware vCops running and configured if you install the adapter like here*

A Windows 2003, 2008, 2008 R2 instance, (64 bits version preferred)

For others requirements, read the vCops integration guide available on VMware website

After downloaded the VMware vCops component, in this example “VMware-vcops-viewadapter-x86_64-1.0.2-997768.exe” on VMware website, run the installer from your Windows Server instance described in Part 1.

Accept the default options, or modify following your configuration :

You can let the box checked if you want to launch the wizard once the setup finishes and click on “install”, the setup copies files and configure the VMware vCops for View:

The setup has finished and the wizard pops up to help you configure the connection with the vCenter Operations instance and set different options (sizing, logging…)

Use the “test” buttons to verify if your details are correctly set and click on “next” at the bottom or click on next Tab

The “vCenter Operations settings” asking for configurations details to enter related to server name (vcops-ui) or IP address and an administrator account. Once done and tested, click on “next”.

On the “Desktop settings” enter an administrator account which is into the “local admins” group of each Desktop VM. This is optional but recommended if you want to monitor VM performance metrics (PCoIP, disk, network…). Type it in : “domain\account” mode.

When you click on “Test”, you’ll be asked to enter a Desktop Pool name to check your admin account. Once validated, click on “Next”

You’ll be at the final tab of this Wizard where you’ll define the size environment and log level collection. Set it by default and click on “Apply” and “close”.

So, the Windows installation and configuration part is done, let’s switch to the vCenter Operations configuration to add the adapter.

Prior to that, if you look into the “c:\program files\vmware\vCenter Operations\View Adapter” folder, just installed, you’ll see the PAK file, which will be added into your vCenter Operations instance. Copy it into a directory that your vCops instance can reach or remember the UNC for next step.

Wait for the progress displayed into this window, it may take a while:

The adapter installation window should close automatically, check if all steps display a “done” status into the vCops-ui admin window as below:

Now that both the Windows and vCops instance are configured, let’s switch to the VMware vCenter Operations Custom View web interface.

This web interface, if you’re familiar with vCops Advanced and Enterprise editions is the additional interface where you can design and configure your views and reports.

Open a browser and go to your vCops Custom Interface, URL as following: https://vcops-ui/vcops-custom and log into the interface with an authorized Admin account.

_

Once logged, you’ll be able to browse among many View Adapter dashboards additionally to others already installed, for example related to Storage, EMS, etc…

_

This VMware adapter adds these Dashboards :

View Main

View Users

View Top Sessions

View Top Desktops VMs

View Pools

View Desktops sessions

So, now vCops for View is installed and you can start to monitor your View environment. Familiarize yourself with the Dashboards. We’ll see in a next post, how to work with.

]]>https://veemanuel.wordpress.com/2013/04/27/install-vmware-vcenter-operations-for-view-step-by-step/feed/0veemanuel001002003004005006007008009010011012014015016017018Changing VMware View user interface default languagehttps://veemanuel.wordpress.com/2012/07/18/changing-vmware-view-user-interface-default-language/
https://veemanuel.wordpress.com/2012/07/18/changing-vmware-view-user-interface-default-language/#commentsTue, 17 Jul 2012 22:32:40 +0000http://veemanuel.wordpress.com/?p=21If you’re using a localized Windows, a non ENG/US english Windows version, you probably noticed that when launching the new VMware View 5.1 Web interface you got a French/German or any of the 5 languages (Japanese, French, German, simplified Chinese, and Korean) added in this version, as per the release notes.

I’m personally used to work in english menus, more usual, so, if you want to stay with this language, please read below.

Unlike vSphere client which is a real client and requires changes into shortcut the VMware View interface is browser based, so we have to modify browser options.

Internet Explorer (7,8 and above) :

Go into “Tools, Internet options” and click on “Languages”

You can see your default Language, click on “Add” :

Then, select ENG/US :

Move up the ENG/US in 1st line, then Close and Save

Mozilla Firefox :

Go to “Tools, Options” (activate menu with Alt key), choose the “Content” button and click on “language” down in the window

Then, add the “English/United States [en-us]” in the scroll list.

Close, and check that the Eng-US is on the top by using the “move up” button.

Et voila, your VMwareView 5.1 should display english interface and menu now ! Don’t forget to apply this to all your browsers in your environment.

]]>https://veemanuel.wordpress.com/2012/07/17/configurer-un-partage-cifs-comme-repository-thinapp-sur-une-baie-de-stockage/feed/0veemanuelfailed_to_access_the_network_pathConfigure CIFS on array as VMware Thinapp Repositoryhttps://veemanuel.wordpress.com/2012/05/10/configure-cifs-on-array-as-vmware-thinapp-repository/
https://veemanuel.wordpress.com/2012/05/10/configure-cifs-on-array-as-vmware-thinapp-repository/#respondThu, 10 May 2012 20:12:18 +0000http://veemanuel.wordpress.com/?p=5As you may know, you can store your Thinapp applications into a dedicated repository based on a Windows Shared folder. I’ve decided to use an array to act as a CIFS folder to get a more reliable solution.

My first attempt after created a CIFS share on my array stuck with an error message “Failed to access the network path.” when I tried to add within “Add repository” menu in “Thinapp Configuration” on VMware View Console UI.

You can find a lot of discussions on VMware communities about this issue but there’s no statement about VMware View support of CIFS array based for Thinapp repositories. Most posts are related to permissions but that’s all.

After many attempts and google browsing, I finally solved it. So, here are steps to follow :

Create a dedicated account in your AD Domain, to act as Service Account

From your storage array, be sure to set permissions to Read and Execute (for the service account) on your CIFS folder or use the Microsoft MMC console to set Windows permissions on a remote computer (CIFS array server)

Reconfigure these VMware View services (View connection server, Framework Component, Web Component) to use this newly created account, then you’ll have to restart all.
Begin with VMware VDMDS that will restart also View Connection Server and don’t forget all View services listd above to apply changes