<?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>Why good scripts may start to fail on you for instance with timestamps like “01/01/0001 00:00:00”!</title><link>http://blogs.technet.com/b/dpm/archive/2010/09/11/why-good-scripts-may-start-to-fail-on-you-for-instance-with-timestamps-like-01-01-0001-00-00-00.aspx</link><description>You may have scripts running fine since early DPM2007 days but start to show unexpected results with DPM2010. This blog explains what is likely happening and how to resolve that. Typically information returned from cmdlets is assumed to be valid unless</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Why good scripts may start to fail on you for instance with timestamps like “01/01/0001 00:00:00”!</title><link>http://blogs.technet.com/b/dpm/archive/2010/09/11/why-good-scripts-may-start-to-fail-on-you-for-instance-with-timestamps-like-01-01-0001-00-00-00.aspx#3489162</link><pubDate>Thu, 29 Mar 2012 13:12:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3489162</guid><dc:creator>YellowOnline</dc:creator><description>&lt;p&gt;Linkback from &lt;a rel="nofollow" target="_new" href="http://yellowonline.tweakblogs.net/blog/7725/scdpm-scripting-trouble-with-lastrecoverypoint.html"&gt;yellowonline.tweakblogs.net/.../scdpm-scripting-trouble-with-lastrecoverypoint.html&lt;/a&gt;.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3489162" width="1" height="1"&gt;</description></item></channel></rss>