On Sun, Nov 2, 2008 at 2:19 AM, Haworth, Michael A. <span dir="ltr">&lt;<a href="mailto:Michael_Haworth@pas-technologies.com">Michael_Haworth@pas-technologies.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
&nbsp; there are multiple changes being considered on our network and (of course) most of them hinge on keeping or eliminating Windows as the Corporate OS. </blockquote></div><br>You should stress to your supervisors that having a single &quot;Corporate OS&quot; locks you in and limits your options.&nbsp; <br>
<br>The Internet is built on open protocols; the rule has always been that a protocol isn&#39;t ready for prime time until there are at least two independent software implementations that interoperate with each other as well as they do talking to themselves. Even when you don&#39;t have open source software, having open protocols gives you the ability to plug in a server running any OS.<br>
<br>So ask yourself if you really need the proprietary extensions that products like IIS use.&nbsp; If you can turn those off, your users will not notice when you swap in a server running a different OS.<br><br><br>