<?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>Best Practices: Are your DIPs alive? Alternate Access Mapping may be the answer...</title><link>http://blogs.technet.com/wbaer/archive/2006/10/27/best-practices-are-your-dips-alive-alternate-access-mapping-may-be-the-answer.aspx</link><description>Historically alternate access settings provided a mechanism to identify the different ways in which users access portal sites; in MSIT we've taken that practice one step further and leverage alternate access mappings (AAM) as a means to identify problem</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator></channel></rss>