<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: VIR358: Hyper-V Architecture, Scenarios, and Networking</title>
	<atom:link href="http://blog.scottlowe.org/2008/06/12/vir358-hyper-v-architecture-scenarios-and-networking/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2008/06/12/vir358-hyper-v-architecture-scenarios-and-networking/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<pubDate>Fri, 21 Nov 2008 21:37:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2008/06/12/vir358-hyper-v-architecture-scenarios-and-networking/#comment-40342</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Wed, 06 Aug 2008 13:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/06/12/vir358-hyper-v-architecture-scenarios-and-networking/#comment-40342</guid>
		<description>Hari,

Yes, you are correct--regardless of the virtualization solution, you need something to manage that virtualization solution.

My disagreement with Jeff was in the way that he positioned Hyper-V (not System Center) as having integrated physical and virtual management. That's not the case; it's System Center that provides that functionality. And even though they both fall under the "System Center" moniker, it's really two different products: System Center Operations Manager (SCOM) and Systems Center Virtual Machine Manager (SCVMM). Yes, there are links between the two (PRO, for example), but it's still two different products.

Thanks for reading and sharing your thoughts!</description>
		<content:encoded><![CDATA[<p>Hari,</p>
<p>Yes, you are correct&#8211;regardless of the virtualization solution, you need something to manage that virtualization solution.</p>
<p>My disagreement with Jeff was in the way that he positioned Hyper-V (not System Center) as having integrated physical and virtual management. That&#8217;s not the case; it&#8217;s System Center that provides that functionality. And even though they both fall under the &#8220;System Center&#8221; moniker, it&#8217;s really two different products: System Center Operations Manager (SCOM) and Systems Center Virtual Machine Manager (SCVMM). Yes, there are links between the two (PRO, for example), but it&#8217;s still two different products.</p>
<p>Thanks for reading and sharing your thoughts!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hari</title>
		<link>http://blog.scottlowe.org/2008/06/12/vir358-hyper-v-architecture-scenarios-and-networking/#comment-40339</link>
		<dc:creator>Hari</dc:creator>
		<pubDate>Wed, 06 Aug 2008 10:26:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/06/12/vir358-hyper-v-architecture-scenarios-and-networking/#comment-40339</guid>
		<description>Hi,

You need a separate product to manage the virtualization whether it is a VMware ESX or a Hyper-V. Hope you agree with me. 

Now, with the given management products (VI from VMware and System Center from Microsoft), VI can manage only the virtual products where as the System center would be able to manage the virtual as well as physical machines. 

I believe this is what Jeff covered in his slides.

--Hari</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>You need a separate product to manage the virtualization whether it is a VMware ESX or a Hyper-V. Hope you agree with me. </p>
<p>Now, with the given management products (VI from VMware and System Center from Microsoft), VI can manage only the virtual products where as the System center would be able to manage the virtual as well as physical machines. </p>
<p>I believe this is what Jeff covered in his slides.</p>
<p>&#8211;Hari</p>
]]></content:encoded>
	</item>
</channel>
</rss>
