In some previous post I explained how to create certificate using OpenSSL and then sign it using your Microsoft root CA web page but there’s an easiest way as I’ll explain here :
The first thing to do is to authorize your servers to request « Web Server » certificates (by default only « Computer » is authorized), for this we’ll clone the default « Web Server » template in order to add requested options (and so we don’t have to do it for all new certificats). Lire la suite
This article is quite the same as KB2020988.
The issue occur when your desktop/laptop used to connect to vCenter is not connected to internet and so his unable to download updated root certificates from « www.download.windowsupdate.com »
The other condition is that your vCenter/ESX certificate are not signed by a root CA (either internal of external) Lire la suite
It could be useful to have a certificate valid for both fqdn and hostname and also with the « alias », so here as a sample the one I used for me (ok I changed hostname from my real one 
). I’d like to thanks Michael Webster concerning his following article (http://longwhiteclouds.com/2012/02/07/the-trouble-with-ca-ssl-certificates-and-vcenter-5/) that help me create it.
I used for both View Connection Server and View Security Server
This have been tested on VNX Simulator and so I need to test it on a real VNX 
The goal is to use the VNX CIFS share to hold ThinApp packages and assign them to pools using View Manager. On a resent post the solution given was to modify the account used to start View services with a account authorized on the VNX ThinApp CIFS share. Personally there’s something that hurt me in this solution as I don’t like modifying such things (that’s could break support etc…).
Following my previous post, I decided to create a specific post with as many HW configuration as possible, so …
For HP servers :
Add-EsxSoftwareDepot -DepotUrl D:\ESXiDepot\Sources\ESXi500-201206001.zip Add-EsxSoftwareDepot -DepotUrl http://vibsdepot.hp.com/hpq/jun2012/index.xml New-EsxImageProfile -CloneProfile ESXi500-20120604001-standard -Name ESXi500-HP-20120604001 Add-EsxSoftwarePackage -ImageProfile ESXi500-HP-20120604001 -SoftwarePackage hpnmi,hp-ams,hpacucli,hponcfg,char-hpilo,hp-smx-provider,hp-smx-limited,hpbootcfg,char-hpcru Export-EsxImageProfile ESXi500-HP-20120604001 -FilePath D:\ESXiDepot\ISO\ESXi500-HP-20120604001.iso -ExportToIso Export-EsxImageProfile ESXi500-HP-20120604001 -FilePath D:\ESXiDepot\ISO\ESXi500-HP-20120604001.zip -ExportToBundle
ESXi let you quickly and easily create an up-to-date ISO that prevent you upgrading it immediately after the installation.
So what you need is :
Ok, so in Part 1, we saw how to deploy and configure the VNX appliance, in Part 2, how to configure the Control Station, now let’s see how to configure the Data Mover :
Note : One more time I’m not a VNX specialist so there’s other way to configure it (without wizard) but the goad is to quickly build a working environement.
Ok let’s continue with the « Setup Wizard for File » :
This is the second article about EMC VNX (simulator) and VMware View. In this one we’ll see how to configure the control station :
Just to be clear, I’m absolutely not a VNX specialist so I show there the easiest way and not necessary the most efficient to configure the VNX.
So, Start IE or Firefox (or what ever you want…) and log on to the Control Station IP (eg : 192.168.98.35 in my case) :
Trust everything that appear and logon as « root » and password « nasadmin » (for real VNX it should sysadmin/sysadmin) :
I’m actually implementing a View infrastructure for a customer and we had to verify if everything will run fine if we moved User Data, Profiles and ThinApp Sandbox to CIFS shares on a VNX filer.
So in order to test this scenario I built a labs using VNX simulator (you can find it if you have a EMC Powerlink account). Because knowledge are best when shared with other than keep for it self, I’m going to write articles about how I build my lab step by step.
This post follow the previous one concerning generating SSL certificate for View 5.1 and concern especially the View Security Servers.