<?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>Fixing your half-baked ADRMS upgrade - Post Mortem</title><link>http://blogs.technet.com/rmssupp/archive/2008/12/13/fixing-your-half-baked-adrms-upgrade-post-mortem.aspx</link><description>I've had a few customers call me recently that for whatever reason, they ended up with a half-baked upgrade. By half-baked, I mean that your DRMS_Logging database, and your logging components do not get updated. By *upgrade* I mean from RMS V1 to ADRMS</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Fixing your half-baked ADRMS upgrade - Post Mortem</title><link>http://blogs.technet.com/rmssupp/archive/2008/12/13/fixing-your-half-baked-adrms-upgrade-post-mortem.aspx#3168109</link><pubDate>Sat, 13 Dec 2008 19:01:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3168109</guid><dc:creator>aschan</dc:creator><description>&lt;p&gt;Great stuff, Jason, as always- thanks!&lt;/p&gt;
</description></item></channel></rss>