Now it’s time to get to the fun stuff!
Before we deploy the View Composer role, let’s identify what the requirements for this role are. Since this information is on the blueprint of the exam, I think it’s a good idea to mention it here.
Preparing SQL Server database
If you’re like me and going to be using a remote SQL server database, you’ll need to make sure that when you install your SQL server, that you create an SA account. View Composer currently does not support Windows Authentication with remote SQL servers, instead you’ll have to us an SA account to authenticate.
Horizon View Limitations
With vSphere 5.1 and Horizon View 5.2, a single instance of vCenter can support up to 10,000 desktops. This is also the maximum number of desktops currently supported per View installation.
vCenter and ESX/ESXi Requirements
- VMware vCenter 5.1 U1
- VMware vCenter 5.1
- VMware vCenter 5.0 U2
- VMware vCenter 5.0
- VMware vCenter 4.1 U3
- VMware vCenter 4.1 U2
- VMware vCenter 4.1 U1
- VMware vCenter 4.1
- VMware vCenter 4.0 U4
- VMware vCenter 4.0 U3
Creating ODBC Connection
Prior to installing the Composer role, we need to create an ODBC connection to the SQL server. Creating an ODBC connection is fairly straight forward. We need to navigate over to the ODBC connecting settings by going to Control Panel -> System and Security -> Administrative Tools -> Data Sources ODBC, once opened, we need to click on the System DSN tab and click on Add on the top right. This will open the “Create New Data Source” Wizard
We’ll need to click Finish and begin creating the connection, in this case fill in the appropriate information and click Next. One thing to note, if you have a remote SQL server deployment with a dedicated instance for the View Composer database, you’ll need to use a backslash to indicate the instance, for example VIEWSQLVIEWCOMPOSER. In my case, I don’t have a dedicated instance
Installing View Composer
Launch the installer and click Next
Review the information and click Install to begin the installation