Install VMware vCenter Operations for View step by step

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.

001 

Accept the default options, or modify following your configuration :

 002

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:

   003

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…)

1st Tab is “View Settings”, enter details as below:

  • Server Name : Netbios name or FQDN
  • Server Port : default
  • Username : “domain\username” with sufficient rights
  • password: password as defined
  • View event database: (optional) : enter the view event username and password

 004

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

 005

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”.

 006

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.

 007

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”

 008

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”.

 009

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.

 010

Go on your vCops Web admin interface, i.e : https://vcops-ui/admin and log into it.
Then, click on “Update” Tab to add the PAK file.

Click on “Browse” and indicate folder where the “VMware-vcops-viewadapter.pak” file as explained previously and confirm that you agree with the update.

 011

012

Accept the EULA and wait for the adapter to be added into the vCops instance and check at upper right if “file uploaded successfully” is displayed at the end of the process.

 

Once PAK file copied, accept the “confirm update” message box to install the adapter.

 014

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

 015

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

 016

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.

 017_

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…

 018_

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.

Changing VMware View user interface default language

If 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.

 

Configurer un partage CIFS comme repository Thinapp sur une baie de stockage

Comme vous le savez sûrement, il est possible de stocker les applications, qui sont passées sous Thinapp, dans un repository sous la forme d’un répertoire partagé Windows. Je vous propose  dans ce post de découvrir comment utiliser un répertoire CIFS d’une baie de stockage, solution recommanée en entreprise, pour de nombreuses raisons évidentes.

Mon premier essai d’ajout de ce répertoire CIFS depuis l’interface de VMware View, s’est soldé par le message d’erreur : “Failed to access the network path.depuis le menu “Add repository”  dans “Thinapp Configuration”.

failed to access the network path

Un grand nombre de discusssions sur les VMware communities font état de ce genre de message d’erreur, mais aucune réelle réponse sur le support ou non d’un répertoire CIFS de baie de stockage. Il est souvent question de problèmes de droits et permissions, mais rien de vraiment précis malheureusement.

Après plusieurs essais et recherches sur Internet, j’ai finalement pu trouver la solution, voici donc comment procéder pour éviter ce message d’erreur :

  • Vérifiez votre configuration au niveau de la baie : Nom d’hôte DNS enregistré et résolution du nom ok
  • Créez un compte de service dédié dans votre domaine Active Directory
  • Depuis votre baie de stockage, assurez vous d’appliquer les permissions “Read & Execute” au répertoire CIFS, pour le compte de service préalablement configuré, soit avec ses outils natifs ou avec une console MMC.
    Dans mon cas, la baie EMC VNX a pu être ajoutée dans la MMC par l’adresse IP de la Control Station comme un simple serveur.
  • Reconfigurez les services VMware View  suivants (View connection server, Framework Component, Web Component) pour qu’ils utilisent ce compte de service, en prenant soin de les redémarrer par la suite pour que les modifications soient prises en compte.
    Commencez par VMware VDMDS qui redémarrera les autres et assurez vous de ne pas en oublier un.
  • Vous pourrez ensuite relancer l’étape d’ajout de ce partage CIFS pour vos applications “thinappées” !

N’hésitez pas à me faire part de vos remarques ou posez moi une questions si besoin,

Configure CIFS on array as VMware Thinapp Repository

As 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.

failed to access the network path

 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 :

  • Check your array configuration : DNS hostname registered and resolution ok
  • 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
  • You should be able to add your CIFS folder as a Thinapp Repository

Feel free to ask me more details or add your comments !

%d bloggers like this: