<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Walk the walk that you talk - PART 1</title><link>http://blogs.technet.com/ritaylor/archive/2008/03/16/walk-the-walk-that-you-talk-part-1.aspx</link><description>So many times you hear &amp;quot;Don't do this in production!&amp;#160; Do this in your Dev or Test environment&amp;quot;.&amp;#160; More times than not, the &amp;quot;Dev&amp;quot; or &amp;quot;Test&amp;quot; environment is the developer's laptop or some spare machine that they have</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Walk the walk that you talk - PART 1</title><link>http://blogs.technet.com/ritaylor/archive/2008/03/16/walk-the-walk-that-you-talk-part-1.aspx#3005570</link><pubDate>Sun, 16 Mar 2008 19:15:11 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3005570</guid><dc:creator>tonyso</dc:creator><description>&lt;P&gt;Why not use the P2V wizard in SCVMM to make virtual machine copies of all your production machines and run the PPE as VMs?&lt;/P&gt;</description></item><item><title>re: Walk the walk that you talk - PART 1</title><link>http://blogs.technet.com/ritaylor/archive/2008/03/16/walk-the-walk-that-you-talk-part-1.aspx#3006945</link><pubDate>Sun, 16 Mar 2008 23:29:12 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3006945</guid><dc:creator>rickt287</dc:creator><description>&lt;p&gt;Ah...and the cost?&lt;/p&gt;
&lt;p&gt;Remember, cost was one of the reasons people don't do PPE. &amp;nbsp;If cost was not an issue, all datacenters would be twice as large as they would simply double hardware footprint.&lt;/p&gt;
&lt;p&gt;In my next segment, we talk about options (SCVMM is one) and how to implement them.&lt;/p&gt;
</description></item><item><title>re: Walk the walk that you talk - PART 1</title><link>http://blogs.technet.com/ritaylor/archive/2008/03/16/walk-the-walk-that-you-talk-part-1.aspx#3273980</link><pubDate>Sun, 16 Aug 2009 21:42:09 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3273980</guid><dc:creator>Jeff Jones</dc:creator><description>&lt;p&gt;All good points Rick. I call mine &amp;quot;staging&amp;quot; and find average people relate to that word well. &amp;nbsp; The matching we try to do on both hardware and software as close as possible and make environment comparison part of our quarterly engineering review (along with security, performance, and capacity).&lt;/p&gt;
&lt;p&gt;The trouble I've had is software deployment. &amp;nbsp;We're trying to require scripts for all changes. &amp;nbsp; It takes time and requires developer staff time but helps us matching and even support (anyone can deploy now).&lt;/p&gt;
&lt;p&gt;They'll never be 100% for the simple fact they are independent systems but we should all strive to get continually closer. &amp;nbsp; =)&lt;/p&gt;</description></item></channel></rss>