VMware ESXi Release and Build Number History

The following listings are a comprehensive collection of the flagship hypervisor product by VMware. All bold versions are downloadable releases. All patches have been named by their release names. Please note that the ESXi hypervisor is available since version 3.5.

vSphere ESXi 6.5

Name Patch Date Build
ESXi 6.5 U1e* ESXi650-201801001 2018-01-09 7526125
ESXi 6.5 Patch 2* ESXi650-201712001 2017-12-19 7388607
ESXi 6.5 Patch 2* (Security only) ESXi650-201712001 2017-12-19 7273056
ESXi 6.5 Express Patch 4 ESXi650-201710401 2017-10-05 6765664
ESXi 6.5 Update 1 ESXi650-update1 2017-07-27 5969303
ESXi 6.5 Update 1 (Security only) ESXi650-update1 2017-07-27 5969300
ESXi 6.5d (vSAN 6.6 Patch) ESXi650-201704001 2017-04-18 5310538
ESXi 6.5 Express Patch 1a ESXi650-201703002 2017-03-28 5224529
ESXi 6.5 Patch 1 ESXi650-201703001 2017-03-09 5146846
ESXi 6.5 Patch 1 (Security Only) ESXi650-201703001 2017-03-09 5146843
ESXi 6.5a ESXi650-201701001 2017-02-02 4887370
ESXi 6.5 GA 2016-11-15 4564106

vSphere ESXi 6.0

Name Patch Date Build
ESXi 6.0 U3d* ESXi600-201801001 2018-01-09 7504637
ESXi 6.0 Patch 6* ESXi600-201711001 2017-11-09 6921384
ESXi 6.0 Patch 6* (Security Only) ESXi600-201711001 2017-11-09 6856897
ESXi 6.0 Express Patch 11 ESXi600-201710301 2017-10-05 6765062
ESXi 6.0 Update 3a (Patch 5) ESXi600-201706001 2017-06-06 5572656
ESXi 6.0 Update 3a (Patch 5) (Security Only) ESXi600-201706001 2017-06-06 5485776
ESXi 6.0 Update 2 (VMSA-2017-0006) ESXi600-201703003 2017-03-28 5251623
ESXi 6.0 Update 1 (VMSA-2017-0006) ESXi600-201703002 2017-03-28 5251621
ESXi 6.0 Express Patch 7a ESXi600-201703001 2017-03-28 5224934
ESXi 6.0 Update 3 ESXi600-update3 2017-02-24 5050593
ESXi 6.0 Update 3 (Security Only) ESXi600-update3 2017-02-24 5047589
ESXi 6.0 Patch 4 ESXi600-201611001 2016-11-22 4600944
ESXi 6.0 Patch 4 (Security Only) ESXi600-201611001 2016-11-22 4558694
ESXi 6.0 Express Patch 7 ESXi600-201610001 2016-10-17 4510822
ESXi 6.0 Patch 3 ESXi600-201608001 2016-08-04 4192238
ESXi 6.0 Patch 3 (Security Only) ESXi600-201608001 2016-08-04 4179598
ESXi 6.0 Express Patch 6 ESXi600-201605001 2016-05-12 3825889
ESXi 6.0 Update 2 ESXi600-update2 2016-03-15 3620759
ESXi 6.0 Update 2 (Security Only) ESXi600-update2 2016-03-15 3568943
ESXi 6.0 Express Patch 5 ESXi600-201602001 2016-02-23 3568940
ESXi 6.0 Update 1b ESXi600-201601001 2016-01-07 3380124
ESXi 6.0 Update 1b (Security only) ESXi600-201601001 2016-01-07 3341439
ESXi 6.0 Express Patch 4 ESXi600-201511001 2015-11-25 3247720
ESXi 6.0 Update 1a ESXi600-201510001 2015-10-06 3073146
ESXi 6.0 Update 1 ESXi600-update1 2015-09-10 3029758
ESXi 6.0 Update 1 (Security only) ESXi600-update1 2015-09-10 3017641
ESXi 6.0b ESXi600-201507001 2015-07-07 2809209
ESXi 6.0b (Security Only) ESXi600-201507001 2015-07-07 2809111
ESXi 6.0 Express Patch 2 ESXi600-201505001 2015-05-14 2715440
ESXi 6.0 Express Patch 1 ESXi600-201504001 2015-04-09 2615704
ESXi 6.0 GA 2015-03-12 2494585

vSphere ESXi 5.5

Name Patch Date Build
ESXi 5.5 U3?* ESXi550-201801002 2018-01-22 7618464
ESXi 5.5 U3g* ESXi550-201801001 2018-01-09 7504623
ESXi 5.5 Patch 11 ESXi550-201709001 2017-09-14 6480324
ESXi 5.5 Patch 11 (Security only) ESXi550-201709001 2017-09-14 6480267
ESXi 5.5 Express Patch 11 ESXi550-201703001 2017-03-28 5230635
ESXi 5.5 Patch 10 (Security only) ESXi550-201612001 2016-12-20 4756874
ESXi 5.5 Patch 10 ESXi550-201612001 2016-12-20 4722766
ESXi 5.5 Patch 9 ESXi550-201609001 2016-09-15 4345813
ESXi 5.5 Patch 9 (Security only) ESXi550-201609001 2016-09-15 4345810
ESXi 5.5 Patch 8 ESXi550-201608001 2016-08-04 4179633
ESXi 5.5 Patch 8 (Security only) ESXi550-201608001 2016-08-04 4179631
ESXi 5.5 Express Patch 10 ESXi550-201602001 2016-02-21 3568722
ESXi 5.5 Express Patch 9 ESXi550-201601001 2016-01-04 3343343
ESXi 5.5 Update 3b ESXi550-201512001 2015-12-08 3248547
ESXi 5.5 Update 3b (Security Only) ESXi550-201512001 2015-12-08 3247226
ESXi 5.5 Update 3a ESXi550-201510001 2015-10-06 3116895
ESXi 5.5 Update 3 ESXi550-update3 2015-09-16 3029944
ESXi 5.5 Update 3 (Security Only) ESXi550-update3 2015-09-16 3029837
ESXi 5.5 Patch 5 re-release ESXi550-201505002 2015-05-08 2718055
ESXi 5.5 Patch 5 (Security Only) ESXi550-201505002 2015-05-08 2702869
ESXi 5.5 Patch 5 (Recalled) ESXi550-201504002 2015-04-30 2702864
ESXi 5.5 Express Patch 7 ESXi550-201504001 2015-04-07 2638301
ESXi 5.5 Express Patch 6 ESXi550-201502001 2015-02-05 2456374
ESXi 5.5 Patch 4 ESXi550-201501001 2015-01-27 2403361
ESXi 5.5 Patch 4 (Security Only) ESXi550-201501001 2015-01-27 2352327
ESXi 5.5 Express Patch 5 ESXi550-201412001 2014-12-02 2302651
ESXi 5.5 Patch 3 ESXi550-201410001 2014-10-15 2143827
ESXi 5.5 Patch 3 (Security Only) ESXi550-201410001 2014-10-15 2093874
ESXi 5.5 Update 2 ESXi550-update2 2014-09-09 2068190
ESXi 5.5 Update 2 (Security Only) ESXi550-update2 2014-09-09 1980513
ESXi 5.5 Patch 2 ESXi550-201407001 2014-07-01 1892794
ESXi 5.5 Patch 2 (Security Only) ESXi550-201407001 2014-07-01 1892623
ESXi 5.5 Express Patch 4 ESXi550-201406001 2014-06-10 1881737
ESXi 5.5 Express Patch 3 ESXi550-201404020 2014-04-19 1746974
ESXi 5.5 Update 1a ESXi550-201404001 2014-04-19 1746018
VMware ESXi 5.5.1 Driver Rollup ESXi550-update1 2014-03-11 1636597
ESXi 5.5 Update 1 ESXi550-update1 2014-03-11 1623387
ESXi 5.5 Update 1 (Security Only) ESXi550-update1 2014-03-11 1598313
ESXi 5.5 Patch 1 ESXi550-201312001 2013-12-22 1474528
ESXi 5.5 Patch 1 (Security Only) ESXi550-201312001 2013-12-22 1474526
vSAN Beta Refresh 2013-11-25 1439689
ESXi 5.5 GA 2013-09-22 1331820

vSphere ESXi 5.1

Name Patch Date Build
ESXi 5.1 Patch 9 ESXi510-201605001 2016-05-24 3872664
ESXi 5.1 Patch 9 ESXi510-201605001 2016-05-24 3872638
ESXi 5.1 Patch 8 ESXi510-201510001 2015-10-01 3070626
ESXi 5.1 Patch 8 (Security Only) ESXi510-201510001 2015-10-01 3021178
ESXi 5.1 Patch 7 ESXi510-201503001 2015-03-26 2583090
ESXi 5.1 Patch 7 (Security Only) ESXi510-201503001 2015-03-26 2575044
ESXi 5.1 Update 3 ESXi510-update3 2014-12-04 2323236
ESXi 5.1 Update 3 (Security Only) ESXi510-update3 2014-12-04 2323231
ESXi 5.1 Patch 6 ESXi510-201410001 2014-10-31 2191751
ESXi 5.1 Patch 6 (Security Only) ESXi510-201410001 2014-10-31 2191354
ESXi 5.1 Patch 5 ESXi510-201407001 2014-07-31 2000251
ESXi 5.1 Patch 5 (Security Only) ESXi510-201407001 2014-07-31 1904929
ESXi 5.1 Express Patch 5 ESXi510-201406001 2014-06-17 1900470
ESXi 5.1 Patch 4 ESXi510-201404001 2014-04-29 1743533
ESXi 5.1 Patch 4 (Security Only) ESXi510-201404001 2014-04-29 1743201
ESXi 5.1 Express Patch 4 ESXi510-201402001 2014-02-27 1612806
ESXi 5.1 Update 2 ESXi510-update2 2014-01-16 1483097
ESXi 5.1 Update 2 (Security Only) ESXi510-update2 2014-01-16 1472666
ESXi 5.1 Patch 3 (Security Only) ESXi510-201310001 2013-10-17 1312874
ESXi 5.1 Patch 3 ESXi510-201310001 2013-10-17 1312873
ESXi 5.1 Patch 2 ESXi510-201307001 2013-07-25 1157734
ESXi 5.1 Patch 2 (Security Only) ESXi510-201307001 2013-07-25 1142907
ESXi 5.1 Express Patch 3 ESXi510-201305001 2013-05-22 1117900
ESXi 5.1 Update 1 ESXi510-update1 2013-04-25 1065491
ESXi 5.1 Update 1 (Security Only) ESXi510-update1 2013-04-25 1063671
ESXi 5.1 Express Patch 2 ESXi510-201303001 2013-03-07 1021289
ESXi 5.1 Patch 1 ESXi510-201212001 2012-12-20 914609
ESXi 5.1 Patch 1 (Security Only) ESXi510-201212001 2012-12-20 911593
ESXi 5.1a ESXi510-201210001 2012-10-24 838463
PP Hot-Patch KB2034796 2012-10-24 837262
ESXi 5.1 GA 2012-09-11 799733

vSphere ESXi 5.0

Name Patch Date Build
ESXi 5.0 Patch 13 ESXi500-201606001 2016-06-14 3982828
ESXi 5.0 Patch 13 (Security Only) ESXi500-201606001 2016-06-14 3982819
ESXi 5.0 Patch 12 ESXi500-201510001 2015-10-01 3086167
ESXi 5.0 Patch 12 (Security Only) ESXi500-201510001 2015-10-01 3021432
ESXi 5.0 Patch 11 ESXi500-201502001 2015-02-26 2509828
ESXi 5.0 Patch 11 (Security Only) ESXi500-201502001 2015-02-26 2486588
ESXi 5.0 Patch 10 ESXi500-201412001 2014-12-04 2312428
ESXi 5.0 Patch 10 (Security Only) ESXi500-201412001 2014-12-04 2216931
ESXi 5.0 Patch 9 ESXi500-201408001 2014-08-28 2000308
ESXi 5.0 Patch 9 (Security Only) ESXi500-201408001 2014-08-28 1979317
ESXi 5.0 Express Patch 6 ESXi500-201407001 2014-07-01 1918656
ESXi 5.0 Patch 8 ESXi500-201405001 2014-05-29 1851670
ESXi 5.0 Patch 8 (Security Only) ESXi500-201405001 2014-05-29 1749766
ESXi 5.0 Patch 7 ESXi500-201401001 2014-01-23 1489271
ESXi 5.0 Patch 7 (Security Only) ESXi500-201401001 2014-01-23 1478905
ESXi 5.0 Update 3 (Security Only) ESXi500-update3 2013-10-17 1311177
ESXi 5.0 Update 3 ESXi500-update3 2013-10-17 1311175
ESXi 5.0 Patch 6 ESXi500-201308001 2013-08-29 1254542
ESXi 5.0 Patch 6 (Security Only) ESXi500-201308001 2013-08-29 1197855
ESXi 5.0 Express Patch 5 ESXi500-201305001 2013-05-15 1117897
ESXi 5.0 Patch 5 ESXi500-201303001 2013-03-28 1024429
ESXi 5.0 Patch 5 (Security Only) ESXi500-201303001 2013-03-28 1022489
ESXi 5.0 Update 2 ESXi500-update2 2012-12-20 914586
ESXi 5.0 Update 2 (Security Only) ESXi500-update2 2012-12-20 912577
ESXi 5.0 Patch 4 (Security Only) ESXi500-201209001 2012-09-27 822948
ESXi 5.0 Patch 4 ESXi500-201209001 2012-09-27 821926
ESXi 5.0 Patch 3 ESXi500-201207001 2012-07-12 768111
ESXi 5.0 Patch 3 (Security Only) ESXi500-201207001 2012-07-12 764879
ESXi 5.0 Express Patch 4 ESXi500-201206001 2012-06-14 721882
ESXi 5.0 Express Patch 3 ESXi500-201205001 2012-05-03 702118
ESXi 5.0 Express Patch 2 ESXi500-201204001 2012-04-12 653509
ESXi 5.0 Update 1 ESXi500-update1 2012-03-15 623860
ESXi 5.0 Update 1 (Security Only) ESXi500-update1 2012-03-15 608089
ESXi 5.0 Patch 2 ESXi500-201112001 2011-12-15 515841
ESXi 5.0 Express Patch 1 ESXi500-201111001 2011-11-03 504890
ESXi 5.0 Patch 1 ESXi500-201109001 2011-09-13 474610
ESXi 5.0 2011-08-24 469512

vSphere ESXi 4.1

Name Patch Date Build
ESXi 4.1 Patch 11 ESXi410-201404001 2014-04-10 1682698
ESXi 4.1 Patch 10 ESXi410-201312001 2013-12-05 1363503
ESXi 4.1 Patch 9 ESXi410-201307001 2013-07-31 1198252
ESXi 4.1 Patch 8 ESXi410-201304001 2013-04-30 1050704
ESXi 4.1 Patch 7 ESXi410-201301001 2013-01-31 988178
ESXi 4.1 Patch 6 ESXi410-201211001 2012-11-15 874690
ESXi 4.1 U3 ESXi410-update3 2012-08-30 800380
ESXi 4.1 Express Patch 3 ESXi410-201206001 2012-06-14 721871
ESXi 4.1 Express Patch 2 ESXi410-201205001 2012-05-03 702113
ESXi 4.1 Patch 5 ESXi410-201204001 2012-04-26 659051
ESXi 4.1 Patch 4 ESXi410-201201001 2012-01-30 582267
ESXi 4.1 U2 ESXi410-update2 2011-10-27 502767
ESXi 4.1 Patch 3 ESXi410-201107001 2011-07-28 433742
ESXi 4.1 Patch 2 ESXi410-201104001 2011-04-28 381591
ESXi 4.1 U1 ESXi410-update1 2011-02-10 348481
ESXi 4.1 Express Patch 1 ESXi410-201011001 2010-11-29 320137
ESXi 4.1 Patch 1 ESXi410-201010001 2010-11-15 320092
ESXi 4.1 GA 2010-07-13 260247

vSphere ESXi 4.0

Name Patch Date Build
ESXi 4.0 Patch 20 ESXi400-201404001 2014-04-10 1682696
ESXi 4.0 Patch 19 ESXi400-201310001 2013-10-24 1335992
ESXi 4.0 Patch 18 ESXi400-201305001 2013-05-30 1070634
ESXi 4.0 Patch 17 ESXi400-201302001 2013-02-07 989856
ESXi 4.0 Patch 16 ESXi400-201209001 2012-09-14 787047
ESXi 4.0 Patch 15 ESXi400-201206001 2012-06-12 721907
ESXi 4.0 Patch 14 ESXi400-201205001 2012-05-03 702116
ESXi 4.0 Patch 13 ESXi400-201203001 2012-03-30 660575
ESXi 4.0 U4 ESXi400-update4 2011-11-17 504850
ESXi 4.0 Patch 12 ESXi400-201110001 2011-10-13 480973
ESXi 4.0 U3 ESXi400-update3 2011-05-05 398348
ESXi 4.0 Patch 11 ESXi400-201104001 2011-04-28 392990
ESXi 4.0 Patch 10 ESXi400-201103001 2011-03-07 360236
ESXi 4.0 Patch 9 ESXi400-201101001 2011-01-04 332073
ESXi 4.0 Patch 8 ESXi400-201009001 2010-09-30 294855
ESXi 4.0 U2 ESXi400-update2 2010-06-10 261974
ESXi 4.0 Patch 7 ESXi400-201005001 2010-05-27 256968
ESXi 4.0 Patch 6 ESXi400-201003001 2010-04-01 244038
ESXi 4.0 Patch 5 ESXi400-201002001 2010-03-03 236512
ESXi 4.0 Patch 4 ESXi400-200912001 2010-01-05 219382
ESXi 4.0 U1 ESXi400-update1 2009-11-19 208167
ESXi 4.0 Patch 3 ESXi400-200909001 2009-09-24 193498
ESXi 4.0 Patch 2 ESXi400-200907001 2009-08-06 181792
ESXi 4.0 Patch 1 ESXi400-200906001 2009-07-09 175625
ESXi 4.0 GA 2009-05-21 164009

ESXi 3.5

Name Version Release Build
ESXe350-201302401-O-SG 3.5 Patch 27 2013-2-21 988599
ESXe350-201206401-O-SG 3.5 Patch 26 2012-06-14 725354
ESXe350-201205401-O-SG 3.5 Patch 25 2012-05-03 702112
ESXe350-201203401-O-SG 3.5 Patch 24 2012-03-09 604481
VMware ESXi 3.5 June 2011 Rollup 3.5 June 2011 Rollup 2011-06-30 391406
ESXe350-201105401-O-SG 3.5 Patch 23 2011-06-02 391406
ESXe350-201012401-O-BG 3.5 Patch 22 2010-12-07 317866
ESXe350-201008401-O-SG 3.5 Patch 21 2010-09-01 283373
ESXe350-201006401-O-SG 3.5 Patch 20 2010-06-24 259926
ESXe350-201003401-O-BG 3.5 Patch 19 2010-03-29 238493
ESXe350-201002401-O-SG 3.5 Patch 18 2010-02-16 226117
ESXe350-200912401-O-BG 3.5 Patch 17 2009-12-29 213532
VMware ESXi 3.5 Update 5 3.5 U5 2009-12-03 207095
ESXe350-200910401-I-SG 3.5 Patch 16 2009-10-16 199239
ESXe350-200908401-I-BG 3.5 Patch 15 2009-08-31 184236
ESXe350-200907401-I-BG 3.5 Patch 14 2009-07-30 176894
ESXe350-200906401-I-BG 3.5 Patch 13 2009-06-30 169697
ESXe350-200905401-I-BG 3.5 Patch 12 2009-05-28 163429
ESXe350-200904401-I-SG 3.5 Patch 11 2009-04-29 158874
VMware ESXi 3.5 Update 4 3.5 U4 2009-03-30 153875
ESXe350-200903411-I-BG 3.5 Patch 10 2009-03-20 153480
ESXe350-200901401-I-SG 3.5 Patch 9 2009-01-30 143129
ESXe350-200811401-I-SG 3.5 Patch 8 2008-12-02 130755
VMware ESXi 3.5 Update 3 3.5 U3 2008-11-06 123629
ESXe350-200809401-I-SG 3.5 Patch 7 2008-10-03 120505
ESXe350-200808501-I-SG 3.5 Patch 6 2008-09-18 113338
VMware ESXi 3.5 Update 2 (reissued) 3.5 U2 2008-08-13 110271
ESXe350-200807812-I-BG 3.5 Patch 5 2008-08-12 110180
VMware ESXi 3.5 Update 2 (timebombed) 3.5 U2 2008-07-25 103909
ESXe350-200805501-I-SG 3.5 Patch 4 2008-06-03 94430
ESXe350-200804401-O-BG 3.5 Patch 3 2008-04-30 85332
VMware ESXi 3.5 Update 1 3.5 U1 2008-04-10 82664
ESXe350-200802401-I-BG 3.5 Patch 2 2008-03-10 76563
ESXe350-200712401-O-BG 3.5 Patch 1 2008-01-17
VMware ESXi 3.5 Initial Release 3.5 2008-01-10 70348
VMware ESXi 3.5 First Public Release 3.5 2007-12-31 67921

The Spectre and Meltdown situation


Many blog posts have been written about the two biggest security vulnerabilities discovered so far in 2018. In fact, we are talking about three different vulnerabilities:

  • CVE-2017-5715 (branch target injection)
  • CVE-2017-5753 (bounds check bypass)
  • CVE-2017-5754 (rogue data cache load)

CVE-2017-5715 and CVE-2017-5753 are known as “Spectre”, CVE-2017-5754 is known as “Meltdown”. If you want to read more about these vulnerabilities, please visit spectreattack.com & meltdownattack.com

Multiple steps are necessary to be protected, and all necessary information are often repeated, but were distributed over several websites, vendor websites, articles, blog posts or security announcements.

How to protect yourself against these attacks

Two (apparent simple) steps are necessary to be protected against these vulnerabilities:

  1. Apply operating system updates
  2. Update the microcode (BIOS) of your server/ workstation/ laptop

If you use a hypervisor to virtualize guest operating systems, then you have to update your hypervisor as well. Just treat it like an ordinary operating system. Also if your using vendor created software appliances that may be based on OS distributions like CentOS then those need to be protected also.

Sounds pretty simple, but it’s not. I will focus on three vendors in this blog post:

  • Microsoft
  • Linux
  • VMware

Let’s start with Microsoft. Microsoft has published the security advisory ADV180002  on 01/03/2018.

Microsoft Windows (Client)

The necessary security updates are available for Windows 7 (SP1), Windows 8.1, and Windows 10. The January 2018 security updates are ONLY offered in one of theses cases (Source: Microsoft):

  • An supported anti-virus application is installed
  • Windows Defender Antivirus, System Center Endpoint Protection, or Microsoft Security Essentials is installed
  • A registry key was added manually


Windows 10 (1709) KB4056892
Windows 10 (1703) KB4056891
Windows 10 (1607) KB4056890
Windows 10 (1511) KB4056888
Windows 10 (initial) KB4056893
Windows 8.1 KB4056898
Windows 7 SP1 KB4056897

Please note, that you also need a microcode update! Reach out to your vendor.

Windows Server

The necessary security updates are available for Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016 and Windows Server Core (1709). The security updates are NOT available for Windows Server 2008 and Server 2012!. The January 2018 security updates are ONLY offered in one of theses cases (Source: Microsoft):

  • An supported anti-virus application is installed
  • Windows Defender Antivirus, System Center Endpoint Protection, or Microsoft Security Essentials is installed
  • A registry key was added manually


OS Update
Windows Server, version 1709 (Server Core Installation) KB4056892
Windows Server 2016 KB4056890
Windows Server 2012 R2 KB4056898
Windows Server 2008 R2 KB4056897

After applying the security update, you have to enable the protection mechanism. This is different to Windows Windows 7, 8.1 or 10! To enable the protection mechanism, you have to add three registry keys:

VMware has published two VMware Security Advisories (VMSA):

VMware Workstation Pro, Player, Fusion, Fusion Pro, and ESXi are affected by CVE-2017-5753 and CVE-2017-5715. VMware products seems to be not affected by CVE-2017-5754. On 09/01/2017, VMware has published VMSA-2018-0004, which also addresses CVE-2017-5715. Just to make this clear:

  • Hypervisor-Specific Remediation (documented in VMSA-2018-0002)
  • Hypervisor-Assisted Guest Remediation (documented in VMSA-2018-0004)

Before you apply any security updates, please make sure that you :

  • Deploy the updated version of vCenter listed in the table (only if vCenter is used).
  • Deploy the ESXi security updates listed in the table.
  • Ensure that your VMs are using Hardware Version 9 or higher. For best performance, Hardware Version 11 or higher is recommended.

For more information about Hardware versions, read VMware KB article 1010675.


OS Update
ESXi 6.5 ESXi650-201712101-SG
ESXi 6.0 ESXi600-201711101-SG
ESXi 5.5 ESXi550-201709101-SG


OS Update
ESXi 6.5 ESXi650-201801401-BG, and
ESXi 6.0 ESXi600-201801401-BG, and
ESXi 5.5 ESXi550-201801401-BG
vCenter 6.5 6.5 U1e
vCenter 6.0 6.0 U3d
vCenter 5.5 5.5 U3g

All you have to do is:

  • Update your vCenter to the latest update release, then
  • Update your ESXi hosts with all available security updates
  • Apply the necessary guest OS security updates and enable the protection (Windows Server)

Make sure that you also apply microcode updates from your server vendor!


Disaster Recovery as a Service: Ten steps to success

Disaster recovery is becoming top of mind for many CIOs. Understanding the success criteria to make the disaster recovery journey of your own organization smooth and successful is critical, but the path to getting there can be difficult.

Follow the ten key steps below, to guide you on the right path to success.

  1. Understand why disaster recovery is important to your business, and what your specific disaster recovery requirements are.

The first key step is understanding why you are looking for a disaster recovery solution for your business, and what your requirements are- from a disaster recovery perspective as well as for the solution in need. Running a Business Impact Analysis (BIA) will assist in the impact of a disruption to your business and will also help expose the effect of such disruption to your reputation including the effect of any loss of data or loss of staff, the BIA is very much the building block and foundation of your disaster recovery planning and knowing what the business impact to outages is probably the most important aspect in defining the answer to the “why” question. Knowing the business impact will not only drive the Service Level Agreements (SLAs) for the business processes they will also assist the disaster recovery plan to minimise any prolonged outages which could be derived from human error during the recovery process. If these aspects are missing and haven’t been thought of yet then running a Business Impact Analysis should be the first thing that you do and will put you in good stead as you move forward.

An additional aspect of the disaster recovery process is to understand your Recovery Point Objective (RPO), Recovery Time Objective (RTO). From a SLA perspective, think about the amount of time and data loss your business can incur. Zero data loss is obviously ideal, but this can exponentially drive up the cost of the solution. Having a limit to the data loss that can be incurred by your business based on the business service is realistic. Both the time and data loss windows will translate to your RTO and RPOs respectively.

Additionally, does your business require adherence to any regulatory compliance or operating rules? For example, do you need to provide proof of a quarterly or yearly disaster recovery test?  Disaster recovery testing is important, and there are a lot of factors to take into consideration here. What kind of replication technology would you choose – expensive hardware-based replication or host-based or even replication to the cloud. What you choose is based on various factors including cost, business policies, SLA requirements, and importantly environmental factors.  For instance, if your data center is located in an area which gets affected by floods, then your disaster recovery location needs to be in a separate geographic area or even in the cloud.

  1. Should you build your own or buy off the shelf?

The next step is driven by how much investment you either want to make operationally or in capital expenditure. You probably have already invested quite heavily into infrastructure at your primary data center location – things such as server hardware, virtualization technologies and storage. You could take a simple approach and invest in another physical data center for disaster recovery, but this would lead to the expense of not only double software / hardware infrastructure costs but also additional physical location costs. A more savvy approach would be to utilize a vendor to supply disaster recovery services at a fraction of the cost of running dual locations. Keep in mind that choosing the right vendor is important too. You will want to look for a leader in the managed disaster recovery services space that has years of credible experience.

  1. Understand the difference between disaster recovery as-a-service and backup and recovery as-a-service.

Understand that disaster recovery and backup are different ball games. While backup is a necessary part of a business continuity strategy, it lends itself to SLAs of hours to days. On the other hand, disaster recovery is better suited to SLA requirements in minutes to hours. Based on the business uptime and data loss requirements specific to a business service, your business would deploy a disaster recovery solution for your business-critical applications, while backup would be sufficient for those non-critical business services which can take some downtime.  Choose a disaster recovery as-a-service solution that can protect your entire estate or at least the critical elements of it that drive your business. This includes physical and virtual systems, as well as the mix of different OSs that typically are run within enterprise businesses today. The disaster recovery as-a-service solution that you choose should also be able to provide you with the ability to run your systems within their cloud location for a period of time, until you can get your infrastructure back up and running and transfer services back to your primary site.

  1. Choose the right Cloud Hypervisor.

It may seem like an easy decision to make- you would seek a vendor that runs the same hypervisor on the backend as you are on your primary site, but keep in mind this is not a necessity.  If you are using VMware vSphere or Microsoft Hyper-V then running these type of hypervisors in the cloud is going to incur some additional licensing costs in a DR solution. Another thing to think about is whether you really need all the bells and whistles when you’ve invoked disaster recovery. Most of your time is going to be taken up with getting services up and running back at your own location as quickly as possible, so maybe not. What you basically need is a hypervisor to host your systems that provides the basic performance, scale and resilience you require. A more cost-efficient stance would be to utilise a KVM-based hypervisor running within OpenStack. This ticks the boxes in terms of enterprise ready and best of all, the service costs should yield a better ROI than those running proprietary hypervisor technologies, saving your business considerable money.

  1. Plan for all business services that need to be protected, including multi-tier services

Now were getting down to the nitty-gritty details. The business services that need to be protected will be primarily driven by the SLAs that brought you down this path. Keep in mind that you capture all operating system types that these business services are running on and also think about how you handle any physical systems that have not yet been virtualized. Moving virtualized applications to the cloud is an easy process, as these are already encapsulated by the hypervisor in use. But pure physical business applications are another matter altogether.  It is not impossible to move physical application data to the cloud, but when it comes to a failback scenario, if the services you select does not have this capability, then you are a sitting duck. This is especially important to keep in mind in the case where a complete outage has occurred and a rebuild is needed. Another thing to think about is when your business services or applications are started in the cloud- can you start or stop these systems in a particular order if a business service is made of different processes, such as a multi-tier application, and also inject manual steps within your failover plan if so required? Controlling multi-tier business applications that span across systems is going to be a high priority, not only while invoking disaster recovery but also when you’re performing a disaster recovery test.

  1. Plan for your RTOs, RPOs, Bandwidth, Latency and IOPs

Understanding how you can achieve your Recovery Point Objective (RPO), Recovery Time Objective (RTO), as well as the IO load of virtual machines, and the peaky nature of writes through the business day within your systems, this data will help you understand what your required WAN bandwidth should be. Determine whether your disaster recovery service vendor can guarantee these RTOs and RPOs, because every additional minute or hour that your business is down as defined by the Business Impact Analysis is going to cost you. If you aim for RPO of 15 minutes or less, then your bandwidth to the cloud needs to be big enough to cope with extended periods of heavy IO within your systems. If your RTO is something like 4 hours, then you need to know if your systems can recover within that time period, keeping in mind that other operations too need to be managed, such as DNS and AD/LDAP updates including any additional infrastructure services that your business needs.

  1. Avoid vendor lock-in while moving data to the cloud

Understanding how your data will be sent to the cloud provider site is important. A solution that employs VMware vSphere on-premises and in the cloud limits you to a replication solution that works only for virtualized systems with no choice of protecting physical OS systems. This may seem acceptable at the time, but you will be locked into this solution and switching DR providers in the future may be difficult.  Seeking a solution that is flexible and can protect all types of major virtualization platforms as well as physical OS gives you the flexibility of choice for the future.

  1. Run successful disaster recovery rehearsals without unexpected costs

Rehearsals or exercises are probably the most important aspect of any disaster recovery solution. Not having an automated disaster recovery rehearsal process that you test on a regular basis can leave your business vulnerable. Your recovery rehearsals should not affect your running production environment. Any rehearsal system should run in parallel albeit within a separate network VLAN, but still have some type of access to infrastructure services such as AD, LDAP and DNS etc. so that full disaster recovery testing can be carried out. Once testing is complete, it is essential that the solution include a provision to easily remove and clean up the rehearsal processes.

  1. How long can you stay in the cloud?

For a moment let’s imagine that the unthinkable has happened, and you have invoked disaster recovery to your cloud service provider. The nature of the outage at your primary location will dictate the length of time you will need to keep your business applications running on your service providers’ infrastructure. It is imperative that you are aware of any clauses within your contract that pertain to length of time you can keep your business running on the cloud providers’ site. There is also a big pull to get enterprises to think about running in the cloud and staying there, but this is a big decision to make. Performance of the systems is going to be one metric to poll against, as is performance of storage, or more precisely the quality of service of the storage that the cloud vendor will provide. On the whole, it makes sense to get back into your own infrastructure as quick as possible, since it is custom built to support your business.

  1. How easy is it to failback business services to your own site?

Getting your data back or reversing the replication data path is going to be important especially as you don’t want to affect your running systems within the cloud by injecting more downtime! Rebuilding your infrastructure is one aspect that needs to be meticulously planned. Any assistance that the solution itself can provide to make this process smoother is a bonus. Your on-premises location is going to need a full re-sync of data from the cloud location which may take some time, so the solution should be able to handle a two-step approach to failback- the re-sync should happen in one operation and once complete, the process to switch back your systems can be done at a time that suits your business.

Success, you’re now armed to create a robust business continuity plan.

Follow the steps above to gain an understanding of what’s needed to be successful on your disaster recovery as a service journey, and use them as checkpoints while developing you own robust business continuity plan for your business.

VMware Integrated Openstack 2.0 set for release before the end of Q3 2015

Its been just six months since VMware released version 1.0 of VMware Integrated Openstack for general availability and now the next release is expected to be available before the end of Q3 2015 for download, here’s what’s new in this 2.0 release:

  • Kilo-based: VMware Integrated OpenStack 2.0 will be based on OpenStack Kilo release, making it current with upstream OpenStack code.
  • Seamless OpenStack Upgrade: VMware Integrated OpenStack 2.0 will introduce an Industry-first seamless upgrade capability between OpenStack releases. Customers will now be able to upgrade from V1.0 (Icehouse) to V2.0 (Kilo), and even roll back if anything goes wrong, in a more operationally efficient manner.
  • Additional Language Support: VMware Integrated OpenStack 2.0 will now available in six more languages: German, French, Traditional Chinese, Simplified Chinese, Japanese and Korean.
  • LBaaS: Load Balancing as a service will be available supported through VMware NSX.
  • Ceilometer Support: VMware Integrated OpenStack 2.0 will now support Ceilometer with Mongo DB as the Backend Database
  • App-Level Auto Scaling using Heat: Auto Scaling will enable users to set up metrics that scale up or down application components. This will enable development teams to address unpredictable changes in demand for the app services. Ceilometer will provide the alarms and triggers, Heat will orchestrate the creation (or deletion) of scale out components and LBaaS will provide load balancing for the scale out components.
  • Backup and Restore: VMware Integrated OpenStack 2.0 will include the ability to backup and restore OpenStack services and configuration data.
  • Advanced vSphere Integration: VMware Integrated OpenStack 2.0 will expose vSphere Windows Guest Customization. VMware admins will be able to specify various attributes such as ability to generate new SIDs, assign admin passwords for the VM, manage compute names etc. There will also be added support for more granular placement of VMs by leveraging vSphere features such as affinity and anti-affinity settings.
  • Qcow2 Image Support: VMware Integrated OpenStack 2.0 will support the popular qcow2 Virtual Machine image format.
  • Available through our vCloud Air Network Partners: Customers will be able to use OpenStack on top of VMware through any of the service providers in out vCloud Air Partner Network.

Goodbye vSphere AppHA, you were just not up to the job, enter Symantec ApplicationHA to the rescue

Well I thought this day would come eventually but I am surprised to see it so soon, its official folks. vSphere AppHA is no more as of vSphere 6.0, the official announcement is here . With the effort that’s required to provide continual support for old and new applications and also having to provide continual support for their updates it looks like the task was not something that VMware wanted to focus on. Don’t think that your covered though with backups, replication, vSphere HA or vSphere FT, non of those will get your application back up and running automatically should it fail.

don’t worry though

Symantec ApplicationHA comes to the rescue…..

As one of the first third party vendors providing support for application availability within virtual machines, Symantec has always been at the forefront providing resilience for applications running within VMware vSphere. ApplicationHA is one solution that has been doing this, and for the past four years its been going from strength to strength adding functionality and automation and importantly, resilience for mission critical applications that enables our customers to sleep at night. If your unfamiliar with Symantec ApplicationHA take a look at this comparison which I made a while back, its very detailed but will give you an insight of ApplicationHA’s true potential. Its inexpensive and doesn’t need vSphere Enterprise Plus to work. Its stable mature technology built on Veritas Cluster Server heritage. The development effort required to keep on top of platform and application updates is a challenge but it’s worth it, after all it’s the applications that drive your business and providing resilience for them should be top of mind.

More info on Symantec Application can be found here there’s also a free trial that you can test drive for 60 days if you like too.

Whats new in VMware Fault Tolerance 6.0

VMware Fault Tolerance (FT) in vSphere 5.5 is one of those features you would love to use but because of its vCPU limitation it was not really helping to protect the Mission Critical applications so for many its left behind. With vSphere 6.0, VMware broken the limitation of a single vCPU for Fault Tolerance, a FT VM now Supports upto 4 vCPUs and 64 GB of RAM. With vSMP support, FT can be used to protect your mission critical applications. Along with the vSMP FT support, let’s take a look at what’s new in vSphere 6.0 Fault Tolerance(FT).

vSphere 6.0 - FT_1

Benefits of Fault Tolerance

  • Continuous Availability with Zero downtime and Zero data loss
  • NO TCP connections loss during failover
  • Fault Tolerance is completely transparent to Guest OS.
  • FT doesn’t depend on Guest OS and application
  • Instantaneous failover from Primary VM to Secondary VM in case of ESXi host failure

What’s New in vSphere 6.0 Fault Tolerance

  • FT support upto 4 vCPUs and 64 GB RAM
  • Fast Check-Pointing, a new Scalable technology is introduced to keep primary and secondary in Sync by replacing “Record-Replay”
  • vSphere 6.0, Supports vMotion of both Primary and Secondary Virtual Machine
  • With vSphere 6.0, You will be able to backup your virtual machines. FT supports for vStorage APIs for Data Protection (VADP) and it also supports all leading VADP solutions in Market like Symantec, EMC, HP ,etc.
  • With vSphere 6.0, FT Supports all Virtual Disk Type like EZT, Thick or Thin Provisioned disks. It supports only Eager Zeroed Thick with vSphere 5.5 and earlier versions
  • Snapshot of FT configured Virtual Machines are supported with vSphere 6.0
  • New version of FT keeps the Separate copies of VM files like .VMX, .VMDk files to protect primary VM from both Host and Storage failures. You are allowed to keep both Primary and Secondary VM files on different datastore.

Difference between vSphere 5.5 and vSphere 6.0 Fault Tolerance (FT)

Difefrence between FT 5.5 amd 6.0

One thing to be aware of with VMware FT is that this feature does not monitor the application its still only virtual machine protection so you still need to think about the application and how it will be protected.

What new features are in vSphere 6.0

Well there has been some public information out there for some time on some of the new features that will or maybe in vSphere 6.0, mainly information that has come from VMworld 2014 and some from the beta which although public did have some NDA with it. As VMware announce the new release below are some of the new features that made the cut into the new version.

vSphere Platform (including ESXi)

  • Increase in vSphere Host Configuration Maximums
    • 480 Physical CPUs per Host
    • Up to 12 TB of Physical Memory
    • Up to 1000 VMs per Host
    • Up to 6000 VMs per Cluster
  • Virtual Hardware v11
    • 128 vCPUs per VM
    • 4 TB RAM per VM
    • Hot-add RAM now vNUMA aware
    • Serial and parallel port enhancements
      • A virtual machine can now have a maximum of 32 serial ports
      • Serial and parallel ports can now be removed
  • ESXi Account & Password Management
    • New ESXCLI commands to add/modify/remove local user accounts
    • Configurable account lockout policies
    • Password complexity setting via VIM API & vCenter Host Advanced System Settings
  • Improved Auditability of ESXi Admin Actions
    • Prior to vSphere 6.0, actions taken through vCenter by any user would show up as ‘vpxuser’ in ESXi logs.
    • In vSphere 6.0 actions taking through vCenter will show the actual username in the ESXi logs
  • Enhanced Microsoft Clustering (MSCS) Support
    • Support for Windows 2012 R2 and SQL 2012
    • Failover Clustering and AlwaysOn Availability Groups
    • IPv6 Support
    • PVSCSI & SCSI controller support
    • vMotion Support
      • Clustering across physical hosts with Physical Compatibility Mode RDMs (Raw Device Mapping)
      • Supported on Windows 2008, 2008 R2, 2012, and 2012 R2

vCenter 6.0

  • Scalability Improvements
    • 1000 Hosts per vCenter
    • 10,000 VMs per vCenter
    • 64 Hosts per cluster (including VSAN!)
    • 6000 VMs per cluster
    • Linked Mode no longer requires MS ADAM
  • New Simplified Architecture with Platform Services Controller
    • Centralizes common services
    • Embedded or Centralized deployment models
  • Content Library
    • Repository for vApps, VM templates, and ISOs
    • Publisher/Subscriber model with two replication models
    • Allow content to be stored in one location and replicated out to “Subscriber” vCenters
  • Certificate Management
    • Certificate management for ESXi hosts & vCenter
    • New VMware Endpoint Certificate Service (VECS)
    • New VMware Certificate Authority
  • New vMotion Capabilities
    • Cross vSwitch vMotion
    • Cross vCenter vMotion
    • Long Distance vMotion
    • vMotion across L3 boundaries

Storage & Availability

  • VMware Virtual Volumes (VVOLS)
    • Logical extension of virtualization into the storage world
    • Policy based management of storage on per-VM basis
    • Offloaded data services
    • Eliminates LUN management
  • Storage Policy-Based Management
    • Leverages VASA API to intelligently map storage to policies and capabilities
    • Polices are assigned to VMs and ensure storage performance & availability
  • Fault Tolerance
    • Multi-vCPU FT for up to 4 vCPUs
    • Enhanced virtual disk format support (thin & thick disks)
    • Ability to hot configure FT
    • Greatly increased FT host compatibility
    • Backup support with snapshots through VADP
    • Now uses copies of VMDKs for added storage redundancy (allowed to be on separate datastores)
  • vSphere Replication
    • End-to-end network compression
    • Network traffic isolation
    • Linux file system quiescing
    • Fast full sync
    • Move replicas without full sync
    • IPv6 support
  • vSphere Data Protection
    • VDP Advanced has been rolled into VDP and is no longer available for purchase (the features of VDP-A are now available for free to Essentials Plus and higher editions of vSphere!)
    • Protects up to 800 VMs per vCenter
    • Up to 20 VDP appliances per vCenter
    • Replicate backup data between VDP & EMC Avamar
    • EMC Data Domain support with DD Boost
    • Automated backup verification

So there you have it – a pretty long list of updates for vSphere 6.0. One thing that I was surprised to see that that vSphere Application HA has been removed in vSphere 6.0 due to a lack of demand for the feature, oddly its not something we have seen at Symantec and still our user base grows quarter by quarter and Symantec ApplicationHA goes on..

Providing high availability and disaster recovery for virtualized SAP within VMware the right way

Over the past couple of years I have been getting more and more involved in SAP architecture designs for HA and DR and one on my pet hates at the start of my journey was the lack of basic information on what the SAP components were for and how they interacted with each other, it was a hard slog, for those who are venturing into SAP or even those hardened SAP veterans out there the paper below covers SAP in great detail and more importantly covers how SAP deployments should be done correctly especially when high availability and disaster recovery is a requirement.

Many organizations rely on SAP applications to support vital business processes. Any disruption of these services translates directly into bottom-line losses. As organization’s information systems become increasingly integrated and interdependent, the potential impact of failures and outages grows to enormous proportions.

The challenge for IT organizations is to maintain continuous SAP application availability in a complex, interconnected, and heterogeneous  application environment. The difficulties are significant:

  • there are many potential points of failure or disruption
  • the interdependencies between components complicates administration
  • the infrastructure itself undergoes constant change

To gain additional competitive advantage, enterprises must now work more closely together and integrate their SAP environment with those of other organizations, such as partners, customers, or suppliers. The availability of these applications is therefore essential.

There are three main availability classes, depending on the degree of availability required:

  • Standard Availability – achievable availability without additional measures
  • High Availability – increased availability after elimination of single points of failure within the local datacenter
  • Disaster Recovery – highest availability, which even overcomes the failure of an entire production site

Symantec helps the organizations that rely on SAP applications with an integrated, out-of-the-box solution for SAP availability. Symantec’s High Availability and Disaster Recovery solutions for SAP enhance both local and global availability for business critical SAP applications.

Local high availability: By clustering critical application components with application-specific monitoring and failover, Symantec’s solutions simplify the management of complex environments. Administrators can manually move services for preventative and proactive maintenance, and the software automatically migrates and restarts applications in case of failures.

Global availability/disaster recovery: By replicating data across geographically dispersed data centers and using global failover capabilities, companies can provide access to essential services in the event of major site disruptions. Using Symantec’s solutions, administrators can migrate applications or an entire data center within minutes, with a single click through a central console. Symantec’s flexible, hardware independent solutions support a variety of cost-effective strategies for leveraging your investment in disaster recovery resources.

Symantec provides High Availability and Disaster Recovery solutions for SAP, utilizing Symantec™ Storage Foundation, powered by Veritas, Symantec™ Replicator Option, Symantec™ Cluster Server, powered by Veritas, and Cluster Server agents that are designed specifically for SAP applications. The result is an out-of-the-box solution that you can quickly deploy to protect critical SAP applications immediately from either planned or unplanned downtime.

Download the full white paper below.


Providing availability of vCenter Server v5.x with Symantec ApplicationHA v6.1

It’s been a while coming but I’ve finally got some time to write this article on protecting vCenter Server availability. It’s probably also come as an opportune time as not so long ago VMware announced the end of availability of vCenter Heartbeat so now many of you are probably looking for ways to protect vCenter Server more than ever especially due to the criticality that it brings in management and operations of your vSphere environment. This article will highlight areas that need to be protected and what options you have.

With release after release of vSphere more functionality goes into vCenter Server and more of the virtualized environment relies on it being available to serve the needs of the administrator. although vCenter Server can typically reside on a single server, it is made up of many critical parts. If you’ve sat through an install of vCenter Server you will know that its broken up into 4 core areas, these are Single Sign-on (SSO), Inventory Service, vCenter Server itself and lastly there is also the vSphere Web Client & Services. SSO is a core component of vSphere since its introduction in v5.1, it’s there to handle authentication requests and also is a security broker handling requests coming from the various vSphere solutions. Although there were some operational hiccups in v5.1, subsequent versions have become stronger and deployment options have increased, I’ll take a look at those in a minute. The Inventory Service is another key component that has two functions firstly it stores the custom tags for the vSphere Web Client and secondly it’s also a proxy for the vSphere Web Client which actually assists in reducing the load on the vCenter Server (VXPD), knowing this little tidbit can actually help in deployment scenarios so if you are breaking up the components onto separate servers then it’s best to keep the Inventory Service close to the vSphere Web Client Services. Next there is the vCenter Server itself which is made up of a number of services and critical to the whole environment. Lastly there is the vCenter Web Server/Services which provides the administrator with a web UI for management and operations of the entire environment.

Now we’ve gone through the critical services let’s take a look at deployment and availability options within each group. Ignoring the simple install option of vCenter for the moment, options available when using the custom install method for SSO provide the ability to install in 3 types of deployment modes, these are single SSO, SSO installed in HA mode and SSO installed for multi-site environment. With single deployment it’s just that, SSO is installed onto a system and acts as a single entity for the whole vSphere environment. HA mode provides the ability to add another SSO system to an existing SSO system and provides a failover mechanism in case the primary SSO system fails; typically a load balancer is used in front of the SSO servers for ease of configuration. Lastly the multisite option provides local authentication in a multiple site scenario, be aware though that there is no failover between sites so if a failed site fails then local authentication for that site will fail too. I don’t want to focus too much on the different scenarios too much as there are plenty of blogs out there which highlight best practices for deploying SSO. What is important is the availability of the services especially in a single SSO deployment which let’s face it will be used by large number of SMBs and enterprise customers.

When deployed on a single system SSO services consist of 5 key services, these are the VMware Certificate Services, VMware Directory Services, VMware Identity Management Services, VMware KDC Services and the VMware Secure Token Services when these services are installed the default Windows Service Manager recovery configuration for most of these services are set to restart upon 1st and 2nd failure, you may think this will be OK for availability but what if the service keeps failing, what if the service doesn’t restart, what effect will it have on the other key components in the environment which as we know now are critical to operations. What’s needed is a method to monitor these services and the other components intelligently and remediate any issues that occur within the environment. The other services such as Inventory, vCenter Server and Web Services do not have any recovery options enabled so the administrator is pretty much left to manage those independently.

Using a solution like Symantec ApplicationHA can assist in protecting all of the vCenter Server services and still have the ability to utilize VMware features like VMwareHA and DRS especially useful if vCenter Server has been deployed onto a virtual machine, which I assume you have. Symantec ApplicationHA provides the ability to monitor all of the key components and in the event it is unable to resolve issues it can pass control to VMwareHA to reset the virtual machine. ApplicationHA has a number of application agents it supports and also has a vCenter agent which can be used to protect vCenter. There is also a wizard which can be launched from with vSphere Web/Desktop Client which can be used to protect vCenter. The current version of the wizard does not include SSO configuration but can be added after the wizard is run. Symantec are aiming to update their wizard to include SSO so for the moment we can script the additional services pretty easily with ApplicationHA commands.

Symantec ApplicationHA auto detects the services within the deployment and provides the ability to also monitor the connection between the SQL database and vCenter itself.

This is of available vCenter services are displayed within the configuration

The dependency of the services is shown by viewing the dependency component view.

Finally the additional SSO services can be added to the configuration by running the script containing the commands below.

haconf -makerw

hatype -modify GenericService RestartLimit 1

hares -add VMWareCertificateService GenericService vCenterServer_SG

hares -modify VMWareCertificateService ServiceName VMWareCertificateService

hares -modify VMWareCertificateService Enabled 1

hares -add VMwareDirectoryService GenericService vCenterServer_SG

hares -modify VMwareDirectoryService ServiceName VMwareDirectoryService

hares -modify VMwareDirectoryService Enabled 1

hares -add VMwareIdentityMgmtService GenericService vCenterServer_SG

hares -modify VMwareIdentityMgmtService ServiceName VMwareIdentityMgmtService

hares -modify VMwareIdentityMgmtService Enabled 1

hares -add VMwareKdcService GenericService vCenterServer_SG

hares -modify VMwareKdcService ServiceName VMwareKdcService

hares -modify VMwareKdcService Enabled 1

hares -add VMwareSTS GenericService vCenterServer_SG

hares -modify VMwareSTS ServiceName VMwareSTS

hares -modify VMwareSTS Enabled 1

hares -add vmwarelogbrowser GenericService vCenterServer_SG

hares -modify vmwarelogbrowser ServiceName vmwarelogbrowser

hares -modify vmwarelogbrowser Enabled 1

hares -link vspherewebclientsvc vpxd

hares -link vimQueryService vctomcat

hares -link vpxd VMwareKdcService

hares -link vpxd VMwareSTS

hares -link vpxd VMWareCertificateService

hares -link VMwareIdentityMgmtService VMwareDirectoryService

hares -link VMwareSTS VMwareIdentityMgmtService

hares -link vmwarelogbrowser vspherewebclientsvc

hares -unlink vimQueryService vpxd

haconf –dump –makero


Here is the final list of all services being monitored by ApplicationHA

And the dependency component view is also updated to include all of the services and the correct dependencies.

Now that the configuration is complete testing for fault scenarios can commence. For more information on ApplicationHA please follow the product link below.

Symantec ApplicationHA



Using VMware vSphere Web Client with Symantec ApplicationHA and Symantec Cluster Server (VCS)

Using VMware vSphere Web Client with Symantec ApplicationHA and Symantec Cluster Server (VCS)

Since v5.1 of vSphere, VMware have focused on providing web based management for the vSphere environment, with v5.5 more functionality has been placed into the vSphere Web Client to bring its capabilities on par to that of the Windows based vSphere Client. Moving forward VMware have stated that any new feature VMware introduces typically is only going to be available within the vSphere Web Client. Due to the move by VMware away from the Windows based vSphere Client Symantec has also developed integration into the vSphere Web Client so that customers using Symantec High Availability solutions can leverage the vSphere Web Client also. This paper describes the steps needed to enable management of Symantec high availability solutions with the vSphere Web Client.

Solution features and support

Symantec High Availability Solutions that leverage vSphere Web Client management include Symantec ApplicationHA and Symantec Cluster Server (VCS), traditionally these solutions use a Windows system that runs the Symantec HA Console for management, guest deployment and application single sign-on all of which are managed via a plugin into the Windows vSphere client. To support the vSphere Web Client the Symantec architecture, Veritas Operations Manager 6.1 (VOM) is used for presenting the information into the Web Client including registration of the plugin for vCenter Servers within the environment. With this release certain functionality is omitted but will be added in subsequent releases.

Operations that are enabled within the vSphere Web Client include

  • Registration of the Symantec High Availability plugin for vSphere Web Client.
  • Configuration/discovery of applications to be placed under Symantec ApplicationHA & VCS control.
  • Management of applications including start/stop and other management tasks.
  • Single sign-on for application authentication from VOM to the vSphere Web Client.
  • Dashboard view and management of applications configured visible from the Cluster or Datacenter views of the vSphere Web Client.

Management tasks omitted in the 6.1 release from the Symantec HA plugin for vSphere Web Client include.

  • Ability to install guest component via vSphere Web Client: You cannot use the vSphere Web Client to install the Symantec ApplicationHA or VCS guest component into the virtual machine. Use either the Windows vSphere Client to install the guest components and then migrate them to the Web Client or use the installer from the Symantec solutions DVD image to push the components to multiple VMs.
  • Symantec High Availability home page will not be available on the vSphere Web Client, and the operations related to Symantec High Availability License Management, single sign-on configuration between sites (for VMware Site Recovery Manager) are not available. The keyless license model is recommended which can be managed through VOM.
  • Integration with Symantec Backup Exec is not supported.


Supported environments.

To use the Symantec HA Console plugin for VMware vSphere Web Client the following platforms and software are supported.

  • VMware vSphere 5.1 or later
  • Symantec ApplicationHA 6.1 or later

    * Earlier versions can be used but the VOM managed host package VRTSsfmh needs to be updated

  • Symantec Cluster Server (Windows) 6.0.1 or later
  • Symantec Cluster Server (Linux) 6.0.2 or later

    * Symantec Cluster Server below v6.1 for both Windows and Linux require the VOM managed host package VRTSsfmh to be updated.

  • Veritas Operations Manager 6.1 or later.

Steps Required to implement solution.

Step 1 – Installation of Veritas Operations Manager.

Veritas Operations Manager (VOM) 6.1 is required to be installed and configured for use with the vSphere environment. VOM is available to download from the Symantec website at http://www.symantec.com/operations-manager click the download link on the page and follow the steps required to download the code. Note that the full package will include the add-ons required by default, select the full package download file to minimize the steps otherwise the add-ons required will need to be installed separately. The VOM management server can be installed on either a Windows or Linux host information on current supported platform is at http://www.symantec.com/operations-manager/system-requirements . Carry out the install by running the installation bin or exe file depending on the desired platform that was downloaded from the Symantec website and follow the install wizard including the management configuration. There are a great set of videos at http://www.symantec.com/connect/vom-videos which have been posted and these are great to review to understand the steps required. Once configured, log in to the VOM server with system administrator privileges and the home page will be presented.

Step 2 – Configuration of the Control Host and Virtualization Add-on.

Once the VOM server is installed, the Control Host (CH) add-on needs to be installed next. The Control host facilitates the discovery of the environment and will be used to discover the vSphere environment, this is carried out via the “Settings icon and then selecting the “Deployment” section, depending on your environment the CH may need to be installed on separate server but for this paper it will be installed on the VOM server. Expand the “Add-on” section and right click on “Control Host and select “Install“. After a few minutes the Control Host will be enabled and installed.

Once the CH is installed next step is to enable the Symantec HA Plugin for vCenter Web Client, this is enable by selecting the “Symantec HA Plugin for vSphere Web Client” Add-on in the left hand column and then right click on the Symantec HA Plugin and select “Install“.


The Add-on must be installed on the VOM Management Server; the VOM Web Server will need to be restarted after the Installation of the add-on. To restart the Web server, click “Restart Web Server” button on the task bar.



Log back into the management server after the restart of the web services. Once logged in, the verification of the add-on installation can be made by selecting the “Repository” or the “Add-on” section in the left hand column and verify that the Control Host and Symantec HA plugin for vSphere Web Client have both been enabled.

Next step is to enable the Virtualization management within VOM. This is carried out by going to the “Settings” section and select “Virtualization“.

Click “Add Virtualization Server” from the task pane and fill in details of the vCenter Server environment that requires the plugin. Multiple vCenter Servers can be added if required.

Discovery of the environment is carried out and selection of ESX servers can be made.

Discovery process completes and information on the environment is displayed.

Side Note: The ESX servers are not used for the registration process but information from the environment can be gained and can be useful. Information such as memory/CPU/network and storage is discovered by the Control Host. Specific information on the environment that has been discovered also includes Storage and Datastores associated to the environment. Information on the environment is viewed from VOM within the virtualization perspective; access to this type of information can be given to users where access via the vSphere Client is restricted.

Step 3 – Registration of the Symantec HA plugin for vSphere Web Client.

Register the plugin against the discovered vCenter servers by carrying out a register task within the Virtualization perspective from the home view. Select the “Solutions” panel at the left hand side and click on “Symantec HA plugin for vSphere Web Client“. Right click on the vCenter Servers that require the plugin to be registered and select “Register“.

Step 4 – Adding Symantec ApplicationHA and VCS guest hosts to the VOM server.

With the plugin registered the next step is to add the virtual machines with ApplicationHA and VCS installed to the VOM server. Do this by selecting “Settings” from the home page and select “Add Hosts” on the task pane, select “Agent” as the type and fill in the required information. Note if you have multiple VMs to be added then a CSV file can be uploaded to the wizard to fill in the required information. The format of the CSV follows.

Host, User, Password


host2, user2,password2

host3, user3,password3


Once the VMs have been added and discovery completes the information of the VMs is displayed. Make sure that the VMs Agent is in a connected state.

Step 5 – Management of the Symantec HA plugin via vSphere Web Client.

Next and final step is to check connectivity via the vSphere Web Client. The VOM Management Servers SSL security certificate must be added to the workstations Trusted Root Cert Authorities repository within the internet options so that a secure communication can be made from the Web Client to VOM.

The Symantec HA plugin should be displayed under the “Monitor” tab within the vSphere Web Client as displayed below. From this point onwards the configuration or management of the application can be carried out.

The Symantec HA Dashboard which provides visibility across all VMs with ApplicationHA or VCS installed within a single view and is available from the vSphere Cluster or Datacenter views as displayed below.

This concludes the steps required to enable the Symantec HA plugin from within the vSphere Web Client. For more information on ApplicationHA and VCS please review the links below.

Symantec Cluster Server


Symantec ApplicationHA