<?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>Now That You Have That New Customer, What Does Their Network Really Look Like?</title><link>http://blogs.technet.com/b/uspartner_ts2team/archive/2012/04/26/now-that-you-have-that-new-customer-what-does-their-network-really-look-like.aspx</link><description>Rob Waggoner &amp;#160; Have you ever gone to install an application into a customer’s environment, especially a new customer’s environment, only to find that Active Directory, DNS, or even Exchange isn’t properly configured?&amp;#160; How do you handle that</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>