VMware Workspace 2.1: before you start clicking…
This blog is number three in sequence but number one to read when starting with VMware Workspace 2.1. This blog will tell you what is needed to setup VMware Workspace without discussing the actual installation which I did already in some previous blog.
Most of the time I create my own diagrams for I hate copying stuff from others. Today I thought different so here’s the diagram as shown on the VMware documentation site.
There used to be four appliances you had to import and configuration of those was a bitch, can’t say it any nicer. Now with only one appliance installing and configuring is pretty easy once you know what you’re up against. It’s no Click-Twice-I’m-Done installation but with a bit of thinking you get there.
Of course the appliance is the main component, you can download the OVF file at VMware.com.
Next on the list, if you’re going to use it for production, is a database server. For a PoC you could use the internal database. Read more about that in one of my previous blogs because if you come in the wrong way you won’t get it working.
You can convert the internal database to an external one later on but I think it’s best to set it up correctly as you start. You don’t want to fiddle around with this product having to find your way through consoles to get it all working again.
The external databases that are supported are found here, it’s Oracle 10 or 11g and VMware vFabric Postgres STD 9.1.6 and 9.2.x That’s not you common database in my opinion but that’s what it is.
What is good about the documentation is that is says what you need for sizing, what’s bad about it is that is starts at 100,000 users and that an awful lot coming from a needlepoint on this planet.
So for 100,000 users you need 64GB and you need to add 20GB for each 10,000 users you add.
I’m sure I can’t do the math and say well 100,000 need 64 so 1000 need 640MB no can I.. that’s something to look into for my customers will have between 200 and 3000 users.
The appliance is installed with a self signed certificate, for testing purposes that fine. When you intend to go to production you should be changing this and add a decent one.
The appliance has some needs to, it will need at least
- 2 CPU’s
- 6GB RAM
- 36GB Disk space
You might add more RAM to give it a bit more power but that is something you will be able to do also after some testing.
As written also in my previous blog you need a A-Record configured and you need to acces the appliance on the FQDN to configure it. Also make sure port 443 is open from the outside to allow users to access the Workspace.
To make sure the network configuration is setup well please take a look at the needed ports.
Workspace-va #2, #3
TCP port to relay outbound mail
389, 646, 3268, 3269
Default values, configurable
PostgrelSQL is 5432, Oracle is 1521
VMware horizon View
Access to VMware Horizon View
VMware ThinApp repository
Access to ThinApp
RSA SecureID system
88, 465, 135
You will be loading the workspace on an ESX server I presume so let’s see about the specs there.
- 2 Quad core processors
- 16GB RAM
- 500GB Disk space
- 1 network card
Last but not least the browsers that are supported are;
- Internet Explorer 10 and 11 for Windows
- Google Chrome 34 and higher for Windows and Mac
- Mozilla FireFox 28 or higher for Windows or MAC
- Safari 6.1.3 or later for Mac
VMware has provided a nice checklist which sums up most of what is being told here.
Take a look at it and make sure the appliance is running smoothly before proceeding to adding desktops or SAAS apps.
With all this in place you can start clicking and set it up following my previous blog posts. Next up is external access.