<?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>Using ISA Server to Extend Server and Domain Isolation to non-Windows Platforms</title><link>http://blogs.technet.com/ianhamer/archive/2007/01/19/using-isa-server-to-extend-server-and-domain-isolation-to-non-windows-platforms.aspx</link><description>One of the biggest pieces of feedback I hear when pitching Server and Domain Isolation to customers (which...btw...is a great first step towards an eventual NAP deployment) is "how will this work with my non-Windows clients?" I don't like to think about</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Link: Using ISA Server to Extend Server and Domain Isolation Interoperability</title><link>http://blogs.technet.com/ianhamer/archive/2007/01/19/using-isa-server-to-extend-server-and-domain-isolation-to-non-windows-platforms.aspx#605549</link><pubDate>Tue, 23 Jan 2007 07:19:31 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:605549</guid><dc:creator>travelling without moving</dc:creator><description>&lt;p&gt;Microsoft have posted a whitepaper on utilising ISA Server as an IPSec gateway/proxy in a domain or server&lt;/p&gt;
</description></item></channel></rss>