<?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>Deep dive into UAG DirectAccess (Tweaking the GPOs)</title><link>http://blogs.technet.com/b/edgeaccessblog/archive/2010/02/18/deep-dive-into-uag-directaccess-tweaking-the-gpos.aspx</link><description>Today I want to talk about UAG DirectAccess Group Policy objects and some useful tweaks you can apply to them. Using an Existing GPO While the script generated by the UAG DirectAccess Configuration Wizard works well in most cases, in some cases you may</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Deep dive into UAG DirectAccess (Tweaking the GPOs)</title><link>http://blogs.technet.com/b/edgeaccessblog/archive/2010/02/18/deep-dive-into-uag-directaccess-tweaking-the-gpos.aspx#3323620</link><pubDate>Wed, 07 Apr 2010 09:47:22 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3323620</guid><dc:creator>MeirM [MSFT]</dc:creator><description>&lt;p&gt;This blog was updated today with some changes to the Manage Out “Only” scenario.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3323620" width="1" height="1"&gt;</description></item></channel></rss>