<?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>Identifying VSS hotfixes to install on new servers</title><link>http://blogs.technet.com/filecab/archive/2006/11/08/identifying-vss-hotfixes-to-install-on-new-servers.aspx</link><description>A customer deploying a new server recently asked us which VSS hotfixes he should install. Turns out there are quite a few VSS hotfixes out there, and he asked if he needed to install them all in order or just a subset. Here’s the rundown of what to install,</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>VSS under Windows 2003 SP1 really needs a "hotfix rollup" publically released</title><link>http://blogs.technet.com/filecab/archive/2006/11/08/identifying-vss-hotfixes-to-install-on-new-servers.aspx#511781</link><pubDate>Fri, 10 Nov 2006 08:58:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:511781</guid><dc:creator>Aaron Tiensivu's Blog</dc:creator><description>&lt;p&gt;This is getting kind of silly now. If you want the latest and greatest bug-fixed versions of the Volume Shadow Service components, which you should if you are using Backup Exec and other programs that take advantage of the subsystem, you have to request&lt;/p&gt;
</description></item></channel></rss>