Home > Horizon Suite, vCenter Server, vSphere, Windows2012R2 > HOWTO: VMware Horizon View 6 – vCenter Server Installation

HOWTO: VMware Horizon View 6 – vCenter Server Installation

This is a document in a series, started by HOWTO: VMware Horizon View 6 – Overview.

In this document, we’ll install the basic vCenter server required for use by Horizon Suite 6. Some general prerequisite notes are:

· We’ll need the vCenter Server v5.5 U1 ISO to perform the installations

· We’ll be utilizing the default administrator@vsphere.local accounts, at least initially. As we go forward, we’ll configure AD groups and roles

· We’ll be utilizing locally installed SQL Express instances for any SQL requirements

· We’ll be utilizing Windows 2012 R2, which will require the installation of .NET 3.5 as a pre-requisite. See: HOWTO: Add .NET 3.5 to Windows 2012 or 2012 R2

· We will be accepting all defaults, for ports, file locations, etc.

With that in mind, let’s begin.

1) Start the vCenter Server installation:

clip_image001

2) Run the vCenter Single Sign-on Installer.

a) Accept the licence agreements, and accept the pre-requisites.

clip_image002

Click NEXT.

b) We’re going to create this as a standalone vCenter Single Sign-on. Bigger more complex environments may wish to use a common single sign-on environment.

clip_image003

Click NEXT.

c) Enter the Administrator@vsphere.local password. Don’t forget to add this to your password documentation.

clip_image004

Click NEXT.

d) Configure the site – we’ll use the default “Default-First-Site”.

clip_image005

Click NEXT.

e) Accept the default port:

clip_image006

Click NEXT.

f) Accept the default destination folder.

clip_image007

Click NEXT.

g) The final screen, will present the installation options to review.

clip_image008

Click INSTALL.

Click FINISH when the installation is complete.

3) Run the vSphere Web Client installer:

a) Accept the licence agreements, and the default Destination Folder.

clip_image009

Click NEXT.

b) Accept the default ports.

clip_image010

Click NEXT.

c) Enter the Adminstrator@vsphere.local password.

clip_image011

Click NEXT.

d) Accept the SSL prompt:

clip_image012

Click YES.

e) You’ll be asked to install the certificate.

clip_image013

Click INSTALL CERTIFICATE.

f) On the Ready to Install screen – click INSTALL.

clip_image014

g) Click FINISH to complete the installation.

4) Launch the vCenter Inventoory Service installer

a) Accept the licence agreements, and the default Destination Folder.

clip_image015

Click NEXT

b) The local FQDN should be automatically and correctly populated.

clip_image016

Click NEXT.

c) Accept the default ports.

clip_image017

Click NEXT

d) Configure the JVM Memory – almost certainly you’ll be “Small”.

clip_image018

Click NEXT.

e) Enter the Adminstrator@vsphere.local password.

clip_image019

Click NEXT

f) Accept the SSL prompt:

clip_image020

Click YES.

g) On the Ready to Install screen, click INSTALL.

clip_image021

Click FINISH

5) Launch the vCenter Server installer:

a) If you did not install .NET 3.5 as per the pre-requisites, you’ll see the following message:

clip_image022

Ensure you go and install .NET 3.5 via the Add-Features.

b) The first screen after the licence agreements, will ask for a licence key:

clip_image023

You’re able to skip this at this point, so click NEXT. We can add licences later if this PoC stays around.

c) Accept the licence agreements, and the default Destination Folder.

d) On the Database Options screen, you’ll need to make some choices.

clip_image024

As this is both small scale, and a PoC, we’ll use an SQL 2008 Express instance. This might work just fine long term for a small environment with a few hosts. Click NEXT.

e) The vCenter Server Service will ask how it will run.

clip_image025

Most sites opt to use a named service account. If you uncheck the USE WINDOWS LOCAL SYSTEM ACCOUNT option, you’ll find that you cannot change the Account Name – this is why we always run the installations logged in as the user who will be the service account. Note, however, this service account doesn’t yet have any rights to SSO or vCenter Inventory, so you may have to go back a step to fix/configure that, if you want to go forward with a named service account. It should be fine to utilize the Local System Account. Click NEXT.

f) Next, we have to choose if we’re using Linked Mode or not.

clip_image026

A proper enterprise deployment would likely consider a Linked Mode deployment. However, there are simplicities that come from having a standalone environment. I’ll be using a standalone vCenter. Click NEXT.

g) On the Configure Ports screen, accept the defaults:

clip_image027

Click NEXT.

h) On the JVM Memory screen, we’ll be selecting SMALL:

clip_image028

Click NEXT.

i) Enter the SSO password for the administrator@vsphere.local account.

clip_image029

Click NEXT

j) Accept the SSL warning.

clip_image030

Click YES.

h) Configure the SSO administrator or group:

clip_image031

We’ll be configuring and confirming all AD group authentication after the fact, so we’ll accept the default. Click NEXT.

i) On the vCenter Inventory Service Information screen, accept the defaults:

clip_image032

Click NEXT.

j) Choose your Destination Folder:

clip_image033

Click NEXT.

k) When the Ready to Install the Program screen appears:

clip_image034

Click INSTALL.

Click FINISH when it is complete.

6) Launch the VMware vSphere Client installer. As this is still vSphere v5.5, we’re going to require the C# client for things like VUM and SRM if we go that far. We’re all familiar with this install, it’s “Next, Next, Finish.”

7) Launch the vSphere Update Manager installer

a) Accept the licence agreements

b) On the Support Information screen, leave the default checkbox for DOWNLOAD UPDATES:

clip_image035

Click NEXT.

c) On the vCenter Server Information screen, remember that we have not yet configured SSO for AD and/or a service account. So you will need to configure this using the administrator@vsphere.local account for the moment. Enter the password for this account:

clip_image036

Click NEXT.

d) VUM requires a database of its own. The default will install a separate instance, which is fine for our needs:

clip_image037

You would almost certainly want to share a database instance with vCenter and/or other infrastructure. Note that VUM still requires a 32bit DSN, which has some hoops to jump through to be created on a 64bit OS. Click NEXT.

e) VUM wants to know how it will be identified on the network. From the drop down choose the FQDN and leave the firewall ports default.

clip_image038

Click NEXT

f) Choose the destination folders:

clip_image039

Click NEXT

g) VUM by default, suggests 120GB free on the VUM drive:

clip_image040

Keep this in mind, as you’ll likely be expanding the VUM disk at some point. Click OK.

h) Click INSTALL to install:

clip_image041

Click FINISH when it is complete.

The next step will be to configure the vCenter server. Steps such as creating a datacenter, a cluster, adding hosts, etc. Also any modifications required for AD roles and assignments.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: