If you missed any of the previous parts of the series or want go back here is the jump list:
13. If deploying a small scale deployment (5 hosts and upto 50 VMs) you can choose to use SQL Server 2008 Express (which is actually 2008 R2)!.
If using an full SQL server installation (either local or remote) like we are here, ensure you created a 64-bit DSN, choose to use an existing database and select your DSN.
Click Next.
15. Choose to run the vCenter service under the "SYSTEM" account or recommended user-specified account.
This can be a standard active directory account with local administrator rights on the vCenter server.
The account will be grated "Log on as a service" right on the server.
Click Next.
16. As this will be the first vCenter installation choose "Create a standalone VMware vCenter Server Instance".
You would create linked mode vCenter servers if you have muliple vCenter servers, most likley if you were deploying a vCenter at two different datacenters for use with Site Recovery Manager.
Click Next.
17. Verify the ports to use for vCenter server, change if required (I recommend keeping the defaults unless you have a very specific reason).
Click Next.
19. Enter your vCenter Single Sign On administrator credentials (This email address is being protected from spambots. You need JavaScript enabled to view it.) to register the vCenter Server with vCenter SSO.
Also enter the lookup service URL (e.g. https://vcenter1.vmadmin.co.uk:7444/lookupservice/sdk)
25. The installation of vCenter server will complete, Click Finish.
Next up is to install the vSphere Web Client (instead of the vSphere Client) so we can connect to and manage our vCenter Server.
If you missed any of the previous parts of the series or want go back here is the jump list:
Share this blog post on social media:
TweetAll advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.