This is pretty cool. Looking through the internet at stuff I can do with my Raspberry Pi (apart from running RISC OS natively) I was interested to see if anyone had begun running a VMware View client on it. The Raspberry PI costs £25 so makes a perfect Thin Client. The video below shows the Pi running the View client nicely. All credits go to the author (not sure of his name) you can visit his blogsite here. He needs help working on thin clients for the Raspberry Pi if anyone has some free time. Further information on the Raspberry Pi can be found here:
Download link for VMware View Client
People keep asking on a regular basis, where can we download the View Client. This is the currently latest version available (at time of writing). Follow this link to the download http://downloads.vmware.com/d/details/view_460_clients_en/ZEB3YnRkcEBiZCpqag== This link will take you to the View 4.6 download page, which includes the current supported MAC version http://downloads.vmware.com/d/details/view_500_clients_en/dCV0YnQqJWhidGVkdA== This link will take you to the View 5.0 download page.
Modifying VMware View 5.0 HTTPS port
Yesterday I installed VMware View into my home lab and configured everything successfully. What I discovered was that my router could not do was any Network Address Port Translation (NAPT) so I could not redirect the external IP port 444 to the internal server IP port of 443. I run a web server on port 443 so could not use this external port for View Connection Server. So how do I change the IP Port on the View Connection Server itself? After googling some scenarios I found a link to this page on myvirtualcloud.net. This is an excellent article, however it only covers View 4.0.x. In View 5.0 there is no locked.properties file in View 5.0, only config.properties and settings.properties. The article above recommends changing the entry “serverPort=xx” in locked.properties however there is no entry for this in either of these files. Hmmmm what to do… In the example below you can quite clearly see that the configuration for the client IP port is set to 444, but there was no serverport entry and telnet rightfully confirmed everything was running on port 443. I decided after some time thinking that the config.properties contents look very similar to the examples provided
Read More…
vCloud Ecosystem components explained
During VMworld Chris Colotti and I presented quite a few group discussions on VMware vCloud. During these discussions some people were amazed to find out how many components/products are involved in making up the vCloud environment. When planning on building a VMware vCloud, you are not just installing vCloud Director and pointing it to vSphere, you are designing/building a whole Ecosystem. The list below shows which components are used in building a full vCloud environment. They are listed in order of priority. vSphere ESXi vCenter vCloud Director vShield Manager vCenter Chargeback Vcenter Update Manager vCenter Orchestrator vCloud Service Manager vCloud Connector So why are these components important? When designing a vCloud environment, you need to take into consideration the availability of certain components, like vCenter for example. This is no longer a management tool that is used to manage your virtual infrastructure. This is a critical component of your vCloud environment passing through all the operational commands a consumer initiates using vCloud Director. How do you protect vCenter? There are 6 databases in a vCloud Ecosystem. How do you protect all the databases? Every component shown above with the exception of ESXi and vCloud Connector have a database that have
Read More…
Cannot add groups to vCD after configuring LDAP
I discovered today building a new vCD 1.5 home lab, that once you configure the System LDAP, you dont have the option to add any LDAP groups. This confused me, it was possible to do this in 1.0.x. Why isn’t it available in 1.5? What I discovered is that the GUI is still configured for non LDAP authentication. Once you have configured LDAP and started the synchronization log out of the vCloud Director GUI and back in. You will then see that groups is listed under the administration tab. The GUI needs to update its configuration options. Simple solution, but still confusing until you realise.
