<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Windows Server 2008 Foundation &#8211; Why Microsoft&#8217;s licensing policy is outdated</title>
	<atom:link href="http://4sysops.com/archives/windows-server-2008-foundation-why-microsofts-licensing-policy-is-outdated/feed/" rel="self" type="application/rss+xml" />
	<link>http://4sysops.com/archives/windows-server-2008-foundation-why-microsofts-licensing-policy-is-outdated/</link>
	<description>For Windows Administrators</description>
	<lastBuildDate>Fri, 20 Nov 2009 22:25:43 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Pietroforte</title>
		<link>http://4sysops.com/archives/windows-server-2008-foundation-why-microsofts-licensing-policy-is-outdated/comment-page-1/#comment-126697</link>
		<dc:creator>Michael Pietroforte</dc:creator>
		<pubDate>Sun, 26 Apr 2009 18:41:27 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2663#comment-126697</guid>
		<description>Hi Lukas, welcome back. Didn&#039;t see you here for a while. I agree that unbundling components will complicate things. However, if Microsoft adopts the way cloud providers handle these things it wouldn&#039;t be that complicated. By the way, Microsoft offers employee-based licensing. But as far as I know only for educational institutions. It makes things unbelievable simple.

Adam, that was just my point. It is in Microsoft&#039;s own interest to make licensing fair and simple.</description>
		<content:encoded><![CDATA[<p>Hi Lukas, welcome back. Didn&#8217;t see you here for a while. I agree that unbundling components will complicate things. However, if Microsoft adopts the way cloud providers handle these things it wouldn&#8217;t be that complicated. By the way, Microsoft offers employee-based licensing. But as far as I know only for educational institutions. It makes things unbelievable simple.</p>
<p>Adam, that was just my point. It is in Microsoft&#8217;s own interest to make licensing fair and simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Ruth</title>
		<link>http://4sysops.com/archives/windows-server-2008-foundation-why-microsofts-licensing-policy-is-outdated/comment-page-1/#comment-126342</link>
		<dc:creator>Adam Ruth</dc:creator>
		<pubDate>Tue, 14 Apr 2009 02:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2663#comment-126342</guid>
		<description>@Lukas

&quot;What i would like as a system administrators (but will never happen anyway) is a very simple licensing model (for example, per employee and software - purchase Exchange based on number of employees, deploy as many Exchange servers you need).&quot;

That&#039;s something I could get behind. It gets a bit frustrating when you start mixing CALs and server licenses. I always get the feeling that I&#039;m paying twice for things. I may not be, but it seems that way sometimes. It&#039;s easy to hesitate on writing another cheque because you&#039;re not sure if you&#039;re paying again for something you already have. If it was simple to determine, then compliance is easy to prove and the cheque easier to write.</description>
		<content:encoded><![CDATA[<p>@Lukas</p>
<p>&#8220;What i would like as a system administrators (but will never happen anyway) is a very simple licensing model (for example, per employee and software &#8211; purchase Exchange based on number of employees, deploy as many Exchange servers you need).&#8221;</p>
<p>That&#8217;s something I could get behind. It gets a bit frustrating when you start mixing CALs and server licenses. I always get the feeling that I&#8217;m paying twice for things. I may not be, but it seems that way sometimes. It&#8217;s easy to hesitate on writing another cheque because you&#8217;re not sure if you&#8217;re paying again for something you already have. If it was simple to determine, then compliance is easy to prove and the cheque easier to write.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lukas Beeler</title>
		<link>http://4sysops.com/archives/windows-server-2008-foundation-why-microsofts-licensing-policy-is-outdated/comment-page-1/#comment-126335</link>
		<dc:creator>Lukas Beeler</dc:creator>
		<pubDate>Mon, 13 Apr 2009 20:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://4sysops.com/?p=2663#comment-126335</guid>
		<description>I don&#039;t agree with fully. Microsoft&#039;s licensing model is already overly complicated as it is, unbundling components will make it even worse.

The reason why companies pirate Microsoft software is because they have unethical bastards working for them - that may or may not start at the top (but it most likely does).

The reason why companies are underlicensed is because Microsoft licensing model is overly complicated. Of course after spending a bit of time studying it, it all starts to make some kind of sense, but everytime i have to explain it to a customer i realize how silly it is.

Usage based pricing will make everything worse - more approvals needed for spending every spec of money, license handling is even more complicated, etc.

What i would like as a system administrators (but will never happen anyway) is a very simple licensing model (for example, per employee and software - purchase Exchange based on number of employees, deploy as many Exchange servers you need). Also, no license enforcement in any way. No license keys. No activation. No dongles. No license servers. Won&#039;t happen, but it would ensure that the best solution would be deployed, not the one which uses the most awkward licensing loopholes to cut cost.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t agree with fully. Microsoft&#8217;s licensing model is already overly complicated as it is, unbundling components will make it even worse.</p>
<p>The reason why companies pirate Microsoft software is because they have unethical bastards working for them &#8211; that may or may not start at the top (but it most likely does).</p>
<p>The reason why companies are underlicensed is because Microsoft licensing model is overly complicated. Of course after spending a bit of time studying it, it all starts to make some kind of sense, but everytime i have to explain it to a customer i realize how silly it is.</p>
<p>Usage based pricing will make everything worse &#8211; more approvals needed for spending every spec of money, license handling is even more complicated, etc.</p>
<p>What i would like as a system administrators (but will never happen anyway) is a very simple licensing model (for example, per employee and software &#8211; purchase Exchange based on number of employees, deploy as many Exchange servers you need). Also, no license enforcement in any way. No license keys. No activation. No dongles. No license servers. Won&#8217;t happen, but it would ensure that the best solution would be deployed, not the one which uses the most awkward licensing loopholes to cut cost.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
