Although I thought that the first post will be on a totally different matter – the following info is too important for not sharing.
As part of a big project – a customer has requested to design and deploy a brand new Horizon View environment based on the latest version – vSphere 5.5U1 and Horizon View 5.3.
So, before getting the planing stage -some checks need to be taken before running to design and implement the solution:
Step 1 – Checking the compatability at “VMWare Product Interoperability “:
Perfect – we can continue….
Step 2 – Checking Horizon View Microsoft SQL Server version support – O.K, this is where it gets interesting.
As you may see in the following attached screenshot, it seems that the SQL Server version which supports Horizon View 5.3 Servers are only “Microsoft SQL Server 2008 (R2) – 32/64bit” WITHOUT ANY SERVICE PACK or “Microsoft SQL Server 2008 SP2” WITHOUT R2 SUPPORT.
Step 3 – Now we’ll check the vCenter’s Microsoft SQL version support (small hint – troubles are ahead…) – As you may already know it – Microsoft SQL Server 2012 is supported as vCenter Database since version 5.5.
Now, we already know that Horizon View doesn’t support Microsoft SQL Server 2012, so let’s check the other SQL Server versions:
It’s seems that the SQL Server 2008 versions supported by Horizon View, are not supported by vCenter 5.5U1 !
This is something that need to take into consideration – since now we know that in our new design, we’ll need two separated Windows Servers – each with different SQL Server version (one that supports the vCenter, and the other one for the Horizon View environment.)
So, all we did until now is just checking the SQL Server version support for all View components.
Step 4 – Let’s continue by checking the Guest OS support.
As for vSphere 5.5U1 – Microsoft Windows Server 2012 is supporteed as Guest OS
BUT – for the broker servers – only Windows Server 2008 R2 or Windows Server 2008 R2 SP1 is supported!
Checking the View Composer component. According to Horizon View 5.2 release notes (same goes for View 5,3) – only Windows Server 2008 R2 and R2 SP1 are being supported
SO – What are the takeaways from this?
- Guest OS – If we wish to install the new View environment based on Windows Server 2012 – only the vCenter will be supported. The brokers servers and the Composer component will have to be deployed on Windows Server 2008 R2 at minimum.
- Another takeaway – if we’ll choose to install vCenter server based on Windows Server 2012, the View Composer cannot be installed on the same vCenter. Remember – the connection servers and Composer are only supported when running on Windows Server 2008 R2/R2 SP1.
- SQL Server version support – As we saw at step 1 and step 2, the vCenter DB and View DB (including the View Composer) – will have to be on two separated server.
I hope you will find this post helpful, and please – SHARE YOUR THOUGHTS!