<?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>UAG SP1 Update 1 Rollup 1 is out!</title><link>http://blogs.technet.com/b/ben/archive/2012/01/13/uag-sp1-update-1-rollup-1-is-out.aspx</link><description>Yesterday we released a new rollup update to UAG – Rollup 1 for SP1 Update 1. This rollup contains 13 fixes to various issues. The full list of fixes is here (with a link to request the download). Please note that this update requires that your UAG server</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: UAG SP1 Update 1 Rollup 1 is out!</title><link>http://blogs.technet.com/b/ben/archive/2012/01/13/uag-sp1-update-1-rollup-1-is-out.aspx#3476570</link><pubDate>Sat, 21 Jan 2012 12:02:30 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3476570</guid><dc:creator>Ahmed Nabil Mahmoud</dc:creator><description>&lt;p&gt;Hi Ben,&lt;/p&gt;
&lt;p&gt;After Applying the new Rollup, the DirectAccess Monitor/Current Status showed unhealthy for the DNS64. I rebooted the UAG server but still the same error. I disabled DirectAccess, activated the configuration, enabled it again and activated again and it all worked fine this time.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Ahmed&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3476570" width="1" height="1"&gt;</description></item></channel></rss>