Everything-Virtual

Category: vCenter

  • Installing the Home Lab – Installing vCenter 5.5 on Windows 2012R2

    This post will detail all the steps required to install vCenter 5.5a on to a Windows 2012R2 guest machine, I should add that at the time of writing 2012R2 isn’t on the supported OS list and that there is an additional step that needs to be done to ensure that the installation succeeds first time.

    You will need to get a copy of OCSetup.exe because for some insane reason Microsoft dropped the use of it in Windows 2012R2 (it’s present in 2012). As a side note you can also use a copy of the file from Windows 2008R2 if you don’t have 2012 available. Once you have a copy place it in the C:\Windows\System32 folder.

    29-09-2013 00-06-5129-09-2013 00-08-0229-09-2013 00-09-04

    (more…)

  • Creating vCenter and VUM 5.5 databases.

    As a precursor to installing vCenter 5.5 in my 2012R2 lab at home I needed to create the vCenter and VUM databases in SQL 2012 and make sure that everything was setup correctly before the vCenter installation.

    To make things easier I used the SQL Scripts below to create two DBs (VC55 and VUMDB) as well as creating the vc_user account and password.

    [code lang=”sql”]USE MASTER;
    GO
    CREATE DATABASE [VC55] ON PRIMARY(
    NAME=’VC55′,
    FILENAME=’D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\VC55.mdf’,
    SIZE=5000KB,
    FILEGROWTH=10%)
    LOG ON
    (NAME=’VC55_log’,
    FILENAME=’E:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\VC55.ldf’,
    SIZE=1000KB,
    FILEGROWTH=10%)
    COLLATE SQL_Latin1_General_CP1_CI_AS
    GO
    [/code]

    (more…)

  • vCenter 5.1 Logbrowser Error – Unauthorised access fix

    After a recent upgrade to our vCenter 5.1 infrastructure we discovered that we were getting the following error when trying to use the log browser component of the web client.

    image

    Having tried a number fixes from the usual sources (Derek Seamans excellent blog) none of them seemed to resolve the issue, a reboot of the infrastructure, a re-install of the Web Client all resulted in the same error cropping up. In the end it took the eyes of a VMware BCS Engineer to have a look at our ca_certificates.crt file and discover some white space present.

    image

    The strange thing here is that there wasn’t any date change on the file since the initial deployment back last year and we had no issues with the log browser working before the upgrade.

    If you experience any issues with the log browser it may be worth checking the C:\ProgramData\VMware\SSL\ca_certificates(_2).crt file to make sure that there isn’t any white space present in the file first.