https://staging.projecthomelab.org/index.php?action=history&feed=atom&title=Running_Your_vSphere_Management_Cluster_on_Hyper-VRunning Your vSphere Management Cluster on Hyper-V - Revision history2026-04-27T00:57:13ZRevision history for this page on the wikiMediaWiki 1.44.2https://staging.projecthomelab.org/index.php?title=Running_Your_vSphere_Management_Cluster_on_Hyper-V&diff=292&oldid=prevTravis: 1 revision imported2020-07-31T17:01:12Z<p>1 revision imported</p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<tr class="diff-title" lang="en">
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 17:01, 31 July 2020</td>
</tr><tr><td colspan="2" class="diff-notice" lang="en"><div class="mw-diff-empty">(No difference)</div>
</td></tr></table>Travishttps://staging.projecthomelab.org/index.php?title=Running_Your_vSphere_Management_Cluster_on_Hyper-V&diff=291&oldid=prevopenhomelab>AlexGalbraith: /* External Links */2016-05-17T19:38:19Z<p><span class="autocomment">External Links</span></p>
<p><b>New page</b></p><div>[[Category:Management]]<br />
{{Wikimedia-stub}}<br />
== Introduction ==<br />
Today i was thinking about a scenario, where i was thinking to put vSphere infra components (Like vCenter server, syslog, AD, DNS, DHCP etc.) above Hyper-V Cluster.<br />
<br />
I know what you're thinking, what absurd thing i'm talking about, what is the need of separate management cluster, Hyper-V is not mature enough to host vSphere Management infra., VMware and Hyper-V don't go Hand-in-Hand etc. and i accept that, because before conceiving this concept i had same thoughts but later I cross questioned myself i.e. what are the pros/cons about this design and how this is going to help customers. So, I'm sharing the pros/cons about this design with you, if you any comments whether good or bad, i'm all ears.<br />
<br />
== Pros and Cons ==<br />
Pros or advantages:-<br />
# Dual Hypervisor strategy with a twist.<br />
# Most of the vSphere infra components require windows OS (yeah,i know about VCSA).<br />
# Utilize "Virtualization-Safe" feature introduced in win2012 (VM-GenerationID, avail. with Hyper-V v3), make SSO robust.<br />
# License cost reduced (at least for management cluster and OS license).<br />
# Utilize existing hardware and windows OS license.<br />
# vCenter server supported on virtual platform (kb10087), nothing mentioned about Hyper-V<br />
<br />
Cons or disadvantages:-<br />
# Requires multi-talented engineers to manage.<br />
# Support-issues from both vendors (support engineer love this sport, Volley-ball).<br />
# Some Third-party software issues (i don't know which, but included it).<br />
# Hard to convince CIO/CTO's (biggest threat to such designs)<br />
<br />
== External Links ==<br />
{| class="wikitable"<br />
|+External Links<br />
|-<br />
! scope="col"| Title<br />
! scope="col"| Description<br />
|- style="vertical-align:top;"<br />
|[http://vforvirtualization.blogspot.in/2014/01/thinking-out-loud-vcenter-server-on.html Original article] ||Original article - has been syndicated by the original author.<br />
|}</div>openhomelab>AlexGalbraith